asn.dev

Observed topology

AS3204 xTom OU

Hosting RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3204: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 54

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

ASNetworkTypeFamiliesPaths seen
AS51087Bling Network LtdUnclassifiedIPv6510
AS139769Guangzhou LinSeek Network Technology Co.LtdUnclassifiedIPv4240
AS212164Jiaxian HeUnclassifiedIPv6214
AS205563Marc GomezUnclassifiedIPv4 IPv6136
AS212085Alexander BruegmannUnclassifiedIPv4 IPv6116
AS13335Cloudflare, Inc.HostingIPv690
AS23347ZYC Network LLCUnclassifiedIPv680
AS399284luYs, Inc.UnclassifiedIPv4 IPv677
AS61228BGP NETWORKS LLCUnclassifiedIPv676
AS200809QUN LINUnclassifiedIPv674

All 54 downstreams →

Adjacency

Adjacent networks

All 94

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

ASNetworkTypeFamiliesPaths seen
AS205794JINZE YANGUnclassifiedIPv62,101
AS3214xTom GmbHHostingIPv4 IPv61,333
AS1299Arelion Sweden ABTransitIPv4 IPv61,190
AS9002RETN LimitedUnclassifiedIPv4 IPv6966
AS51087Bling Network LtdUnclassifiedIPv4 IPv6727
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6305
AS139769Guangzhou LinSeek Network Technology Co.LtdUnclassifiedIPv4240
AS212164Jiaxian HeUnclassifiedIPv6214
AS6233xTomHostingIPv4 IPv6189
AS64049Reliance Jio Infocomm Pte Ltd SingaporeUnclassifiedIPv6172

All 94 adjacent →

Provenance

Where this comes from

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