Network · data from 2026-11-12
AS58608 TATATELE-IN - TTML Mumbai Turbhe
Registry name: TATATELE-IN - TTML Mumbai Turbhe, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58608, 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.3.42.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
AS-SET
AS58608 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 9 are in fix.csv.
- ROA: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.3.42.0/24 | No ROA covers it. Add a ROA for AS58608, maxLength 24. |
Route objects not announced
Route objects with origin AS58608 whose prefix no peer sees AS58608 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 49.248.70.0/24 | APNIC | Valid |
| 49.248.71.0/24 | APNIC | Valid |
| 49.248.125.0/24 | APNIC | Valid |
| 49.248.217.0/24 | APNIC | Valid |
| 49.248.220.0/24 | APNIC | Valid |
| 123.252.148.0/24 | APNIC | Invalid: origin |
| 123.252.174.0/24 | APNIC | Invalid: origin |
| 202.149.220.0/24 | APNIC | Invalid: origin |
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.