asn.dev

Observed topology

AS35415 WEBZILLA Webzilla B.V.

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35415: 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 IPv63,712
AS2914NTT America, Inc.TransitIPv4 IPv63,278
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,862
AS174Cogent Communications, LLCTransitIPv4 IPv62,454
AS13335Cloudflare, Inc.HostingIPv4817

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS205186MetaQuotes LtdUnclassifiedIPv4 IPv692
AS43133Cosmonova Broadcast LLCHostingIPv460
AS16255IridiumProvider OUUnclassifiedIPv421

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv63,805
AS2914NTT America, Inc.TransitIPv4 IPv63,327
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,863
AS174Cogent Communications, LLCTransitIPv4 IPv62,484
AS13335Cloudflare, Inc.HostingIPv4817
AS205186MetaQuotes LtdUnclassifiedIPv4 IPv692
AS43133Cosmonova Broadcast LLCHostingIPv460
AS16255IridiumProvider OUUnclassifiedIPv421

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.