Network · data from 2026-11-12
AS53710 OWENS-CORNING - Owens-Corning
Registry name: OWENS-CORNING - Owens-Corning, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53710, 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.
| 205.204.2.0/23 | No ROA | Other origin only | 672 100% |
| 2620:103:8008::/45 | No ROA | Other origin only | 634 100% |
AS-SET
AS53710 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 7 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.204.2.0/23 | No ROA covers it. Add a ROA for AS53710, maxLength 23. |
| Route object: none | 205.204.2.0/23 | Route objects for it name AS36490. Add a route object with origin AS53710 in the RIR database for the space. |
| ROA: none | 2620:103:8008::/45 | No ROA covers it. Add a ROA for AS53710, maxLength 45. |
| Route object: none | 2620:103:8008::/45 | Route objects for it name AS36490. Add a route object with origin AS53710 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53710 whose prefix no peer sees AS53710 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 205.204.2.0/24 | RADB | No ROA |
| 205.204.3.0/24 | RADB | No ROA |
| 2620:103:8000::/45 | 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.