Network · data from 2026-11-12
AS136625 OOKLA TELECOM
Registry name: OOKLA-AS - Ookla Telecom Pvt.ltd, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS136625, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 103.98.156.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 103.98.156.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.98.157.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.98.158.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.98.159.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.192.72.0/22 | Valid | RIR databaseAPNIC | 534 79% |
| 38.226.63.0/24 | Valid | RIR databaseARIN | 526 78% |
| 38.146.201.0/24 | Valid | RIR databaseARIN | 40 6%low visibility |
| 103.177.31.0/24 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
AS136625's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.
- Route object: not announced10
Route objects not announced
Route objects with origin AS136625 whose prefix no peer sees AS136625 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.98.156.0/23 | APNIC | Valid |
| 103.98.158.0/23 | APNIC | Valid |
| 103.192.72.0/23 | APNIC | Valid |
| 103.192.72.0/24 | APNIC | Valid |
| 103.192.73.0/24 | APNIC | Valid |
| 103.192.74.0/23 | APNIC | Valid |
| 103.192.74.0/24 | APNIC | Valid |
| 103.192.75.0/24 | APNIC | Valid |
| 130.117.119.0/24 | ARIN | No ROA |
| 2401:27a0::/32 | APNIC | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.