Whop Outage History
10 incidents recorded over the last 365 days, 10 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 Whop Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Apr 29, 2026 | Errors Claiming Discord RolesSome users experienced delays when claiming Discord roles. The issue has been identified and resolved. Discord role claiming is now functioning normally. If you're still unable to claim your roles, please try again. | 14 min | Resolved |
| Apr 26, 2026 | Issue loading courses and other multimediaAll media now loads correctly. | 1h 41m | Resolved |
| Apr 14, 2026 | Platform speedWe believe this was caused downstream by Cloudflare, as indicated by their status page. It should be resolved now. | 1h 2m | Resolved |
| Apr 1, 2026 | Partial checkout outageThis issue has been resolved. | 32 min | Resolved |
| Mar 10, 2026 | Android images not loadingThis has been fixed. | 1h 57m | Resolved |
| Feb 27, 2026 | Discord connectivity issuesDiscord issue has been resolved. | 39 min | Resolved |
| Feb 26, 2026 | Users not seeing content inside of whopsThe issue has been resolved. All functionality is back to normal. | 13 min | Resolved |
| Feb 19, 2026 | Splitit checkout errorsAll issues are resolved. You may use Splitit. | 45 min | Resolved |
| Feb 18, 2026 | You may experience delays when joining a Discord server or claiming Discord rolesDiscord access is now instant. | 26 min | Resolved |
| Feb 11, 2026 | Billing portal showing elevated errorsAll fixed! | 31 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 Whop 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 Whop 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 Whop 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 Whop outage in this window ran 1h 57m, against a mean recovery of 48 min. If you depend on Whop 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.