Network · data from 2026-11-12
AS396936 HTH2 - HTH
Registry name: HTH2 - HTH, US · not in PeeringDB
9IPv4 routes
0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
9No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS396936, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS396936, 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.
| 209.51.17.0/24 | No ROA | Other origin onlycovered by 209.51.16.0/20 | 671 100% |
| 204.109.49.0/24 | No ROA | Other origin onlycovered by 204.109.48.0/22 | 668 99% |
| 204.109.50.0/24 | No ROA | Other origin onlycovered by 204.109.48.0/22 | 668 99% |
| 207.150.224.0/24 | No ROA | Other origin onlycovered by 207.150.224.0/20 | 668 99% |
| 207.150.232.0/24 | No ROA | Other origin onlycovered by 207.150.224.0/20 | 668 99% |
| 207.150.233.0/24 | No ROA | Other origin onlycovered by 207.150.224.0/20 | 668 99% |
| 207.150.236.0/24 | No ROA | Other origin onlycovered by 207.150.224.0/20 | 668 99% |
| 209.51.19.0/24 | No ROA | Other origin onlycovered by 209.51.16.0/20 | 668 99% |
| 209.51.22.0/24 | No ROA | Other origin onlycovered by 209.51.16.0/20 | 668 99% |
AS-SET
AS396936 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 23 are in fix.csv.
- ROA: none9
- Route object: none9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.51.17.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 209.51.17.0/24 | Route objects for it name AS396940. A route object for 209.51.16.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 204.109.49.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 204.109.49.0/24 | Route objects for it name AS396940. A route object for 204.109.48.0/22 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 204.109.50.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 204.109.50.0/24 | Route objects for it name AS396940. A route object for 204.109.48.0/22 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 207.150.224.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 207.150.224.0/24 | Route objects for it name AS396940. A route object for 207.150.224.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 207.150.232.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 207.150.232.0/24 | Route objects for it name AS63332, AS396940. A route object for 207.150.224.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 207.150.233.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 207.150.233.0/24 | Route objects for it name AS396940. A route object for 207.150.224.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 207.150.236.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 207.150.236.0/24 | Route objects for it name AS396940. A route object for 207.150.224.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 209.51.19.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 209.51.19.0/24 | Route objects for it name AS396940. A route object for 209.51.16.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
| ROA: none | 209.51.22.0/24 | No ROA covers it. Add a ROA for AS396936, maxLength 24. |
| Route object: none | 209.51.22.0/24 | Route objects for it name AS396940. A route object for 209.51.16.0/20 with origin AS396936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396936 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS396936 whose prefix no peer sees AS396936 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.81.161.0/24 | RADB | No ROA |
| 204.109.32.0/20 | RADB | No ROA |
| 204.109.48.0/22 | RADB | No ROA |
| 207.150.224.0/20 | RADB | No ROA |
| 209.51.16.0/20 | 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.