Announced routes
Every prefix a peer of the route collectors sees with origin AS3213, 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:86c0::/29 | No ROA | Other origin only | 634 100% |
| 193.16.2.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.16.42.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.16.106.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.16.110.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.162.12.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 85.158.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 91.103.128.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.126.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.248.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.172.120.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.178.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2001:4b10::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS3213: RIPE::AS-BOGONS. 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 (AS3213 isn't in the set, or no route object for AS3213 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 | AS3213 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-BOGONS | RIPE | 15 | 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 9 are in fix.csv.
- ROA: none6
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a06:86c0::/29 | No ROA covers it. Add a ROA for AS3213, maxLength 29. |
| Route object: none | 2a06:86c0::/29 | Route objects for it name AS47685. Add a route object with origin AS3213 in the RIR database for the space. |
| ROA: none | 193.16.2.0/24 | No ROA covers it. Add a ROA for AS3213, maxLength 24. |
| ROA: none | 193.16.42.0/24 | No ROA covers it. Add a ROA for AS3213, maxLength 24. |
| ROA: none | 193.16.106.0/24 | No ROA covers it. Add a ROA for AS3213, maxLength 24. |
| ROA: none | 193.16.110.0/24 | No ROA covers it. Add a ROA for AS3213, maxLength 24. |
| ROA: none | 195.162.12.0/23 | No ROA covers it. Add a ROA for AS3213, maxLength 23. |
Route objects not announced
Route objects with origin AS3213 whose prefix no peer sees AS3213 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 132.185.128.0/20 | RIPE | No ROA |
| 193.228.141.0/24 | RIPE | No ROA |
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.