Network · data from 2026-11-12
AS19970 CARRIERDOMAIN-NYC - R&R Managed Telecom Services
Registry name: CARRIERDOMAIN-NYC - R&R Managed Telecom Services, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19970, 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.
| 69.46.233.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 149.13.70.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.48.198.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 154.48.201.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 38.105.229.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.125.23.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 81.2.128.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2602:fa63::/36 | No ROA | RIR databaseARIN | 635 100% |
| 43.231.207.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 61.245.10.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 61.245.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS19970 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 17 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 69.46.233.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 69.46.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.13.70.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 149.13.70.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.48.198.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 154.48.198.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 154.48.201.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 154.48.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.105.229.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 38.105.229.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.125.23.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 38.125.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 81.2.128.0/24 | No ROA covers it. Add a ROA for AS19970, maxLength 24. |
| Route object: RIR | 81.2.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:fa63::/36 | No ROA covers it. Add a ROA for AS19970, maxLength 36. |
| Route object: RIR | 43.231.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19970 whose prefix no peer sees AS19970 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 8.12.122.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.