Network · data from 2026-11-12
AS46785 QUASAR-DATA-CENTER - QUASAR DATA CENTER, LTD.
Registry name: QUASAR-DATA-CENTER - QUASAR DATA CENTER, LTD., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46785, 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.
| 198.176.28.0/24 | No ROA | Other origin onlycovered by 198.176.28.0/22 | 673 100% |
| 74.122.120.0/22 | No ROA | RIR databaseALTDB, ARIN | 673 100% |
| 198.176.28.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 199.188.244.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 204.61.220.0/22 | No ROA | RIR databaseALTDB, ARIN | 673 100% |
| 198.64.248.0/22 | Valid | None | 673 100% |
| 204.2.220.0/24 | Valid | None | 673 100% |
AS-SET
AS46785 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 10 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 198.176.28.0/24 | No ROA covers it. Add a ROA for AS46785, maxLength 24. |
| Route object: none | 198.176.28.0/24 | Route objects for it name AS25956. A route object for 198.176.28.0/22 with origin AS46785 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46785 in the RIR database for the space. |
| ROA: none | 74.122.120.0/22 | No ROA covers it. Add a ROA for AS46785, maxLength 22. |
| ROA: none | 198.176.28.0/22 | No ROA covers it. Add a ROA for AS46785, maxLength 22. |
| ROA: none | 199.188.244.0/22 | No ROA covers it. Add a ROA for AS46785, maxLength 22. |
| ROA: none | 204.61.220.0/22 | No ROA covers it. Add a ROA for AS46785, maxLength 22. |
| Route object: none | 198.64.248.0/22 | No route object for it. Add a route object with origin AS46785 in the RIR database for the space. |
| Route object: none | 204.2.220.0/24 | No route object for it. Add a route object with origin AS46785 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46785 whose prefix no peer sees AS46785 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.213.162.0/24 | ALTDB | No ROA |
| 2605:9700::/32 | ARIN | 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.