Istoricul incidentelor Onfleet

1. 19 august 2026 la 19:00 UTCinvestigating

   Am primit rapoarte de elemente care nu se încarcă pe hartă, în special în ceea ce privește elementele echipei de șoferi care afectează afișarea sarcinilor și, eventual, analiza. Echipa noastră investighează acum.

2. 19 august 2026 la 20:05 UTCmonitoring

   Un hotfix este implementat, elementele ar trebui să apară pe bord acum. În prezent monitorizăm fixarea pentru a ne asigura că totul este stabil.

3. 19 august 2026 la 20:42 UTCresolved

   Acest incident a fost rezolvat, bara laterală Map View a revenit la normal.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 22:45 UTCinvestigating

   Unii clienţi întâmpină erori atunci când creează manifeste. Echipa investighează.

2. 23 iulie 2026 la 22:55 UTCidentified

   Problema pare să fie legată de o schimbare recentă a infrastructurii. Un fix este pregătit.

3. 23 iulie 2026 la 23:07 UTCmonitoring

   A fost aplicat un fix și echipa monitorizează pentru a confirma problema este rezolvată.

4. 23 iulie 2026 la 23:14 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iulie 2026 la 05:05 UTCinvestigating

   Un subset al clienților noștri SUA poate fi afectat de o eroare de livrare SMS. Lucrăm cu furnizori pentru a rezolva această problemă acum.

2. 22 iulie 2026 la 12:33 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 22 iulie 2026 la 17:44 UTCmonitoring

   Actualizare -- SMS Livrare pentru clientii SUA Majoritatea notificărilor SMS afectate au fost restaurate. În această dimineaţă, am redirecţionat traficul printr-un furnizor de telefonie de rezervă după o întrerupere a transportului a afectat livrarea unuia dintre numerele furnizorului nostru primar. Există în continuare un număr mic de deficiențe reziduale ale livrării, care afectează un subset limitat de notificări. Este planificat un fix şi ne aşteptăm ca acestea să fie rezolvate astăzi. Vom actualiza această pagină atunci când complet rezolvate. Ne cerem scuze pentru întrerupere şi apreciem răbdarea ta.

4. 22 iulie 2026 la 20:47 UTCresolved

   Incidentul a fost rezolvat și funcționalitatea SMS este complet restaurată. Vă rugăm să rețineți că mesajele SMS pot arăta un număr de telefon diferit până când vom rezolva problema cu furnizorul nostru primar.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 02:00 UTCinvestigating

   Integrare cu rezultatele POS în amonte în Display-ul de pe Onfleet Investigăm în prezent o problemă care afectează clienţii care creează sarcini prin integrarea unor terţe părţi POS sau API. Sarcinile create prin intermediul acestor integrări pot să nu apară în Dashboard-ul Flotei, chiar dacă au fost create cu succes. Ce este afectat: Sarcini create prin integrarea API (de exemplu, sisteme POS, platforme terțe) Vizibilitatea tabloului de bord a acestor sarcini Ce nu este afectat: Crearea de sarcini în sine sunt create cu succes Sarcini create manual în tabloul de bord Am identificat cauza probabilă şi lucrăm la o soluţie. Vom oferi o actualizare de îndată ce unul este disponibil. Ne cerem scuze pentru deranj.

2. 10 iulie 2026 la 02:00 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 10 iulie 2026 la 02:29 UTCresolved

   Acest incident a fost rezolvat. Sarcinile create prin integrarea API vor afișa acum corect în Dashboard Flotei On. Dacă credeți că orice sarcini create în timpul ferestrei afectate sunt încă lipsesc, vă rugăm să contactați echipa noastră de sprijin și vă vom ajuta cu remediere.

Traducere automată din actualizarea oficială a incidentului.

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

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

3. 19 iunie 2026 la 00:02 UTCresolved

   Anonymized text service has been resolved for affected customers

1. 17 iunie 2026 la 18:39 UTCinvestigating

   SMS canadian deservit de cod scurt se confruntă în prezent eșecuri de livrare. Lucrăm cu furnizorii pentru a rezolva această problemă.

2. 17 iunie 2026 la 21:55 UTCresolved

   Un fix a fost aplicat și sistemul este acum complet operațional. Monitorizăm activ pentru a asigura stabilitatea.

3. 10 iulie 2026 la 18:12 UTCpostmortem

   Pe 17 iunie, codul nostru scurt de SMS canadian comun a fost suspendat temporar în urma unei evaluări a conformității transportatorului, care a întrerupt notificările de livrare SMS pentru destinatarii canadieni. Am redirecţionat traficul printr-un furnizor alternativ în aceeaşi după-amiază pentru a restabili notificările, şi am restaurat complet mesajele de la şofer la destinatar în ziua următoare. Revizuirea conformității s-a încheiat fără sancțiuni, codul scurt a fost restabilit și toate serviciile funcționează în mod normal. Ne cerem scuze pentru întrerupere. Dacă aveți întrebări, echipa noastră de sprijin este bucuroasă să ajute și poate fi contactată la [[email protected]](mailto:[email protected])

Traducere automată din actualizarea oficială a incidentului.

1. 14 mai 2026 la 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 mai 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 18:57 UTCmonitoring

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

3. 7 aprilie 2026 la 19:06 UTCresolved

   This incident has been resolved.

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

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

2. 3 aprilie 2026 la 01:15 UTCmonitoring

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

3. 3 aprilie 2026 la 01:27 UTCresolved

   This incident has been resolved.

4. 6 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 21:34 UTCresolved

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

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

   We are continuing to investigate this issue.

3. 3 noiembrie 2025 la 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 noiembrie 2025 la 21:49 UTCresolved

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

1. 22 octombrie 2025 la 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 octombrie 2025 la 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 octombrie 2025 la 01:01 UTCresolved

   The dashboard display behavior has returned to normal.

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

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

2. 15 octombrie 2025 la 18:38 UTCinvestigating

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

3. 15 octombrie 2025 la 19:12 UTCmonitoring

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

4. 15 octombrie 2025 la 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 iulie 2025 la 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 iulie 2025 la 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 iulie 2025 la 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 iulie 2025 la 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 iunie 2025 la 18:22 UTCinvestigating

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

2. 30 iunie 2025 la 18:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 iulie 2025 la 14:08 UTCresolved

   This incident has been resolved.

1. 9 iunie 2025 la 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 iunie 2025 la 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 iunie 2025 la 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 mai 2025 la 21:39 UTCinvestigating

   We are experiencing errors related to ETA calculations

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

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

3. 21 mai 2025 la 00:01 UTCmonitoring

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

4. 21 mai 2025 la 00:13 UTCresolved

   This incident has been resolved.

1. 5 mai 2025 la 16:54 UTCinvestigating

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

2. 5 mai 2025 la 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 mai 2025 la 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.