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-09 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 45.180.104.0/22 | 45.180.104.0 – 45.180.107.255 | 1,024 |
| 45.180.104.0/23 | 45.180.104.0 – 45.180.105.255 | 512 |
| 45.180.104.0/24 | 45.180.104.0 – 45.180.104.255 | 256 |
| 45.180.105.0/24 | 45.180.105.0 – 45.180.105.255 | 256 |
| 45.180.106.0/23 | 45.180.106.0 – 45.180.107.255 | 512 |
| 45.180.106.0/24 | 45.180.106.0 – 45.180.106.255 | 256 |
| 45.180.107.0/24 | 45.180.107.0 – 45.180.107.255 | 256 |
IPv6 Prefixes
1 prefix · 65,536 × /48 Routing data as of 2026-10-09 00:00 UTC
| Prefix | Addresses |
|---|---|
| 2804:608c:: | 296 |
BGP Neighbours
8 unique neighbours · 4 upstream/peer · 0 downstream · 4 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 (4)