Network · data from 2026-11-12
AS10250 DATAFIVE - INet Solutions
Registry name: DATAFIVE - INet Solutions, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10250, 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.
| 149.19.2.0/24 | No ROA | Nonecovered by 149.19.2.0/23 | 672 100% |
| 149.19.3.0/24 | No ROA | Nonecovered by 149.19.2.0/23 | 672 100% |
| 149.19.192.0/24 | No ROA | Nonecovered by 149.19.192.0/23 | 672 100% |
| 149.19.193.0/24 | No ROA | Nonecovered by 149.19.192.0/23 | 672 100% |
| 149.19.180.0/24 | No ROA | None | 670 100% |
| 149.19.4.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 149.19.204.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS10250 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 19 are in fix.csv.
- ROA: none7
- Route object: none5
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.19.2.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: none | 149.19.2.0/24 | No route object for it. A route object for 149.19.2.0/23 with origin AS10250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10250 in the RIR database for the space. |
| ROA: none | 149.19.3.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: none | 149.19.3.0/24 | No route object for it. A route object for 149.19.2.0/23 with origin AS10250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10250 in the RIR database for the space. |
| ROA: none | 149.19.192.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: none | 149.19.192.0/24 | No route object for it. A route object for 149.19.192.0/23 with origin AS10250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10250 in the RIR database for the space. |
| ROA: none | 149.19.193.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: none | 149.19.193.0/24 | No route object for it. A route object for 149.19.192.0/23 with origin AS10250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10250 in the RIR database for the space. |
| ROA: none | 149.19.180.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: none | 149.19.180.0/24 | No route object for it. Add a route object with origin AS10250 in the RIR database for the space. |
| ROA: none | 149.19.4.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: RIR | 149.19.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 149.19.204.0/24 | No ROA covers it. Add a ROA for AS10250, maxLength 24. |
| Route object: RIR | 149.19.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10250 whose prefix no peer sees AS10250 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 149.19.2.0/23 | RADB | No ROA |
| 149.19.8.0/24 | RADB | No ROA |
| 149.19.9.0/24 | RADB | No ROA |
| 149.19.125.0/24 | RADB | No ROA |
| 149.19.192.0/23 | 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.