Network · data from 2026-11-12
AS5033 AS5033 - Key Information Systems, Inc.
Registry name: AS5033 - Key Information Systems, Inc., US · not in PeeringDB
13IPv4 routes
0.0% RPKI valid · 76.9% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
13No ROA
3 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
35Route objects not announced
registered with origin AS5033, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS5033, 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.
| 207.178.188.0/24 | No ROA | Nonecovered by 207.178.128.0/17 | 673 100% |
| 207.178.224.0/24 | No ROA | Nonecovered by 207.178.128.0/17 | 673 100% |
| 64.162.116.0/24 | No ROA | None | 672 100% |
| 63.204.233.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 64.160.254.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.127.154.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 207.213.112.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 207.213.142.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 209.239.224.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.84.25.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 209.239.248.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 207.178.128.0/17 | No ROA | RIR databaseARIN | 673 100% |
| 216.38.111.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS5033 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 59 are in fix.csv.
- ROA: none13
- Route object: none3
- Route object: RIR8
- Route object: not announced35
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.178.188.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: none | 207.178.188.0/24 | No route object for it. A route object for 207.178.128.0/17 with origin AS5033 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5033 in the RIR database for the space. |
| ROA: none | 207.178.224.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: none | 207.178.224.0/24 | No route object for it. A route object for 207.178.128.0/17 with origin AS5033 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5033 in the RIR database for the space. |
| ROA: none | 64.162.116.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: none | 64.162.116.0/24 | No route object for it. Add a route object with origin AS5033 in the RIR database for the space. |
| ROA: none | 63.204.233.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: RIR | 63.204.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 64.160.254.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: RIR | 64.160.254.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.127.154.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: RIR | 66.127.154.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.213.112.0/22 | No ROA covers it. Add a ROA for AS5033, maxLength 22. |
| Route object: RIR | 207.213.112.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.213.142.0/23 | No ROA covers it. Add a ROA for AS5033, maxLength 23. |
| Route object: RIR | 207.213.142.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.239.224.0/20 | No ROA covers it. Add a ROA for AS5033, maxLength 20. |
| Route object: RIR | 209.239.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.84.25.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
| Route object: RIR | 208.84.25.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.239.248.0/21 | No ROA covers it. Add a ROA for AS5033, maxLength 21. |
| Route object: RIR | 209.239.248.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 207.178.128.0/17 | No ROA covers it. Add a ROA for AS5033, maxLength 17. |
| ROA: none | 216.38.111.0/24 | No ROA covers it. Add a ROA for AS5033, maxLength 24. |
Route objects not announced
Route objects with origin AS5033 whose prefix no peer sees AS5033 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.121.0.0/21 | RADB | No ROA |
| 74.121.0.0/22 | RADB | No ROA |
| 74.121.4.0/22 | RADB | No ROA |
| 146.82.174.0/23 | RADB | No ROA |
| 207.178.128.0/24 | RADB | No ROA |
| 207.178.132.0/24 | RADB | No ROA |
| 207.178.140.0/24 | RADB | No ROA |
| 207.178.142.0/24 | RADB | No ROA |
| 207.178.143.0/24 | RADB | No ROA |
| 207.178.144.0/24 | RADB | No ROA |
| 207.178.145.0/24 | RADB | No ROA |
| 207.178.155.0/24 | RADB | No ROA |
| 207.178.156.0/22 | RADB | No ROA |
| 207.178.156.0/24 | RADB | No ROA |
| 207.178.157.0/24 | RADB | No ROA |
| 207.178.159.0/24 | RADB | No ROA |
| 207.178.160.0/22 | RADB | No ROA |
| 207.178.162.0/24 | RADB | No ROA |
| 207.178.166.0/24 | RADB | No ROA |
| 207.178.167.0/24 | RADB | No ROA |
| 207.178.170.0/24 | RADB | No ROA |
| 207.178.173.0/24 | RADB | No ROA |
| 207.178.197.0/24 | RADB | No ROA |
| 207.178.200.0/24 | RADB | No ROA |
| 207.178.203.0/24 | RADB | No ROA |
| 207.178.206.0/24 | RADB | No ROA |
| 207.178.214.0/24 | RADB | No ROA |
| 207.178.216.0/24 | RADB | No ROA |
| 207.178.236.0/24 | RADB | No ROA |
| 207.178.238.0/24 | RADB | No ROA |
| 207.178.252.0/24 | RADB | No ROA |
| 208.83.96.0/21 | RADB | No ROA |
| 208.84.24.0/24 | RADB | No ROA |
| 209.77.185.0/24 | RADB | No ROA |
| 216.237.40.0/24 | 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.