Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Ubidots outage history

    51 recorded Ubidots incidents since November 2023, with official updates, affected components, duration and resolution information.

    Back to current status

    Degraded email notification delivery

    Started September 23, 2026 at 1:38 PM UTC · 2h 58m

    IssuesMinor incident
    Affected components
    Events EngineEvents Engine
    1. September 23, 2026 at 1:38 PM UTCidentified

      We have identified an issue affecting the delivery of email notifications, including alert emails. Some messages may arrive late or be filtered into spam/junk folders. Our team is actively working on remediation. SMS, webhook and other notification channels are not affected. In the meantime, we recommend checking your spam/junk folder and adding [email protected] to your safe senders list. We will post updates as the situation progresses.

    2. September 23, 2026 at 3:33 PM UTCmonitoring

      A fix has been implemented and email notification delivery has returned to normal. We are monitoring closely to confirm stability. If you still don't see expected alert emails, please check your spam/junk folder and add [email protected] to your safe senders list.

    3. September 23, 2026 at 4:36 PM UTCresolved

      This incident has been resolved. We identified the root cause of the email delivery degradation and deployed a fix. Email notifications, including alert emails, are being delivered normally. If you still don't see expected alert emails, please check your spam/junk folder and add [email protected] to your safe senders list, or contact our support team.

    HTTP, MQTT & TCP

    Started July 10, 2026 at 7:36 PM UTC · 15m

    Pending
    Affected components
    TCPMQTT PublishHTTP
    1. July 10, 2026 at 7:36 PM UTCinvestigating

      We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

    2. July 10, 2026 at 7:47 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. July 10, 2026 at 7:50 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    4. July 10, 2026 at 7:51 PM UTCresolved

      This incident has been resolved.

    HTTP

    Started July 10, 2026 at 1:09 AM UTC · 13h 30m

    Pending
    1. July 10, 2026 at 1:09 AM UTCinvestigating

      We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

    2. July 10, 2026 at 1:20 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. July 10, 2026 at 2:39 PM UTCresolved

      This incident has been resolved.

    Service Unavailable

    Started May 27, 2026 at 1:14 PM UTC · 1d 0h

    Pending
    Affected components
    Login Apps
    1. May 27, 2026 at 1:14 PM UTCinvestigating

      We are currently experiencing a service disruption affecting Ubidots (industrial.ubidots.com) and associated apps. Users may be seeing 503 Service Unavailable errors. Our team is actively investigating a connectivity issue between our connection pooler and the database cluster, following a scheduled PostgreSQL upgrade operation. We are working to restore full service as quickly as possible. We will provide updates every 15–20 minutes. We apologize for the inconvenience.

    2. May 27, 2026 at 1:32 PM UTCmonitoring

      The service has been restored and we are monitoring the platform for full stability. The issue was caused by a configuration incompatibility introduced during our PostgreSQL upgrade. The database server was requiring SSL connections, which prevented our connection pooler from establishing a successful connection. We resolved the issue by updating the database configuration and upgrading the connection pooler. If you are still experiencing issues, please reach out to [email protected]. We will confirm full resolution shortly.

    3. May 28, 2026 at 1:47 PM UTCresolved

      This incident has been resolved.

    Service Unavailable

    Started May 26, 2026 at 3:35 PM UTC · 21h 39m

    Pending
    Affected components
    Login Apps
    1. May 26, 2026 at 3:35 PM UTCinvestigating

      We are currently experiencing an issue affecting Ubidots (industrial.ubidots.com) and associated apps. Users may be seeing 503 Service Unavailable errors. This is related to an ongoing database maintenance operation. Our team is actively working to restore full service. We will provide updates every 15–20 minutes. We apologize for the inconvenience.

    2. May 26, 2026 at 3:59 PM UTCmonitoring

      The database switchover has been completed and we are monitoring the platform for full recovery. Some users may still experience intermittent errors or degraded performance while the system stabilizes. We will confirm full resolution shortly. Thank you for your patience.

    3. May 27, 2026 at 1:15 PM UTCresolved

      This incident has been resolved.

    MQTT

    Started May 21, 2026 at 12:41 PM UTC · 7h 53m

    Pending
    1. May 21, 2026 at 12:41 PM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. May 21, 2026 at 12:51 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 21, 2026 at 8:34 PM UTCresolved

      This incident has been resolved.

    MQTT

    Started May 14, 2026 at 1:12 PM UTC · 1d 1h

    Pending
    1. May 14, 2026 at 1:12 PM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. May 14, 2026 at 1:22 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 15, 2026 at 2:13 PM UTCresolved

      This incident has been resolved.

    HTTP

    Started May 14, 2026 at 1:11 PM UTC · 1d 1h

    Pending
    1. May 14, 2026 at 1:11 PM UTCinvestigating

      We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

    2. May 14, 2026 at 1:21 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 15, 2026 at 2:13 PM UTCresolved

      This incident has been resolved.

    HTTP, MQTT & TCP

    Started May 13, 2026 at 6:14 AM UTC · 8h 12m

    IssuesMinor incident
    Affected components
    TCPMQTT PublishHTTP
    1. May 13, 2026 at 6:14 AM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. May 13, 2026 at 6:25 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 13, 2026 at 2:26 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    4. May 13, 2026 at 2:26 PM UTCresolved

      This incident has been resolved.

    MQTT

    Started May 6, 2026 at 1:53 PM UTC · 1d 0h

    Pending
    1. May 6, 2026 at 1:53 PM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. May 6, 2026 at 2:03 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 7, 2026 at 2:06 PM UTCresolved

      This incident has been resolved.

    HTTP

    Started May 6, 2026 at 1:52 PM UTC · 1d 0h

    Pending
    1. May 6, 2026 at 1:52 PM UTCinvestigating

      We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

    2. May 6, 2026 at 2:03 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. May 7, 2026 at 2:06 PM UTCresolved

      This incident has been resolved.

    MQTT & EVENTS

    Started April 21, 2026 at 2:59 AM UTC · 1h 29m

    IssuesMinor incident
    Affected components
    Events EngineMQTT SubscribeMQTT Publish
    1. April 21, 2026 at 2:59 AM UTCinvestigating

      We have identified an error with our MQTT data ingestion service and Events engine are currently looking into the issue.

    2. April 21, 2026 at 4:00 AM UTCidentified

      The issue has been identified and a fix is being implemented.

    3. April 21, 2026 at 4:00 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. April 21, 2026 at 4:28 AM UTCresolved

      This incident has been resolved.

    HTTP

    Started April 20, 2026 at 11:43 PM UTC · 3h 17m

    IssuesMinor incident
    Affected components
    TCPMQTT PublishHTTP
    1. April 20, 2026 at 11:43 PM UTCinvestigating

      We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

    2. April 20, 2026 at 11:54 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 21, 2026 at 2:58 AM UTCmonitoring

      We are continuing to monitor for any further issues.

    4. April 21, 2026 at 2:59 AM UTCresolved

      This incident has been resolved.

    MQTT

    Started April 16, 2026 at 4:19 PM UTC · 5h 1m

    Pending
    1. April 16, 2026 at 4:19 PM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. April 16, 2026 at 4:30 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 16, 2026 at 9:20 PM UTCresolved

      This incident has been resolved.

    MQTT

    Started April 16, 2026 at 6:49 AM UTC · 6h 24m

    Pending
    1. April 16, 2026 at 6:49 AM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. April 16, 2026 at 7:04 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 16, 2026 at 1:13 PM UTCresolved

      This incident has been resolved.

    MQTT

    Started April 15, 2026 at 2:39 PM UTC · 5h 24m

    Pending
    1. April 15, 2026 at 2:39 PM UTCinvestigating

      We have identified an error with our MQTT publish service and are currently looking into the issue.

    2. April 15, 2026 at 2:50 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 15, 2026 at 8:03 PM UTCresolved

      This incident has been resolved.

    TCP

    Started April 10, 2026 at 7:15 AM UTC · 11h 50m

    Pending
    1. April 10, 2026 at 7:15 AM UTCinvestigating

      We have identified an error with our TCP data ingestion service and are currently looking into the issue.

    2. April 10, 2026 at 7:26 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. April 10, 2026 at 7:05 PM UTCresolved

      This incident has been resolved.

    TCP

    Started February 4, 2026 at 6:41 AM UTC · 28d 9h

    Pending
    1. February 4, 2026 at 6:41 AM UTCinvestigating

      We have identified an error with our TCP data ingestion service and are currently looking into the issue.

    2. February 4, 2026 at 6:59 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. March 4, 2026 at 4:32 PM UTCresolved

      This incident has been resolved.

    TCP

    Started January 28, 2026 at 6:26 AM UTC · 14h 42m

    Pending
    1. January 28, 2026 at 6:26 AM UTCinvestigating

      We have identified an error with our TCP data ingestion service and are currently looking into the issue.

    2. January 28, 2026 at 7:05 AM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. January 28, 2026 at 9:08 PM UTCresolved

      This incident has been resolved.

    Synthetic Variables – Increased Latency

    Started January 26, 2026 at 5:08 PM UTC · 1d 5h

    OutageCritical incident
    Affected components
    Synthetic Variables
    1. January 26, 2026 at 5:08 PM UTCinvestigating

      Earlier today, we identified increased load on one of our underlying database nodes, which led to higher-than-usual latency across dashboards and Synthetic Variables processing in the US deployment. As a result, synthetic variable calculations and updates are delayed, and some dashboards may have experienced slower response times while corrective maintenance is performed to stabilize the platform. The system is gradually returning to normal operation, and we are closely monitoring performance to ensure stability and prevent further impact. We appreciate your patience and understanding.

    2. January 26, 2026 at 8:06 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. January 27, 2026 at 10:26 PM UTCresolved

      This incident has been resolved.