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,024 addresses · 1 top-level Routing data as of 2026-10-03 16:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 138.94.172.0/22 | 138.94.172.0 – 138.94.175.255 | 1,024 |
| 138.94.172.0/23 | 138.94.172.0 – 138.94.173.255 | 512 |
| 138.94.172.0/24 | 138.94.172.0 – 138.94.172.255 | 256 |
| 138.94.173.0/24 | 138.94.173.0 – 138.94.173.255 | 256 |
| 138.94.174.0/23 | 138.94.174.0 – 138.94.175.255 | 512 |
| 138.94.174.0/24 | 138.94.174.0 – 138.94.174.255 | 256 |
| 138.94.175.0/24 | 138.94.175.0 – 138.94.175.255 | 256 |
IPv6 Prefixes
5 prefixes · 65,536 × /48 · 1 top-level Routing data as of 2026-10-03 16:00 UTC
| Prefix | Addresses |
|---|---|
| 2804:2388:: | 296 |
| 2804:2388:: | 294 |
| 2804:2388:4000:: | 294 |
| 2804:2388:8000:: | 294 |
| 2804:2388:c000:: | 294 |
BGP Neighbours
3 unique neighbours · 3 upstream/peer · 0 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. Upstream & peer side (3)