Network · data from 2026-11-12
AS328157 VirtualComms (Pty) Ltd - VirtualComms (Pty) Ltd
Registry name: VirtualComms (Pty) Ltd - VirtualComms (Pty) Ltd, ZA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS328157, 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.204.20.0/22 | Valid | None | 673 100% |
| 160.19.196.0/22 | Valid | RIR databaseAFRINIC | 671 100% |
| 160.19.196.0/24 | Valid | RIR databaseAFRINIC | 129 19% |
| 160.19.197.0/24 | Valid | RIR databaseAFRINIC | 129 19% |
| 160.19.198.0/24 | Valid | RIR databaseAFRINIC | 129 19% |
| 160.19.199.0/24 | Valid | RIR databaseAFRINIC | 129 19% |
AS-SET
AS328157 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.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.204.20.0/22 | No route object for it. Add a route object with origin AS328157 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS328157 whose prefix no peer sees AS328157 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.204.20.0/24 | AFRINIC | Valid |
| 102.204.21.0/24 | AFRINIC | Valid |
| 102.204.22.0/24 | AFRINIC | Valid |
| 102.204.23.0/24 | AFRINIC | Valid |
| 160.19.196.0/23 | AFRINIC | Valid |
| 160.19.198.0/23 | 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.