Network · data from 2026-11-12
AS42192 Leading Broadband ISP
Registry name: India THUNDER NETWORK LIMITED, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42192, 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.
| 2a0e:68c0:7::/48 | No ROA | None | 633 100% |
AS-SET
AS42192'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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:68c0:7::/48 | No ROA covers it. Add a ROA for AS42192, maxLength 48. |
| Route object: none | 2a0e:68c0:7::/48 | No route object for it. Add a route object with origin AS42192 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42192 whose prefix no peer sees AS42192 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 59.155.0.0/16 | RADB | No ROA |
| 112.143.0.0/16 | RADB | No ROA |
| 139.183.0.0/16 | RADB | No ROA |
| 223.254.0.0/16 | RADB | No ROA |
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.