Skip to main content

AS12773

MM-AS

-=[ Upstreams IN ]=-

Registry

Authoritative registration data

AS number
12773
Name
MM-AS
Organisation
-=[ Upstreams IN ]=-
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 AS12773
130.193.73.0/24 IPv4 /24 not checked
185.28.108.0/24 IPv4 /24 RPKI valid
185.28.109.0/24 IPv4 /24 not checked
185.28.111.0/24 IPv4 /24 RPKI valid
93.157.13.0/24 IPv4 /24 not checked
93.157.14.0/24 IPv4 /24 RPKI valid
93.157.15.0/24 IPv4 /24 RPKI valid

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 AS12773
Address families
GNM-IX 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Rostov 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,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 AS12773 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

22 networks seen before AS12773 in AS paths

No rows match “”.

Showing – of

Observed downstreams

11 networks seen after AS12773 in AS paths

Observed downstreams
Families
AS47809 EAST-AS 879 2,108
v4
AS34786 VNET-AS 523 1,931
v4
AS60839 VID-MEDIA-AS 287 1,516
v4
AS25141 SONIKO-AS 283 1,460
v4
AS49757 DKT-KHARTSIZSK-AS 277 1,440
v4
AS211692 LVLDN-AS 286 659
v4
AS57005 SPECTR-AS 206 618
v4
AS44884 DN-ROS-AS 321 403
v4
AS44710 TRK-SIRIUS-AS 282 347
v4
AS31113 ARTKOMM-AS 279 346
v4
AS52213 ISP-EXSTREAM-AS 147 217
v4

No rows match “”.

Showing – of

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

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.