asn.dev

Observed topology

AS25820 IT7NET - IT7 Networks Inc

Hosting ARIN Content

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

Transit

Upstream networks

All 33

Networks observed carrying traffic for AS25820: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv43,840
AS6939Hurricane Electric LLCTransitIPv43,750
AS1299Arelion Sweden ABTransitIPv41,762
AS29802HIVELOCITY, Inc.HostingIPv41,422
AS4785xTomHostingIPv41,322
AS906DMIT Cloud ServicesHostingIPv4910
AS64050BGP Network LimitedHostingIPv4589
AS20473The Constant Company, LLCHostingIPv4 IPv6427
AS24482SG.GSHostingIPv4112
AS17639Converge ICT Solutions Inc.UnclassifiedIPv489

All 33 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 33

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv43,840
AS6939Hurricane Electric LLCTransitIPv43,750
AS1299Arelion Sweden ABTransitIPv41,762
AS29802HIVELOCITY, Inc.HostingIPv41,422
AS4785xTomHostingIPv41,322
AS906DMIT Cloud ServicesHostingIPv4910
AS64050BGP Network LimitedHostingIPv4589
AS20473The Constant Company, LLCHostingIPv4 IPv6427
AS24482SG.GSHostingIPv4112
AS17639Converge ICT Solutions Inc.UnclassifiedIPv489

All 33 adjacent →

Provenance

Where this comes from

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