Amperity Outage History

Amperity is up right now

Amperity had 12 outages in the last 2 years totaling 97h 9m of downtime — averaging 0.5 incidents per month.

There were 12 Amperity outages since September 5, 2025 totaling 97h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.amperity.com

Major July 30, 2026

[Scheduled] Planned Maintenance - Azure Northern Europe

Detected by Pingoru
Jul 30, 2026, 10:13 PM UTC
Resolved
Apr 28, 2026, 08:40 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Jul 30, 2026, 10:13 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  2. resolved Jul 30, 2026, 10:13 PM UTC

    The scheduled maintenance has been completed.

  3. investigating Jul 30, 2026, 10:13 PM UTC

    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.

Read the full incident report →

Notice May 12, 2026

Azure is currently experiencing an outage which is affecting some of our customers

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
  1. 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

  2. monitoring May 12, 2026, 04:18 PM UTC

    Azure has mitigated the issue and we are monitoring the results

  3. resolved May 13, 2026, 04:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026

Amperity is experiencing performance issues

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
  1. 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.

  2. resolved May 09, 2026, 03:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 5, 2026

Amperity is experiencing an incident due to a Klaviyo outage

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
  1. 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

  2. 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 →

Notice April 5, 2026

Amperity is experiencing an outage to all services on our Azure platform

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
  1. investigating Apr 05, 2026, 07:11 PM UTC

    We are currently investigating this issue.

  2. identified Apr 05, 2026, 07:32 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 05, 2026, 08:30 PM UTC

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

  4. resolved Apr 06, 2026, 12:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 30, 2026

Amperity is experiencing failing Predictive workflows due to a Databricks outage

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
  1. 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.

  2. 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.

  3. 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 →

Major March 12, 2026

Amperity AmpAI Outage

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
  1. 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.

  2. 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.

  3. 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 →

Minor March 12, 2026

Amperity is experiencing a partial outage impacting the loading of Segments

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
  1. 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.

  2. 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 →

Minor February 2, 2026

Amperity is experiencing performance issues with Queries

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
  1. 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.

  2. 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.

  3. 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 →

Minor January 26, 2026

Amperity experienced an outage

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
  1. 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

Amperity is experiencing an incident with Azure

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
  1. investigating Sep 10, 2025, 03:00 PM UTC

    We are currently investigating and also implementing a failover to a working region

  2. 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

  3. 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.

  4. 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 →

Minor September 5, 2025

Amperity is experiencing a partial outage with Campaigns and Orchestrations sending to Meta's Replace User endpoint

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
  1. 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.

  2. 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.

  3. monitoring Sep 06, 2025, 02:54 AM UTC

    Our monitoring shows that workflows are still failing. We are continuing to monitor the situation.

  4. 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.

  5. 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 →