asn.dev

Observed topology

AS26076 INFINITECOM

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS26076: 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 IPv6843
AS6461Zayo BandwidthTransitIPv4 IPv6144
AS174Cogent Communications, LLCTransitIPv4127
AS3257GTT Communications Inc.TransitIPv4 IPv657

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS13931MASONIC CHARITY FOUNDATION OF NEW JERSEYUnclassifiedIPv465
AS13785SHORE MEMORIAL HOSPITALUnclassifiedIPv460
AS54472South Jersey Radiology Associates, P.A.UnclassifiedIPv459
AS14529Saint Joseph's UniversityUnclassifiedIPv457
AS46181BCI Mississippi Broadband,LLCUnclassifiedIPv435
AS21690Miles IT CompanyUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,013
AS6461Zayo BandwidthTransitIPv4 IPv6211
AS174Cogent Communications, LLCTransitIPv4140
AS3257GTT Communications Inc.TransitIPv4 IPv684
AS13931MASONIC CHARITY FOUNDATION OF NEW JERSEYUnclassifiedIPv465
AS13785SHORE MEMORIAL HOSPITALUnclassifiedIPv460
AS54472South Jersey Radiology Associates, P.A.UnclassifiedIPv459
AS14529Saint Joseph's UniversityUnclassifiedIPv457
AS46181BCI Mississippi Broadband,LLCUnclassifiedIPv435
AS21690Miles IT CompanyUnclassifiedIPv41

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.