SwitchBot Outage History
3 incidents recorded over the last 365 days, 3 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 SwitchBot Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 9, 2026 | AWS Service OutageThe SwitchBot app experienced a temporary outage on May 8, 2026, from 00:00 to 05:00 UTC due to a significant AWS service disruption. During this period, all users in North America and some users in Asia were unable to… | -2130 min | Resolved |
| Dec 23, 2025 | AWS Service OutageThe SwitchBot app experienced a temporary outage on October 20, 2025, from 7:00 AM to 9:30 AM UTC, caused by a major AWS service disruption. This outage affected users across all regions. During this time, users were… | -92036 min | Resolved |
| Dec 23, 2025 | SwitchBot Service OutageThe SwitchBot app and backend server experienced a temporary outage from December 19, 2025, 7:30 PM UTC to December 20, 2025, 10:00 AM UTC due to an internal server glitch. This outage affected users in the Asian… | -4873 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 SwitchBot 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 SwitchBot 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 SwitchBot 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.