Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
9 prefixes · 2,048 addresses · 1 top-level Routing data as of 2026-10-03 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 92.235.48.0/21 | 92.235.48.0 – 92.235.55.255 | 2,048 |
| 92.235.48.0/24 | 92.235.48.0 – 92.235.48.255 | 256 |
| 92.235.49.0/24 | 92.235.49.0 – 92.235.49.255 | 256 |
| 92.235.50.0/24 | 92.235.50.0 – 92.235.50.255 | 256 |
| 92.235.51.0/24 | 92.235.51.0 – 92.235.51.255 | 256 |
| 92.235.52.0/24 | 92.235.52.0 – 92.235.52.255 | 256 |
| 92.235.53.0/24 | 92.235.53.0 – 92.235.53.255 | 256 |
| 92.235.54.0/24 | 92.235.54.0 – 92.235.54.255 | 256 |
| 92.235.55.0/24 | 92.235.55.0 – 92.235.55.255 | 256 |
IPv6 Prefixes
1 prefix · 1 × /48 Routing data as of 2026-10-03 00:00 UTC
| Prefix | Addresses |
|---|---|
| 2001:67c:490:: | 280 |
BGP Neighbours
2 unique neighbours · 2 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 (2)