asn.dev

Observed topology

AS202914 adeodc Adeo Datacenter ApS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS202914: 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
AS6797GlobalConnect ABUnclassifiedIPv4 IPv6915
AS174Cogent Communications, LLCTransitIPv4653
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv6408

Transit

Downstream networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS205984Powernet ApsUnclassifiedIPv4420
AS34165Novaram ApSUnclassifiedIPv4236
AS198614RockyNordic ApSUnclassifiedIPv4177
AS60958Infolink ApsUnclassifiedIPv4153
AS215686Edelskjold Holding ApSUnclassifiedIPv4 IPv6134
AS208377SECOMEA A/SUnclassifiedIPv4118
AS209528MyWebCity Denmark ApSUnclassifiedIPv4 IPv6104
AS57860Zencurity ApSVPNIPv4 IPv690
AS206084VELOS IOT JERSEY LIMITEDUnclassifiedIPv475
AS204171TD-K A/SUnclassifiedIPv472

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS6797GlobalConnect ABUnclassifiedIPv4 IPv61,709
AS174Cogent Communications, LLCTransitIPv4 IPv61,256
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv6719
AS205984Powernet ApsUnclassifiedIPv4420
AS34165Novaram ApSUnclassifiedIPv4236
AS198614RockyNordic ApSUnclassifiedIPv4177
AS60958Infolink ApsUnclassifiedIPv4153
AS215686Edelskjold Holding ApSUnclassifiedIPv4 IPv6134
AS208377SECOMEA A/SUnclassifiedIPv4118
AS209528MyWebCity Denmark ApSUnclassifiedIPv4 IPv6104

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.