Simplero Outage History
Simplero is up right nowPingoru has recorded 10 incidents for Simplero: 10 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 1 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 2 | 5 of 720 (1%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 2 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 120 (0%) |
Incidents, newest first
Major August 24, 2026 SSL Certificate Warning on Some Custom Domains 1h 41m Website
Started Aug 24, 2026, 01:25 PM UTC· resolved Aug 24, 2026, 03:06 PM UTC
- identified Aug 24, 2026, 01:25 PM UTC
We're aware that few accounts using a custom domain without "www" (e.g. yourdomain.com: http://yourdomain.com rather than www.yourdomain.com: http://www.yourdomain.com) may see a browser security warning when visiting their site. This is caused by a DNS/network configuration issue, not a security breach — no customer data has been accessed or exposed. Accounts using their default Simplero domain, or the "www" version of a custom domain, are not affected. We're actively investigating and will post an update here as soon as we have more information.
- resolved Aug 24, 2026, 03:06 PM UTC
We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected.
- monitoring Aug 24, 2026, 03:07 PM UTC
We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected.
- resolved Sep 03, 2026, 07:57 PM UTC
We've identified the cause of the security warning some customers have seen on their custom domain (e.g. yourdomain.com: http://yourdomain.com instead of www.yourdomain.com: http://www.yourdomain.com). If your domain's DNS settings are managed by you (through your own domain registrar or DNS provider), please check if you have an "A record" set to 18.214.48.22. If so, please update it to: 34.228.154.79 This is usually found in your domain's DNS settings, under a record type "A", pointing to @ or your root domain. If you're not sure how to do this, your domain registrar's support team (GoDaddy, Namecheap, Cloudflare, etc.) can help, or reach out to us and we'll guide you. If Simplero manages your domain's DNS for you, no action is needed — we've already updated this on your behalf. This was caused by a network configuration issue on our end, not a security breach — no customer data was accessed or exposed, and your website, SSL certificate, and account are otherwise unaffected.
Critical June 8, 2026 Custom Domains are presently not working 4h 31m Website
Started Jun 08, 2026, 04:21 PM UTC· resolved Jun 08, 2026, 08:53 PM UTC
- investigating Jun 08, 2026, 04:21 PM UTC
Custom domains for sites are not presently working. The team is investigating
- resolved Jun 08, 2026, 07:15 PM UTC
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.
Minor June 2, 2026 System Down – API, Background processing, Externals (Amazon Web Services), Externals (Spreedly) and 3 more
Started Jun 02, 2026, 07:43 PM UTC· resolved Jun 02, 2026, 07:43 PM UTC
- resolved Jun 02, 2026, 07:43 PM UTC
Temporary Database Crash
Minor April 22, 2026 Test incident 2m Website
Started Apr 22, 2026, 05:19 PM UTC· resolved Apr 22, 2026, 05:22 PM UTC
- identified Apr 22, 2026, 05:19 PM UTC
Message
- resolved Apr 22, 2026, 05:22 PM UTC
We have done X, Y and Z
Minor April 21, 2026 Test incident - Don't panic 28m Externals (Stripe)
Started Apr 21, 2026, 03:57 PM UTC· resolved Apr 21, 2026, 04:26 PM UTC
- investigating Apr 21, 2026, 03:57 PM UTC
This is a test incident and this is the impact that is having on your accounts
- resolved Apr 21, 2026, 04:26 PM UTC
This is now resolved
Major April 17, 2026 Test Incident 1m API
Started Apr 17, 2026, 02:31 PM UTC· resolved Apr 17, 2026, 02:33 PM UTC
- investigating Apr 17, 2026, 02:31 PM UTC
Test Incident
- investigating Apr 17, 2026, 02:33 PM UTC
This has been resolved
- resolved Apr 17, 2026, 05:11 PM UTC
This has been resolved
Minor February 10, 2026 Partial Outage: DNS Degradation Affecting Domains hosted on Simplero 5h 19m
Started Feb 10, 2026, 06:37 PM UTC· resolved Feb 10, 2026, 11:57 PM UTC
- 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.
- resolved Feb 10, 2026, 11:57 PM UTC
This incident has been resolved.
Minor January 22, 2026 Email delivery delays 6h 53m AWS ses-us-east-1
Started Jan 22, 2026, 10:42 PM UTC· resolved Jan 23, 2026, 05:35 AM UTC
- 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.
- 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.
- 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
- resolved Jan 23, 2026, 05:35 AM UTC
This incident has been resolved.
Minor January 20, 2026 Zoom integration errors 23m Web interface and API, Background processing
Started Jan 20, 2026, 01:32 AM UTC· resolved Jan 20, 2026, 01:56 AM UTC
- 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.
- 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.
Major December 29, 2025 Processing delays 4h 39m Background processing
Started Dec 29, 2025, 09:53 AM UTC· resolved Dec 29, 2025, 02:32 PM UTC
- investigating Dec 29, 2025, 09:53 AM UTC
We are currently investigating an issue causing delays on triggers, automations and email delivery.
- identified Dec 29, 2025, 10:17 AM UTC
We have identified the issue and are working on a fix.
- 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
- resolved Dec 29, 2025, 02:32 PM UTC
This incident has been resolved.