Network · data from 2026-11-12
AS393523 WPGIX-TNN
Registry name: AS-WPGIX-GATEWAY-SERVICES - Winnipeg Internet Exchange (WPGIX) INC., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393523, 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.
| 192.31.228.0/24 | Invalid: origin | Other origin only | 29 4%low visibility |
AS-SET
AS393523'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 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 192.31.228.0/24 | ROAs covering it name AS14866, not AS393523. If AS393523 should announce it, add a ROA for AS393523. |
| Route object: none | 192.31.228.0/24 | Route objects for it name AS14866. Add a route object with origin AS393523 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393523 whose prefix no peer sees AS393523 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:504:2c::/48 | ARIN | Valid |
| 2620:4b::/48 | ALTDB, ARIN | 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.