Network · data from 2026-11-12
AS154383 ZWS-AS-AP - ZORNTECH WEB SOLUTIONS
Registry name: ZWS-AS-AP - ZORNTECH WEB SOLUTIONS, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154383, 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.
| 5.83.211.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 178.94.183.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 104.224.52.0/24 | No ROA | None | 1 0%low visibility |
| 185.143.72.0/24 | No ROA | Other origin only | 1 0%low visibility |
| 176.53.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS154383 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: origin2
- ROA: none2
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.83.211.0/24 | ROAs covering it name AS403157, not AS154383. If AS154383 should announce it, add a ROA for AS154383. |
| Route object: none | 5.83.211.0/24 | Route objects for it name AS403157. Add a route object with origin AS154383 in the RIR database for the space. |
| ROA: origin | 178.94.183.0/24 | ROAs covering it name AS20473, AS154408, AS213711, not AS154383. If AS154383 should announce it, add a ROA for AS154383. |
| Route object: none | 178.94.183.0/24 | Route objects for it name AS154408, AS213711. Add a route object with origin AS154383 in the RIR database for the space. |
| ROA: none | 104.224.52.0/24 | No ROA covers it. Add a ROA for AS154383, maxLength 24. |
| Route object: none | 104.224.52.0/24 | No route object for it. Add a route object with origin AS154383 in the RIR database for the space. |
| ROA: none | 185.143.72.0/24 | No ROA covers it. Add a ROA for AS154383, maxLength 24. |
| Route object: none | 185.143.72.0/24 | Route objects for it name AS22769, AS135392. Add a route object with origin AS154383 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154383 whose prefix no peer sees AS154383 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.197.9.0/24 | AFRINIC | Invalid: origin |
| 45.201.34.0/24 | AFRINIC | Invalid: origin |
| 102.135.71.0/24 | AFRINIC | No ROA |
| 154.199.0.0/24 | AFRINIC | Invalid: origin |
| 154.200.0.0/24 | AFRINIC | Invalid: origin |
| 154.201.53.0/24 | AFRINIC | Invalid: origin |
| 2001:df6:5940::/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.