Last checked
Industrial IoT platform for predictive maintenance and smart manufacturing.
Experiencing an issue?
Is Ubidots down?
Status unavailable
Share your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 15m | Yes | Unknown | ||
| 13h 30m | Yes | Unknown | ||
| 24h 33m | Yes | Unknown | ||
| 21h 39m | Yes | Unknown | ||
| 7h 53m | Yes | Unknown | ||
| 25h 1m | Yes | Unknown | ||
| 25h 2m | Yes | Unknown | ||
| 8h 12m | Yes | Minor |
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started Jul 8, 2026, 11:00 AM UTC · Resolved Jul 8, 2026, 12:00 PM UTC
The scheduled maintenance has been completed.
Started Mar 9, 2026, 11:00 AM UTC · Resolved Mar 9, 2026, 03:00 PM UTC
As part of the scheduled update of our In-memory database, we observed the following issues: * **Ingestion service downtime:** Between **8:50 AM and 9:05 AM \(UTC-5\)**, the ingestion service was unavailable. This occurred because authentication tokens—stored in the In-memory database—were inaccessible during the update, resulting in failed authentication requests with `401` errors. * **Events engine backlog:** Between **7:30 AM and 8:00 AM \(UTC-5\)**, the events engine, which also relies on the In-memory database, experienced a backlog of queued events. As a consequence, certain events may have been triggered falsely \(false positives\). To avoid similar issues in future updates of the In-memory database: * For the **events engine**, all workers and event streams must be stopped prior to updating the instances it depends on. This procedure will prevent the buildup of invalid executions and reduce the risk of false-positive triggers. These measures will be integrated into our maintenance playbook and strictly followed in future scheduled updates to ensure service continuity.
Started Sep 24, 2025, 11:00 AM UTC · Resolved Sep 24, 2025, 12:00 PM UTC
The scheduled maintenance has been completed.
Started May 26, 2025, 07:00 PM UTC · Resolved May 26, 2025, 08:00 PM UTC
The scheduled maintenance has been completed.
Started Mar 11, 2025, 11:00 AM UTC · Resolved Mar 11, 2025, 03:00 PM UTC
The scheduled maintenance has been completed.
Started Nov 20, 2024, 11:00 AM UTC · Resolved Nov 20, 2024, 01:00 PM UTC
The scheduled maintenance has been completed.
Started Aug 15, 2024, 01:00 PM UTC · Resolved Aug 15, 2024, 02:00 PM UTC
The scheduled maintenance has been completed.
Started May 2, 2024, 11:00 AM UTC · Resolved May 2, 2024, 01:00 PM UTC
Share your thoughts about Ubidots
Be the first to comment!
Uptimus monitors Ubidots through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.
This page currently includes 16 monitored components, 50 indexed incidents, 15 maintenance windows and 7 days of known history.
Uptimus is an independent monitoring service and is not affiliated with Ubidots. A healthy status does not guarantee that every user, device or region is unaffected.
Get notified when Ubidots or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 50 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “HTTP, MQTT & TCP”.
Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 16 Ubidots components: Functions, Login Apps, Login Apps, HTTP Post. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.
| Comparison criteria | Uptimus | Downdetector |
|---|---|---|
| Community outage reports for Ubidots |
The current official status of Ubidots cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Ubidots in the last 24 hours. Last official check: .
| Included |
| Adaptive baseline that separates isolated reports from wider disruption | Included | Included |
|---|
| 24-hour report activity and regional outage view | Included | Included |
|---|
| One workspace for websites, provider status pages, Steam games and Android apps and games | Included | Separate product |
|---|
| Email, push and webhook alerts from the same workspace | Included | Separate product |
|---|
| Official incident updates and status timeline for Ubidots | Included | User-report led |
|---|
| Component health and maintenance windows kept separate | Included | Limited on public pages |
|---|
Rate this service
No reviews yet