Network · data from 2026-11-12
AS219365 QYRO
Registry name: QYRO Kateryna Maznichenko, UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS219365, 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.
| 2a02:2fc0:2b::/48 | Invalid: origin | Other origin only | 1 0%low visibility |
| 2602:f72e:101::/48 | Valid | RIR databaseARIN | 636 100% |
| 2a0d:d940:80::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a0d:d940:2014::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0f:b240:1a::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS219365: AS219365:AS-QYRO. 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 (AS219365 isn't in the set, or no route object for AS219365 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 | AS219365 in it | Not covered |
|---|---|---|---|---|---|
| AS219365:AS-QYRO | RIPE | 1 | 1 | 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 2 are in fix.csv.
- ROA: origin1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a02:2fc0:2b::/48 | ROAs covering it name AS12586, AS203516, not AS219365. If AS219365 should announce it, add a ROA for AS219365. |
| Route object: none | 2a02:2fc0:2b::/48 | Route objects for it name AS203516. Add a route object with origin AS219365 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS219365 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.