Skip to main content

AS5429

IIP-NET-AS5429

South Moscow Backbone Network

Registry

Authoritative registration data

AS number
5429
Name
IIP-NET-AS5429
Organisation
South Moscow Backbone Network
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS5429
195.178.192.0/19 IPv4 /19 not checked
217.67.112.0/20 IPv4 /20 not checked
85.89.112.0/21 IPv4 /21 not checked
185.92.140.0/22 IPv4 /22 not checked
193.108.182.0/24 IPv4 /24 not checked
193.232.7.0/24 IPv4 /24 not checked
85.89.102.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 AS5429
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 AS5429 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS5429 in AS paths

Observed upstreams
Families
AS20764 RASCOM-AS 762 2,316
v4
AS1299 TWELVE99 168 534
v4
AS25478 125 239
v4
AS47478 58 207
v4
AS9049 41 123
v4
AS50384 W-IX_LTD 29 92
v4
AS25091 IP-Max 9 66
v4

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS5429 in AS paths

Observed downstreams
Families
AS29233 267 351
v4
AS49450 NCAGP-AS 242 306
v4
AS12724 LASERNET-AS 184 231
v4
AS51831 71 89
v4
AS41892 31 41
v4

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 27
v4
AS36236 NETACTUATE 3 9
v4
AS41327 FIBERTELECOM-AS 3 9
v4
AS41722 3 9
v4
AS49673 TRUENETWORK 3 9
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.