Network · data from 2026-11-12
AS26989 H&R Block
Registry name: HR-WORLD-HEADQUARTERS - H&R Block, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26989, 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.
| 168.137.0.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.2.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.4.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.5.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.11.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.104.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.105.0/24 | No ROA | Nonecovered by 168.137.0.0/16 | 673 100% |
| 168.137.100.0/22 | No ROA | RIR databaseARIN | 673 100% |
AS-SET
AS26989'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 16 are in fix.csv.
- ROA: none8
- Route object: none7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.137.0.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.0.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.2.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.2.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.4.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.4.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.5.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.5.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.11.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.11.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.104.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.104.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.105.0/24 | No ROA covers it. Add a ROA for AS26989, maxLength 24. |
| Route object: none | 168.137.105.0/24 | No route object for it. A route object for 168.137.0.0/16 with origin AS26989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26989 in the RIR database for the space. |
| ROA: none | 168.137.100.0/22 | No ROA covers it. Add a ROA for AS26989, maxLength 22. |
Route objects not announced
Route objects with origin AS26989 whose prefix no peer sees AS26989 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.137.0.0/16 | ARIN | 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.