asn.dev

Observed topology

AS34573 OBERON-ASN Information-Computer Center Oberon Plus, LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34573: 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
AS12389PJSC RostelecomResidentialIPv4591
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4345
AS31133PJSC MegaFonMobileIPv4220
AS8359MTS PJSCMobileIPv455
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv442

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49293Digital Tehnology LtdUnclassifiedIPv4551
AS49980Mihail Juriwitsch NovikovUnclassifiedIPv4240

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4904
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4670
AS49293Digital Tehnology LtdUnclassifiedIPv4551
AS31133PJSC MegaFonMobileIPv4331
AS49980Mihail Juriwitsch NovikovUnclassifiedIPv4240
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv484
AS8359MTS PJSCMobileIPv455

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.