Announced routes
Every prefix a peer of the route collectors sees with origin AS51795, 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.
| 46.18.241.0/24 | Valid | Nonecovered by 46.18.240.0/23 | 672 100% |
| 46.18.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.18.240.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.18.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.25.39.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.18.243.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.18.244.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.18.247.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS51795: AS-TV1. 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 (AS51795 isn't in the set, or no route object for AS51795 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 | AS51795 in it | Not covered |
|---|---|---|---|---|---|
| AS-TV1 | 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 11 are in fix.csv.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 46.18.241.0/24 | No route object for it. A route object for 46.18.240.0/23 with origin AS51795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51795 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51795 whose prefix no peer sees AS51795 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.18.244.0/23 | RIPE | Invalid: maxLength |
| 46.18.245.0/24 | RIPE | Valid |
| 46.18.246.0/24 | RIPE | Valid |
| 185.25.36.0/24 | RIPE | Valid |
| 185.25.37.0/24 | RIPE | Valid |
| 185.25.38.0/24 | RIPE | Valid |
| 2a02:e800::/29 | RIPE | No ROA |
| 2a02:e800::/36 | RIPE | No ROA |
| 2a02:e800:1000::/36 | RIPE | No ROA |
| 2a02:e800:2000::/36 | 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.