asn.dev

Observed topology

AS397032 SPARKED - SPARKED HOST LLC

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS397032: 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
AS13335Cloudflare, Inc.HostingIPv4413
AS1002Bytefilter LLCUnclassifiedIPv4192
AS60068Datacamp LimitedHostingIPv4 IPv6168
AS26042FiberState, LLCHostingIPv4 IPv6139
AS58212dataforest GmbHUnclassifiedIPv4122
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv696
AS206216Advin Services LLCHostingIPv462
AS174Cogent Communications, LLCTransitIPv625

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS215120Evolus IT Solutions GmbHUnclassifiedIPv4 IPv698
AS205563Marc GomezUnclassifiedIPv666
AS401558Kage Solutions LLCUnclassifiedIPv466
AS25735Sloth NetworksUnclassifiedIPv462
AS29803FanaticNode LLCUnclassifiedIPv415

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv4413
AS1002Bytefilter LLCUnclassifiedIPv4254
AS26042FiberState, LLCHostingIPv4 IPv6245
AS60068Datacamp LimitedHostingIPv4 IPv6234
AS58212dataforest GmbHUnclassifiedIPv4122
AS215120Evolus IT Solutions GmbHUnclassifiedIPv4 IPv698
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv696
AS174Cogent Communications, LLCTransitIPv4 IPv683
AS205563Marc GomezUnclassifiedIPv666
AS401558Kage Solutions LLCUnclassifiedIPv466

All 14 adjacent →

Provenance

Where this comes from

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