asn.dev

Observed topology

AS8607 TIMICO United Kingdom

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS8607: 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
AS2914NTT America, Inc.TransitIPv4 IPv6456
AS3356Level 3 Parent, LLCTransitIPv4 IPv6432
AS6939Hurricane Electric LLCTransitIPv4 IPv6304
AS33891Core-Backbone GmbHHostingIPv440
AS48185team.blue NVUnclassifiedIPv4 IPv624
AS3216PJSC "Vimpelcom"MobileIPv420
AS3741Dimension DataUnclassifiedIPv420
AS12552GlobalConnect ABUnclassifiedIPv420
AS29169GANDI SASHostingIPv420
AS13030Init7 (Switzerland) Ltd.HostingIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20896Viking Office Europe B.V.UnclassifiedIPv468
AS48706KERRIDGE COMMERCIAL SYSTEMS (KSH) LIMITEDUnclassifiedIPv460
AS12654Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv42

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6507
AS2914NTT America, Inc.TransitIPv4 IPv6483
AS6939Hurricane Electric LLCTransitIPv4 IPv6313
AS20896Viking Office Europe B.V.UnclassifiedIPv468
AS48706KERRIDGE COMMERCIAL SYSTEMS (KSH) LIMITEDUnclassifiedIPv460
AS33891Core-Backbone GmbHHostingIPv444
AS48185team.blue NVUnclassifiedIPv4 IPv629
AS3741Dimension DataUnclassifiedIPv424
AS3216PJSC "Vimpelcom"MobileIPv422
AS12552GlobalConnect ABUnclassifiedIPv422

Provenance

Where this comes from

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