Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
8 prefixes · 2,048 addresses Routing data as of 2026-10-09 08:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 203.80.8.0/24 | 203.80.8.0 – 203.80.8.255 | 256 |
| 203.80.9.0/24 | 203.80.9.0 – 203.80.9.255 | 256 |
| 203.80.10.0/24 | 203.80.10.0 – 203.80.10.255 | 256 |
| 203.80.11.0/24 | 203.80.11.0 – 203.80.11.255 | 256 |
| 203.80.12.0/24 | 203.80.12.0 – 203.80.12.255 | 256 |
| 203.80.13.0/24 | 203.80.13.0 – 203.80.13.255 | 256 |
| 203.80.14.0/24 | 203.80.14.0 – 203.80.14.255 | 256 |
| 203.80.15.0/24 | 203.80.15.0 – 203.80.15.255 | 256 |
IPv6 Prefixes
1 prefix · 65,536 × /48 Routing data as of 2026-10-09 08:00 UTC
| Prefix | Addresses |
|---|---|
| 2405:8e00:: | 296 |
BGP Neighbours
6 unique neighbours · 4 upstream/peer · 0 downstream · 2 collector-only. A neighbour can be seen on more than one side. Rows are ordered by AS paths: the number of BGP paths seen by RIPE RIS that contain the adjacency. Sightings count each IPv4/IPv6 route with the adjacency once per RIS peer that sees it (routes × peers), so they show how widely it is seen, not how many distinct routes it carries. Networks seen to the left of this AS in BGP paths, toward the route collectors — typically its transit providers (upstreams) and peers. Networks seen to the left of this AS only when they peer directly with a RIPE RIS route collector, so the adjacency may be an artefact of that peering; many of them also appear on the downstream side. Upstream & peer side (4)
Collector-only (2)