Network · data from 2026-11-12
AS146869 SPARKINT-AS-IN - SPARKLIGHT INTERNET PRIVATE LIMITED
Registry name: SPARKINT-AS-IN - SPARKLIGHT INTERNET PRIVATE LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS146869, 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.
| 192.120.199.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
AS-SET
AS146869 isn't in PeeringDB, where networks name their 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 192.120.199.0/24 | ROAs covering it name AS834, not AS146869. If AS146869 should announce it, add a ROA for AS146869. |
| Route object: none | 192.120.199.0/24 | Route objects for it name AS834, AS16276. Add a route object with origin AS146869 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS146869 whose prefix no peer sees AS146869 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df7:9a80::/48 | 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.