- Detected by Pingoru
- Oct 20, 2026, 08:02 AM UTC
- Resolved
- Oct 20, 2026, 02:14 PM UTC
- Duration
- 6h 12m
Affected: GCP: United Kingdom-London
Timeline · 5 updates
-
identified Oct 20, 2026, 08:02 AM UTC
We have identified the issue affecting new Pods creation for eu-west2 region and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
identified Oct 20, 2026, 09:42 AM UTC
Power has been restored to the affected Vendor Availability Zone. Pega Cloud is operating normally following successful service failover and we continue to closely monitor the environment.
-
identified Oct 20, 2026, 12:41 PM UTC
The issue has been mitigated across all three Vendor Availability Zones. Recovery activities are continuing to fully restore the affected infrastructure and services.
-
monitoring Oct 20, 2026, 02:06 PM UTC
It has been confirmed that the majority of services have been restored. We continue to closely monitor the environment.
-
resolved Oct 20, 2026, 02:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2026, 12:21 AM UTC
- Resolved
- Sep 22, 2026, 12:49 AM UTC
- Duration
- 27m
Affected: AWS: USA - Northern Virginia
Timeline · 2 updates
-
identified Sep 22, 2026, 12:21 AM UTC
We have identified elevated error rates impacting new EC2 instance launches in the Northern Virginia region. Our engineers are actively engaged and working towards recovering. Performance issues may be encountered.
-
resolved Sep 22, 2026, 12:49 AM UTC
Our teams have identified and resolved an issue affecting new EC2 instance launches in the Northern Virginia region. Services are now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 05:11 AM UTC
- Resolved
- Aug 17, 2026, 01:19 PM UTC
- Duration
- 8h 8m
Affected: AWS: Germany - Frankfurt
Timeline · 3 updates
-
investigating Aug 17, 2026, 05:11 AM UTC
We are currently experiencing AWS Direct Connect issue in Europe (Frankfurt) specifically for Equinix service provider that may affect multiple clients. Clients might face issues while login into the environment. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.
-
identified Aug 17, 2026, 06:20 AM UTC
We have identified the issue affecting AWS Direct Connect in Europe (Frankfurt), specifically impacting the Equinix service provider, which may affect multiple clients. Our team is actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved Aug 17, 2026, 01:19 PM UTC
Our teams have identified and partially resolved an issue affecting AWS Direct Connect issue in Europe (Frankfurt) specifically for Equinix service provider. A work around has been provided to minimize business impact.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 12:32 PM UTC
- Resolved
- Jul 27, 2026, 01:38 PM UTC
- Duration
- 1h 5m
Affected: AWS: USA - Northern Virginia
Timeline · 3 updates
-
identified Jul 27, 2026, 12:32 PM UTC
We have identified the issue affecting API failures in US east1 / Northern Virginia intermittently and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
identified Jul 27, 2026, 01:04 PM UTC
We have identified the issue affecting intermittent API failures that may result in latency or failures during restarts or launching new instances in the Northern Virginia region. We are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved Jul 27, 2026, 01:38 PM UTC
Our teams have identified and resolved an issue affecting API connections in the US East 1/Northern Virginia region. API services are now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 12:43 PM UTC
- Resolved
- Jul 24, 2026, 01:08 PM UTC
- Duration
- 24m
Affected: AWS: USA – Oregon
Timeline · 2 updates
-
investigating Jul 24, 2026, 12:43 PM UTC
Our vendor partners have addressed an issue affecting multiple services in the US West (Oregon) region, which may have impacted several clients. We are actively monitoring the environment to ensure stability. We apologize for any inconvenience and appreciate your patience.
-
resolved Jul 24, 2026, 01:08 PM UTC
Our vendor partners have identified and resolved an issue affecting multiple services in the US West (Oregon) region. All services are now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 01:30 PM UTC
- Resolved
- Jul 06, 2026, 04:11 PM UTC
- Duration
- 2h 40m
Affected: AWS: USA - Northern Virginia
Timeline · 4 updates
-
investigating Jul 06, 2026, 01:30 PM UTC
We are currently experiencing an intermittent issue with Cloud service provider in US East 1 that may affect multiple clients. Clients might face service degradation while we work on fixing the issue with the provider . Please refrain from performing any restarts from MPC while we investigate this issue. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.
-
identified Jul 06, 2026, 02:17 PM UTC
We have identified the issue affecting wake-up actions in the AWS-East1 and are actively working to restore service. Please refrain from performing any restarts from MPC while we investigate this issue. We apologize for the inconvenience. Updates will be provided here when available.
-
monitoring Jul 06, 2026, 02:34 PM UTC
We're seeing services begin to recover. We will continue to monitor the issue and report back with a final update shortly. Please refrain from performing any restarts from MPC while we advise that services have completely recovered. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.
-
resolved Jul 06, 2026, 04:11 PM UTC
All services have fully recovered. This incident is now resolved and users may proceed with performing restarts from MPC.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 10:47 AM UTC
- Resolved
- Jul 06, 2026, 12:07 PM UTC
- Duration
- 1h 20m
Affected: AWS: USA - Northern Virginia
Timeline · 3 updates
-
investigating Jul 06, 2026, 10:47 AM UTC
We are currently experiencing an intermittent issue with Cloud service provider in US East 1 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.
-
monitoring Jul 06, 2026, 11:21 AM UTC
The issue has been identified and fixed and we are seeing services begin to recover. We will continue to monitor the issue and report back with a final update shortly.
-
resolved Jul 06, 2026, 12:07 PM UTC
The issue affecting Cloud Services in the US East 1 region have been resolved. Cloud services are stable and and available for all users.
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 12:44 PM UTC
- Resolved
- May 29, 2026, 01:25 PM UTC
- Duration
- 40m
Affected: Pega GenAI BlueprintPega GenAI
Timeline · 4 updates
-
investigating May 29, 2026, 12:44 PM UTC
We are currently experiencing degraded performance issue with GenAI and Blueprint services that is impacting multiple clients globally 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.
-
monitoring May 29, 2026, 01:08 PM UTC
We're seeing services begin to recover. We will continue to monitor the issue and report back with a final update shortly.
-
monitoring May 29, 2026, 01:10 PM UTC
We are continuing to monitor for any further issues.
-
resolved May 29, 2026, 01:25 PM UTC
Our teams have identified and resolved the global issue affecting GenAI and Blueprint utilizing the Azure models. GenAI and Blueprint are now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 01:35 AM UTC
- Resolved
- May 28, 2026, 03:56 AM UTC
- Duration
- 2h 20m
Affected: My Pega
Timeline · 3 updates
-
investigating May 28, 2026, 01:35 AM UTC
We are currently experiencing an outage with MYPega Application Globally 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.
-
identified May 28, 2026, 03:08 AM UTC
We have identified the issue affecting MYPega Application Globally and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved May 28, 2026, 03:56 AM UTC
Our teams have identified and resolved an issue affecting MYPega Application Globally. MYPega Application is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- May 26, 2026, 12:48 PM UTC
- Resolved
- May 26, 2026, 02:59 PM UTC
- Duration
- 2h 10m
Affected: AWS: SingaporeGCP: USA-Northern VirginiaAWS: USA – Northern VirginiaAWS: Australia - SydneyAWS: USA - Northern CaliforniaAWS: Germany - FrankfurtAWS: United Kingdom - LondonPega GenAIAWS: USA - Northern VirginiaAWS: Ireland – DublinAWS: Japan - TokyoAWS: Germany - FrankfurtAWS: USA - OhioAWS: United Kingdom - LondonAWS: India – MumbaiAWS: Australia - SydneyAWS: USA – OregonAWS: France - ParisAWS: Hong KongGCP: USA-Northern VirginiaAWS: Brazil – Sao PaoloAWS: Sweden – StockholmAWS: Indonesia - JakartaGCP: Germany - FrankfurtAWS: Canada – CentralAWS: Italy – MilanAWS: South Korea - SeoulGCP: United Kingdom-LondonAWS: Switzerland - ZurichGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - EemshavenMy Pega CloudMy Pega
Timeline · 7 updates
-
investigating May 26, 2026, 12:48 PM UTC
We are currently experiencing an outage with authentication services impacting multiple PEGA services. The impact is Global and 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.
-
identified May 26, 2026, 01:30 PM UTC
PEGA has identified an issue impacting Authentication Services, this is globally impacting clients' capabilities to access multiple PEGA services (like search). We are actively working to restore service. We apologize for the inconvenience. The next update will be at 9:45 AM ET.
-
identified May 26, 2026, 01:48 PM UTC
PEGA has identified an issue impacting Authentication Services, this is globally impacting clients' capabilities to access multiple PEGA services (like search). PEGA is in the process to recover services. We apologize for the inconvenience. The next update will be at 10:00 AM ET.
-
identified May 26, 2026, 01:59 PM UTC
PEGA has identified an issue impacting Authentication Services, this is globally impacting clients' capabilities to access multiple PEGA services (like search). Services are now recovering and PEGA continues to monitor the recovery process. We apologize for the inconvenience. The next update will be at 10:15 AM ET.
-
identified May 26, 2026, 02:13 PM UTC
PEGA has identified an issue impacting Authentication Services, this is globally impacting clients' capabilities to access multiple PEGA services (like search). Services have been recovered in the NCSA and EMEA regions. PEGA has initiated the recovery process in the APAC region. We apologize for the inconvenience. The next update will be at 10:30 AM ET.
-
monitoring May 26, 2026, 02:31 PM UTC
Services have been fully recovered. PEGA is currently monitoring services. We apologize for the inconvenience. The next update will be at 11:00 AM ET.
-
resolved May 26, 2026, 02:59 PM UTC
Our teams have identified and resolved an issue affecting Authentication Services, having a global impact. Access to all impacted services are now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 06:14 AM UTC
- Resolved
- May 07, 2026, 11:45 AM UTC
- Duration
- 7d 5h
Affected: AWS: Australia - SydneyAWS: United Kingdom - London
Timeline · 10 updates
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 06:43 AM UTC
- Resolved
- Mar 13, 2026, 07:49 AM UTC
- Duration
- 1h 6m
Affected: AWS: USA - Northern Virginia
Timeline · 3 updates
-
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.
-
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.
-
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.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 03:27 PM UTC
- Resolved
- Feb 11, 2026, 05:20 PM UTC
- Duration
- 1h 53m
Affected: Pega GenAI Blueprint
Timeline · 3 updates
-
investigating Feb 11, 2026, 03:27 PM UTC
We are currently experiencing an issue with PEGA Blueprint GenAI is not available for users in all regions except for the United States and Singapore. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.
-
identified Feb 11, 2026, 04:26 PM UTC
We have identified the issue affecting the PEGA Blueprint GenAI issue in the EU, UK, JP, and AUS regions and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved Feb 11, 2026, 05:20 PM UTC
Our teams have identified and resolved an issue affecting PEGA Blueprint GenAI in the AUS, EU, Japan, and UK regions. Blueprint is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 03:15 PM UTC
- Resolved
- Jan 15, 2026, 03:15 PM UTC
- Duration
- –
Affected: My Pega CloudMy Support PortalMy Pega
Timeline · 1 update
-
resolved Jan 15, 2026, 03:15 PM UTC
Our teams have identified and resolved an issue affecting access to "login.pega.com" page. Issue has been remediated and access is available.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 02:21 PM UTC
- Resolved
- Dec 03, 2025, 05:11 PM UTC
- Duration
- 2h 50m
Affected: Pega GenAI BlueprintMy Pega CloudMy Support PortalMy Pega
Timeline · 4 updates
-
investigating Dec 03, 2025, 02:21 PM UTC
We are currently experiencing an intermittent issue with logins to various Pega websites due to a vendor service disruption. We apologize for any inconvenience and appreciate your patience while we work with the vendor to resolve the issue.
-
investigating Dec 03, 2025, 03:12 PM UTC
We continue to experience intermittent issues with logins to various Pega websites due to a vendor service disruption. We apologize for any inconvenience and appreciate your patience while we work with the vendor to resolve the issue.
-
monitoring Dec 03, 2025, 04:32 PM UTC
All Pega website should now be accessible. The vendor is seeing recovery following successful mitigation efforts, and continue to closely monitor system stability.
-
resolved Dec 03, 2025, 05:11 PM UTC
The vendor has confirmed successful resolution, website login issues resolved.
Read the full incident report →
Critical December 3, 2025 - Detected by Pingoru
- Dec 03, 2025, 06:45 AM UTC
- Resolved
- Dec 03, 2025, 10:15 AM UTC
- Duration
- 3h 29m
Affected: Pega GenAI Blueprint
Timeline · 3 updates
-
investigating Dec 03, 2025, 06:45 AM UTC
We are currently experiencing a functional issue around creating blueprint via document, video or any other file type upload, that may affect multiple users. We apologize for any inconvenience and appreciate your patience while we work to resolve the issue.
-
identified Dec 03, 2025, 09:58 AM UTC
We have identified the issue affecting creation of blueprint via document, video or any other file type upload, and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved Dec 03, 2025, 10:15 AM UTC
Our teams have identified and resolved an issue affecting creation of blueprint via document, video or any other file type upload. Blueprint is now fully functional for all the users.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 02:11 PM UTC
- Resolved
- Nov 18, 2025, 05:23 PM UTC
- Duration
- 3h 12m
Affected: AWS: SingaporeGCP: USA-Northern VirginiaAWS: Australia - SydneyAWS: USA - Northern CaliforniaAWS: Germany - FrankfurtAWS: USA - Northern VirginiaAWS: Ireland – DublinAWS: Japan - TokyoAWS: USA - OhioAWS: United Kingdom - LondonAWS: India – MumbaiAWS: USA – OregonAWS: France - ParisAWS: Hong KongAWS: Brazil – Sao PaoloAWS: Sweden – StockholmAWS: Indonesia - JakartaAWS: Canada – CentralAWS: Italy – MilanAWS: South Korea - SeoulAWS: Switzerland - ZurichGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - Eemshaven
Timeline · 3 updates
-
investigating Nov 18, 2025, 02:11 PM UTC
We are currently experiencing intermittent connectivity issues with the following Pega websites: Pega.com Pega.com/Blueprint Academy.pega.com Community.pega.com Launchpad.io Partners.pega.com Docs-previous.pega.com Docs.pega.com Saleshub.pega.com Support.pega.com Accounts.pega.com This 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.
-
monitoring Nov 18, 2025, 02:59 PM UTC
Cloudflare has identified the issue and applied a change that is expected to have restored connectivity. Pega support teams are validating and monitoring access to ensure stability.
-
resolved Nov 18, 2025, 05:23 PM UTC
The issues affecting website connectivity have been identified and resolved. Access is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:50 AM UTC
- Resolved
- Oct 20, 2025, 11:38 PM UTC
- Duration
- 13h 47m
Affected: AWS: USA – Northern VirginiaAWS: USA – Northern Virginia 1AWS: SingaporeGCP: USA-Northern VirginiaAWS: USA – Northern VirginiaAWS: USA – Northern VirginiaAWS: USA – Northern VirginiaAWS: USA – Northern VirginiaPega GenAI BlueprintAWS: Australia - SydneyAWS: USA - Northern CaliforniaAWS: Germany - FrankfurtAWS: Canada – CentralAWS: USA – Northern Virginia 2AWS: United Kingdom - LondonPega GenAIAWS: USA - Northern VirginiaAWS: Ireland – DublinAWS: Japan - TokyoAWS: Ireland – DublinAWS: Germany - FrankfurtAWS: United Kingdom - LondonAWS: USA - OhioAWS: United Kingdom - LondonAWS: USA – Northern VirginiaAWS: Ireland - DublinAWS: India – MumbaiAWS: Australia - SydneyAWS: USA – OregonAWS: France - ParisAWS: Canada – CentralAWS: Hong KongGCP: USA-Northern VirginiaAWS: Brazil – Sao PaoloAWS: Sweden – StockholmAWS: Ireland – DublinAWS: Indonesia - JakartaGCP: Germany - FrankfurtAWS: Canada – CentralAWS: Italy – MilanAWS: South Korea - SeoulGCP: United Kingdom-LondonAWS: Switzerland - ZurichGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - EemshavenMy Pega CloudMy Support PortalMy Pega
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 08:35 AM UTC
- Resolved
- Sep 25, 2025, 12:20 PM UTC
- Duration
- 3h 44m
Affected: AWS: SingaporeGCP: USA-Northern VirginiaAWS: Australia - SydneyAWS: USA - Northern CaliforniaAWS: Germany - FrankfurtAWS: USA - Northern VirginiaAWS: Ireland – DublinAWS: Japan - TokyoAWS: USA - OhioAWS: United Kingdom - LondonAWS: India – MumbaiAWS: USA – OregonAWS: France - ParisAWS: Hong KongAWS: Brazil – Sao PaoloAWS: Sweden – StockholmAWS: Indonesia - JakartaAWS: Canada – CentralAWS: Italy – MilanAWS: South Korea - SeoulAWS: Switzerland - ZurichGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - Eemshaven
Timeline · 2 updates
-
investigating Sep 25, 2025, 08:35 AM UTC
We are currently aware that some clients have encountered intermittent issues with SFTP services, which may also affect others depending on the specific platform or application in use. Our engineering teams are actively investigating the root cause. Mitigation measures have been implemented where feasible, and we are working diligently toward a full resolution. We sincerely apologize for any inconvenience this may cause and appreciate your continued patience and understanding as we address the issue.
-
resolved Sep 25, 2025, 12:20 PM UTC
Our teams have identified and resolved an issue intermittently affecting the SFTP service. SFTP is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2025, 07:02 AM UTC
- Resolved
- Sep 08, 2025, 07:49 AM UTC
- Duration
- 47m
Affected: My Pega Cloud
Timeline · 3 updates
-
investigating Sep 08, 2025, 07:02 AM UTC
We are currently experiencing restart failures in My Pega Cloud 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. If you have a business-critical issue that requires immediate support, please raise an incident with us at msp.pega.com.
-
identified Sep 08, 2025, 07:29 AM UTC
We have identified the issue affecting restart failures in My Pega Cloud and are actively working to restore service. We apologize for the inconvenience. Updates will be provided here when available.
-
resolved Sep 08, 2025, 07:49 AM UTC
Our teams have identified and resolved an issue affecting restart failures in My Pega Cloud. My Pega Cloud's restart functionality is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 03:47 PM UTC
- Resolved
- Aug 04, 2025, 04:32 PM UTC
- Duration
- 45m
Affected: My Pega Cloud
Timeline · 3 updates
-
investigating Aug 04, 2025, 03:47 PM UTC
We are currently investigating a reported issue where Cloud3 clients are receiving error messages when attempting to restart environments.
-
identified Aug 04, 2025, 03:51 PM UTC
We have identified the issue affecting restart capabilities using MPC for Cloud3 environments and are actively working to restore service. We apologize for the inconvenience. Clients can attempt to clear cache and initiate any environment restarts while in Incognito mode. Updates will be provided here when available.
-
resolved Aug 04, 2025, 04:32 PM UTC
Our teams have identified a work around to resolve an issue affecting capabilities to restart Cloud 3 environments utilizing the MPC portal. If you experience an issue initiating a restart of a Cloud 3 environment, please perform one of the following steps: 1. Open a new MPC portal session and clear cache. 2. Initiate the restart process while in incognito mode. 3. Contact PEGA to restart the environment for them (work around).
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2025, 05:40 AM UTC
- Resolved
- Jul 30, 2025, 05:43 AM UTC
- Duration
- 3m
Affected: Pega GenAI
Timeline · 2 updates
-
investigating Jul 30, 2025, 05:40 AM UTC
We are currently experiencing an outage with the Support Buddy and Sales Buddy globally 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.
-
resolved Jul 30, 2025, 05:43 AM UTC
Our teams have identified and resolved an issue affecting Support Buddy and Sales Buddy globally. Support Buddy and Sales Buddy is now stable and available for all users.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2025, 04:07 PM UTC
- Resolved
- Jun 16, 2025, 06:01 PM UTC
- Duration
- 1h 53m
Affected: AWS: SingaporeGCP: USA-Northern VirginiaAWS: Australia - SydneyAWS: USA - Northern CaliforniaAWS: Germany - FrankfurtAWS: USA - Northern VirginiaAWS: Ireland – DublinAWS: Japan - TokyoAWS: USA - OhioAWS: United Kingdom - LondonAWS: India – MumbaiAWS: USA – OregonAWS: France - ParisAWS: Hong KongAWS: Brazil – Sao PaoloAWS: Sweden – StockholmAWS: Indonesia - JakartaAWS: Canada – CentralAWS: Italy – MilanAWS: South Korea - SeoulAWS: Switzerland - ZurichGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - Eemshaven
Timeline · 3 updates
-
investigating Jun 16, 2025, 04:07 PM UTC
PEGA has identified a service impact that may cause issues with the authentication process when attempting to login to PEGA services. Apologies for any inconvenience caused. Future updates will be provided here.
-
identified Jun 16, 2025, 04:09 PM UTC
PEGA has identified the cause of the reported issue. Please open a ticket with PEGA if users are unable to login to PEGA through authentication or SSO methods.
-
resolved Jun 16, 2025, 06:01 PM UTC
Our teams have identified a work around for the identified issue that may affect SSO or Authentication methods. Please open a ticket with PEGA if this issue is being experienced as our assistance will be required to apply the work around.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 08:11 PM UTC
- Resolved
- Jun 13, 2025, 05:08 AM UTC
- Duration
- 8h 56m
Affected: GCP: USA-Northern VirginiaGCP: USA-Northern VirginiaGCP: Germany - FrankfurtGCP: United Kingdom-LondonGCP: USA-OregonGCP: Belgium - St. GhislainGCP: Canada-MontrealGCP: United Kingdom-LondonGCP: Brazil – Sao PaoloGCP: Germany - FrankfurtGCP: Italy - MilanGCP: Netherlands - Eemshaven
Timeline · 2 updates
-
identified Jun 12, 2025, 08:11 PM UTC
Earlier today at approximately 2:00 PM ET, Google advised they experienced a Global outage. All regions except for US-Central have recovered as of 2:41 PM ET. Currently no PEGA services are impacted, however, if you experience any issues related to your PEGA service residing on GCP, please open a ticket through the PEGA.com portal.
-
resolved Jun 13, 2025, 05:08 AM UTC
The issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2025, 07:18 AM UTC
- Resolved
- May 08, 2025, 08:17 AM UTC
- Duration
- 58m
Affected: Pega GenAI Blueprint
Timeline · 2 updates
-
investigating May 08, 2025, 07:18 AM UTC
We are currently experiencing an intermittent issue with Pega GenAI Blueprint 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.
-
resolved May 08, 2025, 08:17 AM UTC
Our teams have identified and resolved an issue affecting Pega GenAI Blueprint. Pega GenAI Blueprint is now stable and available for all users.
Read the full incident report →
