Network · data from 2026-11-12
AS50183 Century-LTD CenturyNetworks Ltd
Registry name: Century-LTD CenturyNetworks Ltd, MH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50183, 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.
| 156.238.200.0/24 | Valid | Other origin onlycovered by 156.238.192.0/20 | 119 18% |
| 85.149.224.0/21 | Valid | Other IRR onlyRADB | 671 100% |
| 94.154.178.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 172.96.38.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 192.198.184.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 193.148.95.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 195.246.194.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 198.13.22.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 199.36.102.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 156.238.192.0/20 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
AS-SET
AS50183 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 11 are in fix.csv.
- Route object: none1
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 156.238.200.0/24 | Route objects for it name AS17561. A route object for 156.238.192.0/20 with origin AS50183 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50183 in the RIR database for the space. |
| Route object: RIR | 85.149.224.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 94.154.178.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 172.96.38.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.198.184.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 193.148.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 195.246.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.13.22.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 199.36.102.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50183 whose prefix no peer sees AS50183 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 156.238.192.0/21 | RADB | Valid |
| 156.238.194.0/24 | AFRINIC, RADB | 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.