Observed topology
AS4777 APNIC-COLO - Asia Pacific Network Information Centre
Unclassified APNIC Non-Profit
Transit
Upstream networks
Networks observed carrying traffic for AS4777: 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 |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 84 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 IPv6 | 44 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 25 |
| AS2500 | WIDE Project | Unclassified | IPv4 IPv6 | 13 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 | 11 |
| AS134148 | SingAREN | Unclassified | IPv4 IPv6 | 6 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 2 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS4777 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS45192 | ASN for APNICTRAINING LAB DC | Unclassified | IPv4 IPv6 | 93 |
| AS18368 | Asia Pacific Network Information Centre | Hosting | IPv4 IPv6 | 64 |
| AS18369 | Asia Pacific Network Information Centre | Unclassified | IPv4 IPv6 | 15 |
| AS18366 | Asia Pacific Network Information Centre | Unclassified | IPv4 IPv6 | 9 |
| AS18367 | Asia Pacific Network Information Centre | Unclassified | IPv4 | 9 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4777 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 189 |
| AS45192 | ASN for APNICTRAINING LAB DC | Unclassified | IPv4 IPv6 | 93 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 IPv6 | 73 |
| AS18368 | Asia Pacific Network Information Centre | Hosting | IPv4 IPv6 | 64 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 60 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 | 17 |
| AS18369 | Asia Pacific Network Information Centre | Unclassified | IPv4 IPv6 | 15 |
| AS2500 | WIDE Project | Unclassified | IPv4 IPv6 | 13 |
| AS134148 | SingAREN | Unclassified | IPv4 IPv6 | 11 |
| AS18366 | Asia Pacific Network Information Centre | Unclassified | IPv4 IPv6 | 9 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.