asn.dev

Observed topology

AS204805 voipedeu Voiped Wholesale BV

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS204805: 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
AS174Cogent Communications, LLCTransitIPv4 IPv61,256
AS1299Arelion Sweden ABTransitIPv4 IPv61,218
AS6939Hurricane Electric LLCTransitIPv4 IPv6465
AS20562Broadband Hosting B.V.HostingIPv4265
AS8487Phibee Telecom SASUnclassifiedIPv4172
AS24785Broadband Hosting B.V.HostingIPv4124
AS41327Fiber Telecom S.p.A.ResidentialIPv493
AS3257GTT Communications Inc.TransitIPv4 IPv685
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv646

All 34 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 34

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv61,256
AS1299Arelion Sweden ABTransitIPv4 IPv61,218
AS6939Hurricane Electric LLCTransitIPv4 IPv6465
AS20562Broadband Hosting B.V.HostingIPv4265
AS8487Phibee Telecom SASUnclassifiedIPv4172
AS24785Broadband Hosting B.V.HostingIPv4124
AS41327Fiber Telecom S.p.A.ResidentialIPv493
AS3257GTT Communications Inc.TransitIPv4 IPv685
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv646

All 34 adjacent →

Provenance

Where this comes from

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