- Detected by Pingoru
- May 12, 2026, 01:34 PM UTC
- Resolved
- May 13, 2026, 04:12 PM UTC
- Duration
- 1d 2h
Affected: WebsiteSourcesAzure PlatformSegmentsDestinationsWorkflows
Timeline · 3 updates
-
investigating May 12, 2026, 01:34 PM UTC
We're experiencing an Azure outage that may impact some customers. We're working with Azure on the issue and will update shortly
-
monitoring May 12, 2026, 04:18 PM UTC
Azure has mitigated the issue and we are monitoring the results
-
resolved May 13, 2026, 04:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 05:55 PM UTC
- Resolved
- May 09, 2026, 03:45 PM UTC
- Duration
- 21h 49m
Affected: WebsiteSourcesAzure PlatformSegmentsDestinations
Timeline · 2 updates
-
investigating May 08, 2026, 05:55 PM UTC
Some parts of the Amperity platform are experiencing performance issues. We're working on the problem and expect it to be resolved shortly.
-
resolved May 09, 2026, 03:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 09:57 PM UTC
- Resolved
- May 06, 2026, 03:00 AM UTC
- Duration
- 5h 2m
Affected: SourcesSegmentsDestinations
Timeline · 2 updates
-
investigating May 05, 2026, 09:57 PM UTC
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
-
resolved May 06, 2026, 03:00 AM UTC
Klaviyo has confirmed the outage to be resolved and Amperity has validated as resolved as well. We will continue to monitor overnight.
Read the full incident report →
- Detected by Pingoru
- Apr 05, 2026, 07:11 PM UTC
- Resolved
- Apr 06, 2026, 12:00 AM UTC
- Duration
- 4h 48m
Affected: Azure Platform
Timeline · 4 updates
-
investigating Apr 05, 2026, 07:11 PM UTC
We are currently investigating this issue.
-
identified Apr 05, 2026, 07:32 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 05, 2026, 08:30 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 06, 2026, 12:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 10:34 PM UTC
- Resolved
- Mar 31, 2026, 02:50 AM UTC
- Duration
- 4h 15m
Affected: Workflows
Timeline · 3 updates
-
monitoring Mar 30, 2026, 10:34 PM UTC
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.
-
monitoring Mar 30, 2026, 11:29 PM UTC
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.
-
resolved Mar 31, 2026, 02:50 AM UTC
We have successfully restarted all failed workflows and the incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 11:36 PM UTC
- Resolved
- Mar 13, 2026, 12:45 AM UTC
- Duration
- 1h 9m
Affected: AWS PlatformAzure Platform
Timeline · 3 updates
-
investigating Mar 12, 2026, 11:36 PM UTC
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.
-
identified Mar 13, 2026, 12:29 AM UTC
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.
-
resolved Mar 13, 2026, 12:45 AM UTC
The AmpAI service has been fully restored, and the incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 07:47 PM UTC
- Resolved
- Mar 12, 2026, 07:59 PM UTC
- Duration
- 11m
Affected: Segments
Timeline · 2 updates
-
identified Mar 12, 2026, 07:47 PM UTC
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.
-
resolved Mar 12, 2026, 07:59 PM UTC
The code change that caused the issue has been reverted and Segments are loading across all tenants now. The incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 06:52 PM UTC
- Resolved
- Feb 02, 2026, 08:27 PM UTC
- Duration
- 1h 34m
Affected: AWS PlatformCustomer 360Segments
Timeline · 3 updates
-
investigating Feb 02, 2026, 06:52 PM UTC
Amperity is tracking an issue with Queries in the AWS North America tenants. We're working on the problem.
-
monitoring Feb 02, 2026, 08:07 PM UTC
A fix has been applied and we are now seeing retries succeed. The Amperity Engineering team is retrying the failed queries now.
-
resolved Feb 02, 2026, 08:27 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 26, 2026, 04:09 PM UTC
- Resolved
- Jan 26, 2026, 04:09 PM UTC
- Duration
- —
Affected: WebsiteAWS PlatformAzure Platform
Timeline · 1 update
-
resolved Jan 26, 2026, 04:09 PM UTC
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.
Read the full incident report →
Notice September 10, 2025 - Detected by Pingoru
- Sep 10, 2025, 03:00 PM UTC
- Resolved
- Sep 10, 2025, 08:31 PM UTC
- Duration
- 5h 30m
Affected: Azure Platform
Timeline · 4 updates
-
investigating Sep 10, 2025, 03:00 PM UTC
We are currently investigating and also implementing a failover to a working region
-
identified Sep 10, 2025, 03:44 PM UTC
We have confirmed that this is an incident at Azure and we are in the process of failing over to a working region
-
monitoring Sep 10, 2025, 05:11 PM UTC
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.
-
resolved Sep 10, 2025, 08:31 PM UTC
Azure has resolved their incident and Amperity has failed over back to the fixed cluster and this incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 05, 2025, 03:38 PM UTC
- Resolved
- Sep 06, 2025, 05:47 PM UTC
- Duration
- 1d 2h
Affected: Destinations
Timeline · 5 updates
-
monitoring Sep 05, 2025, 03:38 PM UTC
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.
-
monitoring Sep 05, 2025, 06:57 PM UTC
We are seeing some workflows succeeding, but we do not see a 100% recovery yet. We are continuing to monitor the situation.
-
monitoring Sep 06, 2025, 02:54 AM UTC
Our monitoring shows that workflows are still failing. We are continuing to monitor the situation.
-
monitoring Sep 06, 2025, 03:58 PM UTC
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.
-
resolved Sep 06, 2025, 05:47 PM UTC
All failed workflows have been retried, Campaigns and Orchestrations to Meta are now succeeding, and the incident is now closed.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2025, 04:57 PM UTC
- Resolved
- Jun 13, 2025, 08:31 PM UTC
- Duration
- 3h 33m
Affected: AWS PlatformSegmentsWorkflows
Timeline · 3 updates
-
investigating Jun 13, 2025, 04:57 PM UTC
The query service of the Amperity platform in AWS are experiencing performance issues. We're working on the problem and expect it to be resolved shortly.
-
monitoring Jun 13, 2025, 05:42 PM UTC
The issue is due to performance issues in the underlying AWS platform. AWS has identified the problem and are on the path to recovery. Amperity is continuing to monitor the AWS resolution actions.
-
resolved Jun 13, 2025, 08:31 PM UTC
AWS has confirmed that the issue is resolved. Amperity monitored and restarted all the failed workflows and has confirmed that this incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 09:47 PM UTC
- Resolved
- Jun 13, 2025, 01:34 AM UTC
- Duration
- 3h 47m
Affected: WebsiteAWS PlatformAzure Platform
Timeline · 3 updates
-
investigating Jun 12, 2025, 09:47 PM UTC
Many parts of the Amperity platform are currently experiencing an outage. We’re working to fix the problem as quickly as we can. We’ll share another update shortly.
-
monitoring Jun 12, 2025, 10:02 PM UTC
We have implemented a fix and monitoring the results.
-
resolved Jun 13, 2025, 01:34 AM UTC
Amperity has confirmed that the incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2025, 06:06 PM UTC
- Resolved
- Jun 06, 2025, 06:06 PM UTC
- Duration
- —
Affected: AWS PlatformAzure Platform
Timeline · 1 update
-
resolved Jun 06, 2025, 06:06 PM UTC
Between 4:30 PM PT on June 5th and 10:30 AM PT on June 6th, the Amperity AI assistant was unavailable. This issue has now been resolved. We’re taking steps to improve our monitoring and recovery processes to prevent future disruptions. Thank you for your patience, and please don’t hesitate to contact our Support team if you have any questions.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2025, 03:28 PM UTC
- Resolved
- Apr 03, 2025, 05:10 PM UTC
- Duration
- 1h 41m
Affected: AWS PlatformDestinationsWorkflows
Timeline · 3 updates
-
monitoring Apr 03, 2025, 03:28 PM UTC
Amperity has identified an issue with tik-tok campaign executions in AWS. The issue was identified as having started 20 hours ago, and the cause has been fixed. We are monitoring and restarting any failed workflows. No action is required from our customers at this time.
-
monitoring Apr 03, 2025, 05:10 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 03, 2025, 05:10 PM UTC
All failed workflows have been retried and the incident is now closed.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2025, 05:45 PM UTC
- Resolved
- Jan 12, 2025, 08:34 PM UTC
- Duration
- 2h 48m
Affected: WebsiteSourcesAzure PlatformStitchCustomer 360SegmentsDestinationsWorkflows
Timeline · 3 updates
-
investigating Jan 12, 2025, 05:45 PM UTC
We're experiencing an issue with scheduling Orchestration jobs which may impact our customers on Azure. We're working on the issue and expect to resolve it shortly.
-
monitoring Jan 12, 2025, 06:03 PM UTC
A fix has been implemented to recover orchestration scheduling and we are monitoring the results.
-
resolved Jan 12, 2025, 08:34 PM UTC
We’re back! Amperity should be up and running normally. Thanks for bearing with us.
Read the full incident report →
- Detected by Pingoru
- Nov 02, 2024, 02:09 AM UTC
- Resolved
- Nov 02, 2024, 03:17 AM UTC
- Duration
- 1h 8m
Affected: Workflows
Timeline · 3 updates
-
identified Nov 02, 2024, 02:09 AM UTC
We're experiencing an outage that may impact Workflow processing for some customers. We have identified the potential cause and are working on resolving the issue.
-
monitoring Nov 02, 2024, 02:28 AM UTC
We have deployed a hotfix and are monitoring.
-
resolved Nov 02, 2024, 03:17 AM UTC
Our monitoring shows that all the Workflows that were stuck have completed successfully, Workflows started after the fix was deployed are also running to completion and the system is healthy.
Read the full incident report →
Notice September 10, 2024 - Detected by Pingoru
- Sep 10, 2024, 12:07 AM UTC
- Resolved
- Sep 10, 2024, 03:03 AM UTC
- Duration
- 2h 56m
Affected: SourcesAzure PlatformStitchCustomer 360
Timeline · 2 updates
-
investigating Sep 10, 2024, 12:07 AM UTC
Some parts of the Amperity platform are experiencing performance issues due to an Azure incident. Amperity is working with Azure to resolve the incident and will provide updates shortly.
-
resolved Sep 10, 2024, 03:03 AM UTC
This incident has been resolved. We apologize for the inconvenience. If there are any issues or questions please reach out to Amperity Support and we will follow up.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2024, 09:58 PM UTC
- Resolved
- Sep 03, 2024, 11:14 PM UTC
- Duration
- 1h 15m
Affected: SourcesAzure PlatformSegmentsWorkflows
Timeline · 3 updates
-
identified Sep 03, 2024, 09:58 PM UTC
The performance of some internal Amperity services degraded, and as a result some application features are unavailable on our Azure platform, including workflow management, source configuration, in-app notifications, and queries. Our Platform Engineering teams have identified the services impacted, and are working to restore those services along with any impacted workflows. We will update this incident as we work to restore all features of the Amperity application.
-
monitoring Sep 03, 2024, 10:13 PM UTC
The affected services have been recovered and the application functionality has been restored. We are monitoring for further interruption. If your workflows were impacted, those will be restarted.
-
resolved Sep 03, 2024, 11:14 PM UTC
The application functionality has been fully restored and all failed workflows have been restarted. We apologize for the inconvenience and if you encounter any issues, please submit a Support ticket.
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2024, 10:09 AM UTC
- Resolved
- Aug 29, 2024, 10:36 AM UTC
- Duration
- 26m
Affected: AWS Platform
Timeline · 3 updates
-
investigating Aug 29, 2024, 10:09 AM UTC
Most parts of the Amperity platform are experiencing an outage. We’re working with AWS to fix the problem as quickly as we can. We’ll share another update shortly.
-
monitoring Aug 29, 2024, 10:27 AM UTC
AWS has identified the issue and has applied a resolution and we will continue to monitor.
-
resolved Aug 29, 2024, 10:36 AM UTC
AWS has resolved the incident and all Amperity services are fully functional. We apologize for the inconvenience and if you encounter any issues, please submit a Support ticket.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2024, 04:51 PM UTC
- Resolved
- Jul 30, 2024, 09:33 PM UTC
- Duration
- 4h 41m
Affected: Azure PlatformCustomer 360Workflows
Timeline · 3 updates
-
investigating Jul 30, 2024, 04:51 PM UTC
We are currently experiencing a degraded state of operations due to a global networking outage at Azure. In response to this outage, we have transitioned to our failover data center and are observing favorable progress. Our team is actively monitoring the actions Azure is taking to resolve this issue. We are also monitoring our customers' workflows and taking appropriate actions to resolve any failures. We understand the impact this may have on your business, and we sincerely apologize for any inconvenience caused. We appreciate your patience and understanding during this time. If you have any further questions or concerns, please don't hesitate to reach out to our support team, who will be happy to assist you.
-
monitoring Jul 30, 2024, 04:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 30, 2024, 09:33 PM UTC
We’re back! Amperity should be up and running normally. Thanks for bearing with us.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2024, 02:13 PM UTC
- Resolved
- Jul 19, 2024, 02:13 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 19, 2024, 02:13 PM UTC
We are aware of a Microsoft outage affecting Windows PC. Please be assured that Amperity is not affected, but we are monitoring the situation and will update as necessary.
Read the full incident report →
