asn.dev

Observed topology

AS60670 WIDEFM-LTD

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS60670: 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
AS3257GTT Communications Inc.TransitIPv4 IPv6271
AS6939Hurricane Electric LLCTransitIPv464
AS5511Orange S.A.TransitIPv452
AS44684Mythic Beasts LtdHostingIPv446
AS34549meerfarbig GmbH & Co. KGHostingIPv424
AS50304Blix Solutions ASUnclassifiedIPv416
AS3741Dimension DataUnclassifiedIPv48
AS4657StarHub LtdResidentialIPv48
AS12552GlobalConnect ABUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv48

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS196745Datacenta Hosting LtdUnclassifiedIPv4 IPv6371
AS50468CITRUS TELECOMMUNICATIONS LTDUnclassifiedIPv4150

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv6679
AS196745Datacenta Hosting LtdUnclassifiedIPv4 IPv6371
AS50468CITRUS TELECOMMUNICATIONS LTDUnclassifiedIPv4150
AS5511Orange S.A.TransitIPv4129
AS6939Hurricane Electric LLCTransitIPv464
AS44684Mythic Beasts LtdHostingIPv446
AS34549meerfarbig GmbH & Co. KGHostingIPv430
AS50304Blix Solutions ASUnclassifiedIPv420
AS24482SG.GSHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412

All 22 adjacent →

Provenance

Where this comes from

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