asn.dev

Observed topology

AS58314 B2B-Telecom SvyazResurs-Kuban, LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58314: 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
AS31133PJSC MegaFonMobileIPv4 IPv6408
AS12389PJSC RostelecomResidentialIPv4310

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34855Stroy-Telecom LTDUnclassifiedIPv4 IPv697
AS200442Kotsarev Alexey EvgenevichUnclassifiedIPv459
AS199583Municipal Government Institution of Krasnodar city Municipal formation "Electronic Krasnodar"UnclassifiedIPv432
AS198645JSC International airport KRASNODARUnclassifiedIPv415
AS34777JSC "AGROKOMPLEKS" IM.N.I. TKACHEVAUnclassifiedIPv49

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv6484
AS12389PJSC RostelecomResidentialIPv4355
AS57304JSC "RetnNet"UnclassifiedIPv4199
AS200442Kotsarev Alexey EvgenevichUnclassifiedIPv4179
AS34855Stroy-Telecom LTDUnclassifiedIPv4 IPv697
AS199583Municipal Government Institution of Krasnodar city Municipal formation "Electronic Krasnodar"UnclassifiedIPv432
AS198645JSC International airport KRASNODARUnclassifiedIPv415
AS9002RETN LimitedUnclassifiedIPv412
AS34777JSC "AGROKOMPLEKS" IM.N.I. TKACHEVAUnclassifiedIPv49

Provenance

Where this comes from

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