asn.dev

Observed topology

AS33071 ISC-F-AS

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS33071: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS1299Arelion Sweden ABTransitIPv4 IPv615
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv41
AS11164Internet2EducationIPv41
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24406China Internet Network Infomation CenterUnclassifiedIPv4 IPv6444
AS3557Internet Systems Consortium, Inc.UnclassifiedIPv4 IPv619

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6521
AS24406China Internet Network Infomation CenterUnclassifiedIPv4 IPv6444
AS1299Arelion Sweden ABTransitIPv4 IPv634
AS3557Internet Systems Consortium, Inc.UnclassifiedIPv4 IPv619
AS11164Internet2EducationIPv45
AS24482SG.GSHostingIPv4 IPv63
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv41

Provenance

Where this comes from

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