THIS IS A SCHEDULED EVENT Jul <var data-var='date'>8</var>, <var data-var='time'>11:00</var> - <var data-var='time'>12:00</var> UTC Jul <var data-var='date'> 2</var>, <var data-var='time'>14:53</var> UTC Scheduled - We will be performing a scheduled Kubernetes version upgrade as part of our end-of-support maintenance cycle. We do not expect any service interruptions during this window, but brief instability is possible. We will update this page if any issues arise.

Kubernetes Infrastructure Upgrade

Jul <var data-var='date'> 3</var>, <var data-var='time'>07:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'> 3</var>, <var data-var='time'>06:50</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

May <var data-var='date'>28</var>, <var data-var='time'>13:47</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>27</var>, <var data-var='time'>13:32</var> UTC Monitoring - 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 support@ubidots.com. We will confirm full resolution shortly. May <var data-var='date'>27</var>, <var data-var='time'>13:14</var> UTC Investigating - 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.

Service Unavailable

May <var data-var='date'>27</var>, <var data-var='time'>13:15</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>26</var>, <var data-var='time'>15:59</var> UTC Monitoring - 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. May <var data-var='date'>26</var>, <var data-var='time'>15:35</var> UTC Investigating - 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.

May <var data-var='date'>21</var>, <var data-var='time'>20:34</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>21</var>, <var data-var='time'>12:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>21</var>, <var data-var='time'>12:41</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

MQTT

May <var data-var='date'>15</var>, <var data-var='time'>14:13</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>14</var>, <var data-var='time'>13:21</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>14</var>, <var data-var='time'>13:11</var> UTC Investigating - We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

HTTP

May <var data-var='date'>15</var>, <var data-var='time'>14:13</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>14</var>, <var data-var='time'>13:22</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>14</var>, <var data-var='time'>13:12</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

May <var data-var='date'>13</var>, <var data-var='time'>14:26</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>13</var>, <var data-var='time'>14:26</var> UTC Update - We are continuing to monitor for any further issues. May <var data-var='date'>13</var>, <var data-var='time'>06:25</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>13</var>, <var data-var='time'>06:14</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

HTTP, MQTT & TCP

May <var data-var='date'> 7</var>, <var data-var='time'>14:06</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 6</var>, <var data-var='time'>14:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 6</var>, <var data-var='time'>13:52</var> UTC Investigating - We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

May <var data-var='date'> 7</var>, <var data-var='time'>14:06</var> UTC Resolved - This incident has been resolved. May <var data-var='date'> 6</var>, <var data-var='time'>14:03</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'> 6</var>, <var data-var='time'>13:53</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

Apr <var data-var='date'>21</var>, <var data-var='time'>04:28</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>21</var>, <var data-var='time'>04:00</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>21</var>, <var data-var='time'>04:00</var> UTC Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>21</var>, <var data-var='time'>02:59</var> UTC Investigating - We have identified an error with our MQTT data ingestion service and Events engine are currently looking into the issue.

MQTT & EVENTS

Apr <var data-var='date'>21</var>, <var data-var='time'>02:59</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>21</var>, <var data-var='time'>02:58</var> UTC Update - We are continuing to monitor for any further issues. Apr <var data-var='date'>20</var>, <var data-var='time'>23:54</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>20</var>, <var data-var='time'>23:43</var> UTC Investigating - We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

Apr <var data-var='date'>16</var>, <var data-var='time'>21:20</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>16</var>, <var data-var='time'>16:30</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>16</var>, <var data-var='time'>16:19</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

Apr <var data-var='date'>16</var>, <var data-var='time'>13:13</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>16</var>, <var data-var='time'>07:04</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>16</var>, <var data-var='time'>06:49</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

Apr <var data-var='date'>15</var>, <var data-var='time'>20:03</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>15</var>, <var data-var='time'>14:50</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>15</var>, <var data-var='time'>14:39</var> UTC Investigating - We have identified an error with our MQTT publish service and are currently looking into the issue.

Apr <var data-var='date'>10</var>, <var data-var='time'>19:05</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'>10</var>, <var data-var='time'>07:26</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr <var data-var='date'>10</var>, <var data-var='time'>07:15</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

Mar <var data-var='date'> 9</var>, <var data-var='time'>15:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'> 9</var>, <var data-var='time'>11:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 4</var>, <var data-var='time'>19:14</var> UTC Scheduled - We will be performing a scheduled infrastructure upgrade on our US deployment cluster. During this window, we will migrate our Kubernetes environment from EKS 1.32 to EKS 1.33 ahead of the end of standard support for EKS 1.32 on March 23, 2026. What to expect: This upgrade is not expected to cause any service interruption. However, as with any infrastructure change, there is a possibility of transient errors and increased latency in event processing during the maintenance window. All other regions and deployments are unaffected. We will post updates here throughout the window. Thank you for your patience.

Scheduled Maintenance – US Cluster (EKS Upgrade)

Mar <var data-var='date'> 4</var>, <var data-var='time'>16:32</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'> 4</var>, <var data-var='time'>06:59</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'> 4</var>, <var data-var='time'>06:41</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

Jan <var data-var='date'>28</var>, <var data-var='time'>21:08</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>28</var>, <var data-var='time'>07:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'>28</var>, <var data-var='time'>06:26</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

Jan <var data-var='date'>27</var>, <var data-var='time'>22:26</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>26</var>, <var data-var='time'>20:06</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan <var data-var='date'>26</var>, <var data-var='time'>17:08</var> UTC Investigating - 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.

Synthetic Variables – Increased Latency

Nov <var data-var='date'> 1</var>, <var data-var='time'>15:12</var> UTC Resolved - Summary: We identified an issue that limited the number of active connections to one of our servers. The root cause was a kernel-level restriction on the maximum number of open files (file descriptors), which also affects network sockets. Impact: The limitation caused a temporary reduction in the number of simultaneous connections the server could handle, potentially affecting availability for some users. Resolution: The kernel and system-level limits for open files were increased to ensure sufficient capacity for concurrent connections. After applying the changes and restarting the affected services, the system returned to normal operation. Preventive Actions: We’ve updated our configuration management to enforce higher default limits across all environments, preventing similar constraints in the future. Status: This incident has been fully resolved, and all systems are operating normally. Oct <var data-var='date'>31</var>, <var data-var='time'>13:53</var> UTC Monitoring - We have restarted the load balancer for the UbiFunction module. This has restored the operation in the module. Oct <var data-var='date'>31</var>, <var data-var='time'>13:28</var> UTC Investigating - We’ve identified an issue affecting the UbiFunction module. Our DevOps team is currently investigating the root cause.

[UbiFunction] Module experiencing degradation

Oct <var data-var='date'> 1</var>, <var data-var='time'>11:23</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'> 1</var>, <var data-var='time'>07:24</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'> 1</var>, <var data-var='time'>07:03</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

Sep <var data-var='date'>26</var>, <var data-var='time'>00:00</var> UTC Resolved - Incident window: September 25, 2025 – 7:00 PM (UTC-5) to September 26, 2025 – 4:20 AM (UTC-5) Impact: During the incident window, MQTT subscriptions experienced disruptions that prevented data from being delivered in real time. Devices attempting to subscribe or maintain subscriptions may have encountered failures, delays, or missing data. Resolution: Our engineering team identified abnormal connection behavior that led to message queue saturation within the MQTT service. To restore functionality, queues were purged, affected MQTT clients were reset, and supporting services were restarted. Service was fully restored by 4:20 AM (UTC-5) on September 26. Current Status: The MQTT service is operating normally, and monitoring has been reinforced to ensure stability.

MQTT Subscription Disruption

Sep <var data-var='date'>24</var>, <var data-var='time'>20:14</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>06:38</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>24</var>, <var data-var='time'>06:18</var> UTC Investigating - We have identified an error with our TCP data ingestion service and are currently looking into the issue.

Sep <var data-var='date'>24</var>, <var data-var='time'>20:14</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>24</var>, <var data-var='time'>16:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>24</var>, <var data-var='time'>16:19</var> UTC Investigating - We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

Is Ubidots down?

Ubidots status is UP

Lastest published events

Kubernetes Infrastructure Upgrade

TCP

Service Unavailable

Ubidots Services, Components and Regions

Recent Ubidots events

Kubernetes Infrastructure Upgrade

TCP

Service Unavailable

Service Unavailable

MQTT

HTTP

Get your FREE account now,
5 monitors included!

Is Ubidots down?

Ubidots status is UP

Lastest published events

Kubernetes Infrastructure Upgrade

TCP

Service Unavailable

Ubidots Services, Components and Regions

Recent Ubidots events

Kubernetes Infrastructure Upgrade

TCP

Service Unavailable

Service Unavailable

MQTT

HTTP

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!