Prodly Outage History

Prodly is up right now

Prodly had 5 outages in the last 2 years totaling 9h 10m of downtime — averaging 0.2 incidents per month.

There were 5 Prodly outages since August 19, 2025 totaling 9h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.prodly.co

Notice July 8, 2026

An interruption in the Prodly AppOps service has occurred.

Detected by Pingoru
Jul 08, 2026, 05:10 PM UTC
Resolved
Jul 08, 2026, 05:16 PM UTC
Duration
5m
Affected: AppOps
Timeline · 3 updates
  1. investigating Jul 08, 2026, 05:10 PM UTC

    An interruption in the Prodly AppOps service has occurred. Users may have trouble accessing the AppOps Release Tab. We are actively investigating the issue and will provide further updates.

  2. investigating Jul 08, 2026, 05:15 PM UTC

    This incident has been resolved and services are back to normal. We will continue to monitor in case of any reoccurrence.

  3. resolved Jul 08, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 21, 2026

Intermittent Connectivity Issues with Salesforce

Detected by Pingoru
May 21, 2026, 09:31 PM UTC
Resolved
May 22, 2026, 03:38 AM UTC
Duration
6h 6m
Affected: AppOps DeploymentAppOpsMetadataMonitor
Timeline · 3 updates
  1. identified May 21, 2026, 09:31 PM UTC

    Salesforce is reporting a performance degradation affecting its core services which seems to be impacting connectivity between Salesforce and Prodly services. User may experience intermittent errors accessing Prodly or performing deployments. We are monitoring https://status.salesforce.com/incidents/20004037 for updates.

  2. monitoring May 21, 2026, 10:58 PM UTC

    We are no longer seeing connectivity errors in our application logs but are continuing to monitor the Salesforce incident.

  3. resolved May 22, 2026, 03:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

Peformance Degradation - Next Gen Deployments

Detected by Pingoru
Mar 02, 2026, 04:49 PM UTC
Resolved
Feb 27, 2026, 09:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 02, 2026, 04:49 PM UTC

    AWS reported an issue with hardware degradation on one of our EC2 instances. As a result, deployments using the Next Gen deployment service may appear stuck or timing out.

Read the full incident report →

Major February 26, 2026

Prodly AppOps Service Outage

Detected by Pingoru
Feb 26, 2026, 10:27 PM UTC
Resolved
Feb 26, 2026, 11:10 PM UTC
Duration
43m
Affected: AppOps DeploymentAppOpsMetadataVersion ControlMonitorAWS ec2-us-east-2
Timeline · 3 updates
  1. investigating Feb 26, 2026, 10:27 PM UTC

    Prodly is currently experiencing a service outage within AWS. We are actively investigating the problem and will provide updates here.

  2. monitoring Feb 26, 2026, 10:40 PM UTC

    We have identified that the issue is related to and outage within AWS Systems Manager which appears to be resolved now. Functionality should be returned to normal, however we are monitoring the service.

  3. resolved Feb 26, 2026, 11:10 PM UTC

    This incident has been resolved and services are back to normal. We will continue to monitor in case of any reoccurrence.

Read the full incident report →

Minor December 22, 2025

Partial Service Outage - Degraded Performance

Detected by Pingoru
Dec 22, 2025, 02:06 PM UTC
Resolved
Dec 22, 2025, 04:21 PM UTC
Duration
2h 15m
Affected: AppOps DeploymentAppOpsMetadata
Timeline · 3 updates
  1. investigating Dec 22, 2025, 02:06 PM UTC

    We are currently experiencing a partial outage which may impact some users. Our engineering team is investigating the issue and working on a fix. Impact: Data and Metadata Deployments may be triggered but not appear in Deployment History. In that case you will see the usual pop up that your deployment was submitted, but the deployment will not go through. We recommend retrying the deployment in that case. We will provide updates here as soon as more information is available. Thank you for your patience.

  2. monitoring Dec 22, 2025, 02:38 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 22, 2025, 04:21 PM UTC

    This incident has been resolved.

Read the full incident report →