asn.dev

Observed topology

AS207003 WEB1-AS Web1 Oy

Hosting RIPE

Upstreams 6 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 7
Upstream graph Who carries AS207003, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS207003 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207003: 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
AS6667Elisa OyjResidentialIPv4 IPv61,150
AS199508S1 Networks OyResidentialIPv4 IPv699
AS20473The Constant Company, LLCHostingIPv628
AS29802HIVELOCITY, Inc.HostingIPv4 IPv623
AS12552GlobalConnect ABUnclassifiedIPv412
AS719Elisa OyjUnclassifiedIPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213468HD-decor OyUnclassifiedIPv4 IPv6511
AS198936Tietotunkki oyUnclassifiedIPv464
AS61395sysops Finland OyUnclassifiedIPv458
AS211368Cuitunet OyResidentialIPv4 IPv654

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6667Elisa OyjResidentialIPv4 IPv61,255
AS213468HD-decor OyUnclassifiedIPv4 IPv6721
AS719Elisa OyjUnclassifiedIPv4 IPv6619
AS199508S1 Networks OyResidentialIPv4 IPv6271
AS198936Tietotunkki oyUnclassifiedIPv464
AS61395sysops Finland OyUnclassifiedIPv458
AS211368Cuitunet OyResidentialIPv4 IPv654
AS20473The Constant Company, LLCHostingIPv628
AS29802HIVELOCITY, Inc.HostingIPv4 IPv623
AS12552GlobalConnect ABUnclassifiedIPv420

Provenance

Where this comes from

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