Observed topology

AS48589 TIGER Tiger Network Limited

Unclassified Spamhaus ASN-DROP RIPE

Upstreams 3 carry this network

Downstreams 5 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 1

Upstream graph Who carries AS48589, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS48589 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48589: 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.

AS	Network	Type	Families	Paths seen
AS64050	BGP Network Limited	Hosting	IPv4	598
AS6939	Hurricane Electric LLC	Transit	IPv4	121
AS43668	"AS43668" LLC	Residential	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS210528	Navox co.,Ltd	Unclassified	IPv4	355
AS208525	Airu Limited	Unclassified	IPv4	66
AS18207	YOU Broadband & Cable India Ltd.	Unclassified	IPv4	59
AS19056	Qualcomm, Inc.	Unclassified	IPv4	59
AS18198	MATHIAS-NZ Mathias Technologies	Unclassified	IPv4	58

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS64050	BGP Network Limited	Hosting	IPv4	1,129
AS210528	Navox co.,Ltd	Unclassified	IPv4	355
AS6939	Hurricane Electric LLC	Transit	IPv4	187
AS208525	Airu Limited	Unclassified	IPv4	66
AS18207	YOU Broadband & Cable India Ltd.	Unclassified	IPv4	59
AS19056	Qualcomm, Inc.	Unclassified	IPv4	59
AS18198	MATHIAS-NZ Mathias Technologies	Unclassified	IPv4	58
AS43668	"AS43668" LLC	Residential	IPv6	32

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.