Network · data from 2026-11-12
AS39889 DCS Networks - Nordic
Registry name: DCS-Networks-AS Fredrik Holmqvist, SE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39889, 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.
| 193.234.15.0/24 | No ROA | Other origin only | 673 100% |
| 195.189.182.0/23 | No ROA | Other origin only | 672 100% |
| 193.234.32.0/21 | No ROA | Other origin only | 671 100% |
| 2a00:1c20::/32 | Valid | Other origin only | 636 100% |
| 193.104.214.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS39889: AS-I2B. 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 (AS39889 isn't in the set, or no route object for AS39889 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 | AS39889 in it | Not covered |
|---|---|---|---|---|---|
| AS-I2B | RIPE1 member set in no database: AS199746:AS-NEXTSERV | 230 | 67 | Yes | 4 |
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 10 are in fix.csv.
- ROA: none3
- Route object: none4
- AS-SET: missing member1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.234.15.0/24 | No ROA covers it. Add a ROA for AS39889, maxLength 24. |
| Route object: none | 193.234.15.0/24 | Route objects for it name AS50989. Add a route object with origin AS39889 in the RIR database for the space. |
| ROA: none | 195.189.182.0/23 | No ROA covers it. Add a ROA for AS39889, maxLength 23. |
| Route object: none | 195.189.182.0/23 | Route objects for it name AS50989. Add a route object with origin AS39889 in the RIR database for the space. |
| ROA: none | 193.234.32.0/21 | No ROA covers it. Add a ROA for AS39889, maxLength 21. |
| Route object: none | 193.234.32.0/21 | Route objects for it name AS50989. Add a route object with origin AS39889 in the RIR database for the space. |
| Route object: none | 2a00:1c20::/32 | Route objects for it name AS50989. Add a route object with origin AS39889 in the RIR database for the space. |
| AS-SET: missing member | AS-I2B | AS-I2B (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
Route objects not announced
Route objects with origin AS39889 whose prefix no peer sees AS39889 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.189.24.0/23 | RIPE | No ROA |
| 195.189.26.0/23 | RIPE | No ROA |
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.