Network · data from 2026-11-12
AS16080 Dalenys
Registry name: Dalenys Payplug Enterprise SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16080, 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.
| 80.70.222.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2a02:d48:bb::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS16080: AS-DALENYS. 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 (AS16080 isn't in the set, or no route object for AS16080 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 | AS16080 in it | Not covered |
|---|---|---|---|---|---|
| AS-DALENYS | RIPE | 6 | 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 1 are in fix.csv.
- Route object: not announced1
Route objects not announced
Route objects with origin AS16080 whose prefix no peer sees AS16080 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.89.122.0/24 | RIPE | Invalid: origin |
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.