asn.dev

Observed topology

AS64245 AS-DIGITALFYRE

Unclassified ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS64245: 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
AS397423Tier.Net Technologies LLCHostingIPv4 IPv6779
AS19318Interserver, IncHostingIPv4 IPv6369
AS149020WebHorizon Internet ServicesHostingIPv4 IPv6131
AS42831UK Dedicated Servers LimitedHostingIPv4 IPv6127
AS26666Interserver, IncUnclassifiedIPv4 IPv695
AS49981WorldStream B.V.HostingIPv4 IPv692
AS35200TransitX LtdUnclassifiedIPv429

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55280RackByte LLCHostingIPv4 IPv6214
AS206042Suhail HarisUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS397423Tier.Net Technologies LLCHostingIPv4 IPv61,030
AS19318Interserver, IncHostingIPv4 IPv6369
AS55280RackByte LLCHostingIPv4 IPv6214
AS149020WebHorizon Internet ServicesHostingIPv4 IPv6131
AS42831UK Dedicated Servers LimitedHostingIPv4 IPv6127
AS26666Interserver, IncUnclassifiedIPv4 IPv695
AS49981WorldStream B.V.HostingIPv4 IPv692
AS206042Suhail HarisUnclassifiedIPv637
AS35200TransitX LtdUnclassifiedIPv429

Provenance

Where this comes from

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