Pegasystems incident

Kafka service is currently unavailable

Critical Resolved View vendor source →

Pegasystems experienced a critical incident on March 13, 2026 affecting AWS: USA - Northern Virginia, lasting 1h 6m. The incident has been resolved; the full update timeline is below.

Started
Mar 13, 2026, 06:43 AM UTC
Resolved
Mar 13, 2026, 07:49 AM UTC
Duration
1h 6m
Detected by Pingoru
Mar 13, 2026, 06:43 AM UTC

Affected components

AWS: USA - Northern Virginia

Update timeline

  1. investigating Mar 13, 2026, 06:43 AM UTC

    We are currently experiencing an issue with Kafka service in US East (N. Virginia) that may affect multiple clients. The impact on your experience may vary based on your platform or application. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.

  2. identified Mar 13, 2026, 07:32 AM UTC

    We have identified the issue affecting Kafka service in US East (N. Virginia) and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.

  3. resolved Mar 13, 2026, 07:49 AM UTC

    Our teams have identified and resolved an issue affecting Kafka service in US East (N. Virginia). Kafka service is now stable and available for all users.