Network · data from 2026-11-12
AS198219 Charlie Camilleri
Registry name: CHARLIE-AS Charlie Camilleri, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198219, 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.
| 44.31.225.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a0e:97c0:abd::/48 | Valid | None | 636 100% |
| 2a0e:97c0:ab0::/45 | Valid | RIR databaseRADB, RIPE | 636 100% |
| 2a0e:97c0:abb::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a0e:97c0:abc::/48 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS198219: RS-CHARLIE-AS. 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 (AS198219 isn't in the set, or no route object for AS198219 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 | AS198219 in it | Not covered | |
|---|---|---|---|---|---|---|
| RS-CHARLIE-AS | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.31.225.0/24 | No ROA covers it. Add a ROA for AS198219, maxLength 24. |
| Route object: RIR | 44.31.225.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2a0e:97c0:abd::/48 | No route object for it. Add a route object with origin AS198219 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198219 whose prefix no peer sees AS198219 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.95.186.0/24 | RIPE | Valid |
| 109.95.187.0/24 | RIPE | Valid |
| 2a0e:97c0:ab0::/48 | RIPE | Valid |
| 2a0e:97c0:ab1::/48 | 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.