Simon Data had 14 outages in the last 2 years totaling 940h 48m of downtime — averaging 0.6 incidents per month.
There were 14 Simon Data outages since October 16, 2025 totaling 940h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are seeing a drop in the expected volume of incoming events. We are investigating
After further investigation of the anomalous event volume, there appears to be no incident. Following the recent API maintenance the team wanted to be certain that there were not any misconfigurations that went unchecked.
We are actively investigating sporadic 500 level errors that are impacting some users within the web app.
We've identified an issue with the database and are actively working to remediate it. We are seeing signs of recovery.
The issue with the database has been resolved. Replication was behind due to increased load, which caused unexpected behavior loading some pages within the application.
We're seeing errors on our web console and Audience API and are actively investigating.
Services appear to be back to healthy. We're investigating the root cause.
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.
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.
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.
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.
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.
Our Zendesk account issues have been remediated.
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.
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
This incident has been resolved.
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.
This incident has been resolved.
We're aware of sporadic login issues and we're investigating
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring.
This incident has been resolved.
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/
Snowflake continues to make progress here, there are some aspects of data sharing that are now operational.
At this time we are starting to see Snowflake processes recover.
We are investigating an issue with Journeys that may cause service degradation for some users.
Journeys service has been restored and is now operational. We are actively monitoring the service to ensure full recovery.
This incident has been resolved.
We're experiencing an degraded performance impacting Audience API and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
After additional investigation and monitoring from the previous incident, the following services are listed as degraded until the AWS incident is fully resolved.
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.
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.
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.
After our continued monitoring, Simon is considering this issue resolved.
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
We've successfully recovered from the AWS incident.
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.