asn.dev

Observed topology

AS4913 NET-CPRK

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS4913: 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
AS174Cogent Communications, LLCTransitIPv41,392
AS49915Megaport (UK) LimitedUnclassifiedIPv4826
AS25180Exponential-E Ltd.UnclassifiedIPv4640
AS4826Vocus Connect International BackboneUnclassifiedIPv4413
AS2914NTT America, Inc.TransitIPv4241
AS4230CLARO S.A.ResidentialIPv4172
AS133012Cocoa Oriental Network LimitedUnclassifiedIPv4171
AS8896GLOBALCONNECT ASUnclassifiedIPv476
AS33874Epic Communications LimitedUnclassifiedIPv459
AS25400Telia Norge ASUnclassifiedIPv442

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57740Hermes Datacommunications International LimitedUnclassifiedIPv4116

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv41,508
AS49915Megaport (UK) LimitedUnclassifiedIPv4826
AS25180Exponential-E Ltd.UnclassifiedIPv4640
AS4826Vocus Connect International BackboneUnclassifiedIPv4413
AS2914NTT America, Inc.TransitIPv4241
AS4230CLARO S.A.ResidentialIPv4172
AS133012Cocoa Oriental Network LimitedUnclassifiedIPv4171
AS57740Hermes Datacommunications International LimitedUnclassifiedIPv4116
AS8896GLOBALCONNECT ASUnclassifiedIPv476
AS33874Epic Communications LimitedUnclassifiedIPv459

Provenance

Where this comes from

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