Network · data from 2026-11-12
AS63015 DALLAS-DATACENTER - Dallas Data Center
Registry name: DALLAS-DATACENTER - Dallas Data Center, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63015, 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.
| 162.250.224.0/24 | No ROA | Other origin onlycovered by 162.250.224.0/21 | 673 100% |
| 162.250.225.0/24 | No ROA | Other origin onlycovered by 162.250.224.0/21 | 673 100% |
| 162.250.226.0/24 | No ROA | Other origin onlycovered by 162.250.224.0/21 | 673 100% |
| 162.250.227.0/24 | No ROA | Other origin onlycovered by 162.250.224.0/21 | 673 100% |
| 162.250.230.0/24 | No ROA | Nonecovered by 162.250.224.0/21 | 673 100% |
| 162.250.231.0/24 | No ROA | Nonecovered by 162.250.224.0/21 | 673 100% |
AS-SET
AS63015 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 13 are in fix.csv.
- ROA: none6
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 162.250.224.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.224.0/24 | Route objects for it name AS31893. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
| ROA: none | 162.250.225.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.225.0/24 | Route objects for it name AS31893. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
| ROA: none | 162.250.226.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.226.0/24 | Route objects for it name AS31893. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
| ROA: none | 162.250.227.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.227.0/24 | Route objects for it name AS31893. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
| ROA: none | 162.250.230.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.230.0/24 | No route object for it. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
| ROA: none | 162.250.231.0/24 | No ROA covers it. Add a ROA for AS63015, maxLength 24. |
| Route object: none | 162.250.231.0/24 | No route object for it. A route object for 162.250.224.0/21 with origin AS63015 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63015 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63015 whose prefix no peer sees AS63015 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.250.224.0/21 | 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.