Gumlet Outage History
5 incidents recorded over the last 365 days, 5 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 Gumlet Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 2, 2026 | Delivery of Uncached images is affected in India region | 379h 46m | Resolved |
| Jul 18, 2026 | Delivery of Uncached images is affected in India region | 1489h 52m | Resolved |
| Jun 24, 2026 | Delivery of Uncached images is affected | 1651h 50m | Resolved |
| Jun 22, 2026 | Image processing failures in BLR region | 1693h 5m | Resolved |
| Jun 15, 2026 | Delivery of images is slow in India region. | 1854h 2m | 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 Gumlet 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 Gumlet 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 Gumlet 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 Gumlet outage in this window ran 77d 6h, against a mean recovery of 58d 21h. If you depend on Gumlet 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.