Network · data from 2026-11-12
AS54826 WITG - Western I.T. Group Inc.
Registry name: WITG - Western I.T. Group Inc., CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54826, 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.
| 2604:7480:1::/48 | No ROA | Nonecovered by 2604:7480::/32 | 636 100% |
| 2604:7480::/48 | No ROA | Other IRR onlyRADB | 635 100% |
| 192.96.0.0/24 | No ROA | RIR databaseARIN, BELL | 673 100% |
| 192.110.172.0/22 | No ROA | RIR databaseARIN, BELL | 671 100% |
AS-SET
AS54826 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: none4
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2604:7480:1::/48 | No ROA covers it. Add a ROA for AS54826, maxLength 48. |
| Route object: none | 2604:7480:1::/48 | No route object for it. A route object for 2604:7480::/32 with origin AS54826 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54826 in the RIR database for the space. |
| ROA: none | 2604:7480::/48 | No ROA covers it. Add a ROA for AS54826, maxLength 48. |
| Route object: RIR | 2604:7480::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.96.0.0/24 | No ROA covers it. Add a ROA for AS54826, maxLength 24. |
| ROA: none | 192.110.172.0/22 | No ROA covers it. Add a ROA for AS54826, maxLength 22. |
Route objects not announced
Route objects with origin AS54826 whose prefix no peer sees AS54826 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2604:7480::/32 | ARIN, BELL, RADB | 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.