Network · data from 2026-11-12
AS25154 Currency One
Registry name: CurrencyOneSA Currency One S.A., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25154, 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.
| 212.91.18.0/24 | Valid | None | 2 0%low visibility |
| 212.91.19.0/24 | Valid | None | 2 0%low visibility |
| 5.252.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.252.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS25154: AS25154. 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 (AS25154 isn't in the set, or no route object for AS25154 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 | AS25154 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS25154 | A single AS number, not a set: AS25154 (this network), 2 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 2 are in fix.csv.
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 212.91.18.0/24 | No route object for it. Add a route object with origin AS25154 in the RIR database for the space. |
| Route object: none | 212.91.19.0/24 | No route object for it. Add a route object with origin AS25154 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS25154 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.