Ubidots 中断历史

1. 2026年9月23日 UTC 13:38identified

   我们发现了一个影响电子邮件通知发送的问题,包括提醒电子邮件。 一些信件可能来得较晚或被过滤入垃圾邮件/垃圾邮件文件夹. 我们的小组正在积极进行补救。 短消息、网钩和其他通知渠道不受影响。 同时,我们建议检查您的垃圾邮件/垃圾邮件文件夹,并在您的安全发送者名单中加入 [email protected]. 我们将随着局势的发展公布最新情况.

2. 2026年9月23日 UTC 15:33monitoring

   一项固定措施已经实施,电子邮件通知的发送已经恢复正常。 我们正在密切监测,以确认稳定。 如果您仍未看到预期的提醒邮件, 请检查您的垃圾邮件/ junk 文件夹, 并在您的安全发送者列表中添加 no- reply@ iot- Notifications.com .

3. 2026年9月23日 UTC 16:36resolved

   这一事件已经得到解决。 我们查明了电子邮件发送退化的根本原因,并采取了补救措施。 电子邮件通知,包括提醒电子邮件,通常都在发送。 如果您仍未看到预期的提醒邮件, 请检查您的垃圾邮件/ junk 文件夹, 并在您的安全发送者列表中添加 no- reply@iot- Notifications.com, 或者联系我们的支援团队 .

自动翻译自官方事件更新。

1. 2026年7月10日 UTC 19:36investigating

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

2. 2026年7月10日 UTC 19:47monitoring

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

3. 2026年7月10日 UTC 19:50monitoring

   We are continuing to monitor for any further issues.

4. 2026年7月10日 UTC 19:51resolved

   This incident has been resolved.

1. 2026年7月10日 UTC 01:09investigating

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

2. 2026年7月10日 UTC 01:20monitoring

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

3. 2026年7月10日 UTC 14:39resolved

   This incident has been resolved.

1. 2026年5月27日 UTC 13:14investigating

   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. 2026年5月27日 UTC 13:32monitoring

   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. 2026年5月28日 UTC 13:47resolved

   This incident has been resolved.

1. 2026年5月26日 UTC 15:35investigating

   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. 2026年5月26日 UTC 15:59monitoring

   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. 2026年5月27日 UTC 13:15resolved

   This incident has been resolved.

1. 2026年5月21日 UTC 12:41investigating

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

2. 2026年5月21日 UTC 12:51monitoring

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

3. 2026年5月21日 UTC 20:34resolved

   This incident has been resolved.

1. 2026年5月14日 UTC 13:12investigating

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

2. 2026年5月14日 UTC 13:22monitoring

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

3. 2026年5月15日 UTC 14:13resolved

   This incident has been resolved.

1. 2026年5月14日 UTC 13:11investigating

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

2. 2026年5月14日 UTC 13:21monitoring

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

3. 2026年5月15日 UTC 14:13resolved

   This incident has been resolved.

1. 2026年5月13日 UTC 06:14investigating

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

2. 2026年5月13日 UTC 06:25monitoring

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

3. 2026年5月13日 UTC 14:26monitoring

   We are continuing to monitor for any further issues.

4. 2026年5月13日 UTC 14:26resolved

   This incident has been resolved.

1. 2026年5月6日 UTC 13:53investigating

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

2. 2026年5月6日 UTC 14:03monitoring

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

3. 2026年5月7日 UTC 14:06resolved

   This incident has been resolved.

1. 2026年5月6日 UTC 13:52investigating

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

2. 2026年5月6日 UTC 14:03monitoring

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

3. 2026年5月7日 UTC 14:06resolved

   This incident has been resolved.

1. 2026年4月21日 UTC 02:59investigating

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

2. 2026年4月21日 UTC 04:00identified

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

3. 2026年4月21日 UTC 04:00monitoring

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

4. 2026年4月21日 UTC 04:28resolved

   This incident has been resolved.

1. 2026年4月20日 UTC 23:43investigating

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

2. 2026年4月20日 UTC 23:54monitoring

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

3. 2026年4月21日 UTC 02:58monitoring

   We are continuing to monitor for any further issues.

4. 2026年4月21日 UTC 02:59resolved

   This incident has been resolved.

1. 2026年4月16日 UTC 16:19investigating

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

2. 2026年4月16日 UTC 16:30monitoring

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

3. 2026年4月16日 UTC 21:20resolved

   This incident has been resolved.

1. 2026年4月16日 UTC 06:49investigating

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

2. 2026年4月16日 UTC 07:04monitoring

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

3. 2026年4月16日 UTC 13:13resolved

   This incident has been resolved.

1. 2026年4月15日 UTC 14:39investigating

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

2. 2026年4月15日 UTC 14:50monitoring

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

3. 2026年4月15日 UTC 20:03resolved

   This incident has been resolved.

1. 2026年4月10日 UTC 07:15investigating

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

2. 2026年4月10日 UTC 07:26monitoring

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

3. 2026年4月10日 UTC 19:05resolved

   This incident has been resolved.

1. 2026年2月4日 UTC 06:41investigating

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

2. 2026年2月4日 UTC 06:59monitoring

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

3. 2026年3月4日 UTC 16:32resolved

   This incident has been resolved.

1. 2026年1月28日 UTC 06:26investigating

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

2. 2026年1月28日 UTC 07:05monitoring

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

3. 2026年1月28日 UTC 21:08resolved

   This incident has been resolved.

1. 2026年1月26日 UTC 17:08investigating

   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. 2026年1月26日 UTC 20:06monitoring

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

3. 2026年1月27日 UTC 22:26resolved

   This incident has been resolved.