Network · data from 2026-11-12
AS48971 DATAWIRE AG
Registry name: DATAWIRE-AS DATAWIRE AG, CH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48971, 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.
| 203.56.178.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 94.231.80.0/21 | Valid | Nonecovered by 94.231.80.0/20 | 673 100% |
| 94.231.94.0/24 | Valid | Nonecovered by 94.231.80.0/20 | 394 59% |
| 94.231.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 94.231.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.19.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.2.228.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.225.116.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:41c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS48971: AS-DATAWIRE. 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 (AS48971 isn't in the set, or no route object for AS48971 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 | AS48971 in it | Not covered |
|---|---|---|---|---|---|
| AS-DATAWIRE | RIPE2 member sets in no database: AS-TYRASUKI, AS-ZUGERNET:AS-CUSTOMERS | 12 | 2 | 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 11 are in fix.csv.
- ROA: none1
- Route object: none2
- AS-SET: missing member2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.56.178.0/24 | No ROA covers it. Add a ROA for AS48971, maxLength 24. |
| Route object: none | 94.231.80.0/21 | No route object for it. A route object for 94.231.80.0/20 with origin AS48971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48971 in the RIR database for the space. |
| Route object: none | 94.231.94.0/24 | No route object for it. A route object for 94.231.80.0/20 with origin AS48971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48971 in the RIR database for the space. |
| AS-SET: missing member | AS-DATAWIRE | AS-DATAWIRE (RIPE) lists AS-TYRASUKI; no IRR database read has it. |
| AS-SET: missing member | AS-DATAWIRE | AS-DATAWIRE (RIPE) lists AS-ZUGERNET:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS48971 whose prefix no peer sees AS48971 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.231.95.0/24 | RIPE | Valid |
| 136.144.36.0/23 | RIPE | No ROA |
| 136.144.36.0/24 | RIPE | No ROA |
| 136.144.37.0/24 | RIPE | No ROA |
| 2001:470:15f::/48 | ARIN | Valid |
| 2a00:41c0::/32 | 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.