asn.dev

Observed topology

AS43519 NOMINETANYCAST

Hosting RIPE

Upstreams 31 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 26
Adjacent (IPv6) 19
Upstream graph Who carries AS43519, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS43519 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS43519: 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 IPv6979
AS6939Hurricane Electric LLCTransitIPv4 IPv6596
AS2914NTT America, Inc.TransitIPv4 IPv6524
AS3257GTT Communications Inc.TransitIPv4 IPv6312
AS9002RETN LimitedUnclassifiedIPv4 IPv6104
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv662
AS48185team.blue NVUnclassifiedIPv4 IPv659
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv657
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv657

All 31 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6979
AS6939Hurricane Electric LLCTransitIPv4 IPv6596
AS2914NTT America, Inc.TransitIPv4 IPv6524
AS3257GTT Communications Inc.TransitIPv4 IPv6312
AS9002RETN LimitedUnclassifiedIPv4 IPv6104
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv675
AS24482SG.GSHostingIPv4 IPv662
AS48185team.blue NVUnclassifiedIPv4 IPv659
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv657
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv657

All 31 adjacent →

Provenance

Where this comes from

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