Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
6 prefixes · 1,280 addresses · 4 top-level Routing data as of 2026-10-11 08:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 103.102.12.0/23 | 103.102.12.0 – 103.102.13.255 | 512 |
| 103.102.12.0/24 | 103.102.12.0 – 103.102.12.255 | 256 |
| 103.102.13.0/24 | 103.102.13.0 – 103.102.13.255 | 256 |
| 103.102.14.0/24 | 103.102.14.0 – 103.102.14.255 | 256 |
| 103.239.22.0/24 | 103.239.22.0 – 103.239.22.255 | 256 |
| 103.239.23.0/24 | 103.239.23.0 – 103.239.23.255 | 256 |
IPv6 Prefixes
1 prefix · 65,536 × /48 Routing data as of 2026-10-11 08:00 UTC
| Prefix | Addresses |
|---|---|
| 2401:db40:: | 296 |
BGP Neighbours
5 unique neighbours · 3 upstream/peer · 0 downstream · 2 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 (3)
Collector-only (2)