Network · data from 2026-11-12
AS18066 TCLL-AS-AP - Tata Communications Lanka Ltd
Registry name: TCLL-AS-AP - Tata Communications Lanka Ltd, LK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18066, 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.
| 59.163.244.0/24 | Invalid: maxLength | Nonecovered by 59.163.240.0/20 | 2 0%low visibility |
| 59.163.245.0/24 | Invalid: maxLength | Nonecovered by 59.163.240.0/20 | 1 0%low visibility |
| 5.157.88.0/24 | Valid | None | 657 98% |
| 59.163.240.0/20 | Valid | RIR databaseAPNIC | 672 100% |
| 103.84.160.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 115.112.124.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 14.140.56.0/21 | Valid | RIR databaseAPNIC | 671 100% |
| 14.140.61.0/24 | Valid | RIR databaseAPNIC | 3 0%low visibility |
AS-SET
AS18066 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 15 are in fix.csv.
- ROA: maxLength2
- Route object: none3
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 59.163.244.0/24 | ROA 59.163.240.0/20 AS18066 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 59.163.244.0/24. |
| Route object: none | 59.163.244.0/24 | No route object for it. A route object for 59.163.240.0/20 with origin AS18066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18066 in the RIR database for the space. |
| ROA: maxLength | 59.163.245.0/24 | ROA 59.163.240.0/20 AS18066 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 59.163.245.0/24. |
| Route object: none | 59.163.245.0/24 | No route object for it. A route object for 59.163.240.0/20 with origin AS18066 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18066 in the RIR database for the space. |
| Route object: none | 5.157.88.0/24 | No route object for it. Add a route object with origin AS18066 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS18066 whose prefix no peer sees AS18066 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 115.110.130.0/24 | APNIC | Valid |
| 159.153.168.0/21 | RADB | No ROA |
| 159.153.172.0/22 | RADB | No ROA |
| 2400:a240::/48 | APNIC | Valid |
| 2400:a240:1::/48 | APNIC | Valid |
| 2400:a240:2::/48 | APNIC | Valid |
| 2400:a240:3::/48 | APNIC | Valid |
| 2400:a240:10::/48 | APNIC | Valid |
| 2400:a240:11::/48 | APNIC | Valid |
| 2400:a240:12::/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.