Announced routes
Every prefix a peer of the route collectors sees with origin AS206874, 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.
| 109.74.82.0/24 | Valid | Nonecovered by 109.74.82.0/23 | 673 100% |
| 109.74.83.0/24 | Valid | Nonecovered by 109.74.82.0/23 | 673 100% |
| 185.164.124.0/24 | Valid | Nonecovered by 185.164.124.0/22 | 673 100% |
| 185.164.125.0/24 | Valid | Nonecovered by 185.164.124.0/22 | 673 100% |
| 185.164.126.0/24 | Valid | Nonecovered by 185.164.124.0/22 | 673 100% |
| 185.164.127.0/24 | Valid | Nonecovered by 185.164.124.0/22 | 673 100% |
| 109.74.82.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.164.124.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS206874: RIPE::RS-KYXAR. 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 (AS206874 isn't in the set, or no route object for AS206874 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 | AS206874 in it | Not covered | |
|---|---|---|---|---|---|---|
| RIPE::RS-KYXAR | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 6 are in fix.csv.
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.74.82.0/24 | No route object for it. A route object for 109.74.82.0/23 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
| Route object: none | 109.74.83.0/24 | No route object for it. A route object for 109.74.82.0/23 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
| Route object: none | 185.164.124.0/24 | No route object for it. A route object for 185.164.124.0/22 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
| Route object: none | 185.164.125.0/24 | No route object for it. A route object for 185.164.124.0/22 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
| Route object: none | 185.164.126.0/24 | No route object for it. A route object for 185.164.124.0/22 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
| Route object: none | 185.164.127.0/24 | No route object for it. A route object for 185.164.124.0/22 with origin AS206874 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206874 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS206874 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.