Skip to main content

AS51200

DIDI-AS

di-di.ru

Registry

Authoritative registration data

AS number
51200
Name
DIDI-AS
Organisation
di-di.ru
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

42

IPv6 prefixes

1

Total announced

43

Announced prefixes

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

Prefixes announced by AS51200
212.192.40.0/22 IPv4 /22 RPKI not found
83.219.252.0/22 IPv4 /22 not checked
91.230.136.0/22 IPv4 /22 not checked
193.232.210.0/23 IPv4 /23 not checked
194.85.114.0/23 IPv4 /23 RPKI not found
194.85.210.0/23 IPv4 /23 RPKI not found
46.29.232.0/23 IPv4 /23 not checked
185.102.138.0/24 IPv4 /24 RPKI valid
193.135.13.0/24 IPv4 /24 RPKI valid
193.176.156.0/24 IPv4 /24 not checked
193.232.212.0/24 IPv4 /24 not checked
193.242.105.0/24 IPv4 /24 not checked
194.190.109.0/24 IPv4 /24 not checked
194.190.110.0/24 IPv4 /24 not checked
194.226.109.0/24 IPv4 /24 not checked
194.226.129.0/24 IPv4 /24 RPKI not found
194.85.210.0/24 IPv4 /24 not checked
194.85.211.0/24 IPv4 /24 RPKI not found
195.18.26.0/24 IPv4 /24 RPKI valid
195.208.36.0/24 IPv4 /24 not checked
212.192.192.0/24 IPv4 /24 not checked
212.192.193.0/24 IPv4 /24 RPKI not found
212.192.202.0/24 IPv4 /24 not checked
212.192.203.0/24 IPv4 /24 RPKI not found
212.193.101.0/24 IPv4 /24 not checked
212.193.102.0/24 IPv4 /24 not checked
46.29.232.0/24 IPv4 /24 RPKI valid
46.29.233.0/24 IPv4 /24 RPKI valid
62.76.94.0/24 IPv4 /24 not checked
62.76.95.0/24 IPv4 /24 RPKI not found
83.219.236.0/24 IPv4 /24 RPKI valid
83.219.237.0/24 IPv4 /24 not checked
83.219.252.0/24 IPv4 /24 not checked
83.219.255.0/24 IPv4 /24 RPKI invalid
91.230.136.0/24 IPv4 /24 RPKI valid
91.230.137.0/24 IPv4 /24 not checked
91.230.138.0/24 IPv4 /24 not checked
91.230.139.0/24 IPv4 /24 RPKI valid
92.241.15.0/24 IPv4 /24 RPKI valid
92.241.17.0/24 IPv4 /24 not checked
92.241.19.0/24 IPv4 /24 not checked
92.241.20.0/24 IPv4 /24 RPKI valid
2001:67c:2b88::/48 IPv6 /48 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 AS51200
Address families
PITER-IX Frankfurt 100,000 Mbps IPv4
PITER-IX Helsinki 100,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 100,000 Mbps IPv4
PITER-IX Rostov 100,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 100,000 Mbps IPv4
Sea-IX 30,000 Mbps 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 AS51200 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS51200 in AS paths

Observed upstreams
Families
AS12389 ROSTELECOM-AS 468 7,106
v4
AS3216 SOVAM-AS 739 5,852
v4
AS58002 SINFORM 369 1,439
v4
AS25091 IP-Max 25 357
v4 v6
AS49434 FBWNETWORKS 6 42
v4
AS61049 EXASCALE 6 42
v4
AS6939 HURRICANE 37 40
v4
AS34927 iFog-GmbH 6 38
v4
AS28917 Fiord-AS 5 38
v4
AS21030 CDNNOW-AS 1 4
v4
AS9198 KAZTELECOM-AS 2 2
v4
AS50629 LWLCOM 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS51200 in AS paths

Observed downstreams
Families
AS201097 kvanta-llc 295 386
v4
AS211114 asDataCenter 277 345
v4
AS3216 SOVAM-AS 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 92
v4
AS35598 INETCOM 2 26
v4
AS28910 INTAL-ASN 3 21
v4
AS41722 MIRAN-AS 3 21
v4
AS205112 PHILUNET 3 21
v4
AS37721 ORG-VTS1-AFRINIC 2 20
v4
AS199524 GCORE 1 1
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.