Announced routes
Every prefix a peer of the route collectors sees with origin AS56786, 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.
| 142.249.224.0/22 | No ROA | RIR databaseARIN | 673 100% |
| 84.21.179.0/24 | Valid | Nonecovered by 84.21.176.0/22 | 673 100% |
| 84.21.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.229.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.250.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0d:f540::/29 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS56786: AS56786:AS-NEXIM. 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 (AS56786 isn't in the set, or no route object for AS56786 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 | AS56786 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS56786:AS-NEXIM | In no IRR database read today. | |||||
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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- AS-SET: not found1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 142.249.224.0/22 | No ROA covers it. Add a ROA for AS56786, maxLength 22. |
| Route object: none | 84.21.179.0/24 | No route object for it. A route object for 84.21.176.0/22 with origin AS56786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56786 in the RIR database for the space. |
| AS-SET: not found | AS56786:AS-NEXIM | PeeringDB names AS56786:AS-NEXIM; no IRR database read has it. |
Route objects not announced
Route objects with origin AS56786 whose prefix no peer sees AS56786 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.21.176.0/24 | RIPE | Valid |
| 84.21.177.0/24 | 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.