asn.dev

Observed topology

AS207043 DEDIK-IO

Unclassified Spamhaus ASN-DROP RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207043: 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
AS197071active 1 GmbHUnclassifiedIPv4 IPv6992
AS58291ColoCenter b.v.HostingIPv4 IPv6446
AS16276OVH SASHostingIPv4366
AS135392MillenialHost LimitedUnclassifiedIPv4172
AS18450WebNX, Inc.HostingIPv4130
AS30823aurologic GmbHHostingIPv4119
AS215703FREAKHOSTING LTDUnclassifiedIPv460
AS133398Tele Asia LimitedUnclassifiedIPv457

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS135388RMP Protection LimitedUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS197071active 1 GmbHUnclassifiedIPv4 IPv61,051
AS58291ColoCenter b.v.HostingIPv4 IPv6446
AS16276OVH SASHostingIPv4366
AS135392MillenialHost LimitedUnclassifiedIPv4172
AS18450WebNX, Inc.HostingIPv4130
AS30823aurologic GmbHHostingIPv4119
AS215703FREAKHOSTING LTDUnclassifiedIPv460
AS135388RMP Protection LimitedUnclassifiedIPv459
AS133398Tele Asia LimitedUnclassifiedIPv457

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.