We started checking SmartThings on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when SmartThings reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what SmartThings's own status page declared. Below it, any public chatter we saw about SmartThings and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what SmartThings's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about SmartThings in the last 24 hours, which is not evidence that nothing is wrong.
SmartThings's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is SmartThings's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention SmartThings next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
577
US-West
100.00%
429
Europe
100.00%
393
Asia-Pacific
100.00%
236
Their declared record
SmartThings's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Oct 20, 2025, 10:48 PM UTC to Oct 21, 2025, 9:35 PM UTC (22h 47m)resolved
their latest update (Oct 21, 2025, 9:35 PM UTC): SmartThings services remain stable and operational. This incident is fully resolved.
Matter Device Control and Onboarding IssuesAll systems operational
Aug 22, 2023, 7:00 PM UTC to Aug 22, 2023, 7:00 PM UTC (0 min)resolved
their latest update (Aug 22, 2023, 7:00 PM UTC): Some users may have briefly experienced issues controlling or viewing current devices states for Matter devices from the SmartThings platform. During this time onboarding Matter devices via SmartThings may have failed as well. The issue is now resolved and for users still experie…
SmartThings Platform Degraded PerformanceAll systems operational
Jun 1, 2023, 11:35 PM UTC to Jul 17, 2023, 4:17 PM UTC (45d 16h)resolved
their latest update (Jul 17, 2023, 4:17 PM UTC): This incident has been resolved.
SmartThings and Aeotec Cameras: Live streaming and clip recording degraded performanceMinor incident
May 9, 2023, 8:13 PM UTC to May 9, 2023, 9:39 PM UTC (1h 26m)resolved
their latest update (May 9, 2023, 9:39 PM UTC): SmartThings and Aeotec camera features have returned to normal.
May 2, 2023, 4:02 PM UTC to May 2, 2023, 4:36 PM UTC (34 min)resolved
their latest update (May 2, 2023, 4:36 PM UTC): Scenes execution and listing is working and latencies have returned to normal
Issues with Hubs, Device Control and Automation ExecutionMinor incident
Apr 11, 2023, 10:51 PM UTC to Apr 12, 2023, 1:55 AM UTC (3h 3m)resolved
their latest update (Apr 12, 2023, 1:55 AM UTC): This issue was opened with an abundance of caution, but upon further investigation it was determined that there was no noticeable impact to users.
Disconnected DevicesAll systems operational
Apr 5, 2023, 8:00 PM UTC to Apr 5, 2023, 8:00 PM UTC (0 min)resolved
their latest update (Apr 5, 2023, 8:00 PM UTC): Due to a planned change a very small set of users unintentionally had some of their devices removed from SmartThings. We have implemented a fix to prevent this from happening in the future, and have restored functionality where possible. We will also send an email to impacted use…
Few of the Smart Lighting automations not working for todayAll systems operational
Mar 12, 2023, 11:26 PM UTC to Mar 13, 2023, 5:43 PM UTC (18h 18m)resolved
their latest update (Mar 13, 2023, 5:43 PM UTC): The issue has been resolved as the new day started.
Names of capabilities can show up incorrectly in the mobile appMinor incident
Mar 7, 2023, 7:40 PM UTC to Mar 7, 2023, 9:20 PM UTC (1h 40m)resolved
their latest update (Mar 7, 2023, 9:20 PM UTC): This incident has been resolved.
St Station connection issuesMinor incident
Mar 7, 2023, 6:44 PM UTC to Mar 7, 2023, 7:38 PM UTC (54 min)resolved
their latest update (Mar 7, 2023, 7:38 PM UTC): This incident has been resolved.
Showing the 10 most recent of 50 incidents SmartThings has declared in the history we hold.
These entries are SmartThings's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
SmartThings's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.