Ubidots status history
Current state: operational — “All Systems Operational” per https://status.ubidots.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Ubidots incidents last?
From 28 incidents with a vendor-posted start and resolve time. Longest on record: TCP — 28.4 days (2026-02-04 06:41 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (28)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-10 19:36 UTC | HTTP, MQTT & TCP | resolved | none | 14 min |
| 2026-07-10 01:09 UTC | HTTP | resolved | none | 13 h 30 min |
| 2026-05-27 13:14 UTC | Service Unavailable | resolved | none | 24 h 32 min |
| 2026-05-26 15:35 UTC | Service Unavailable | resolved | none | 21 h 39 min |
| 2026-05-21 12:41 UTC | MQTT | resolved | none | 7 h 53 min |
| 2026-05-14 13:12 UTC | MQTT | resolved | none | 25 h 01 min |
| 2026-05-14 13:11 UTC | HTTP | resolved | none | 25 h 02 min |
| 2026-05-13 06:14 UTC | HTTP, MQTT & TCP | resolved | minor | 8 h 12 min |
| 2026-05-06 13:53 UTC | MQTT | resolved | none | 24 h 13 min |
| 2026-05-06 13:52 UTC | HTTP | resolved | none | 24 h 14 min |
| 2026-04-21 02:59 UTC | MQTT & EVENTS | resolved | minor | 1 h 28 min |
| 2026-04-20 23:43 UTC | HTTP | resolved | minor | 3 h 16 min |
| 2026-04-16 16:19 UTC | MQTT | resolved | none | 5 h 01 min |
| 2026-04-16 06:49 UTC | MQTT | resolved | none | 6 h 23 min |
| 2026-04-15 14:39 UTC | MQTT | resolved | none | 5 h 24 min |
| 2026-04-10 07:15 UTC | TCP | resolved | none | 11 h 50 min |
| 2026-02-04 06:41 UTC | TCP | resolved | none | 28 d 9 h |
| 2026-01-28 06:26 UTC | TCP | resolved | none | 14 h 41 min |
| 2026-01-26 17:08 UTC | Synthetic Variables – Increased Latency | resolved | critical | 29 h 17 min |
| 2025-10-31 13:28 UTC | [UbiFunction] Module experiencing degradation | resolved | critical | 25 h 43 min |
| 2025-10-01 07:03 UTC | TCP | resolved | minor | 4 h 19 min |
| 2025-09-26 00:00 UTC | MQTT Subscription Disruption | resolved | none | 0 min |
| 2025-09-24 16:20 UTC | MQTT | resolved | none | 3 h 53 min |
| 2025-09-24 16:19 UTC | HTTP | resolved | none | 3 h 55 min |
| 2025-09-24 06:18 UTC | TCP | resolved | none | 13 h 56 min |
| 2025-08-21 19:23 UTC | Issues loading ubidots.com website | resolved | none | 33 min |
| 2025-08-18 17:18 UTC | Generalized platform latency Core and API | resolved | minor | 2 h 32 min |
| 2025-08-13 14:41 UTC | HTML Canvas and Widget plugins not working | resolved | major | 3 h 24 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Ubidots with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ubidots"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}