Amperity had 13 outages in the last 2 years totaling 188h 17m of downtime — averaging 0.5 incidents per month.
There were 13 Amperity outages since September 5, 2025 totaling 188h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
If you feel you are experiencing an issue with your Google Ads, please submit a Support ticket.
A fix has been identified and is currently being tested.
The fix has been successfully tested and implemented. Please contact Support if you have any questions.
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The scheduled maintenance has been completed.
Planned Maintenance - Azure Northern Europe | Tuesday, April 28th This maintenance affects Azure Northern Europe tenants only. All other tenants will not be impacted. Amperity will be performing Azure system maintenance on Tuesday, April 28th, beginning at 1:30 PM PDT. During this window, customers may experience brief, temporary errors within the application. Any impact is expected to last no more than a few minutes. If you encounter errors during this time, manually restarting affected workflow tasks should resolve them.
We're experiencing an Azure outage that may impact some customers. We're working with Azure on the issue and will update shortly
Azure has mitigated the issue and we are monitoring the results
This incident has been resolved.
Some parts of the Amperity platform are experiencing performance issues. We're working on the problem and expect it to be resolved shortly.
This incident has been resolved.
Most parts of the Amperity platform are experiencing issues due to a Klaviyo outage. We are monitoring the situation with them and will update as they make progress
Klaviyo has confirmed the outage to be resolved and Amperity has validated as resolved as well. We will continue to monitor overnight.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Amperity is tracking a Databricks outage that might cause Predictive workflows to fail. We are monitoring the status of resolution on the Databricks side. In the meantime, we are pausing all Predictive tasks and will re-enable them once the Databricks incident is resolved. During this time, the workflows will remain in the Running state, even if all the other tasks succeed. The Databricks incident status can be tracked here: https://status.databricks.com/ If the Databricks incident is resolved within 24 hours, most customers should not see any observable impact to their operations that rely on Predictive inference.
Databricks has confirmed that their incident is resolved. Amperity is unpausing all Predictive tasks and will be restarting the workflows that failed due to this issue.
We have successfully restarted all failed workflows and the incident has been resolved.
Amperity AmpAI is currently experiencing an outage. This may impact AI functionality in Queries, Segments, Journeys, and other areas of the platform that rely on AmpAI. The issue has been identified, and our Platform Engineering team is actively deploying a fix. We will provide further updates as they become available.
We have identified the cause of the AmpAI issue and have implemented a partial fix. Our team is continuing work to fully resolve the problem and expects to have it resolved shortly. We will provide further updates as they become available.
The AmpAI service has been fully restored, and the incident is now resolved.
We're experiencing a partial outage that is impacting the loading of Segments. We're working on the issue and expect to resolve it shortly.
The code change that caused the issue has been reverted and Segments are loading across all tenants now. The incident is now resolved.
Amperity is tracking an issue with Queries in the AWS North America tenants. We're working on the problem.
A fix has been applied and we are now seeing retries succeed. The Amperity Engineering team is retrying the failed queries now.
All the failed tasks have been restarted and every failed workflow has either succeeded or is running past the point of previous failure. The incident is considered resolved.
This morning at 7:00am PST, the Amperity UI stopped loading on all tenants in all stacks, except for AWS US. The issue was quickly identified and resolved by 7:40am PST. The impact was limited to the UI only, so users would not have been able to access the platform, however all backend processes were operational. Amperity is performing an after action review to identify the root cause and preventative measures.
We are currently investigating and also implementing a failover to a working region
We have confirmed that this is an incident at Azure and we are in the process of failing over to a working region
We have successfully failed over to a working region and we are restarting all jobs, but queries may be slow as we work with Azure to resolve.
Azure has resolved their incident and Amperity has failed over back to the fixed cluster and this incident is now resolved.
We are experiencing a partial outage at Meta that is causing some of our API calls to the Replace User endpoint to fail with 500s. We are monitoring Meta and will keep you apprised of any changes. Our tasks will retry until the requests are successful or retries are exhausted. Tasks can be manually restarted as well.
We are seeing some workflows succeeding, but we do not see a 100% recovery yet. We are continuing to monitor the situation.
Our monitoring shows that workflows are still failing. We are continuing to monitor the situation.
Our monitoring shows that the Meta Replace User endpoint is now responding without errors and the workflows are succeeding. We are retrying the workflows that failed yesterday, but were not scheduled to run again today. We will update this notification once all failed workflows are retried.
All failed workflows have been retried, Campaigns and Orchestrations to Meta are now succeeding, and the incident is now closed.