Network · data from 2026-11-12
AS21280 Liquid Telecommunications Operations Limited - Liquid Telecommunications Operations Limited
Registry name: Liquid Telecommunications Operations Limited - Liquid Telecommunications Operations Limited, MU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21280, 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.
| 41.173.184.0/23 | No ROA | Nonecovered by 41.173.184.0/22 | 671 100% |
| 41.173.186.0/23 | No ROA | Nonecovered by 41.173.184.0/22 | 671 100% |
| 41.173.184.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS21280 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 22 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: RIR1
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 41.173.184.0/23 | No ROA covers it. Add a ROA for AS21280, maxLength 23. |
| Route object: none | 41.173.184.0/23 | No route object for it. A route object for 41.173.184.0/22 with origin AS21280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21280 in the RIR database for the space. |
| ROA: none | 41.173.186.0/23 | No ROA covers it. Add a ROA for AS21280, maxLength 23. |
| Route object: none | 41.173.186.0/23 | No route object for it. A route object for 41.173.184.0/22 with origin AS21280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21280 in the RIR database for the space. |
| ROA: none | 41.173.184.0/22 | No ROA covers it. Add a ROA for AS21280, maxLength 22. |
| Route object: RIR | 41.173.184.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS21280 whose prefix no peer sees AS21280 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.240.192.0/21 | RIPE-NONAUTH | No ROA |
| 80.240.196.0/24 | RIPE-NONAUTH | No ROA |
| 80.240.204.0/23 | RIPE-NONAUTH | No ROA |
| 196.216.65.0/24 | RIPE-NONAUTH | No ROA |
| 196.216.74.0/24 | RIPE-NONAUTH | No ROA |
| 196.216.75.0/24 | RIPE-NONAUTH | No ROA |
| 196.216.79.0/24 | RIPE-NONAUTH | No ROA |
| 196.216.80.0/21 | RIPE-NONAUTH | No ROA |
| 196.216.90.0/24 | RIPE-NONAUTH | No ROA |
| 217.21.112.0/21 | RIPE-NONAUTH | No ROA |
| 217.21.112.0/22 | RIPE-NONAUTH | No ROA |
| 217.21.116.0/22 | RIPE-NONAUTH | No ROA |
| 217.21.118.0/23 | RIPE-NONAUTH | No ROA |
| 217.21.120.0/22 | RIPE-NONAUTH | No ROA |
| 217.21.124.0/23 | RIPE-NONAUTH | No ROA |
| 2001:4238::/32 | ALTDB | 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.