IFTTT Outage History
9 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 IFTTT Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 24, 2026 | Issues Loading IFTTT.com and the IFTTT mobile appsThis incident has been resolved. | 3h 6m | Resolved |
| Aug 24, 2026 | Issues Loading IFTTT.com and the IFTTT mobile appsWe're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue. | -9 min | Resolved |
| Aug 24, 2026 | Scheduled maintenance for the X (Twitter) serviceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Aug 12, 2026 | Scheduled maintenance for the SmartThings serviceThe scheduled maintenance has been completed. | 1h 15m | Scheduled |
| Aug 5, 2026 | Scheduled maintenance for the SMS serviceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jun 25, 2026 | Issue Affecting The SMS Service's Send Me An SMS ActionThis incident has been resolved. | 115h 34m | Resolved |
| Apr 30, 2026 | Schedule Maintenance Thursday April 30th - Blogger ServiceThe scheduled maintenance has been completed. | 2h 30m | Scheduled |
| Apr 8, 2026 | Applet Run DelaysThis incident has been resolved. | 3h 6m | Resolved |
| Dec 5, 2025 | The Etsy service is pausedThis incident has been resolved. | 962h 8m | 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 IFTTT 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 IFTTT 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 IFTTT 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 IFTTT outage in this window ran 40d 2h, against a mean recovery of 5d 16h. If you depend on IFTTT 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.