Announced routes
Every prefix a peer of the route collectors sees with origin AS197068, 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.
| 2a03:70c1:27d6::/48 | Valid | Nonecovered by 2a03:70c1::/32 | 634 100% |
| 193.23.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.43.79.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.43.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.43.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.43.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.43.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.152.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:70c1:610::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:754::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:17bc::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:3bf6::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:9693::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:b8ec::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:da11::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a03:70c1:dcc2::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS197068: RIPE::AS197068:AS-SET. 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 (AS197068 isn't in the set, or no route object for AS197068 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 | AS197068 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS197068:AS-SET | RIPElists itself further down7 member sets in no database: AS-DURABLE, AS-GLOBALNET02, AS-INITQ, AS-SERVERSCOM, AS-WZ-ASIA … | 505 | 63 | Yes | 0 |
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 16 are in fix.csv.
- Route object: none1
- AS-SET: missing member7
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a03:70c1:27d6::/48 | No route object for it. A route object for 2a03:70c1::/32 with origin AS197068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197068 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-DURABLE; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-GLOBALNET02; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-INITQ; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-SERVERSCOM; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-WZ-ASIA; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS-WZ-EU; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS197068:AS-SET | AS197068:AS-SET (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it. |
Route objects not announced
Route objects with origin AS197068 whose prefix no peer sees AS197068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.116.91.0/24 | RADB | No ROA |
| 45.152.115.0/24 | RIPE | Valid |
| 92.241.165.0/24 | RADB, RIPE | No ROA |
| 185.226.149.0/24 | RIPE | No ROA |
| 185.226.150.0/24 | RIPE | No ROA |
| 195.43.92.0/23 | RIPE | Valid |
| 2a03:70c1::/32 | RIPE | Valid |
| 2a03:70c1:8698::/48 | RIPE | Valid |
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.