Historial de interrupciones de Onfleet

1. 19 de agosto de 2026 a las 19:00 UTCinvestigating

   Hemos recibido informes de elementos que no se cargan en la vista del mapa, específicamente relacionados con elementos del equipo de conductor que afectan la visualización de tareas y posiblemente análisis. Nuestro equipo está investigando ahora.

2. 19 de agosto de 2026 a las 20:05 UTCmonitoring

   Un hotfix está desplegado, los elementos deben aparecer en el panel de control ahora. Actualmente estamos monitoreando la solución para asegurarnos de que todo sea estable.

3. 19 de agosto de 2026 a las 20:42 UTCresolved

   Este incidente ha sido resuelto, la barra lateral de Map View ha vuelto a la normalidad.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de julio de 2026 a las 22:45 UTCinvestigating

   Algunos clientes están encontrando errores al crear manifiestos. El equipo está investigando.

2. 23 de julio de 2026 a las 22:55 UTCidentified

   La cuestión parece estar relacionada con un cambio reciente de infraestructura. Se está preparando una solución.

3. 23 de julio de 2026 a las 23:07 UTCmonitoring

   Se ha aplicado una solución y el equipo está vigilando para confirmar la cuestión.

4. 23 de julio de 2026 a las 23:14 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de julio de 2026 a las 5:05 UTCinvestigating

   Un subconjunto de nuestros clientes de EE.UU. puede ser impactado por un error de envío SMS. Estamos trabajando con proveedores para resolver este problema ahora.

2. 22 de julio de 2026 a las 12:33 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 22 de julio de 2026 a las 17:44 UTCmonitoring

   Actualización - Envío de SMS para clientes estadounidenses Se ha restablecido la mayoría de las notificaciones de SMS afectadas. A principios de esta mañana, reenviamos el tráfico a través de un proveedor de telefonía de respaldo después de que una interrupción del lado del transportista afectara la entrega en uno de los números de nuestro proveedor primario. Sigue habiendo un pequeño número de fallos de entrega residual, lo que afecta a un subconjunto limitado de notificaciones. Una solución está planificada y esperamos que estos sean resueltos hoy. Actualizaremos esta página cuando se resuelva completamente. Nos disculpamos por la perturbación y apreciamos su paciencia.

4. 22 de julio de 2026 a las 20:47 UTCresolved

   El incidente se ha resuelto y la funcionalidad SMS está completamente restaurada. Tenga en cuenta que los mensajes SMS pueden mostrar un número de teléfono diferente hasta que hayamos resuelto el problema con nuestro proveedor primario.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 2:00 UTCinvestigating

   Integración con resultados de POS en la pantalla de pérdida en la flota Actualmente estamos investigando un problema que afecta a los clientes que crean tareas a través de integraciones de terceros POS o API. Las tareas creadas a través de estas integraciones pueden no aparecer en el panel de la flota, aunque hayan sido creadas con éxito. Qué se ve afectada: Tareas creadas a través de integraciones API (por ejemplo, sistemas POS, plataformas de terceros) Visibilidad del panel de control de esas tareas Lo que no se ve afectado: Creación de tareas en sí misma: se están creando tareas con éxito Tareas creadas manualmente en el Dashboard Hemos identificado la causa probable y estamos trabajando en una solución. Proporcionaremos una actualización tan pronto como esté disponible. Nos disculpamos por la molestia.

2. 10 de julio de 2026 a las 2:00 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 10 de julio de 2026 a las 2:29 UTCresolved

   Este incidente ha sido resuelto. Las tareas creadas a través de las integraciones de API ahora se mostrarán correctamente en el panel Onfleet. Si usted cree que cualquier tarea creada durante la ventana afectada todavía falta, por favor contacte con nuestro equipo de soporte y le ayudaremos con la remediación.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de junio de 2026 a las 17:30 UTCidentified

   We've identified an issue affecting anonymized (masked-number) text messaging between drivers and recipients for Canadian customers. Standard delivery notifications are not affected. Our engineering team has identified the cause and is actively working on a fix.

2. 18 de junio de 2026 a las 21:13 UTCmonitoring

   We have deployed a fix and are monitoring the results. Affected users should now see normal service restored.

3. 19 de junio de 2026 a las 0:02 UTCresolved

   Anonymized text service has been resolved for affected customers

1. 17 de junio de 2026 a las 18:39 UTCinvestigating

   El SMS canadiense servido por código corto está experimentando fallos de entrega. Estamos trabajando con los proveedores para resolver este problema.

2. 17 de junio de 2026 a las 21:55 UTCresolved

   Se ha aplicado una solución y el sistema está en pleno funcionamiento. Estamos monitoreando activamente para garantizar la estabilidad.

3. 10 de julio de 2026 a las 18:12 UTCpostmortem

   El 17 de junio, nuestro código corto común de SMS canadiense fue suspendido temporalmente después de una revisión del cumplimiento del transportista, que interrumpió las notificaciones de envío de SMS para los destinatarios canadienses. Rerouted traffic through an alternative provider the same afternoon to restore notifications, and fully restored driver-to-recipient messaging the following day. El examen de cumplimiento ha concluido desde entonces sin sanciones, se ha restablecido el código breve y todo el servicio funciona normalmente. Nos disculpamos por la interrupción. Si tiene alguna pregunta, nuestro equipo de apoyo está encantado de ayudar y puede ser alcanzado en [[email protected]](mailto:[email protected])

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de mayo de 2026 a las 20:39 UTCidentified

   We are currently experiencing an outage affecting the Integrations Marketplace component. Our engineering team has identified the issue and is actively working to deploy a fix as quickly as possible. We understand the impact this may have on your operations and appreciate your patience while we work to restore full functionality. Further updates will be provided as progress is made.

2. 14 de mayo de 2026 a las 21:45 UTCresolved

   The issue affecting the Integrations Marketplace component has been resolved. Our team deployed the fix successfully, and services are now operating normally. We will continue to monitor the platform closely to ensure stability. Thank you for your patience and understanding.

1. 7 de abril de 2026 a las 18:42 UTCidentified

   An issue has been detected in the release this morning that resulted in degraded performance with task selection. The team is rolling back this release and monitoring the update.

2. 7 de abril de 2026 a las 18:57 UTCmonitoring

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

3. 7 de abril de 2026 a las 19:06 UTCresolved

   This incident has been resolved.

4. 8 de abril de 2026 a las 23:32 UTCpostmortem

   On April 7th, 2026, from approximately 11:08–11:58 AM PDT, some customers experienced out of memory errors in Firefox. This was caused by a bug introduced in a release deployed earlier that day, which introduced a memory leak for customers using this browser. We rolled back the release at 11:58 AM PDT and confirmed full system stability by 12:13 PM PDT. We apologize for the disruption and are examining memory usage and other possible runtime issues with this patch.

1. 3 de abril de 2026 a las 0:54 UTCinvestigating

   We have located the issue and we are working to mitigate it ASAP.

2. 3 de abril de 2026 a las 1:15 UTCmonitoring

   We have identified a potential fix and are monitoring the situation.

3. 3 de abril de 2026 a las 1:27 UTCresolved

   This incident has been resolved.

4. 6 de abril de 2026 a las 17:31 UTCpostmortem

   On April 2, 2026, from approximately 5:00–6:07 PM PDT, some customers experienced dashboard crashes when selecting tasks. This was caused by a bug introduced in a release deployed earlier that day, which caused a crash under high task-count conditions. We rolled back the release at 5:44 PM PDT and confirmed full system stability by 6:07 PM PDT. We apologize for the disruption and are working to resolve the underlying issue before re-releasing.

1. 16 de marzo de 2026 a las 21:11 UTCinvestigating

   Our infrastructure team has rolled out a change to proof of delivery image hosting, and some notification steps were not followed. The change is being rolled back - if you are having issues retrieving images please don't hesitate to reach out to [email protected] for updated instructions

2. 16 de marzo de 2026 a las 21:15 UTCmonitoring

   A rollback has been put in place - legacy image URLs should now be working. Our documentation will be updated shortly.

3. 16 de marzo de 2026 a las 21:34 UTCresolved

   This issue should now be resolved by rollback. Notice will be sent in advance of changes.

1. 3 de noviembre de 2025 a las 21:11 UTCinvestigating

   Route manifest generation and the integrations configuration page are currently affected by an authentication issue. The team is investigating at high priority.

2. 3 de noviembre de 2025 a las 21:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 de noviembre de 2025 a las 21:40 UTCmonitoring

   The team has traced the issue to a recent infrastructure configuration adjustment. A fix is being put in place now and the system should be stabilizing over the next 10-15 minutes.

4. 3 de noviembre de 2025 a las 21:49 UTCresolved

   We believe that the issue should now be resolved. Please reach out to Onfleet support with any lingering concerns.

1. 22 de octubre de 2025 a las 0:02 UTCinvestigating

   The usual task color-coding is not currently functioning as expected. All tasks are being displayed as the default gray color. Other functions should not be affected. The team is investigating.

2. 22 de octubre de 2025 a las 0:41 UTCmonitoring

   The issue has been tracked to a failed deployment rollback and a fix is now in place. The dashboard should now be operational as normal.

3. 22 de octubre de 2025 a las 1:01 UTCresolved

   The dashboard display behavior has returned to normal.

1. 20 de octubre de 2025 a las 13:14 UTCresolved

   AWS has fully recovered from a service disruption that occurred between Oct 20, 12:11 AM and 3:35 AM PDT, which caused elevated error rates and delays across some systems. Since our infrastructure relies on AWS services, we’re sharing this update for transparency — all systems have now returned to normal operation, and no further impact is expected.

1. 15 de octubre de 2025 a las 18:37 UTCinvestigating

   The Onfleet dashboard is currently experiencing performance issues - the team is investigating.

2. 15 de octubre de 2025 a las 18:38 UTCinvestigating

   Initial indications relate to an issue with a server restart. The team is investigating with top priority.

3. 15 de octubre de 2025 a las 19:12 UTCmonitoring

   The system has been rolled back to a known good state and performance is stabilizing.

4. 15 de octubre de 2025 a las 20:12 UTCresolved

   The system has been stabilized via a rollback to a known good state and consistency check have completed. Please report any lingering issues to Onfleet support.

1. 14 de julio de 2025 a las 19:00 UTCinvestigating

   We are experiencing an emergent issue affecting overall system performance. All system functions are available with decreased performance. Our team is actively working to mitigate this issue.

2. 14 de julio de 2025 a las 21:07 UTCmonitoring

   We are seeing system latency normalizing after putting some mitigations in place. Our infrastructure and database teams are continuing to monitor this situation.

3. 14 de julio de 2025 a las 22:06 UTCresolved

   System responsiveness is returning to normal. Our engineering teams will continue to work on root causes to avoid latency spikes in the future.

4. 17 de julio de 2025 a las 19:10 UTCpostmortem

   We have just concluded a major effort to diagnose and address the periodic performance decreases that have recently affected the Onfleet system. At this time, we believe that bottlenecks have been identified and that the root causes have been addressed, and we are observing improvements on performance-related metrics across the board. This was a major effort that included the following: * Database performance improvements, by means of node redistribution, query optimization, and adjustment of indices * Refactoring of the primary dashboard-oriented data loading endpoints * Improvements to our webhook message processing system * Development of a modern incremental fetching scheme to decrease dashboard lock time * Significant adjustments to our internal server architecture provisioning In aggregate, these changes are not only allowing the system to cope with higher load levels, but are also delivering an improved performance baseline. Our team will continue efforts to improve our instrumentation in order to proactively identify choke points in the future. Additionally, the team will maintain a focus on performance improvements with a particular focus on customers with high task usage.

1. 30 de junio de 2025 a las 18:22 UTCinvestigating

   Monitoring indicates increased response times overall. Our teams are investigating the issue.

2. 30 de junio de 2025 a las 18:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 de julio de 2025 a las 14:08 UTCresolved

   This incident has been resolved.

1. 9 de junio de 2025 a las 23:30 UTCinvestigating

   There is currently an issue blocking initial logins with new devices on the iOS app. Most devices that have previously logged in will not be affected. The team is investigating this now.

2. 10 de junio de 2025 a las 0:02 UTCidentified

   The issue has been identified as an issue with a deployment script. A fix is in process and the system is stabilizing.

3. 10 de junio de 2025 a las 1:11 UTCresolved

   The team has applied the fix for the configuration issue causing provisioning problems. The issue should be fully resolved now.

1. 30 de mayo de 2025 a las 21:39 UTCinvestigating

   We are experiencing errors related to ETA calculations

2. 30 de mayo de 2025 a las 23:57 UTCresolved

   The ETA calculation issue has been tracked to a configuration issue, and has now been identified and resolved. We will be improving our monitoring and response process to handle similar issues more expediently in the future

1. 20 de mayo de 2025 a las 23:56 UTCinvestigating

   We are currently experiencing an issue where webhooks are not firing when an image is uploaded. A fix has been found and we are in the process of testing and deploying

2. 20 de mayo de 2025 a las 23:56 UTCidentified

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

3. 21 de mayo de 2025 a las 0:01 UTCmonitoring

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

4. 21 de mayo de 2025 a las 0:13 UTCresolved

   This incident has been resolved.

1. 5 de mayo de 2025 a las 16:54 UTCinvestigating

   Monitoring indicates increased response times overall. Our infrastructure teams are investigating the issue.

2. 5 de mayo de 2025 a las 18:23 UTCidentified

   The team has identified some changes to database queries to alleviate this issue, and will be publishing these changes as soon as possible.

3. 5 de mayo de 2025 a las 20:25 UTCresolved

   System performance has improved significantly and most if not all functions should be operating without excessive delay. Further adjustments to database queries are in progress to avoid this issue in the future.