Network · data from 2026-11-12
AS55705 Times Internet
Registry name: INDIATIMES-IN - I World Tower, DLF CITY, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55705, 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.
| 2407:3c80:1::/48 | No ROA | Nonecovered by 2407:3c80::/32 | 636 100% |
| 103.10.76.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.10.77.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.36.157.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.238.101.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.41.26.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.41.27.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.41.28.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.41.29.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.41.31.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.124.109.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.18.140.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.18.141.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.18.142.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.156.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.158.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.36.159.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.225.61.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.225.62.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.225.63.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.238.100.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.238.102.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.238.103.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 188.209.154.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.41.22.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.41.23.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.41.24.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.41.25.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 202.41.30.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.55.102.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 203.55.103.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 223.165.29.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 223.165.30.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 223.165.31.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.124.108.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.165.24.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.165.25.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.165.27.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.165.28.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 223.165.26.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
AS-SET
AS55705'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 | 2407:3c80:1::/48 | No ROA covers it. Add a ROA for AS55705, maxLength 48. |
| Route object: none | 2407:3c80:1::/48 | No route object for it. A route object for 2407:3c80::/32 with origin AS55705 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55705 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55705 whose prefix no peer sees AS55705 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.18.143.0/24 | APNIC, RADB | Valid |
| 103.225.60.0/24 | APNIC, RADB | Valid |
| 2407:3c80::/32 | APNIC | No ROA |
| 2407:3c80::/48 | APNIC, 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.