Announced routes
Every prefix a peer of the route collectors sees with origin AS51681, 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.
| 185.191.8.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.191.9.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.191.10.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.191.11.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.251.188.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.251.189.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.251.190.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 178.239.208.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 185.105.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.105.17.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 185.105.18.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 185.105.19.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS51681: AS51681. 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 (AS51681 isn't in the set, or no route object for AS51681 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 | AS51681 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS51681 | A single AS number, not a set: AS51681 (this network), 12 route objects. | |||||
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 7 are in fix.csv.
- ROA: none7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.191.8.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.191.9.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.191.10.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.191.11.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.251.188.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.251.189.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
| ROA: none | 185.251.190.0/24 | No ROA covers it. Add a ROA for AS51681, maxLength 24. |
Route objects not announced
Every route object with origin AS51681 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.