Historique des pannes de Ubidots

1. 23 septembre 2026 à 13:38 UTCidentified

   Nous avons identifié un problème touchant la livraison des notifications par courriel, y compris les courriels d'alerte. Certains messages peuvent arriver en retard ou être filtrés dans des dossiers spam/junk. Notre équipe travaille activement à l'assainissement. SMS, webhook et autres canaux de notification ne sont pas touchés. En attendant, nous vous recommandons de vérifier votre dossier spam/junk et d'ajouter [email protected] à votre liste d'expéditeurs sécurisés. Nous publierons les mises à jour au fur et à mesure que la situation progresse.

2. 23 septembre 2026 à 15:33 UTCmonitoring

   Une correction a été mise en place et la notification par courriel est revenue à la normale. Nous surveillons étroitement la stabilité. Si vous ne voyez toujours pas les courriels d'alerte attendus, veuillez vérifier votre dossier spam/junk et ajouter [email protected] à votre liste d'expéditeurs sécurisés.

3. 23 septembre 2026 à 16:36 UTCresolved

   Cet incident a été résolu. Nous avons identifié la cause profonde de la dégradation de la livraison de courriels et avons déployé une correction. Les notifications par courriel, y compris les courriels d'alerte, sont livrées normalement. Si vous ne voyez toujours pas les courriels d'alerte attendus, veuillez vérifier votre dossier spam/junk et ajouter [email protected] à votre liste d'expéditeurs sécurisés, ou contacter notre équipe de support.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 10 juillet 2026 à 19:36 UTCinvestigating

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

2. 10 juillet 2026 à 19:47 UTCmonitoring

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

3. 10 juillet 2026 à 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 juillet 2026 à 19:51 UTCresolved

   This incident has been resolved.

1. 10 juillet 2026 à 01:09 UTCinvestigating

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

2. 10 juillet 2026 à 01:20 UTCmonitoring

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

3. 10 juillet 2026 à 14:39 UTCresolved

   This incident has been resolved.

1. 27 mai 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 mai 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 mai 2026 à 13:47 UTCresolved

   This incident has been resolved.

1. 26 mai 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 mai 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 mai 2026 à 13:15 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 à 12:41 UTCinvestigating

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

2. 21 mai 2026 à 12:51 UTCmonitoring

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

3. 21 mai 2026 à 20:34 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 à 13:12 UTCinvestigating

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

2. 14 mai 2026 à 13:22 UTCmonitoring

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

3. 15 mai 2026 à 14:13 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 à 13:11 UTCinvestigating

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

2. 14 mai 2026 à 13:21 UTCmonitoring

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

3. 15 mai 2026 à 14:13 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 à 06:14 UTCinvestigating

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

2. 13 mai 2026 à 06:25 UTCmonitoring

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

3. 13 mai 2026 à 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 mai 2026 à 14:26 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 à 13:53 UTCinvestigating

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

2. 6 mai 2026 à 14:03 UTCmonitoring

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

3. 7 mai 2026 à 14:06 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 à 13:52 UTCinvestigating

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

2. 6 mai 2026 à 14:03 UTCmonitoring

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

3. 7 mai 2026 à 14:06 UTCresolved

   This incident has been resolved.

1. 21 avril 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 avril 2026 à 04:00 UTCidentified

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

3. 21 avril 2026 à 04:00 UTCmonitoring

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

4. 21 avril 2026 à 04:28 UTCresolved

   This incident has been resolved.

1. 20 avril 2026 à 23:43 UTCinvestigating

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

2. 20 avril 2026 à 23:54 UTCmonitoring

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

3. 21 avril 2026 à 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 avril 2026 à 02:59 UTCresolved

   This incident has been resolved.

1. 16 avril 2026 à 16:19 UTCinvestigating

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

2. 16 avril 2026 à 16:30 UTCmonitoring

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

3. 16 avril 2026 à 21:20 UTCresolved

   This incident has been resolved.

1. 16 avril 2026 à 06:49 UTCinvestigating

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

2. 16 avril 2026 à 07:04 UTCmonitoring

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

3. 16 avril 2026 à 13:13 UTCresolved

   This incident has been resolved.

1. 15 avril 2026 à 14:39 UTCinvestigating

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

2. 15 avril 2026 à 14:50 UTCmonitoring

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

3. 15 avril 2026 à 20:03 UTCresolved

   This incident has been resolved.

1. 10 avril 2026 à 07:15 UTCinvestigating

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

2. 10 avril 2026 à 07:26 UTCmonitoring

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

3. 10 avril 2026 à 19:05 UTCresolved

   This incident has been resolved.

1. 4 février 2026 à 06:41 UTCinvestigating

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

2. 4 février 2026 à 06:59 UTCmonitoring

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

3. 4 mars 2026 à 16:32 UTCresolved

   This incident has been resolved.

1. 28 janvier 2026 à 06:26 UTCinvestigating

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

2. 28 janvier 2026 à 07:05 UTCmonitoring

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

3. 28 janvier 2026 à 21:08 UTCresolved

   This incident has been resolved.

1. 26 janvier 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 janvier 2026 à 20:06 UTCmonitoring

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

3. 27 janvier 2026 à 22:26 UTCresolved

   This incident has been resolved.