asn.dev

Observed topology

AS13213 UK2NET-AS THG HOSTING LIMITED

Hosting RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS13213: 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
AS1299Arelion Sweden ABTransitIPv4 IPv62,439
AS6461Zayo BandwidthTransitIPv4 IPv61,443
AS6939Hurricane Electric LLCTransitIPv4 IPv6358
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6122
AS50304Blix Solutions ASUnclassifiedIPv480
AS3216PJSC "Vimpelcom"MobileIPv441
AS24482SG.GSHostingIPv4 IPv641
AS33891Core-Backbone GmbHHostingIPv441
AS48185team.blue NVUnclassifiedIPv4 IPv641
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv641

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS16339Virtual Internet (UK) LimitedUnclassifiedIPv458
AS197651FIC SHARECO LIMITEDUnclassifiedIPv458
AS29854WestHost, Inc.HostingIPv631

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv62,500
AS6461Zayo BandwidthTransitIPv4 IPv61,475
AS6939Hurricane Electric LLCTransitIPv4 IPv6376
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6128
AS50304Blix Solutions ASUnclassifiedIPv484
AS16339Virtual Internet (UK) LimitedUnclassifiedIPv458
AS197651FIC SHARECO LIMITEDUnclassifiedIPv458
AS3216PJSC "Vimpelcom"MobileIPv443
AS24482SG.GSHostingIPv4 IPv643
AS33891Core-Backbone GmbHHostingIPv443

All 26 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.