asn.dev

Observed topology

AS138968 RAINBOWIDC-AS-AP - rainbow network limited

Unclassified Spamhaus ASN-DROP APNIC Route Server

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138968: 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
AS64050BGP Network LimitedHostingIPv4527
AS17676SoftBank Corp.MobileIPv4 IPv6315
AS134823Sky Digital Co., Ltd.ResidentialIPv4237
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS136826PT TITIK TERANG MAKMURUnclassifiedIPv445
AS134196ANYUN INTERNET TECHNOLOGY (HK) CO.,LIMITEDUnclassifiedIPv442
AS24482SG.GSHostingIPv4 IPv618
AS55933Cloudie LimitedHostingIPv46
AS9002RETN LimitedUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208525Airu LimitedUnclassifiedIPv4290

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS64050BGP Network LimitedHostingIPv4817
AS17676SoftBank Corp.MobileIPv4 IPv6315
AS208525Airu LimitedUnclassifiedIPv4290
AS134823Sky Digital Co., Ltd.ResidentialIPv4237
AS6939Hurricane Electric LLCTransitIPv4 IPv6139
AS136826PT TITIK TERANG MAKMURUnclassifiedIPv445
AS134196ANYUN INTERNET TECHNOLOGY (HK) CO.,LIMITEDUnclassifiedIPv442
AS24482SG.GSHostingIPv4 IPv618
AS55933Cloudie LimitedHostingIPv46
AS9002RETN LimitedUnclassifiedIPv43

Provenance

Where this comes from

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