Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
20 prefixes · 68,608 addresses · 18 top-level Routing data as of 2026-10-07 16:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 27.133.192.0/20 | 27.133.192.0 – 27.133.207.255 | 4,096 |
| 61.215.224.0/20 | 61.215.224.0 – 61.215.239.255 | 4,096 |
| 101.96.32.0/19 | 101.96.32.0 – 101.96.63.255 | 8,192 |
| 103.225.120.0/22 | 103.225.120.0 – 103.225.123.255 | 1,024 |
| 110.232.224.0/21 | 110.232.224.0 – 110.232.231.255 | 2,048 |
| 110.232.232.0/22 | 110.232.232.0 – 110.232.235.255 | 1,024 |
| 113.197.56.0/21 | 113.197.56.0 – 113.197.63.255 | 2,048 |
| 119.63.16.0/20 | 119.63.16.0 – 119.63.31.255 | 4,096 |
| 157.250.224.0/20 | 157.250.224.0 – 157.250.239.255 | 4,096 |
| 202.125.48.0/20 | 202.125.48.0 – 202.125.63.255 | 4,096 |
| 203.88.176.0/20 | 203.88.176.0 – 203.88.191.255 | 4,096 |
| 210.166.0.0/19 | 210.166.0.0 – 210.166.31.255 | 8,192 |
| 210.166.0.0/20 | 210.166.0.0 – 210.166.15.255 | 4,096 |
| 210.166.16.0/20 | 210.166.16.0 – 210.166.31.255 | 4,096 |
| 210.171.208.0/20 | 210.171.208.0 – 210.171.223.255 | 4,096 |
| 211.19.192.0/22 | 211.19.192.0 – 211.19.195.255 | 1,024 |
| 216.8.0.0/20 | 216.8.0.0 – 216.8.15.255 | 4,096 |
| 216.8.16.0/20 | 216.8.16.0 – 216.8.31.255 | 4,096 |
| 218.223.208.0/20 | 218.223.208.0 – 218.223.223.255 | 4,096 |
| 218.228.16.0/20 | 218.228.16.0 – 218.228.31.255 | 4,096 |
IPv6 Prefixes
1 prefix · 65,536 × /48 Routing data as of 2026-10-07 16:00 UTC
| Prefix | Addresses |
|---|---|
| 2404:200:: | 296 |
BGP Neighbours
10 unique neighbours · 5 upstream/peer · 0 downstream · 5 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 (5)
Collector-only (5)