asn.dev

Observed topology

AS13208 NEWTELSOLUTIONS-AS Channel Islands

Upstreams 23 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 26
Adjacent (IPv6) 0

Transit

Upstream networks

inferred

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, LLCTransitIPv4856
AS6939Hurricane Electric LLCTransitIPv4227
AS3356Level 3 Parent, LLCTransitIPv4194
AS50673Serverius Holding B.V.UnclassifiedIPv448
AS24482SG.GSHostingIPv424
AS57463NetIX Communications JSCUnclassifiedIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv424
AS56655Gigahost ASUnclassifiedIPv424
AS49673Truenetwork LLCUnclassifiedIPv424
AS7575Australian Academic and Research Network (AARNet)EducationIPv419
AS50629LWLcom GmbHUnclassifiedIPv413
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS50304Blix Solutions ASUnclassifiedIPv42
AS33891Core-Backbone GmbHHostingIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv41
AS12552GlobalConnect ABUnclassifiedIPv41
AS3741Dimension DataUnclassifiedIPv41
AS50300CustodianDC LimitedUnclassifiedIPv41
AS37100SEACOM LimitedUnclassifiedIPv41
AS15802Emirates Integrated Telecommunications Company PJSCUnclassifiedIPv41
AS8218Zayo Infrastructure France SAUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41

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.

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 LimitedUnclassifiedIPv4122
AS25040I.T. Consultancy LimitedUnclassifiedIPv446
AS211875Government of JerseyUnclassifiedIPv416

Adjacency

Adjacent networks

26 shown

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4885
AS3356Level 3 Parent, LLCTransitIPv4349
AS6939Hurricane Electric LLCTransitIPv4227
AS204648Calligo LimitedUnclassifiedIPv4122
AS50673Serverius Holding B.V.UnclassifiedIPv448
AS25040I.T. Consultancy LimitedUnclassifiedIPv446
AS57463NetIX Communications JSCUnclassifiedIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS56655Gigahost ASUnclassifiedIPv424
AS24482SG.GSHostingIPv424
AS49673Truenetwork LLCUnclassifiedIPv424
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv424
AS7575Australian Academic and Research Network (AARNet)EducationIPv419
AS211875Government of JerseyUnclassifiedIPv416
AS50629LWLcom GmbHUnclassifiedIPv413
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS33891Core-Backbone GmbHHostingIPv42
AS50304Blix Solutions ASUnclassifiedIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv41
AS12552GlobalConnect ABUnclassifiedIPv41
AS3741Dimension DataUnclassifiedIPv41
AS37100SEACOM LimitedUnclassifiedIPv41
AS15802Emirates Integrated Telecommunications Company PJSCUnclassifiedIPv41
AS50300CustodianDC LimitedUnclassifiedIPv41
AS20562Broadband Hosting B.V.HostingIPv41
AS8218Zayo Infrastructure France SAUnclassifiedIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS13208, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 1 exchange across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
LINX LON1London, United Kingdom195.66.224.202925

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.