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,304 addresses Routing data as of 2026-10-07 00:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 103.74.5.0/24 | 103.74.5.0 – 103.74.5.255 | 256 |
| 103.219.248.0/24 | 103.219.248.0 – 103.219.248.255 | 256 |
| 103.219.249.0/24 | 103.219.249.0 – 103.219.249.255 | 256 |
| 103.219.250.0/24 | 103.219.250.0 – 103.219.250.255 | 256 |
| 103.219.251.0/24 | 103.219.251.0 – 103.219.251.255 | 256 |
| 103.235.72.0/24 | 103.235.72.0 – 103.235.72.255 | 256 |
| 103.235.74.0/24 | 103.235.74.0 – 103.235.74.255 | 256 |
| 103.235.75.0/24 | 103.235.75.0 – 103.235.75.255 | 256 |
| 141.11.78.0/24 | 141.11.78.0 – 141.11.78.255 | 256 |
IPv6 Prefixes
2 prefixes · 2 × /48 Routing data as of 2026-10-07 00:00 UTC
| Prefix | Addresses |
|---|---|
| 2001:df1:a9c0:: | 280 |
| 2001:df2:5a00:: | 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)