Memberful Outage History
9 incidents recorded over the last 365 days, 1 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 Memberful Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Routine maintenanceMaintenance will begin as scheduled in 60 minutes. | 1h 0m | Scheduled |
| Jul 10, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jun 16, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jun 10, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Apr 15, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 20h 0m | Scheduled |
| Apr 2, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 20h 0m | Scheduled |
| Jan 27, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jan 12, 2026 | Routine maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Nov 18, 2025 | Service DegradationThe issue has been fully resolved, and all services are operating normally. Thank you for your patience. | 4h 48m | 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 Memberful 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 Memberful 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 Memberful 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 Memberful outage in this window ran 20h, against a mean recovery of 5h 22m. If you depend on Memberful 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.