bgpreport

Network · data from 2026-11-12

AS26519 Ace Data Centers DCH-2

Registry name: ACE-002 - Ace Data Centers II, L.L.C., US · PeeringDB

1IPv4 routes 100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS26519, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26519, 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.

2.26.210.0/24 Valid Nonecovered by 2.26.208.0/21 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS26519: 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 (AS26519 isn't in the set, or no route object for AS26519 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.

NameDatabaseASNsSets Route objectsAS26519 in itNot covered
ARIN::AS-ACEDC ARIN1 member set in no database: AS219143:AS-ACEDC 1011,140 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 8 are in fix.csv.

  • Route object: none1
  • AS-SET: missing member1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none2.26.210.0/24No route object for it. A route object for 2.26.208.0/21 with origin AS26519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26519 in the RIR database for the space.673 of 673
AS-SET: missing memberARIN::AS-ACEDCAS-ACEDC (ARIN) lists AS219143:AS-ACEDC; no IRR database read has it.

Route objects not announced

Route objects with origin AS26519 whose prefix no peer sees AS26519 announce. Many are kept on purpose (backup routes, space announced only in some places).

2.26.208.0/21RIPEValid
69.27.160.0/20ARINValid
166.0.234.0/24ARINValid
199.58.196.0/22ARINValid
2604:3140::/32ARINValid
2604:ba00::/32ARINValid

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.