Ubidots の障害履歴

1. 2026年9月23日 13:38 UTCidentified

   アラートメールを含むメール通知の配信に影響を与える問題を特定しました。 一部のメッセージは、遅く到着するか、スパム/ジャンクフォルダにフィルタリングされる可能性があります。 私たちのチームは、積極的に是正に取り組んでいます。 SMS、webhookおよび他の通知チャネルは影響されません。 その間に、スパム/ジャンクフォルダを確認し、安全な送信者に[email protected]を追加することをお勧めします。 状況が進むにつれてアップデートを投稿します.

2. 2026年9月23日 15:33 UTCmonitoring

   修正が実装され、メール通知の配信が正常に戻りました。 安定性確認のため、密接に監視しています。 警告メールが見つからない場合は、迷惑メール/迷惑メールフォルダを確認し、迷惑メールリストに[email protected]を追加してください.

3. 2026年9月23日 16:36 UTCresolved

   この事件は解決しました。 当社は、メール配信劣化の根本原因を特定し、修正を実施しました。 アラートメールを含むメール通知は、通常配信されます。 警告メールが見つからない場合は、迷惑メール/迷惑メールフォルダを確認し、迷惑メールリストに[email protected]を追加するか、サポートチームに連絡してください.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月10日 19:36 UTCinvestigating

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

2. 2026年7月10日 19:47 UTCmonitoring

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

3. 2026年7月10日 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026年7月10日 19:51 UTCresolved

   This incident has been resolved.

1. 2026年7月10日 1:09 UTCinvestigating

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

2. 2026年7月10日 1:20 UTCmonitoring

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

3. 2026年7月10日 14:39 UTCresolved

   This incident has been resolved.

1. 2026年5月27日 13:14 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. 2026年5月27日 13:32 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. 2026年5月28日 13:47 UTCresolved

   This incident has been resolved.

1. 2026年5月26日 15:35 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. 2026年5月26日 15:59 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. 2026年5月27日 13:15 UTCresolved

   This incident has been resolved.

1. 2026年5月21日 12:41 UTCinvestigating

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

2. 2026年5月21日 12:51 UTCmonitoring

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

3. 2026年5月21日 20:34 UTCresolved

   This incident has been resolved.

1. 2026年5月14日 13:12 UTCinvestigating

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

2. 2026年5月14日 13:22 UTCmonitoring

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

3. 2026年5月15日 14:13 UTCresolved

   This incident has been resolved.

1. 2026年5月14日 13:11 UTCinvestigating

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

2. 2026年5月14日 13:21 UTCmonitoring

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

3. 2026年5月15日 14:13 UTCresolved

   This incident has been resolved.

1. 2026年5月13日 6:14 UTCinvestigating

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

2. 2026年5月13日 6:25 UTCmonitoring

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

3. 2026年5月13日 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026年5月13日 14:26 UTCresolved

   This incident has been resolved.

1. 2026年5月6日 13:53 UTCinvestigating

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

2. 2026年5月6日 14:03 UTCmonitoring

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

3. 2026年5月7日 14:06 UTCresolved

   This incident has been resolved.

1. 2026年5月6日 13:52 UTCinvestigating

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

2. 2026年5月6日 14:03 UTCmonitoring

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

3. 2026年5月7日 14:06 UTCresolved

   This incident has been resolved.

1. 2026年4月21日 2:59 UTCinvestigating

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

2. 2026年4月21日 4:00 UTCidentified

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

3. 2026年4月21日 4:00 UTCmonitoring

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

4. 2026年4月21日 4:28 UTCresolved

   This incident has been resolved.

1. 2026年4月20日 23:43 UTCinvestigating

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

2. 2026年4月20日 23:54 UTCmonitoring

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

3. 2026年4月21日 2:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026年4月21日 2:59 UTCresolved

   This incident has been resolved.

1. 2026年4月16日 16:19 UTCinvestigating

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

2. 2026年4月16日 16:30 UTCmonitoring

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

3. 2026年4月16日 21:20 UTCresolved

   This incident has been resolved.

1. 2026年4月16日 6:49 UTCinvestigating

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

2. 2026年4月16日 7:04 UTCmonitoring

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

3. 2026年4月16日 13:13 UTCresolved

   This incident has been resolved.

1. 2026年4月15日 14:39 UTCinvestigating

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

2. 2026年4月15日 14:50 UTCmonitoring

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

3. 2026年4月15日 20:03 UTCresolved

   This incident has been resolved.

1. 2026年4月10日 7:15 UTCinvestigating

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

2. 2026年4月10日 7:26 UTCmonitoring

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

3. 2026年4月10日 19:05 UTCresolved

   This incident has been resolved.

1. 2026年2月4日 6:41 UTCinvestigating

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

2. 2026年2月4日 6:59 UTCmonitoring

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

3. 2026年3月4日 16:32 UTCresolved

   This incident has been resolved.

1. 2026年1月28日 6:26 UTCinvestigating

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

2. 2026年1月28日 7:05 UTCmonitoring

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

3. 2026年1月28日 21:08 UTCresolved

   This incident has been resolved.

1. 2026年1月26日 17:08 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. 2026年1月26日 20:06 UTCmonitoring

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

3. 2026年1月27日 22:26 UTCresolved

   This incident has been resolved.