Simon Data Outage History

Simon Data is up right now

Pingoru has recorded 51 incidents for Simon Data: 13 in the last 12 months and 2 in the last 90 days.

Source: status.simondata.com

51incidents recorded
13last 12 months
2last 90 days
3 daystypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Simon Data in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202628 of 744 (1%)
June 202611 of 720 (0%)
July 202622 of 744 (0%)
August 202613 of 744 (0%)
September 202600 of 720 (0%)
October 202612 of 744 (0%)
November 202600 of 19 (0%)

Incidents, newest first

Minor October 21, 2026 Snowflake EU-West- 1 2h 5m Journeys, Simon Data Syncs

Started Oct 21, 2026, 08:45 PM UTC· resolved Oct 21, 2026, 10:51 PM UTC

  1. investigating Oct 21, 2026, 08:45 PM UTC

    There is a current Snowflake outage impacting the EU-West- 1 only

  2. investigating Oct 21, 2026, 08:57 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 21, 2026, 09:52 PM UTC

    Simon is working through recovery as Snowflake progresses through their recovery.

  4. resolved Oct 21, 2026, 10:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2026 Simon Pipe Refreshes and Journey Syncs 3h 14m Journeys, Simon Data Pipes

Started Aug 21, 2026, 05:07 PM UTC· resolved Aug 21, 2026, 08:21 PM UTC

  1. identified Aug 21, 2026, 05:07 PM UTC

    We are currently recovering from an issue that has impacted pipe refresh completions and journey syncs

  2. resolved Aug 21, 2026, 08:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 30, 2026 Incoming Event Volume Degraded 1h 12m Simon Event Trigger Flows

Started Jul 30, 2026, 07:08 PM UTC· resolved Jul 30, 2026, 08:21 PM UTC

  1. investigating Jul 30, 2026, 07:08 PM UTC

    We are seeing a drop in the expected volume of incoming events. We are investigating

  2. resolved Jul 30, 2026, 08:21 PM UTC

    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.

Read the full incident report →

Minor July 13, 2026 Sporadic 500s in the Web App 1h 38m Simon Web App

Started Jul 13, 2026, 01:55 PM UTC· resolved Jul 13, 2026, 03:34 PM UTC

  1. investigating Jul 13, 2026, 01:55 PM UTC

    We are actively investigating sporadic 500 level errors that are impacting some users within the web app.

  2. identified Jul 13, 2026, 02:50 PM UTC

    We've identified an issue with the database and are actively working to remediate it. We are seeing signs of recovery.

  3. resolved Jul 13, 2026, 03:34 PM UTC

    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.

Read the full incident report →

Minor June 2, 2026 Web Console and Audience API services degraded 52m Simon Web App, Simon Audience API

Started Jun 02, 2026, 04:17 PM UTC· resolved Jun 02, 2026, 05:09 PM UTC

  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 7d 6h Simon Web App

Started May 22, 2026, 05:55 PM UTC· resolved May 30, 2026, 12:08 AM UTC

  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 7h 52m Simon Web App, Journeys, Simon Data Pipes, Simon Data Syncs

Started May 08, 2026, 01:00 PM UTC· resolved May 08, 2026, 08:52 PM UTC

  1. monitoring May 08, 2026, 01:00 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 3h 4m Simon Data Pipes

Started Feb 26, 2026, 06:05 PM UTC· resolved Feb 26, 2026, 09:09 PM UTC

  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 3h 36m Simon Web App

Started Feb 19, 2026, 06:27 PM UTC· resolved Feb 19, 2026, 10:04 PM UTC

  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 1h 38m Simon Web App

Started Dec 16, 2025, 12:45 PM UTC· resolved Dec 16, 2025, 02:23 PM UTC

  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 10m Journeys

Started Dec 02, 2025, 10:39 PM UTC· resolved Dec 02, 2025, 10:50 PM UTC

  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 02, 2025, 10:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 24, 2025 Monitoring Meta 27d 21h Simon Data Syncs

Started Nov 24, 2025, 08:28 PM UTC· resolved Dec 22, 2025, 06:04 PM UTC

  1. investigating Nov 24, 2025, 08:28 PM UTC

    Simon submitted Facebook (Meta) required integration updates weeks ago and is continuing to wait for confirmation that our app is completely updated. Due to this pending confirmation, Simon is at risk of losing and/or having downgraded performance with Facebook. Facebook has not given a specific date on when this would happen. While we continue to escalate this with Facebook, it is important to prepare should there be connection issues this week or through the weekend. To prepare for this impact, Simon is suggesting the following: 1. Create a segment export in Simon, adding the correct custom context fields needed (example: fn, ln, etc.) 2. Upload the list manually to Facebook - https://www.facebook.com/business/help/170456843145568?id=2469097953376494 https://www.facebook.com/business/help/2082575038703844?id=2469097953376494 3. For existing peak campaigns that include branches and/or variants to Facebook, we ask that you isolate all Facebook-related campaigns to their own individual flow/journey. This will help ensure Facebook integration issues do not impact any Email, SMS, Push, or other paid media syncs. To help you monitor our Facebook connection, we'll be providing updates through our status page to effectively communicate if and when Facebook shuts off our integration, at the moment it will show Facebook as operational. Simon leadership will continue to keep our team updated and will continue to escalate with Meta until this is resolved.

  2. investigating Nov 25, 2025, 03:34 AM UTC

    Simon has lost access to the Facebook Marketing API, despite escalation from Simon leadership. The impact is that flows/journeys with Facebook actions are in an error state and cannot proceed until the connection has been restored. See the previous message for the workaround for time sensitive custom audiences. Otherwise, Simon will continue to push to restore access to the marketing API and resume normal syncing operations.

  3. investigating Nov 26, 2025, 01:15 AM UTC

    Simon has provisioned a new authentication app and set it to live, but we are blocked awaiting approvals. Our attempts to escalate this have been unsuccessful. We have also exhausted several other workarounds to try to put the previous app back into good standing. We will continue to closely monitor this and attempt to expedite, but we cannot guarantee any remediation timeline. We advise you to continue to utilize manual segment exports used until resolved.

  4. investigating Nov 27, 2025, 01:26 PM UTC

    Simon is continuing to wait for approvals from Facebook in order to reset the connection to Facebook. Simon has provisioned a new authentication app and set it to live, but we are blocked awaiting approvals. Our attempts to escalate this have been unsuccessful, though we will continue to do so. We have also exhausted several other workarounds to try to put the previous app back into good standing. We still advise the same manual upload process to Facebook. We will continue to closely monitor this throughout the Holiday weekend.

  5. investigating Dec 01, 2025, 09:43 PM UTC

    Simon remains dependent on Facebook approvals to reestablish the connection. While a new authentication app has been provisioned and set to live status, we are currently blocked awaiting the necessary approvals. Despite ongoing escalation efforts, we have not yet achieved a resolution. Additionally, we have explored and exhausted multiple workarounds aimed at restoring the previous app to good standing. At this time, we continue to recommend proceeding with the manual upload process to Facebook.

  6. investigating Dec 05, 2025, 08:34 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  7. investigating Dec 09, 2025, 09:46 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  8. investigating Dec 10, 2025, 05:54 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  9. investigating Dec 11, 2025, 05:22 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  10. investigating Dec 12, 2025, 05:37 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  11. investigating Dec 17, 2025, 05:41 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  12. investigating Dec 21, 2025, 02:48 PM UTC

    Despite continued escalations and attempted workarounds to restore the app's connection, we continue to be in the same state. We recommend you continue with the manual upload workflow.

  13. resolved Dec 22, 2025, 06:04 PM UTC

    Excited to announce that the Meta incident has been resolved. As a next step you must reauthenticate your Meta account to Simon. Including a Loom video below to walk through the process to re-auth your account in Simon https://www.loom.com/share/7af86a95cdf14d2c8a48553d08918166 Once this is done, please open up a Support Ticket in your Simon account so that we can resume your Meta syncs.

Read the full incident report →

Minor November 12, 2025 Audience API performance degraded 1d 22h Simon Audience API

Started Nov 12, 2025, 11:25 PM UTC· resolved Nov 14, 2025, 09:46 PM UTC

  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 1d 6h Simon Web App, Journeys, Simon Event Trigger Flows, Simon Data Pipes and 1 more

Started Oct 20, 2025, 01:32 PM UTC· resolved Oct 21, 2025, 07:48 PM UTC

  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 25m Journeys, Simon Event Trigger Flows, Simon Data Pipes, Simon Data Syncs

Started Oct 20, 2025, 10:00 AM UTC· resolved Oct 20, 2025, 10:26 AM UTC

  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 31m

Started Oct 16, 2025, 07:55 AM UTC· resolved Oct 16, 2025, 08:26 AM UTC

  1. resolved Oct 16, 2025, 08:30 AM 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 →

Major March 30, 2025 System outage 1h 6m Simon Event Trigger Flows, Simon Data Syncs

Started Mar 30, 2025, 11:59 PM UTC· resolved Mar 31, 2025, 01:06 AM UTC

  1. identified Mar 30, 2025, 11:59 PM UTC

    We're experiencing an outage. Flows and journeys will be delayed as we repair the impacted system.

  2. monitoring Mar 31, 2025, 12:26 AM UTC

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

  3. resolved Mar 31, 2025, 01:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2025 Snowflake Partial Outage 2h 51m Simon Event Trigger Flows, Simon Data Pipes, Simon Data Syncs

Started Mar 19, 2025, 06:22 PM UTC· resolved Mar 19, 2025, 09:14 PM UTC

  1. identified Mar 19, 2025, 06:22 PM UTC

    Simon is experiencing impacts to all data pipe refreshes, syncs, and journeys due to the Snowflake partial outage described here, https://status.snowflake.com/.

  2. resolved Mar 19, 2025, 09:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2025 Simon Web App and Audience API Disruption 57m Simon Web App, Simon Audience API

Started Mar 05, 2025, 09:17 PM UTC· resolved Mar 05, 2025, 10:14 PM UTC

  1. investigating Mar 05, 2025, 09:17 PM UTC

    We are currently experiencing a service disruption with the Simon Web App and Audience API. We are investigating the degraded performance.

  2. identified Mar 05, 2025, 09:44 PM UTC

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

  3. resolved Mar 05, 2025, 10:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 4, 2025 Simon Web App Service Disruption 20h 53m Simon Web App, Simon Audience API

Started Mar 04, 2025, 10:56 PM UTC· resolved Mar 05, 2025, 07:50 PM UTC

  1. investigating Mar 04, 2025, 10:56 PM UTC

    We are currently experiencing a service disruption with the Simon Web App and are investigating the degraded performance.

  2. investigating Mar 04, 2025, 11:16 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 04, 2025, 11:17 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 04, 2025, 11:17 PM UTC

    We are continuing to investigate this issue.

  5. identified Mar 04, 2025, 11:42 PM UTC

    Simon experienced a database outage. The database was restarted, we are working with AWS to determine the root cause.

  6. monitoring Mar 05, 2025, 12:16 AM UTC

    A fix has been implemented and we are monitoring the results. Web App may be slower to load.

  7. resolved Mar 05, 2025, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 19, 2025 Simon Documents Page Not Accessible 3h

Started Feb 19, 2025, 12:32 AM UTC· resolved Feb 19, 2025, 03:32 AM UTC

  1. identified Feb 19, 2025, 12:32 AM UTC

    docs.simondata.com is currently unavailable. We are communicating with our partner on resolution. We will post more updates as the issue is resolved. We apologize for the inconvenience.

  2. monitoring Feb 19, 2025, 01:52 AM UTC

    Access to the Simon Documents pages have been restored and we are monitoring the results. We apologize for the downtime.

  3. resolved Feb 19, 2025, 03:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 13, 2024 Journey Log Data Outage 1h 40m

Started Dec 13, 2024, 06:00 PM UTC· resolved Dec 13, 2024, 07:40 PM UTC

  1. resolved Dec 13, 2024, 06:00 PM UTC

    From 13:00 to 14:40 EST, Journey actions, e.g. sends, delays, continued as expected. However, the associated log data was not written to Journey Contact History. Therefore, Journey actions during this time will not be reflected in Simon Journey's Reporting UI as well as available in Contact History log data feeds.

Read the full incident report →