Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
7 prefixes · 1,792 addresses Routing data as of 2026-10-04 08:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 38.123.103.0/24 | 38.123.103.0 – 38.123.103.255 | 256 |
| 154.3.169.0/24 | 154.3.169.0 – 154.3.169.255 | 256 |
| 154.41.93.0/24 | 154.41.93.0 – 154.41.93.255 | 256 |
| 202.47.134.0/24 | 202.47.134.0 – 202.47.134.255 | 256 |
| 202.47.135.0/24 | 202.47.135.0 – 202.47.135.255 | 256 |
| 204.141.218.0/24 | 204.141.218.0 – 204.141.218.255 | 256 |
| 204.141.229.0/24 | 204.141.229.0 – 204.141.229.255 | 256 |
IPv6 Prefixes
2 prefixes · 2 × /48 Routing data as of 2026-10-04 08:00 UTC
| Prefix | Addresses |
|---|---|
| 2001:418:149b:: | 280 |
| 2001:418:149c:: | 280 |
BGP Neighbours
6 unique neighbours · 5 upstream/peer · 2 downstream. 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 right of this AS in BGP paths — networks whose routes it carries, typically its customers (downstreams). Upstream & peer side (5)
Downstream side (2)