Simplero Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Simplero Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 16, 2026 | Database tuningMaintenance has started | 130h 35m | Resolved |
| Aug 24, 2026 | SSL Certificate Warning on Some Custom DomainsWe'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… | 1h 41m | Resolved |
| Jun 8, 2026 | Custom Domains are presently not working 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… | 2h 53m | Resolved |
| Jun 2, 2026 | System Down Temporary Database Crash | 0 min | Resolved |
| Apr 22, 2026 | Test incidentWe have done X, Y and Z | 2 min | Resolved |
| Apr 21, 2026 | Test incident - Don't panicThis is now resolved | 28 min | Resolved |
| Apr 17, 2026 | Test IncidentThis has been resolved | 2h 39m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Simplero incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Simplero Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Simplero acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Simplero outage in this window ran 5d 10h, against a mean recovery of 19h 45m. If you depend on Simplero in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.