asn.dev

Observed topology

AS34119 WILDCARD-AS Wildcard UK Limited

Hosting RIPE NSP

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS34119: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6282
AS2914NTT America, Inc.TransitIPv4 IPv6215
AS3257GTT Communications Inc.TransitIPv4144
AS6939Hurricane Electric LLCTransitIPv488
AS34549meerfarbig GmbH & Co. KGHostingIPv433
AS33891Core-Backbone GmbHHostingIPv422
AS50304Blix Solutions ASUnclassifiedIPv422
AS3216PJSC "Vimpelcom"MobileIPv411
AS3741Dimension DataUnclassifiedIPv411
AS4657StarHub LtdResidentialIPv411

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202067Advantex Network Solutions LtdUnclassifiedIPv4118
AS216207Newcastle City CouncilUnclassifiedIPv469

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6343
AS2914NTT America, Inc.TransitIPv4 IPv6257
AS3257GTT Communications Inc.TransitIPv4144
AS202067Advantex Network Solutions LtdUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv4112
AS216207Newcastle City CouncilUnclassifiedIPv469
AS34549meerfarbig GmbH & Co. KGHostingIPv442
AS33891Core-Backbone GmbHHostingIPv428
AS50304Blix Solutions ASUnclassifiedIPv428
AS3216PJSC "Vimpelcom"MobileIPv414

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