asn.dev

Observed topology

AS13208 NEWTELSOLUTIONS-AS Channel Islands

Unclassified RIPE

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

Transit

Upstream networks

All 24

Networks observed carrying traffic for AS13208: 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
AS174Cogent Communications, LLCTransitIPv4826
AS6939Hurricane Electric LLCTransitIPv4233
AS3356Level 3 Parent, LLCTransitIPv4192
AS24482SG.GSHostingIPv424
AS33891Core-Backbone GmbHHostingIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS48185team.blue NVUnclassifiedIPv424
AS49673Truenetwork LLCUnclassifiedIPv424
AS50673Serverius Holding B.V.UnclassifiedIPv424
AS56655Gigahost ASUnclassifiedIPv424

All 24 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204648Calligo LimitedUnclassifiedIPv4120
AS25040I.T. Consultancy LimitedUnclassifiedIPv443
AS211875Government of JerseyUnclassifiedIPv412

Adjacency

Adjacent networks

All 27

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4850
AS3356Level 3 Parent, LLCTransitIPv4343
AS6939Hurricane Electric LLCTransitIPv4233
AS204648Calligo LimitedUnclassifiedIPv4120
AS25040I.T. Consultancy LimitedUnclassifiedIPv443
AS24482SG.GSHostingIPv424
AS33891Core-Backbone GmbHHostingIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS48185team.blue NVUnclassifiedIPv424
AS49673Truenetwork LLCUnclassifiedIPv424

All 27 adjacent →

Provenance

Where this comes from

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