Network · data from 2026-11-12
AS1006 RACKDOG - Rackdog, LLC
Registry name: RACKDOG - Rackdog, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS1006, 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.
| 149.51.225.156/30 | No ROA | Nonecovered by 149.51.225.0/24 | 1 0%low visibility |
| 149.51.244.0/24 | No ROA | None | 1 0%low visibility |
AS-SET
AS1006 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 5 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.51.225.156/30 | No ROA covers it. Add a ROA for AS1006, maxLength 30. |
| Route object: none | 149.51.225.156/30 | No route object for it. A route object for 149.51.225.0/24 with origin AS1006 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS1006 in the RIR database for the space. |
| ROA: none | 149.51.244.0/24 | No ROA covers it. Add a ROA for AS1006, maxLength 24. |
| Route object: none | 149.51.244.0/24 | No route object for it. Add a route object with origin AS1006 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS1006 whose prefix no peer sees AS1006 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 149.51.225.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.