asn.dev

Observed topology

AS142594 SPEEDYPAGELTD-AS-AP SpeedyPage Ltd

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142594: 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
AS60068Datacamp LimitedHostingIPv4 IPv6530
AS35200TransitX LtdUnclassifiedIPv4 IPv6467
AS399244AME Hosting LLCUnclassifiedIPv4 IPv6299
AS20326TeraSwitch Networks Inc.UnclassifiedIPv4 IPv6255
AS136557Host Universal Pty LtdUnclassifiedIPv4 IPv6227
AS60800Netwise Hosting LtdHostingIPv4 IPv6104

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216101Homura Network LimitedUnclassifiedIPv4 IPv6619

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv61,147
AS216101Homura Network LimitedUnclassifiedIPv4 IPv6619
AS35200TransitX LtdUnclassifiedIPv4 IPv6467
AS399244AME Hosting LLCUnclassifiedIPv4 IPv6299
AS20326TeraSwitch Networks Inc.UnclassifiedIPv4 IPv6257
AS136557Host Universal Pty LtdUnclassifiedIPv4 IPv6227
AS60800Netwise Hosting LtdHostingIPv4 IPv6104

Provenance

Where this comes from

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