Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
2 prefixes · 512 addresses Routing data as of 2026-10-04 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 103.186.96.0/24 | 103.186.96.0 – 103.186.96.255 | 256 |
| 103.186.97.0/24 | 103.186.97.0 – 103.186.97.255 | 256 |
IPv6 Prefixes
9 prefixes · 65,536 × /48 · 1 top-level Routing data as of 2026-10-04 00:00 UTC
| Prefix | Addresses |
|---|---|
| 2400:aca0:: | 296 |
| 2400:aca0:: | 293 |
| 2400:aca0:2000:: | 293 |
| 2400:aca0:4000:: | 293 |
| 2400:aca0:6000:: | 293 |
| 2400:aca0:8000:: | 293 |
| 2400:aca0:a000:: | 293 |
| 2400:aca0:c000:: | 293 |
| 2400:aca0:e000:: | 293 |
BGP Neighbours
6 unique neighbours · 4 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 (4)
Downstream side (2)