CapaSystems CapaOne incident

CapaOne is not responding

Notice Resolved View vendor source →

CapaSystems CapaOne experienced a notice incident on June 3, 2026 affecting CapaOne Core and CapaOne Drivers and 1 more component, lasting 4h 21m. The incident has been resolved; the full update timeline is below.

Started
Jun 03, 2026, 08:04 AM UTC
Resolved
Jun 03, 2026, 12:26 PM UTC
Duration
4h 21m
Detected by Pingoru
Jun 03, 2026, 08:04 AM UTC

Affected components

CapaOne CoreCapaOne DriversCapaOne ProvisioningCapaOne PrivilegesCapaOne SecurityCapaOne Apple MDMCapaOne Android MDM

Update timeline

  1. investigating Jun 03, 2026, 08:04 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 03, 2026, 08:05 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 03, 2026, 08:14 AM UTC

    A Cloud provider caused a server nodes restart. Servers seems up again

  4. resolved Jun 03, 2026, 12:26 PM UTC

    This incident has been resolved.