Network · data from 2026-11-12
AS36003 NOS-NOG
Registry name: NOS-NOG - NOS Network Operations Group, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36003, 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.
| 208.69.80.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 208.69.83.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2607:cc00::/32 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
AS36003'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: none3
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 208.69.80.0/24 | No ROA covers it. Add a ROA for AS36003, maxLength 24. |
| Route object: RIR | 208.69.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.69.83.0/24 | No ROA covers it. Add a ROA for AS36003, maxLength 24. |
| Route object: RIR | 208.69.83.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2607:cc00::/32 | No ROA covers it. Add a ROA for AS36003, maxLength 32. |
| Route object: RIR | 2607:cc00::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS36003 is announced.
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.