Network · data from 2026-11-12
AS328297 QCell (SL) Limited
Registry name: QCell (SL) Limited - QCell (SL) Limited, SL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328297, 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.
| 102.143.64.0/18 | Valid | Nonecovered by 102.143.0.0/17 | 2 0%low visibility |
| 102.143.0.0/18 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 102.143.0.0/17 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
AS-SET
AS328297'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 9 are in fix.csv.
- Route object: none1
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.143.64.0/18 | No route object for it. A route object for 102.143.0.0/17 with origin AS328297 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328297 in the RIR database for the space. |
| Route object: RIR | 102.143.0.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS328297 whose prefix no peer sees AS328297 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.143.0.0/19 | RADB | Valid |
| 102.143.0.0/20 | RADB | Valid |
| 102.143.0.0/21 | RADB | Valid |
| 102.143.0.0/22 | RADB | Valid |
| 102.143.0.0/23 | RADB | Valid |
| 102.143.0.0/24 | RADB | Valid |
| 2c0f:eeb0::/32 | AFRINIC | 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.