asn.dev

Observed topology

AS396313 MOCTEL - MocTel

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396313: 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
AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPResidentialIPv4177
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS396879airVitesseUnclassifiedIPv433
AS394232TelKel inc.UnclassifiedIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS395214Microcom Informatique, Inc.UnclassifiedIPv4173
AS398299Fraxion Communications IncUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS396879airVitesseUnclassifiedIPv4238
AS21723GOCO TECHNOLOGY LIMITED PARTNERSHIPResidentialIPv4177
AS174Cogent Communications, LLCTransitIPv4 IPv6173
AS395214Microcom Informatique, Inc.UnclassifiedIPv4173
AS398299Fraxion Communications IncUnclassifiedIPv432
AS394232TelKel inc.UnclassifiedIPv414

Provenance

Where this comes from

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