asn.dev

Observed topology

AS214783 DEDICATEDNODES-AS

Unclassified RIPE NSP

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS214783: 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 IPv6146
AS49544i3D.net B.VUnclassifiedIPv4 IPv696
AS20326TeraSwitch Networks Inc.UnclassifiedIPv4 IPv693
AS2914NTT America, Inc.TransitIPv4 IPv681
AS6939Hurricane Electric LLCTransitIPv4 IPv663
AS58212dataforest GmbHUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS33891Core-Backbone GmbHHostingIPv46
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv65

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213535YottaSrcHostingIPv4 IPv6268

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6286
AS213535YottaSrcHostingIPv4 IPv6268
AS2914NTT America, Inc.TransitIPv4 IPv6160
AS6939Hurricane Electric LLCTransitIPv4 IPv6112
AS49544i3D.net B.VUnclassifiedIPv4 IPv696
AS20326TeraSwitch Networks Inc.UnclassifiedIPv4 IPv693
AS58212dataforest GmbHUnclassifiedIPv460
AS24482SG.GSHostingIPv4 IPv67
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS33891Core-Backbone GmbHHostingIPv46

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