asn.dev

Observed topology

AS215703 FREAKHOSTING _

Unclassified RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215703: 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
AS58212dataforest GmbHUnclassifiedIPv4 IPv61,831
AS13335Cloudflare, Inc.HostingIPv4289
AS36352HostPapaHostingIPv4285
AS202520SkyPass Solutions Sp. z o.o.HostingIPv4120
AS30823aurologic GmbHHostingIPv459
AS30456Cosmic Global NetworksUnclassifiedIPv436

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214062ITITAN HOSTING SOLUTIONS SRLUnclassifiedIPv4180
AS201129SARL AUUnclassifiedIPv460
AS207043DEDIK SERVICES LIMITEDUnclassifiedIPv460
AS218589Jan BenesUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS58212dataforest GmbHUnclassifiedIPv4 IPv62,132
AS13335Cloudflare, Inc.HostingIPv4289
AS36352HostPapaHostingIPv4285
AS214062ITITAN HOSTING SOLUTIONS SRLUnclassifiedIPv4180
AS202520SkyPass Solutions Sp. z o.o.HostingIPv4120
AS201129SARL AUUnclassifiedIPv460
AS207043DEDIK SERVICES LIMITEDUnclassifiedIPv460
AS30823aurologic GmbHHostingIPv459
AS30456Cosmic Global NetworksUnclassifiedIPv436
AS218589Jan BenesUnclassifiedIPv41

Provenance

Where this comes from

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