Network · data from 2026-11-12
AS8934 NITC
Registry name: NITC National Information Technology Center, JO · PeeringDB
26IPv4 routes
100.0% RPKI valid · 96.2% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
69Route objects not announced
registered with origin AS8934, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS8934, 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.
| 185.109.120.0/22 | Valid | None | 672 100% |
| 193.188.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.67.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.68.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.69.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.70.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.72.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.78.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.82.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.85.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.188.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.188.95.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 93.93.144.0/21 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 193.188.73.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.188.77.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.188.81.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.188.90.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.188.91.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.188.65.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 193.188.74.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 193.188.84.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a02:9c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS8934'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 70 are in fix.csv.
- Route object: none1
- Route object: not announced69
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.109.120.0/22 | No route object for it. Add a route object with origin AS8934 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8934 whose prefix no peer sees AS8934 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.93.144.0/22 | RIPE | Valid |
| 93.93.144.0/23 | RIPE | Valid |
| 93.93.144.0/24 | RIPE | Valid |
| 93.93.145.0/24 | RADB, RIPE | Valid |
| 93.93.146.0/23 | RIPE | Valid |
| 93.93.146.0/24 | RIPE | Valid |
| 93.93.147.0/24 | RIPE | Valid |
| 93.93.148.0/22 | RIPE | Valid |
| 93.93.148.0/23 | RIPE | Valid |
| 93.93.148.0/24 | RIPE | Valid |
| 93.93.149.0/24 | RADB, RIPE | Valid |
| 93.93.150.0/23 | RADB, RIPE | Valid |
| 93.93.150.0/24 | RADB, RIPE | Valid |
| 93.93.151.0/24 | RADB, RIPE | Valid |
| 193.188.67.32/27 | RIPE | Invalid: maxLength |
| 193.188.76.0/24 | RADB, RIPE | Valid |
| 193.188.80.0/24 | RIPE | Valid |
| 193.188.80.0/27 | RIPE | Invalid: maxLength |
| 193.188.80.32/27 | RIPE | Invalid: maxLength |
| 193.188.80.64/27 | RIPE | Invalid: maxLength |
| 193.188.80.96/27 | RIPE | Invalid: maxLength |
| 193.188.80.128/29 | RIPE | Invalid: maxLength |
| 193.188.80.192/29 | RIPE | Invalid: maxLength |
| 193.188.80.216/29 | RIPE | Invalid: maxLength |
| 193.188.80.224/29 | RIPE | Invalid: maxLength |
| 193.188.81.24/29 | RIPE | Invalid: maxLength |
| 193.188.81.32/29 | RIPE | Invalid: maxLength |
| 193.188.81.40/29 | RIPE | Invalid: maxLength |
| 193.188.81.48/29 | RIPE | Invalid: maxLength |
| 193.188.81.64/29 | RIPE | Invalid: maxLength |
| 193.188.81.80/29 | RIPE | Invalid: maxLength |
| 193.188.81.88/29 | RIPE | Invalid: maxLength |
| 193.188.81.104/29 | RIPE | Invalid: maxLength |
| 193.188.81.112/29 | RIPE | Invalid: maxLength |
| 193.188.81.120/29 | RIPE | Invalid: maxLength |
| 193.188.81.128/29 | RIPE | Invalid: maxLength |
| 193.188.81.136/29 | RIPE | Invalid: maxLength |
| 193.188.81.144/29 | RIPE | Invalid: maxLength |
| 193.188.81.152/29 | RIPE | Invalid: maxLength |
| 193.188.83.0/24 | RADB, RIPE | Valid |
| 193.188.84.176/28 | RIPE | Invalid: maxLength |
| 193.188.84.192/28 | RIPE | Invalid: maxLength |
| 193.188.86.0/24 | RADB, RIPE | Valid |
| 193.188.87.0/24 | RADB, RIPE | Valid |
| 193.188.87.168/29 | RIPE | Invalid: maxLength |
| 193.188.88.192/27 | RIPE | Invalid: maxLength |
| 193.188.90.80/28 | RIPE | Invalid: maxLength |
| 193.188.90.96/27 | RIPE | Invalid: maxLength |
| 193.188.91.16/29 | RIPE | Invalid: maxLength |
| 193.188.91.24/29 | RIPE | Invalid: maxLength |
| 193.188.91.32/29 | RIPE | Invalid: maxLength |
| 193.188.91.40/29 | RIPE | Invalid: maxLength |
| 193.188.91.48/29 | RIPE | Invalid: maxLength |
| 193.188.91.56/29 | RIPE | Invalid: maxLength |
| 193.188.91.64/27 | RIPE | Invalid: maxLength |
| 193.188.91.112/29 | RIPE | Invalid: maxLength |
| 193.188.91.120/29 | RIPE | Invalid: maxLength |
| 193.188.91.168/29 | RIPE | Invalid: maxLength |
| 193.188.91.176/29 | RIPE | Invalid: maxLength |
| 193.188.91.184/29 | RIPE | Invalid: maxLength |
| 193.188.91.192/28 | RIPE | Invalid: maxLength |
| 193.188.91.208/29 | RIPE | Invalid: maxLength |
| 193.188.91.216/29 | RIPE | Invalid: maxLength |
| 193.188.92.0/24 | RADB, RIPE | Valid |
| 193.188.93.0/24 | RADB, RIPE | Valid |
| 193.188.93.0/25 | RIPE | Invalid: maxLength |
| 193.188.94.0/24 | RADB, RIPE | Valid |
| 193.188.95.144/28 | RIPE | Invalid: maxLength |
| 2a02:9c0::/32 | RIPE | 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.