Skip to main content

AS25189

COUNTRYCOM

AO Countrycom

Registry

Authoritative registration data

AS number
25189
Name
COUNTRYCOM
Organisation
AO Countrycom
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS25189
213.251.208.0/20 IPv4 /20 not checked
213.251.240.0/20 IPv4 /20 not checked
213.251.255.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS25189
Address families
MSK-IX Moscow: MSK-IX peering network — IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS25189 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS25189 in AS paths

Observed upstreams
Families
AS25159 SONICDUO-AS 438 676
v4
AS29076 CITYTELECOM-AS 206 501
v4
AS57304 RETNRU-AS 180 413
v4
AS1299 TWELVE99 78 185
v4
AS25091 IP-Max 8 16
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS25189 in AS paths

Observed downstreams
Families
AS44542 COUNTRYCOM 304 712
v4
AS210739 neolinkgroup 161 374
v4
AS43089 Enline_LLC 147 169
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 12
v4
AS49673 TRUENETWORK 3 6
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.