История сбоев Ubidots

1. 23 сентября 2026 г. в 13:38 UTCidentified

   Мы выявили проблему, затрагивающую доставку уведомлений по электронной почте, включая оповещения по электронной почте. Некоторые сообщения могут приходить с опозданием или фильтроваться в спам-папки. Наша команда активно работает над восстановлением. SMS, webhook и другие каналы уведомлений не затронуты. В то же время мы рекомендуем проверить вашу папку спама / мусора и добавить [email protected] в список безопасных отправителей. Мы будем публиковать обновления по мере развития ситуации.

2. 23 сентября 2026 г. в 15:33 UTCmonitoring

   Реализовано исправление, и доставка уведомлений по электронной почте вернулась к нормальному состоянию. Мы внимательно следим, чтобы подтвердить стабильность. Если вы все еще не видите ожидаемых писем с предупреждением, пожалуйста, проверьте свою папку спама / мусора и добавьте [email protected] в свой список безопасных отправителей.

3. 23 сентября 2026 г. в 16:36 UTCresolved

   Этот инцидент был урегулирован. Мы определили первопричину деградации доставки электронной почты и внедрили исправление. Уведомления по электронной почте, включая уведомления по электронной почте, доставляются обычно. Если вы все еще не видите ожидаемых писем с предупреждением, пожалуйста, проверьте свою папку спама / мусора и добавьте [email protected] в свой список безопасных отправителей или свяжитесь с нашей службой поддержки.

Автоматический перевод официального обновления инцидента.

1. 10 июля 2026 г. в 19:36 UTCinvestigating

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

2. 10 июля 2026 г. в 19:47 UTCmonitoring

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

3. 10 июля 2026 г. в 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 июля 2026 г. в 19:51 UTCresolved

   This incident has been resolved.

1. 10 июля 2026 г. в 01:09 UTCinvestigating

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

2. 10 июля 2026 г. в 01:20 UTCmonitoring

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

3. 10 июля 2026 г. в 14:39 UTCresolved

   This incident has been resolved.

1. 27 мая 2026 г. в 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. 27 мая 2026 г. в 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. 28 мая 2026 г. в 13:47 UTCresolved

   This incident has been resolved.

1. 26 мая 2026 г. в 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. 26 мая 2026 г. в 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. 27 мая 2026 г. в 13:15 UTCresolved

   This incident has been resolved.

1. 21 мая 2026 г. в 12:41 UTCinvestigating

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

2. 21 мая 2026 г. в 12:51 UTCmonitoring

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

3. 21 мая 2026 г. в 20:34 UTCresolved

   This incident has been resolved.

1. 14 мая 2026 г. в 13:12 UTCinvestigating

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

2. 14 мая 2026 г. в 13:22 UTCmonitoring

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

3. 15 мая 2026 г. в 14:13 UTCresolved

   This incident has been resolved.

1. 14 мая 2026 г. в 13:11 UTCinvestigating

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

2. 14 мая 2026 г. в 13:21 UTCmonitoring

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

3. 15 мая 2026 г. в 14:13 UTCresolved

   This incident has been resolved.

1. 13 мая 2026 г. в 06:14 UTCinvestigating

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

2. 13 мая 2026 г. в 06:25 UTCmonitoring

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

3. 13 мая 2026 г. в 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 мая 2026 г. в 14:26 UTCresolved

   This incident has been resolved.

1. 6 мая 2026 г. в 13:53 UTCinvestigating

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

2. 6 мая 2026 г. в 14:03 UTCmonitoring

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

3. 7 мая 2026 г. в 14:06 UTCresolved

   This incident has been resolved.

1. 6 мая 2026 г. в 13:52 UTCinvestigating

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

2. 6 мая 2026 г. в 14:03 UTCmonitoring

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

3. 7 мая 2026 г. в 14:06 UTCresolved

   This incident has been resolved.

1. 21 апреля 2026 г. в 02:59 UTCinvestigating

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

2. 21 апреля 2026 г. в 04:00 UTCidentified

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

3. 21 апреля 2026 г. в 04:00 UTCmonitoring

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

4. 21 апреля 2026 г. в 04:28 UTCresolved

   This incident has been resolved.

1. 20 апреля 2026 г. в 23:43 UTCinvestigating

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

2. 20 апреля 2026 г. в 23:54 UTCmonitoring

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

3. 21 апреля 2026 г. в 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 апреля 2026 г. в 02:59 UTCresolved

   This incident has been resolved.

1. 16 апреля 2026 г. в 16:19 UTCinvestigating

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

2. 16 апреля 2026 г. в 16:30 UTCmonitoring

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

3. 16 апреля 2026 г. в 21:20 UTCresolved

   This incident has been resolved.

1. 16 апреля 2026 г. в 06:49 UTCinvestigating

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

2. 16 апреля 2026 г. в 07:04 UTCmonitoring

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

3. 16 апреля 2026 г. в 13:13 UTCresolved

   This incident has been resolved.

1. 15 апреля 2026 г. в 14:39 UTCinvestigating

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

2. 15 апреля 2026 г. в 14:50 UTCmonitoring

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

3. 15 апреля 2026 г. в 20:03 UTCresolved

   This incident has been resolved.

1. 10 апреля 2026 г. в 07:15 UTCinvestigating

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

2. 10 апреля 2026 г. в 07:26 UTCmonitoring

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

3. 10 апреля 2026 г. в 19:05 UTCresolved

   This incident has been resolved.

1. 4 февраля 2026 г. в 06:41 UTCinvestigating

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

2. 4 февраля 2026 г. в 06:59 UTCmonitoring

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

3. 4 марта 2026 г. в 16:32 UTCresolved

   This incident has been resolved.

1. 28 января 2026 г. в 06:26 UTCinvestigating

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

2. 28 января 2026 г. в 07:05 UTCmonitoring

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

3. 28 января 2026 г. в 21:08 UTCresolved

   This incident has been resolved.

1. 26 января 2026 г. в 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. 26 января 2026 г. в 20:06 UTCmonitoring

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

3. 27 января 2026 г. в 22:26 UTCresolved

   This incident has been resolved.