Network · data from 2026-11-12
AS50009 QUARTZ TELECOM
Registry name: QUARTZ-AS QUARTZ TELECOM LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50009, 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.
| 2a05:7e83::/32 | No ROA | Nonecovered by 2a05:7e80::/29 | 635 100% |
| 194.35.46.0/23 | No ROA | Other origin only | 10 1%low visibility |
| 109.94.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 176.109.32.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.80.248.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a05:7e80::/29 | No ROA | RIR databaseRIPE | 634 100% |
| 109.94.0.0/20 | No ROA | RIR databaseRIPE | 92 14% |
| 109.94.16.0/20 | No ROA | RIR databaseRIPE | 92 14% |
| 176.109.32.0/21 | No ROA | RIR databaseRIPE | 92 14% |
| 176.109.40.0/21 | No ROA | RIR databaseRIPE | 92 14% |
| 185.80.248.0/23 | No ROA | RIR databaseRIPE | 92 14% |
| 185.80.250.0/23 | No ROA | RIR databaseRIPE | 92 14% |
| 46.249.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 46.249.16.0/21 | Valid | RIR databaseRIPE | 92 14% |
| 46.249.24.0/21 | Valid | RIR databaseRIPE | 92 14% |
AS-SET
PeeringDB's irr_as_set for AS50009: AS-QUARTZ. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS50009 isn't in the set, or no route object for AS50009 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS50009 in it | Not covered |
|---|---|---|---|---|---|
| AS-QUARTZ | RIPE | 5 | 2 | Yes | 1 |
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 14 are in fix.csv.
- ROA: none12
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a05:7e83::/32 | No ROA covers it. Add a ROA for AS50009, maxLength 32. |
| Route object: none | 2a05:7e83::/32 | No route object for it. A route object for 2a05:7e80::/29 with origin AS50009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50009 in the RIR database for the space. |
| ROA: none | 194.35.46.0/23 | No ROA covers it. Add a ROA for AS50009, maxLength 23. |
| Route object: none | 194.35.46.0/23 | Route objects for it name AS197826. Add a route object with origin AS50009 in the RIR database for the space. |
| ROA: none | 109.94.0.0/19 | No ROA covers it. Add a ROA for AS50009, maxLength 19. |
| ROA: none | 176.109.32.0/20 | No ROA covers it. Add a ROA for AS50009, maxLength 20. |
| ROA: none | 185.80.248.0/22 | No ROA covers it. Add a ROA for AS50009, maxLength 22. |
| ROA: none | 2a05:7e80::/29 | No ROA covers it. Add a ROA for AS50009, maxLength 29. |
| ROA: none | 109.94.0.0/20 | No ROA covers it. Add a ROA for AS50009, maxLength 20. |
| ROA: none | 109.94.16.0/20 | No ROA covers it. Add a ROA for AS50009, maxLength 20. |
| ROA: none | 176.109.32.0/21 | No ROA covers it. Add a ROA for AS50009, maxLength 21. |
| ROA: none | 176.109.40.0/21 | No ROA covers it. Add a ROA for AS50009, maxLength 21. |
| ROA: none | 185.80.248.0/23 | No ROA covers it. Add a ROA for AS50009, maxLength 23. |
| ROA: none | 185.80.250.0/23 | No ROA covers it. Add a ROA for AS50009, maxLength 23. |
Route objects not announced
Every route object with origin AS50009 is announced.
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.