Network · data from 2026-11-12
AS20681 Saxo Bank
Registry name: SaxoBank Saxo Bank A/S, DK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20681, 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.
| 46.19.248.0/24 | Valid | Nonecovered by 46.19.248.0/21 | 671 100% |
| 46.19.251.0/24 | Valid | Nonecovered by 46.19.248.0/21 | 671 100% |
| 46.19.252.0/24 | Valid | Nonecovered by 46.19.248.0/21 | 671 100% |
| 46.19.254.0/24 | Valid | Nonecovered by 46.19.248.0/21 | 671 100% |
| 46.19.248.0/21 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.16.140.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 193.178.175.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 193.219.31.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 2a01:8300::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS20681: AS-SAXOBANK. 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 (AS20681 isn't in the set, or no route object for AS20681 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 | AS20681 in it | Not covered |
|---|---|---|---|---|---|
| AS-SAXOBANK | 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 4 are in fix.csv.
- Route object: none4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 46.19.248.0/24 | No route object for it. A route object for 46.19.248.0/21 with origin AS20681 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20681 in the RIR database for the space. |
| Route object: none | 46.19.251.0/24 | No route object for it. A route object for 46.19.248.0/21 with origin AS20681 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20681 in the RIR database for the space. |
| Route object: none | 46.19.252.0/24 | No route object for it. A route object for 46.19.248.0/21 with origin AS20681 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20681 in the RIR database for the space. |
| Route object: none | 46.19.254.0/24 | No route object for it. A route object for 46.19.248.0/21 with origin AS20681 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20681 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS20681 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.