Pegasystems incident

Cloud 2 clients experiencing slow response.

Pegasystems experienced a minor incident on October 16, 2024 affecting AWS: USA - Northern California and AWS: USA - Northern Virginia and 1 more component, lasting 8h 1m. The incident has been resolved; the full update timeline is below.

Started: Oct 16, 2024, 04:15 PM UTC
Resolved: Oct 17, 2024, 12:17 AM UTC
Duration: 8h 1m
Detected by Pingoru: Oct 16, 2024, 04:15 PM UTC

Affected components

AWS: USA - Northern CaliforniaAWS: USA - Northern VirginiaAWS: USA - OhioAWS: USA – OregonAWS: Brazil – Sao PaoloAWS: Canada – Central

Update timeline

investigating Oct 16, 2024, 04:15 PM UTC

We are currently investigating an issue within PEGA Cloud 2. Some clients may experience slowness resulting in PEGA application performance issues during this time. We apologize for the inconvenience. Updates will be provided here.
identified Oct 16, 2024, 05:14 PM UTC

We are currently identified the cause of an issue within PEGA Cloud 2. PEGA teams are developing next steps to address this issue. Updates will be provided here.
identified Oct 16, 2024, 05:19 PM UTC

We are currently identified the cause of an issue within PEGA Cloud 2. PEGA teams are developing next steps to address this issue. Updates will be provided here.
identified Oct 16, 2024, 05:20 PM UTC

We are currently identified the cause of an issue within PEGA Cloud 2. PEGA teams are developing next steps to address this issue. Updates will be provided here.
identified Oct 16, 2024, 06:42 PM UTC

We are currently working on a solution to resolve the reported issue within PEGA Cloud 2. Updates will be provided here
identified Oct 16, 2024, 08:42 PM UTC

We have identified the issue and are actively working on a solution to resolve the reported issue within PEGA Cloud 2. Updates will be provided here.
resolved Oct 17, 2024, 01:27 AM UTC

Our teams have identified and resolved the issues affecting Cloud 2 clients. All formerly impacted services are now available.