Vendor Status Watch

← all vendors

Ubidots status history

Current state: operational — “All Systems Operational” per https://status.ubidots.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
2incidents, last 90 days
28incidents on record
Incidents per week, last 12 weeks:

How long do Ubidots incidents last?

8.0 hmedian incident duration28 measured
25.0 h90th percentile1 in 10 ran longer
25.7 hmedian, major/critical only3 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-10 19:36 UTCHTTP, MQTT & TCPresolvednone14 min
2026-07-10 01:09 UTCHTTPresolvednone13 h 30 min
2026-05-27 13:14 UTCService Unavailableresolvednone24 h 32 min
2026-05-26 15:35 UTCService Unavailableresolvednone21 h 39 min
2026-05-21 12:41 UTCMQTTresolvednone7 h 53 min
2026-05-14 13:12 UTCMQTTresolvednone25 h 01 min
2026-05-14 13:11 UTCHTTPresolvednone25 h 02 min
2026-05-13 06:14 UTCHTTP, MQTT & TCPresolvedminor8 h 12 min
2026-05-06 13:53 UTCMQTTresolvednone24 h 13 min
2026-05-06 13:52 UTCHTTPresolvednone24 h 14 min
2026-04-21 02:59 UTCMQTT & EVENTSresolvedminor1 h 28 min
2026-04-20 23:43 UTCHTTPresolvedminor3 h 16 min
2026-04-16 16:19 UTCMQTTresolvednone5 h 01 min
2026-04-16 06:49 UTCMQTTresolvednone6 h 23 min
2026-04-15 14:39 UTCMQTTresolvednone5 h 24 min
2026-04-10 07:15 UTCTCPresolvednone11 h 50 min
2026-02-04 06:41 UTCTCPresolvednone28 d 9 h
2026-01-28 06:26 UTCTCPresolvednone14 h 41 min
2026-01-26 17:08 UTCSynthetic Variables – Increased Latencyresolvedcritical29 h 17 min
2025-10-31 13:28 UTC[UbiFunction] Module experiencing degradationresolvedcritical25 h 43 min
2025-10-01 07:03 UTCTCPresolvedminor4 h 19 min
2025-09-26 00:00 UTCMQTT Subscription Disruptionresolvednone0 min
2025-09-24 16:20 UTCMQTTresolvednone3 h 53 min
2025-09-24 16:19 UTCHTTPresolvednone3 h 55 min
2025-09-24 06:18 UTCTCPresolvednone13 h 56 min
2025-08-21 19:23 UTCIssues loading ubidots.com websiteresolvednone33 min
2025-08-18 17:18 UTCGeneralized platform latency Core and APIresolvedminor2 h 32 min
2025-08-13 14:41 UTCHTML Canvas and Widget plugins not workingresolvedmajor3 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
}