Network · data from 2026-11-12
AS28876 suec//dacor GmbH
Registry name: SUEC-DACOR-AS suec // dacor GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28876, 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.
| 2a00:9d80::/33 | Valid | Nonecovered by 2a00:9d80::/32 | 462 73% |
| 2a00:9d80:8000::/33 | Valid | Nonecovered by 2a00:9d80::/32 | 462 73% |
| 2a00:9d81::/33 | Valid | Nonecovered by 2a00:9d81::/32 | 462 73% |
| 2a00:9d81:8000::/33 | Valid | Nonecovered by 2a00:9d81::/32 | 462 73% |
| 5.100.0.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 5.100.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.61.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 81.89.160.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 176.52.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.53.216.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.24.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:9d80::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:9d81::/32 | Valid | RIR databaseRIPE | 636 100% |
| 5.100.0.0/19 | Valid | RIR databaseRIPE | 389 58% |
| 5.100.32.0/19 | Valid | RIR databaseRIPE | 389 58% |
| 81.89.160.0/21 | Valid | RIR databaseRIPE | 389 58% |
| 81.89.168.0/21 | Valid | RIR databaseRIPE | 389 58% |
| 217.24.48.0/21 | Valid | RIR databaseRIPE | 389 58% |
| 217.24.56.0/21 | Valid | RIR databaseRIPE | 389 58% |
AS-SET
PeeringDB's irr_as_set for AS28876: AS-SUEC-DACOR. 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 (AS28876 isn't in the set, or no route object for AS28876 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 | AS28876 in it | Not covered |
|---|---|---|---|---|---|
| AS-SUEC-DACOR | RIPElists itself further down | 30 | 14 | 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 7 are in fix.csv.
- Route object: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a00:9d80::/33 | No route object for it. A route object for 2a00:9d80::/32 with origin AS28876 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28876 in the RIR database for the space. |
| Route object: none | 2a00:9d80:8000::/33 | No route object for it. A route object for 2a00:9d80::/32 with origin AS28876 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28876 in the RIR database for the space. |
| Route object: none | 2a00:9d81::/33 | No route object for it. A route object for 2a00:9d81::/32 with origin AS28876 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28876 in the RIR database for the space. |
| Route object: none | 2a00:9d81:8000::/33 | No route object for it. A route object for 2a00:9d81::/32 with origin AS28876 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28876 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28876 whose prefix no peer sees AS28876 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.100.32.0/20 | RIPE | Invalid: maxLength |
| 176.52.192.0/22 | RIPE | Invalid: maxLength |
| 2a00:9d80::/29 | 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.