Network · data from 2026-11-12
AS13857 Online Northwest
Registry name: ONLINEMAC - Online Northwest, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13857, 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.
| 144.86.148.0/22 | No ROA | Other IRR onlyRADB | 667 99% |
| 69.168.112.0/21 | Valid | RIR databaseARIN | 670 100% |
| 69.168.120.0/21 | Valid | RIR databaseARIN | 670 100% |
| 187.40.128.0/21 | Valid | RIR databaseARIN, RADB | 670 100% |
| 206.212.224.0/21 | Valid | RIR databaseARIN | 670 100% |
| 206.212.232.0/21 | Valid | RIR databaseARIN | 670 100% |
| 208.83.192.0/21 | Valid | RIR databaseALTDB, ARIN, RADB | 669 99% |
| 208.85.232.0/21 | Valid | RIR databaseALTDB, ARIN, RADB | 669 99% |
| 199.66.196.0/22 | Valid | RIR databaseALTDB, ARIN, RADB | 667 99% |
| 2604:be40::/32 | Valid | RIR databaseARIN, RADB | 635 100% |
AS-SET
AS13857'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 6 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 144.86.148.0/22 | No ROA covers it. Add a ROA for AS13857, maxLength 22. |
| Route object: RIR | 144.86.148.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13857 whose prefix no peer sees AS13857 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.168.112.0/20 | ARIN, RADB | Valid |
| 198.92.64.0/22 | RADB | No ROA |
| 206.212.224.0/20 | ARIN, RADB | Valid |
| 2607:2980::/32 | 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.