Network · data from 2026-11-12
AS329444 BEELINE TELECOMS LIMITED - BEELINE TELECOMS LIMITED
Registry name: BEELINE TELECOMS LIMITED - BEELINE TELECOMS LIMITED, ZM · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS329444, 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.208.220.0/24 | No ROA | Nonecovered by 102.208.220.0/23 | 2 0%low visibility |
| 102.208.221.0/24 | No ROA | RIR databaseAFRINIC | 2 0%low visibility |
AS-SET
AS329444 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 7 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.208.220.0/24 | No ROA covers it. Add a ROA for AS329444, maxLength 24. |
| Route object: none | 102.208.220.0/24 | No route object for it. A route object for 102.208.220.0/23 with origin AS329444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329444 in the RIR database for the space. |
| ROA: none | 102.208.221.0/24 | No ROA covers it. Add a ROA for AS329444, maxLength 24. |
Route objects not announced
Route objects with origin AS329444 whose prefix no peer sees AS329444 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.204.66.0/23 | AFRINIC | No ROA |
| 102.204.66.0/24 | AFRINIC | No ROA |
| 102.204.67.0/24 | AFRINIC | No ROA |
| 102.208.220.0/23 | AFRINIC | 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.