Onfleet driftsforstyrrelser

1. 19. august 2026 kl. 19.00 UTCinvestigating

   Vi har modtaget rapporter om elementer, der ikke indlæses i kortvisning, specielt relateret til driverteamelementer, som påvirker visning af opgaveopgaver og eventuelt analytics. Vores hold undersøger det nu.

2. 19. august 2026 kl. 20.05 UTCmonitoring

   Et hotfix er indsat, elementerne skal vises på instrumentbrættet nu. Vi overvåger i øjeblikket fixet for at sikre, at alt er stabilt.

3. 19. august 2026 kl. 20.42 UTCresolved

   Denne hændelse er blevet løst, kortet View sidebar er vendt tilbage til normal.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 22.45 UTCinvestigating

   Nogle kunder støder på fejl, når de opretter manifester. Holdet efterforsker.

2. 23. juli 2026 kl. 22.55 UTCidentified

   Spørgsmålet synes at være relateret til en nylig infrastrukturændring. Et fix er under forberedelse.

3. 23. juli 2026 kl. 23.07 UTCmonitoring

   Et fix er blevet anvendt, og holdet overvåger for at bekræfte problemet er løst.

4. 23. juli 2026 kl. 23.14 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juli 2026 kl. 05.05 UTCinvestigating

   En delmængde af vores amerikanske kunder kan blive påvirket af en SMS levering fejl. Vi samarbejder med udbyderne om at løse dette problem nu.

2. 22. juli 2026 kl. 12.33 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 22. juli 2026 kl. 17.44 UTCmonitoring

   Opdatering -- SMS levering til amerikanske kunder De fleste berørte SMS-meddelelser er blevet genoprettet. Tidligt i morges, vi omdirigeret trafik gennem en backup telefoni udbyder efter en carrier-side afbrydelse påvirket levering på en af vores primære udbyder numre. Der er stadig et lille antal resterende leveringsfejl, som påvirker en begrænset delmængde af anmeldelser. Der er planlagt en løsning, og vi forventer, at de bliver løst i dag. Vi opdaterer denne side, når den er løst. Vi undskylder forstyrrelsen og værdsætter din tålmodighed.

4. 22. juli 2026 kl. 20.47 UTCresolved

   Hændelsen er blevet løst, og SMS-funktionalitet er fuldt restaureret. Bemærk venligst, at SMS-beskeder kan vise et andet telefonnummer, indtil vi har løst problemet med vores primære udbyder.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 02.00 UTCinvestigating

   Integration med opstrøms POS resultater i Manglende Display på Onfleet Vi er i øjeblikket ved at undersøge et problem, der påvirker kunder, der skaber opgaver via tredjeparts POS eller API-integreringer. Opgaver skabt gennem disse integreringer kan ikke vises i Onfleet Dashboard, selv om de er blevet oprettet med succes. Hvad er påvirket: Opgaver oprettet via API-integreringer (f.eks. POS-systemer, tredjepartsplatforme) Dashboards synlighed af disse opgaver Hvad der ikke påvirkes: Selve opgaveskabelsen - opgaver er ved at blive skabt med succes Manuelt oprettede opgaver i instrumentbrættet Vi har identificeret den sandsynlige årsag og arbejder på et fix. Vi vil give en opdatering, så snart en er tilgængelig. Vi undskylder ulejligheden.

2. 10. juli 2026 kl. 02.00 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 10. juli 2026 kl. 02.29 UTCresolved

   Denne hændelse er blevet løst. Opgaver oprettet via API-integration vil nu vise korrekt i Onfleet Dashboard. Hvis du mener, at der stadig mangler opgaver i det berørte vindue, bedes du kontakte vores support team, og vi vil hjælpe med oprydning.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. juni 2026 kl. 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. juni 2026 kl. 21.13 UTCmonitoring

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

3. 19. juni 2026 kl. 00.02 UTCresolved

   Anonymized text service has been resolved for affected customers

1. 17. juni 2026 kl. 18.39 UTCinvestigating

   Canadisk SMS serveret af kortkode oplever i øjeblikket leveringsfejl. Vi samarbejder med udbyderne om at løse dette problem.

2. 17. juni 2026 kl. 21.55 UTCresolved

   Et fix er blevet anvendt, og systemet er nu fuldt funktionsdygtigt. Vi overvåger aktivt for at sikre stabilitet.

3. 10. juli 2026 kl. 18.12 UTCpostmortem

   Den 17. juni blev vores fælles canadiske SMS-kode midlertidigt suspenderet efter en gennemgang af luftfartsselskabets overholdelse, som afbrød SMS-leveringsmeddelelser for canadiske modtagere. Vi omdirigerede trafik gennem en alternativ udbyder samme eftermiddag for at gendanne meddelelser, og fuldt restaureret driverto- modtager messaging den følgende dag. Overholdelsesundersøgelsen er siden afsluttet med ingen sanktioner, den korte kode er blevet genindført, og al service fungerer normalt. Vi undskylder forstyrrelsen. Hvis du har spørgsmål, er vores support team glade for at hjælpe og kan nås på [support @ onfleet.com] (mailto: support @ onfleet.com)

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. maj 2026 kl. 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. maj 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 18.57 UTCmonitoring

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

3. 7. april 2026 kl. 19.06 UTCresolved

   This incident has been resolved.

4. 8. april 2026 kl. 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. april 2026 kl. 00.54 UTCinvestigating

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

2. 3. april 2026 kl. 01.15 UTCmonitoring

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

3. 3. april 2026 kl. 01.27 UTCresolved

   This incident has been resolved.

4. 6. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 21.34 UTCresolved

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

1. 3. november 2025 kl. 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. november 2025 kl. 21.11 UTCinvestigating

   We are continuing to investigate this issue.

3. 3. november 2025 kl. 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. november 2025 kl. 21.49 UTCresolved

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

1. 22. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 01.01 UTCresolved

   The dashboard display behavior has returned to normal.

1. 20. oktober 2025 kl. 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. oktober 2025 kl. 18.37 UTCinvestigating

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

2. 15. oktober 2025 kl. 18.38 UTCinvestigating

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

3. 15. oktober 2025 kl. 19.12 UTCmonitoring

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

4. 15. oktober 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juli 2025 kl. 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. juni 2025 kl. 18.22 UTCinvestigating

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

2. 30. juni 2025 kl. 18.23 UTCinvestigating

   We are continuing to investigate this issue.

3. 1. juli 2025 kl. 14.08 UTCresolved

   This incident has been resolved.

1. 9. juni 2025 kl. 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. juni 2025 kl. 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. juni 2025 kl. 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. maj 2025 kl. 21.39 UTCinvestigating

   We are experiencing errors related to ETA calculations

2. 30. maj 2025 kl. 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. maj 2025 kl. 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. maj 2025 kl. 23.56 UTCidentified

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

3. 21. maj 2025 kl. 00.01 UTCmonitoring

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

4. 21. maj 2025 kl. 00.13 UTCresolved

   This incident has been resolved.

1. 5. maj 2025 kl. 16.54 UTCinvestigating

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

2. 5. maj 2025 kl. 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. maj 2025 kl. 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.