Network · data from 2026-11-12
AS26969 Ace Data Centers DCH
Registry name: ACE-002 - Ace Data Centers II, L.L.C., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS26969, 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.
| 177.1.188.0/23 | Invalid: origin | None | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS26969: ARIN::AS-ACEDC. 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 (AS26969 isn't in the set, or no route object for AS26969 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 | AS26969 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-ACEDC | ARIN1 member set in no database: AS219143:AS-ACEDC | 10 | 1 | Yes | 1 |
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 9 are in fix.csv.
- ROA: origin1
- Route object: none1
- AS-SET: missing member1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 177.1.188.0/23 | ROAs covering it name AS213520, not AS26969. If AS26969 should announce it, add a ROA for AS26969. |
| Route object: none | 177.1.188.0/23 | No route object for it. Add a route object with origin AS26969 in the RIR database for the space. |
| AS-SET: missing member | ARIN::AS-ACEDC | AS-ACEDC (ARIN) lists AS219143:AS-ACEDC; no IRR database read has it. |
Route objects not announced
Route objects with origin AS26969 whose prefix no peer sees AS26969 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.26.208.0/21 | RIPE | Valid |
| 69.27.160.0/20 | ARIN | Valid |
| 166.0.234.0/24 | ARIN | Valid |
| 199.58.196.0/22 | ARIN | Valid |
| 2604:3140::/32 | ARIN | Valid |
| 2604:ba00::/32 | ARIN | 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.