asn.dev

Observed topology

AS28884 MR-SIB-MTSAS MR Sibir

Unclassified RIPE

Upstreams 1 carry this network
Downstreams 6 this network carries
Adjacent (IPv4) 7
Adjacent (IPv6) 1
Upstream graph Who carries AS28884, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS28884 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS28884: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS8359MTS PJSCMobileIPv4 IPv6766

Transit

Downstream networks

inferred

Networks for which AS28884 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS30922MTS PJSCUnclassifiedIPv4585
AS21365MTS PJSCUnclassifiedIPv4354
AS50567OOO SibenergotelecomUnclassifiedIPv458
AS42558BrokerCreditService Ltd.UnclassifiedIPv42
AS197880ARQA Technologies LLCUnclassifiedIPv42
AS210889KRASTSVETMET OJSCUnclassifiedIPv41

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS28884 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS8359MTS PJSCMobileIPv4 IPv62,529
AS30922MTS PJSCUnclassifiedIPv41,345
AS21365MTS PJSCUnclassifiedIPv4355
AS50567OOO SibenergotelecomUnclassifiedIPv458
AS42558BrokerCreditService Ltd.UnclassifiedIPv42
AS197880ARQA Technologies LLCUnclassifiedIPv42
AS210889KRASTSVETMET OJSCUnclassifiedIPv41

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.