Bettermode Outage History
12 incidents recorded over the last 365 days, 12 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 Bettermode Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 22, 2026 | Update on PHP2Shell security vulnerabilityBettermode is aware of the recently disclosed PHP security vulnerability. PHP isn't part of Bettermode's infrastructure, and we are not aware of any impact to our platform or customers. We will continue to watch the… | -746 min | Resolved |
| Sep 28, 2026 | Outage in email delivery serviceThis incident has been resolved. | 1h 52m | Resolved |
| Aug 5, 2026 | Sitewide 502 ErrorsThis incident has been resolved. | 48 min | Resolved |
| Jun 12, 2026 | Failure in initial page loadingThis incident has been resolved. | 47 min | Resolved |
| Jun 9, 2026 | Server errors on logins for a subset of usersThe fix has been deployed on all environments and systems are back to full operation | 7h 38m | Resolved |
| Jun 8, 2026 | Service disruption on US and EU sitesThis incident has been resolved. | 2h 25m | Resolved |
| Feb 12, 2026 | Service disruption on US sites.This incident has been resolved. | 1h 58m | Resolved |
| Jan 23, 2026 | Partial outage on communities (US)This incident has been resolved. | 2 min | Resolved |
| Jan 12, 2026 | Analytics consumption on EU pausedChanges are complete and analytics are back online. | 4h 52m | Resolved |
| Dec 5, 2025 | New content not appearing in the search resultsThe patch was effective and time to index is now back to normal. | 5h 6m | Resolved |
| Nov 18, 2025 | All communities are downThis incident has been resolved. | 3h 7m | Resolved |
| Nov 12, 2025 | Communities InaccessibleThis incident has been resolved. | 39 min | 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 Bettermode 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 Bettermode 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 Bettermode 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 Bettermode outage in this window ran 7h 38m, against a mean recovery of 2h 40m. If you depend on Bettermode 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.