Announced routes
Every prefix a peer of the route collectors sees with origin AS8302, 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.
| 2a06:1b00:101::/48 | Valid | Nonecovered by 2a06:1b00::/32 | 635 100% |
| 91.123.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a06:1b00::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:97::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:99::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:100::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:103::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:106::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a06:1b00:107::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS8302: RIPE::AS-ZATTOO. 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 (AS8302 isn't in the set, or no route object for AS8302 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 | AS8302 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ZATTOO | RIPE | 1 | 1 | 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 13 are in fix.csv.
- Route object: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a06:1b00:101::/48 | No route object for it. A route object for 2a06:1b00::/32 with origin AS8302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8302 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8302 whose prefix no peer sees AS8302 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.123.96.0/24 | RIPE | Invalid: maxLength |
| 91.123.98.0/24 | RIPE | Invalid: maxLength |
| 91.123.100.0/22 | RIPE | Invalid: maxLength |
| 91.123.102.0/24 | RIPE | Invalid: maxLength |
| 91.123.105.0/24 | RIPE | Invalid: maxLength |
| 91.123.108.0/23 | RIPE | Invalid: maxLength |
| 91.123.110.0/24 | RIPE | Invalid: maxLength |
| 91.123.111.0/24 | RIPE | Invalid: maxLength |
| 185.112.8.0/24 | RADB, RIPE | No ROA |
| 2a06:1b00::/29 | RIPE | No ROA |
| 2a06:1b00:98::/48 | RIPE | Invalid: maxLength |
| 2a06:1b00:105::/48 | RIPE | Invalid: maxLength |
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.