Registration
The registry's RDAP record for this AS number could not be retrieved; it is looked up again automatically.
IPv4 Prefixes
8 prefixes · 2,048 addresses Routing data as of 2026-10-11 08:00 UTC
| Prefix | Range | Addresses |
|---|---|---|
| 103.90.196.0/24 | 103.90.196.0 – 103.90.196.255 | 256 |
| 103.90.197.0/24 | 103.90.197.0 – 103.90.197.255 | 256 |
| 103.90.198.0/24 | 103.90.198.0 – 103.90.198.255 | 256 |
| 103.90.199.0/24 | 103.90.199.0 – 103.90.199.255 | 256 |
| 175.106.16.0/24 | 175.106.16.0 – 175.106.16.255 | 256 |
| 175.106.17.0/24 | 175.106.17.0 – 175.106.17.255 | 256 |
| 175.106.18.0/24 | 175.106.18.0 – 175.106.18.255 | 256 |
| 175.106.19.0/24 | 175.106.19.0 – 175.106.19.255 | 256 |
IPv6 Prefixes
This AS does not currently announce any IPv6 prefixes.
BGP Neighbours
7 unique neighbours · 3 upstream/peer · 2 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 right of this AS in BGP paths — networks whose routes it carries, typically its customers (downstreams). 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)
Downstream side (2)
Collector-only (2)