Announced routes
Every prefix a peer of the route collectors sees with origin AS2818, 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.
| 132.185.112.0/20 | No ROA | Nonecovered by 132.185.0.0/16 | 673 100% |
| 132.185.0.0/16 | No ROA | RIR databaseRIPE | 673 100% |
| 132.185.128.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 212.58.224.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:41c1::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:41c2::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:41c0::/32 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS2818: RIPE::AS-BBC. 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 (AS2818 isn't in the set, or no route object for AS2818 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 | AS2818 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-BBC | RIPE | 3 | 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 80 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: not announced72
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 132.185.112.0/20 | No ROA covers it. Add a ROA for AS2818, maxLength 20. |
| Route object: none | 132.185.112.0/20 | No route object for it. A route object for 132.185.0.0/16 with origin AS2818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2818 in the RIR database for the space. |
| ROA: none | 132.185.0.0/16 | No ROA covers it. Add a ROA for AS2818, maxLength 16. |
| ROA: none | 132.185.128.0/20 | No ROA covers it. Add a ROA for AS2818, maxLength 20. |
| ROA: none | 212.58.224.0/19 | No ROA covers it. Add a ROA for AS2818, maxLength 19. |
| ROA: none | 2001:41c1::/32 | No ROA covers it. Add a ROA for AS2818, maxLength 32. |
| ROA: none | 2001:41c2::/32 | No ROA covers it. Add a ROA for AS2818, maxLength 32. |
| ROA: none | 2001:41c0::/32 | No ROA covers it. Add a ROA for AS2818, maxLength 32. |
Route objects not announced
Route objects with origin AS2818 whose prefix no peer sees AS2818 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 132.185.132.0/24 | RIPE | No ROA |
| 132.185.144.0/20 | RIPE | No ROA |
| 132.185.144.0/24 | RIPE | No ROA |
| 132.185.145.0/24 | RIPE | No ROA |
| 132.185.146.0/24 | RIPE | No ROA |
| 132.185.147.0/24 | RIPE | No ROA |
| 132.185.148.0/24 | RIPE | No ROA |
| 132.185.149.0/24 | RIPE | No ROA |
| 132.185.150.0/24 | RIPE | No ROA |
| 132.185.151.0/24 | RIPE | No ROA |
| 132.185.152.0/24 | RIPE | No ROA |
| 132.185.153.0/24 | RIPE | No ROA |
| 132.185.154.0/24 | RIPE | No ROA |
| 132.185.155.0/24 | RIPE | No ROA |
| 132.185.156.0/24 | RIPE | No ROA |
| 132.185.157.0/24 | RIPE | No ROA |
| 132.185.158.0/24 | RIPE | No ROA |
| 132.185.159.0/24 | RIPE | No ROA |
| 132.185.240.0/20 | RIPE | No ROA |
| 132.185.240.0/24 | RIPE | No ROA |
| 132.185.241.0/24 | RIPE | No ROA |
| 132.185.242.0/24 | RIPE | No ROA |
| 132.185.243.0/24 | RIPE | No ROA |
| 132.185.244.0/24 | RIPE | No ROA |
| 132.185.245.0/24 | RIPE | No ROA |
| 132.185.246.0/24 | RIPE | No ROA |
| 132.185.247.0/24 | RIPE | No ROA |
| 132.185.248.0/24 | RIPE | No ROA |
| 132.185.249.0/24 | RIPE | No ROA |
| 132.185.250.0/24 | RIPE | No ROA |
| 132.185.251.0/24 | RIPE | No ROA |
| 132.185.252.0/24 | RIPE | No ROA |
| 132.185.253.0/24 | RIPE | No ROA |
| 132.185.254.0/24 | RIPE | No ROA |
| 132.185.255.0/24 | RIPE | No ROA |
| 212.58.224.0/20 | RIPE | No ROA |
| 212.58.224.0/24 | RIPE | No ROA |
| 212.58.225.0/24 | RIPE | No ROA |
| 212.58.226.0/24 | RIPE | No ROA |
| 212.58.227.0/24 | RIPE | No ROA |
| 212.58.228.0/24 | RIPE | No ROA |
| 212.58.229.0/24 | RIPE | No ROA |
| 212.58.230.0/24 | RIPE | No ROA |
| 212.58.231.0/24 | RIPE | No ROA |
| 212.58.232.0/24 | RIPE | No ROA |
| 212.58.233.0/24 | RIPE | No ROA |
| 212.58.234.0/24 | RIPE | No ROA |
| 212.58.235.0/24 | RIPE | No ROA |
| 212.58.236.0/24 | RIPE | No ROA |
| 212.58.237.0/24 | RIPE | No ROA |
| 212.58.238.0/24 | RIPE | No ROA |
| 212.58.239.0/24 | RIPE | No ROA |
| 212.58.240.0/20 | RIPE | No ROA |
| 212.58.240.0/24 | RIPE | No ROA |
| 212.58.241.0/24 | RIPE | No ROA |
| 212.58.242.0/24 | RIPE | No ROA |
| 212.58.243.0/24 | RIPE | No ROA |
| 212.58.244.0/24 | RIPE | No ROA |
| 212.58.245.0/24 | RIPE | No ROA |
| 212.58.246.0/24 | RIPE | No ROA |
| 212.58.247.0/24 | RIPE | No ROA |
| 212.58.248.0/24 | RIPE | No ROA |
| 212.58.249.0/24 | RIPE | No ROA |
| 212.58.250.0/24 | RIPE | No ROA |
| 212.58.251.0/24 | RIPE | No ROA |
| 212.58.252.0/24 | RIPE | No ROA |
| 212.58.253.0/24 | RIPE | No ROA |
| 212.58.254.0/24 | RIPE | No ROA |
| 212.58.255.0/24 | RIPE | No ROA |
| 2001:41c0::/33 | RIPE | No ROA |
| 2001:41c1:4040::/48 | RIPE | No ROA |
| 2001:41c2::/48 | 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.