Network · data from 2026-11-12
AS17386 GRAINGER - W.W.GRAINGER
Registry name: GRAINGER - W.W.GRAINGER, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17386, 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.
| 167.115.0.0/16 | No ROA | None | 673 100% |
| 167.115.0.0/18 | No ROA | None | 673 100% |
| 167.115.128.0/18 | No ROA | None | 673 100% |
| 167.115.128.0/24 | No ROA | None | 673 100% |
| 167.115.150.0/24 | No ROA | None | 673 100% |
| 167.115.190.0/24 | No ROA | None | 673 100% |
| 167.115.252.0/24 | No ROA | Nonecovered by 167.115.252.0/23 | 673 100% |
| 167.115.2.0/24 | No ROA | None | 2 0%low visibility |
| 167.115.248.0/24 | No ROA | Other IRR onlyRADB | 1 0%low visibility |
AS-SET
AS17386 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 20 are in fix.csv.
- ROA: none9
- Route object: none8
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.115.0.0/16 | No ROA covers it. Add a ROA for AS17386, maxLength 16. |
| Route object: none | 167.115.0.0/16 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.0.0/18 | No ROA covers it. Add a ROA for AS17386, maxLength 18. |
| Route object: none | 167.115.0.0/18 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.128.0/18 | No ROA covers it. Add a ROA for AS17386, maxLength 18. |
| Route object: none | 167.115.128.0/18 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.128.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: none | 167.115.128.0/24 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.150.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: none | 167.115.150.0/24 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.190.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: none | 167.115.190.0/24 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.252.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: none | 167.115.252.0/24 | No route object for it. A route object for 167.115.252.0/23 with origin AS17386 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.2.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: none | 167.115.2.0/24 | No route object for it. Add a route object with origin AS17386 in the RIR database for the space. |
| ROA: none | 167.115.248.0/24 | No ROA covers it. Add a ROA for AS17386, maxLength 24. |
| Route object: RIR | 167.115.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17386 whose prefix no peer sees AS17386 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 167.115.252.0/23 | RADB | No ROA |
| 167.115.254.0/23 | 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.