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,536 addresses Routing data as of 2026-10-03 16:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 103.148.130.0/24 | 103.148.130.0 – 103.148.130.255 | 256 |
| 103.148.131.0/24 | 103.148.131.0 – 103.148.131.255 | 256 |
| 103.158.121.0/24 | 103.158.121.0 – 103.158.121.255 | 256 |
| 103.174.238.0/24 | 103.174.238.0 – 103.174.238.255 | 256 |
| 165.101.230.0/24 | 165.101.230.0 – 165.101.230.255 | 256 |
| 165.101.231.0/24 | 165.101.231.0 – 165.101.231.255 | 256 |
IPv6 Prefixes
1 prefix · 1 × /48 Routing data as of 2026-10-03 16:00 UTC
| Prefix | Addresses |
|---|---|
| 2001:df5:5280:: | 280 |
BGP Neighbours
5 unique neighbours · 2 upstream/peer · 0 downstream · 3 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 (2)
Collector-only (3)