Simon Data Outage History

Simon Data is up right now

Simon Data had 12 outages in the last 2 years totaling 937h 57m of downtime — averaging 0.5 incidents per month.

There were 12 Simon Data outages since October 16, 2025 totaling 937h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simondata.com

Minor June 2, 2026

Web Console and Audience API services degraded

Detected by Pingoru
Jun 02, 2026, 04:17 PM UTC
Resolved
Jun 02, 2026, 05:09 PM UTC
Duration
52m
Affected: Simon Web AppSimon Audience API
Timeline · 3 updates
  1. investigating Jun 02, 2026, 04:17 PM UTC

    We're seeing errors on our web console and Audience API and are actively investigating.

  2. monitoring Jun 02, 2026, 04:31 PM UTC

    Services appear to be back to healthy. We're investigating the root cause.

  3. resolved Jun 02, 2026, 05:09 PM UTC

    There was a network hiccup from all of our services to our application database. All of our services momentarily lost connectivity during the outage. Restarting services restored connectivity.

Read the full incident report →

Notice May 22, 2026

Intermittent Issues Affecting Support Ticket Submission

Detected by Pingoru
May 22, 2026, 05:55 PM UTC
Resolved
May 30, 2026, 12:08 AM UTC
Duration
7d 6h
Affected: Simon Web App
Timeline · 5 updates
  1. investigating May 22, 2026, 05:55 PM UTC

    We are investigating an issue affecting the ability to submit and interact with support tickets through the Simon Web App. Customers can continue to respond to existing open tickets via email while we work to resolve the issue. We will provide further updates as more information becomes available.

  2. monitoring May 26, 2026, 02:48 PM UTC

    Following some difficulties rolling over to a new Zendesk contract, we are now able to submit and edit tickets in Support Center. We are actively monitoring the issue for any other outstanding failure points.

  3. identified May 27, 2026, 04:38 PM UTC

    The issue with our authentication into Zendesk has regressed. We are actively working with Zendesk support and our internal team to implement a fix for it.

  4. identified May 27, 2026, 08:17 PM UTC

    We are still experiencing an API issue affecting our Support Center. During this time, ticket submissions through the Simon UI are unavailable. Our team is actively investigating and working to restore full functionality as quickly as possible. We apologize for the inconvenience. What to do in the meantime: - Submit new tickets via email Send your support request directly to [email protected]. Your ticket will be created automatically. - Reply to existing tickets via email Please reply directly to the email thread for your ticket rather than responding within the Simon UI. This ensures your message is received by our team.

  5. resolved May 30, 2026, 12:08 AM UTC

    Our Zendesk account issues have been remediated.

Read the full incident report →

Major May 8, 2026

AWS Redshift Outage

Detected by Pingoru
May 08, 2026, 01:00 PM UTC
Resolved
May 08, 2026, 08:52 PM UTC
Duration
7h 52m
Affected: Simon Web AppJourneysSimon Data PipesSimon Data Syncs
Timeline · 3 updates
  1. monitoring May 08, 2026, 07:14 PM UTC

    We are tracking a service event at AWS in us-east-1 that is impacting Amazon Redshift availability. Some customers may see delayed or failing data refreshes. AWS has resolved the incident and we are working towards recovery.

  2. monitoring May 08, 2026, 07:30 PM UTC

    AWS has resolved the upstream Redshift issue, and we are observing recovery across affected workloads. Queue depth is decreasing and queries are completing, though some processing may remain slower than normal as the backlog clears. A subset of customers may have seen delays in data refreshes, syncs, journeys, and parts of the Simon Web App during the impact window; some customers were not affected. We are continuing to monitor for full stability and will post another update once recovery is complete. AWS status: https://health.aws.com/health/status

  3. resolved May 08, 2026, 08:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2026

AWS Access Issue

Detected by Pingoru
Feb 26, 2026, 06:05 PM UTC
Resolved
Feb 26, 2026, 09:09 PM UTC
Duration
3h 4m
Affected: Simon Data Pipes
Timeline · 2 updates
  1. monitoring Feb 26, 2026, 06:05 PM UTC

    Data pipelines experienced an unexpected delay due to an AWS access issue. This has since been resolved and we are actively ensuring pipelines finish as quickly as possible.

  2. resolved Feb 26, 2026, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2026

Sporadic login issues

Detected by Pingoru
Feb 19, 2026, 06:27 PM UTC
Resolved
Feb 19, 2026, 10:04 PM UTC
Duration
3h 36m
Affected: Simon Web App
Timeline · 4 updates
  1. investigating Feb 19, 2026, 06:27 PM UTC

    We're aware of sporadic login issues and we're investigating

  2. investigating Feb 19, 2026, 06:27 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 19, 2026, 07:09 PM UTC

    A fix has been implemented and we are monitoring.

  4. resolved Feb 19, 2026, 10:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 16, 2025

Snowflake Data Cloud - Degraded Service

Detected by Pingoru
Dec 16, 2025, 12:45 PM UTC
Resolved
Dec 16, 2025, 02:23 PM UTC
Duration
1h 38m
Affected: Simon Web App
Timeline · 3 updates
  1. monitoring Dec 16, 2025, 12:45 PM UTC

    Customers utilizing Snowflake services in the following regions are experiencing service disruption: Regions Impacted: AWS - US West (Oregon) AWS - Europe (Ireland) AWS - Asia Pacific (Mumbai) Users are unable to execute queries against Snowflake databases, tables, and views. Error message presented: "SQL execution internal error" or similar messages. Snowflake has identified the root cause and is actively developing a fix -- https://status.snowflake.com/

  2. monitoring Dec 16, 2025, 02:11 PM UTC

    Snowflake continues to make progress here, there are some aspects of data sharing that are now operational.

  3. resolved Dec 16, 2025, 02:23 PM UTC

    At this time we are starting to see Snowflake processes recover.

Read the full incident report →

Minor December 2, 2025

Journey Service Degradation

Detected by Pingoru
Dec 02, 2025, 10:49 PM UTC
Resolved
Dec 02, 2025, 10:50 PM UTC
Duration
1m
Affected: Journeys
Timeline · 3 updates
  1. investigating Dec 02, 2025, 10:39 PM UTC

    We are investigating an issue with Journeys that may cause service degradation for some users.

  2. monitoring Dec 02, 2025, 10:49 PM UTC

    Journeys service has been restored and is now operational. We are actively monitoring the service to ensure full recovery.

  3. resolved Dec 03, 2025, 01:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 12, 2025

Audience API performance degraded

Detected by Pingoru
Nov 12, 2025, 11:25 PM UTC
Resolved
Nov 14, 2025, 09:46 PM UTC
Duration
1d 22h
Affected: Simon Audience API
Timeline · 3 updates
  1. investigating Nov 12, 2025, 11:25 PM UTC

    We're experiencing an degraded performance impacting Audience API and are currently looking into the issue.

  2. monitoring Nov 13, 2025, 03:06 AM UTC

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

  3. resolved Nov 14, 2025, 09:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Third Party Outage: AWS - Ongoing

Detected by Pingoru
Oct 20, 2025, 01:32 PM UTC
Resolved
Oct 21, 2025, 07:48 PM UTC
Duration
1d 6h
Affected: Simon Web AppJourneysSimon Event Trigger FlowsSimon Data PipesSimon Data Syncs
Timeline · 5 updates
  1. identified Oct 20, 2025, 01:32 PM UTC

    After additional investigation and monitoring from the previous incident, the following services are listed as degraded until the AWS incident is fully resolved.

  2. identified Oct 20, 2025, 09:07 PM UTC

    Some AWS services are beginning to recover from today's incident, but AWS Redshift continues to experience issues, which impacts Simon AI's segmentation and customer filtering features. We expect these issues to continue for several hours.

  3. identified Oct 21, 2025, 02:36 AM UTC

    Simon continues to monitor the AWS recovery progress. At this time, the AWS Redshift cluster recovery is still outstanding with AWS engineers. Services continue to remain impacted.

  4. monitoring Oct 21, 2025, 05:26 AM UTC

    All services are up and back to operational. AWS has resolved the last of the Redshift issues that have been impacting us. Our batch processing is continuing as scheduling and the team is monitoring progress.

  5. resolved Oct 21, 2025, 07:48 PM UTC

    After our continued monitoring, Simon is considering this issue resolved.

Read the full incident report →

Minor October 20, 2025

Third Party Outage: AWS

Detected by Pingoru
Oct 20, 2025, 10:00 AM UTC
Resolved
Oct 20, 2025, 10:26 AM UTC
Duration
25m
Affected: JourneysSimon Event Trigger FlowsSimon Data PipesSimon Data Syncs
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 10:00 AM UTC

    AWS had an outage that impacted a number of services that we rely on, including our ability to update our Status Page in a timely manner. The only impacted region was us-east-1. Journeys, Syncs, and Pipes have delayed processing that we are actively recovering from. Incoming events were delayed. More information on the outage. https://health.aws.amazon.com/health/status

  2. resolved Oct 20, 2025, 10:26 AM UTC

    We've successfully recovered from the AWS incident.

Read the full incident report →

Notice October 16, 2025

Audience API issue

Detected by Pingoru
Oct 16, 2025, 01:03 PM UTC
Resolved
Oct 16, 2025, 08:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 16, 2025, 01:03 PM UTC

    This morning (Time frame: 3:55 am-4:26 am ET), Simon AI experienced an internal Elasticsearch issue that caused Audience API requests to fail. The issue has been fixed and we are continuing to monitor the health of the Audience API.

Read the full incident report →