Network · data from 2026-11-12
AS208220 offerhostinc
Registry name: offerhostinc Offerhost Solutions Inc, SC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208220, 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.
| 45.8.92.0/24 | Invalid: origin | None | 2 0%low visibility |
| 87.120.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.156.167.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.60.101.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 78.159.156.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.31.194.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.31.195.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 154.6.12.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS208220'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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.8.92.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS208220 should announce it, add a ROA for AS208220. |
| Route object: none | 45.8.92.0/24 | No route object for it. Add a route object with origin AS208220 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208220 whose prefix no peer sees AS208220 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 150.251.59.0/24 | RIPE | 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.