Announced routes
Every prefix a peer of the route collectors sees with origin AS25048, 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.
| 81.90.143.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2a00:e20:150::/48 | Valid | Other IRR onlyRADB | 636 100% |
| 2a00:e20:154::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 81.90.132.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 81.90.133.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.90.135.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.90.139.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 2a00:e20::/32 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a00:e21::/32 | Valid | RIR databaseRADB, RIPE | 634 100% |
| 2a00:e26::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS25048: AS-DSNET. 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 (AS25048 isn't in the set, or no route object for AS25048 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 | AS25048 in it | Not covered |
|---|---|---|---|---|---|
| AS-DSNET | 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 8 are in fix.csv.
- Route object: RIR3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 81.90.143.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a00:e20:150::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2a00:e20:154::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25048 whose prefix no peer sees AS25048 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.90.128.0/20 | RIPE | Valid |
| 81.90.128.0/22 | RIPE | Valid |
| 81.90.136.0/23 | RIPE | Valid |
| 81.90.140.0/22 | RIPE | Valid |
| 2a00:e20::/29 | 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.