asn.dev

Observed topology

AS210250 WPX

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS210250: 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
AS60068Datacamp LimitedHostingIPv463
AS20473The Constant Company, LLCHostingIPv426
AS29802HIVELOCITY, Inc.HostingIPv45
AS43350NForce Entertainment B.V.UnclassifiedIPv44
AS56630Melbikomas UABHostingIPv44
AS56655Gigahost ASUnclassifiedIPv44
AS63473HostHatch, LLCUnclassifiedIPv44
AS25369Hydra Communications LtdHostingIPv43
AS208226Ouiheberg SARLUnclassifiedIPv43
AS394177SHIFT HOSTING LLCHostingIPv43

All 14 upstreams →

Transit

Downstream networks

inferred

Networks for which AS210250 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 14

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv463
AS20473The Constant Company, LLCHostingIPv426
AS29802HIVELOCITY, Inc.HostingIPv45
AS43350NForce Entertainment B.V.UnclassifiedIPv44
AS56630Melbikomas UABHostingIPv44
AS56655Gigahost ASUnclassifiedIPv44
AS63473HostHatch, LLCUnclassifiedIPv44
AS25369Hydra Communications LtdHostingIPv43
AS208226Ouiheberg SARLUnclassifiedIPv43
AS394177SHIFT HOSTING LLCHostingIPv43

All 14 adjacent →

Provenance

Where this comes from

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