Shorthand Outage History
6 incidents recorded over the last 365 days, 4 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 Shorthand Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | PHP security vulnerabilities: Shorthand unaffectedThis incident has been resolved. | 5h 24m | Resolved |
| Sep 8, 2026 | Service DisruptionThis incident has been resolved. | 2h 42m | Resolved |
| Jun 27, 2026 | Platform Maintenance NoticeThe scheduled maintenance has been completed. | 10h 0m | Scheduled |
| Jun 26, 2026 | Platform Maintenance NoticeThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Feb 4, 2026 | Media uploads & Publishing failingThis incident has been resolved, if you're still seeing issues uploading media please try removing and re-uploading the media in that area. | 1h 22m | Resolved |
| Nov 13, 2025 | Media uploads & Publishing failingThis incident has been resolved, if you're still seeing issues uploading media please try removing and re-uploading the media in that area. | 47 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 Shorthand 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 Shorthand 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 Shorthand 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 Shorthand outage in this window ran 10h, against a mean recovery of 4h 43m. If you depend on Shorthand 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.