Histórico de interrupções do Onfleet

1. 19 Eost 2026 da 19:00 UTCinvestigating

   Recebemos relatórios de elementos que não são carregados na vista do mapa, especificamente relacionados com elementos da equipe do driver que afetam a exibição de tarefas e possivelmente análises. A nossa equipa está a investigar agora.

2. 19 Eost 2026 da 20:05 UTCmonitoring

   Um hotfix é implantado, os elementos devem aparecer no painel agora. Estamos atualmente monitorando a correção para garantir que tudo está estável.

3. 19 Eost 2026 da 20:42 UTCresolved

   Este incidente foi resolvido, a barra lateral Map View voltou ao normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 22:45 UTCinvestigating

   Alguns clientes estão encontrando erros ao criar manifestos. A equipa está a investigar.

2. 23 Gouere 2026 da 22:55 UTCidentified

   A questão parece estar relacionada com uma recente mudança de infra-estrutura. Está a ser preparada uma solução.

3. 23 Gouere 2026 da 23:07 UTCmonitoring

   Uma correção foi aplicada e a equipe está monitorando para confirmar que o problema está resolvido.

4. 23 Gouere 2026 da 23:14 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 05:05 UTCinvestigating

   Um subconjunto de nossos clientes EUA pode ser impactado por uma falha de entrega de SMS. Estamos a trabalhar com fornecedores para resolver esta questão agora.

2. 22 Gouere 2026 da 12:33 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 22 Gouere 2026 da 17:44 UTCmonitoring

   Atualizar -- Entrega de SMS para clientes dos EUA A maioria das notificações SMS afetadas foram restauradas. No início desta manhã, redireccionámos o tráfego através de um fornecedor de telefonia de reserva após uma interrupção do lado da transportadora ter afectado a entrega num dos números do nosso fornecedor primário. Resta um pequeno número de falhas residuais de entrega, afetando um subconjunto limitado de notificações. Planeamos uma solução e esperamos que esta seja resolvida hoje. Atualizaremos esta página quando estiver totalmente resolvida. Pedimos desculpa pela interrupção e apreciamos a sua paciência.

4. 22 Gouere 2026 da 20:47 UTCresolved

   O incidente foi resolvido e a funcionalidade SMS está totalmente restaurada. Por favor, note que as mensagens SMS podem mostrar um número de telefone diferente até que tenhamos resolvido o problema com o nosso provedor primário.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 02:00 UTCinvestigating

   Integração com os resultados de POS upstream em Exibição em Falta na Onfleet Atualmente estamos investigando um problema que afeta clientes que criam tarefas através de integração de POS ou APIs de terceiros. Tarefas criadas através dessas integrações podem não aparecer no Painel Onfleet, mesmo que tenham sido criadas com sucesso. O que é afectado: Tarefas criadas através de integrações API (por exemplo, sistemas POS, plataformas de terceiros) Visibilidade do painel dessas tarefas O que não é afectado: Criação de tarefas — as tarefas estão a ser criadas com sucesso Tarefas criadas manualmente no Painel Identificamos a causa provável e estamos a trabalhar numa solução. Nós forneceremos uma atualização assim que estiver disponível. Pedimos desculpa pelo inconveniente.

2. 10 Gouere 2026 da 02:00 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 10 Gouere 2026 da 02:29 UTCresolved

   Este incidente foi resolvido. As tarefas criadas através de integrações API agora serão exibidas corretamente no Painel Onfleet. Se você acredita que quaisquer tarefas criadas durante a janela afetada ainda estão faltando, entre em contato com nossa equipe de suporte e nós ajudaremos com a reparação.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 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 Mezheven 2026 da 21:13 UTCmonitoring

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

3. 19 Mezheven 2026 da 00:02 UTCresolved

   Anonymized text service has been resolved for affected customers

1. 17 Mezheven 2026 da 18:39 UTCinvestigating

   SMS canadense servido por shortcode está atualmente experimentando falhas de entrega. Estamos a trabalhar com os fornecedores para resolver esta questão.

2. 17 Mezheven 2026 da 21:55 UTCresolved

   Uma correção foi aplicada e o sistema está agora totalmente operacional. Estamos a monitorizar activamente para garantir a estabilidade.

3. 10 Gouere 2026 da 18:12 UTCpostmortem

   Em 17 de junho, nosso código curto de SMS canadense compartilhado foi temporariamente suspenso após uma revisão de conformidade da operadora, que interrompeu as notificações de entrega de SMS para os destinatários canadenses. Nós redirecionamos o tráfego através de um provedor alternativo na mesma tarde para restaurar as notificações, e totalmente restaurado driver-to-recipient mensagens no dia seguinte. A revisão de conformidade concluiu desde então sem penalidades, o código curto foi reintegrado, e todo o serviço está funcionando normalmente. Pedimos desculpa pela interrupção. Se você tiver alguma dúvida, nossa equipe de suporte está feliz em ajudar e pode ser contatada em [[email protected]](mailto:[email protected])

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Mae 2026 da 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 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 18:57 UTCmonitoring

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

3. 7 Ebrel 2026 da 19:06 UTCresolved

   This incident has been resolved.

4. 8 Ebrel 2026 da 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 Ebrel 2026 da 00:54 UTCinvestigating

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

2. 3 Ebrel 2026 da 01:15 UTCmonitoring

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

3. 3 Ebrel 2026 da 01:27 UTCresolved

   This incident has been resolved.

4. 6 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 21:34 UTCresolved

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

1. 3 Du 2025 da 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 Du 2025 da 21:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 Du 2025 da 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 Du 2025 da 21:49 UTCresolved

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

1. 22 Here 2025 da 00: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 Here 2025 da 00: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 Here 2025 da 01:01 UTCresolved

   The dashboard display behavior has returned to normal.

1. 20 Here 2025 da 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 Here 2025 da 18:37 UTCinvestigating

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

2. 15 Here 2025 da 18:38 UTCinvestigating

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

3. 15 Here 2025 da 19:12 UTCmonitoring

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

4. 15 Here 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Mezheven 2025 da 18:22 UTCinvestigating

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

2. 30 Mezheven 2025 da 18:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 Gouere 2025 da 14:08 UTCresolved

   This incident has been resolved.

1. 9 Mezheven 2025 da 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 Mezheven 2025 da 00: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 Mezheven 2025 da 01:11 UTCresolved

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

1. 30 Mae 2025 da 21:39 UTCinvestigating

   We are experiencing errors related to ETA calculations

2. 30 Mae 2025 da 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 Mae 2025 da 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 Mae 2025 da 23:56 UTCidentified

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

3. 21 Mae 2025 da 00:01 UTCmonitoring

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

4. 21 Mae 2025 da 00:13 UTCresolved

   This incident has been resolved.

1. 5 Mae 2025 da 16:54 UTCinvestigating

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

2. 5 Mae 2025 da 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 Mae 2025 da 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.