Simplero Outage History

Simplero is up right now

Simplero had 13 outages in the last 2 years totaling 186h 39m of downtime — averaging 0.5 incidents per month.

There were 13 Simplero outages since June 19, 2025 totaling 186h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.simplero.com

Minor June 8, 2026

Custom Domains are presently not working

Detected by Pingoru
Jun 08, 2026, 07:15 PM UTC
Resolved
Jun 08, 2026, 07:15 PM UTC
Duration
Affected: Website
Timeline · 2 updates
  1. investigating Jun 08, 2026, 04:21 PM UTC

    Status: Investigating Custom domains for sites are not presently working. The team is investigating Affected components Website (Full outage)

  2. resolved Jun 08, 2026, 07:15 PM UTC

    Status: Resolved We have fully identified and fixed the issue. The custom domains were not broken across the whole system. The issue was isolated and only happened to those who tried changing where custom domains point to since today morning 9am EDT. 4 domains were affected and fixed manually. The fix on the UI that caused the bug to happen has been patched and deployed to production. Affected components Website (Operational)

Read the full incident report →

Minor June 2, 2026

System Down

Detected by Pingoru
Jun 02, 2026, 07:43 PM UTC
Resolved
Jun 02, 2026, 07:43 PM UTC
Duration
Affected: APIBackground processingAmazon Web ServicesSpreedlyWebsiteTwilioStripe
Timeline · 1 update
  1. resolved Jun 02, 2026, 07:43 PM UTC

    Status: Resolved Temporary Database Crash Affected components Twilio (Operational) Website (Operational) API (Operational) Background processing (Operational) Spreedly (Operational) Stripe (Operational) Amazon Web Services (Operational)

Read the full incident report →

Minor April 22, 2026

Test incident

Detected by Pingoru
Apr 22, 2026, 05:22 PM UTC
Resolved
Apr 22, 2026, 05:22 PM UTC
Duration
Affected: Website
Timeline · 2 updates
  1. identified Apr 22, 2026, 05:19 PM UTC

    Status: Identified Message Affected components Website (Degraded performance)

  2. resolved Apr 22, 2026, 05:22 PM UTC

    Status: Resolved We have done X, Y and Z Affected components Website (Operational)

Read the full incident report →

Minor April 21, 2026

Test incident - Don't panic

Detected by Pingoru
Apr 21, 2026, 04:26 PM UTC
Resolved
Apr 21, 2026, 04:26 PM UTC
Duration
Affected: Stripe
Timeline · 2 updates
  1. investigating Apr 21, 2026, 03:57 PM UTC

    Status: Investigating This is a test incident and this is the impact that is having on your accounts Affected components Stripe (Degraded performance)

  2. resolved Apr 21, 2026, 04:26 PM UTC

    Status: Resolved This is now resolved Affected components Stripe (Operational)

Read the full incident report →

Minor April 17, 2026

Test Incident

Detected by Pingoru
Apr 17, 2026, 05:11 PM UTC
Resolved
Apr 17, 2026, 05:11 PM UTC
Duration
Affected: API
Timeline · 3 updates
  1. investigating Apr 17, 2026, 02:31 PM UTC

    Status: Investigating Test Incident Affected components API (Partial outage)

  2. investigating Apr 17, 2026, 02:33 PM UTC

    Status: Investigating This has been resolved Affected components API (Operational)

  3. resolved Apr 17, 2026, 05:11 PM UTC

    Status: Resolved This has been resolved Affected components API (Operational)

Read the full incident report →

Minor February 10, 2026

Partial Outage: DNS Degradation Affecting Domains hosted on Simplero

Detected by Pingoru
Feb 10, 2026, 06:37 PM UTC
Resolved
Feb 10, 2026, 11:57 PM UTC
Duration
5h 19m
Timeline · 2 updates
  1. identified Feb 10, 2026, 06:37 PM UTC

    We’re currently experiencing a partial outage affecting some domains due to a service degradation at our DNS provider. As a result, some visitors may see intermittent issues such as: - Website not loading / “site can’t be reached” - SSL warnings (in some cases) - Missing pages or broken links - Intermittent access to Simplero-hosted pages on impacted domains/subdomains We’re actively investigating and monitoring the status while working to reduce impact.

  2. resolved Feb 10, 2026, 11:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 22, 2026

Email delivery delays

Detected by Pingoru
Jan 22, 2026, 10:42 PM UTC
Resolved
Jan 23, 2026, 05:35 AM UTC
Duration
6h 53m
Affected: AWS ses-us-east-1
Timeline · 4 updates
  1. identified Jan 22, 2026, 10:42 PM UTC

    AWS has notified us that there is a increase in delivery time for emails on our region.

  2. identified Jan 23, 2026, 12:00 AM UTC

    AWS updated that the issue has improved, but not yet fully resolved. They are continuing to monitor and follow up with their third party provider until it is fully fixed.

  3. identified Jan 23, 2026, 12:33 AM UTC

    AWS notified about improvements on the delay but no confirmation of a full resolution has been given yet. We will continue to follow their updates until it gets resolved

  4. resolved Jan 23, 2026, 05:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 20, 2026

Zoom integration errors

Detected by Pingoru
Jan 20, 2026, 01:32 AM UTC
Resolved
Jan 20, 2026, 01:56 AM UTC
Duration
23m
Affected: Web interface and APIBackground processing
Timeline · 2 updates
  1. identified Jan 20, 2026, 01:32 AM UTC

    We investigated and found an issue on our zoom integration. It was caused by an unannounced change on the zoom API, causing the authentication with zoom to fail. This error meant that our integration thought it had lost access, and disabled the integration. We will try to restore all the zoom accounts to their correct state once the fix has been deployed.

  2. resolved Jan 20, 2026, 01:56 AM UTC

    The fix has been deployed and we were able to restore all accounts and zoom integrations that were affected, Scheduling links that have received bookings during the time should soon retry the synchronization process. You should expect in some cases 2 calendar events, one with zoom link and one without. Other processes that are related to zoom and failed should automatically retry unless they are manually triggered.

Read the full incident report →

Major December 29, 2025

Processing delays

Detected by Pingoru
Dec 29, 2025, 09:53 AM UTC
Resolved
Dec 29, 2025, 02:32 PM UTC
Duration
4h 39m
Affected: Background processing
Timeline · 4 updates
  1. investigating Dec 29, 2025, 09:53 AM UTC

    We are currently investigating an issue causing delays on triggers, automations and email delivery.

  2. identified Dec 29, 2025, 10:17 AM UTC

    We have identified the issue and are working on a fix.

  3. monitoring Dec 29, 2025, 11:23 AM UTC

    A fix has been implemented and emails, automations and triggers should all be executing normally. There is an edge case that was causing issues and bringing the whole system down. We will continue monitoring the processes in case another edge case happens

  4. resolved Dec 29, 2025, 02:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 26, 2025

NMI outage

Detected by Pingoru
Sep 26, 2025, 09:57 PM UTC
Resolved
Sep 26, 2025, 11:16 PM UTC
Duration
1h 18m
Affected: Spreedly Gateway Integrations
Timeline · 2 updates
  1. investigating Sep 26, 2025, 09:57 PM UTC

    A payment gateway called NMI is currently experiencing issues. Only transactions going through this particular processor are not working. They are aware of this, and we'll announce here once they resolve it

  2. resolved Sep 26, 2025, 11:16 PM UTC

    NMI has resolved the issue and are now monitoring.

Read the full incident report →

Minor September 11, 2025

Delivered Email Reports may not show accurate statistics.

Detected by Pingoru
Sep 11, 2025, 04:31 PM UTC
Resolved
Sep 12, 2025, 03:02 PM UTC
Duration
22h 30m
Affected: Background processing
Timeline · 5 updates
  1. investigating Sep 11, 2025, 04:31 PM UTC

    Emails are being delivered. However, some may be showing as ‘Sent’ rather than ‘Delivered’ in Simplero. This affects emails sent between Sept 4 and September 11. Fix is in progress.

  2. identified Sep 11, 2025, 06:33 PM UTC

    We have identified what caused email events (delivered, opened, etc) to not be processed. We will be able to restore all the events from September 10th afternoon EST, though it will take some time until we catch up and be able to process all events coming live. Until this is fixed, you will still see some stats missing due to the queue mentioned above.

  3. identified Sep 11, 2025, 10:12 PM UTC

    We are still processing the list of events from September 10th - September 11th (missing 1/3 as of now). Some broadcasts and emails might show up as "overdelivered" or with wrong stats since we are processing all the events, including some that may have been processed through the old behavior, which will be decommissioned when the queue catches up. All the stats for broadcasts delivered since September 10th will be recalculated at the end of this process to eliminate any duplication.

  4. monitoring Sep 12, 2025, 01:03 AM UTC

    We have finished processing all the events from September 10th to 11th and the processing queue has now caught up with the present time. We also recalculated all the stats for the broadcasts delivered in the period. We'll continue monitoring over the next 10-12 hours before considering this issue resolved.

  5. resolved Sep 12, 2025, 03:02 PM UTC

    Since the last update on September 11th, we have seen that all the new events for delivered, opened, etc have been correctly processed as they come. GIven this, we'll consider this issue resolved.

Read the full incident report →

Notice June 19, 2025

Microsoft has decided to mark some of our domains as "suspicious"

Detected by Pingoru
Jun 19, 2025, 01:30 PM UTC
Resolved
Jun 25, 2025, 01:43 PM UTC
Duration
6d
Timeline · 2 updates
  1. identified Jun 19, 2025, 01:30 PM UTC

    There's no good reason for this, as far as we're aware. It's happened once before, many moons ago, and it was a fluke. It's something they do from time to time, and there's little we can do. We've reached out to them and we hope they'll get it fixed soon. In the meantime, please: * mark the site as 'safe' * tell your clients to do the same * tell your clients to ignore the warning or use another browser Telling Microsoft the site is safe will hopefully help change their minds. We're super sorry about this, but sometimes these giant corporations do what they do and we can't stop them.

  2. resolved Jun 25, 2025, 01:43 PM UTC

    We seem to be off the naughty list! Our testing shows that the warning doesn't appear anymore when using Microsoft Defender SmartScreen. Big thanks to all of you who reported the domains as safe.

Read the full incident report →