Onfleet had 27 outages in the last 2 years totaling 73h 13m of downtime — averaging 1.1 incidents per month.
There were 27 Onfleet outages since July 30, 2024 totaling 73h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
Canadian SMS served by shortcode is currently experiencing delivery failures. We are working with the providers to resolve this issue.
A fix has been applied and the system is now fully operational. We are actively monitoring to ensure stability.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We have located the issue and we are working to mitigate it ASAP.
We have identified a potential fix and are monitoring the situation.
This incident has been resolved.
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.
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
A rollback has been put in place - legacy image URLs should now be working. Our documentation will be updated shortly.
This issue should now be resolved by rollback. Notice will be sent in advance of changes.
Route manifest generation and the integrations configuration page are currently affected by an authentication issue. The team is investigating at high priority.
We are continuing to investigate this issue.
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.
We believe that the issue should now be resolved. Please reach out to Onfleet support with any lingering concerns.
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.
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.
The dashboard display behavior has returned to normal.
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.
The Onfleet dashboard is currently experiencing performance issues - the team is investigating.
Initial indications relate to an issue with a server restart. The team is investigating with top priority.
The system has been rolled back to a known good state and performance is stabilizing.
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.
Monitoring indicates increased response times overall. Our teams are investigating the issue.
We are continuing to investigate this issue.
This incident has been resolved.
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.
The issue has been identified as an issue with a deployment script. A fix is in process and the system is stabilizing.
The team has applied the fix for the configuration issue causing provisioning problems. The issue should be fully resolved now.
We are experiencing errors related to ETA calculations
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
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
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We briefly experienced partial service outage and increased response times following an application update. All systems are now operating normally. We apologize for any inconvenience caused during this incident.
The increase in system latency was caused by a query which was designed to depend on a new database index, but the index had not been created in production at the time of the deployment. We are reviewing our deployment practices to add safeguards for this type of issue in the future.
Chat is currently unavailable due to an issue with an upstream provider.
The provider has confirmed the issue and identified a root cause. A fix should be available shortly.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
This incident has been resolved.
At this time the internal process for managing task creation queues for the asynchronous batch task creation endpoint is experiencing issues. This is being investigated with high urgency.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 11:45 a.m. and 12:20 p.m. PST, a batch request began to loop unexpectedly, interfering with each other and causing container contention. Because of how batch creations are processed, this prevented other jobs from being processed until they were cleared manually. Once the job was manually stopped, the system returned to normal batch processing. The team will implement enhanced monitoring to avoid this scenario in the future.
Route Optimizations are currently running very slowly or failing. Initial signs point to an issue with an upstream provider.
The upstream provider has confirmed the issue and is currently investigating the problem.
We have detected a slight decrease in errors for Route Optimization.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
“The Onfleet integrations subsystem is currently experiencing issues, blocking creation of manifests as well as some other 3rd party integrations.”
Our DevOps team was able to find a glitch within our AWS infrastructure that required a manual override. All systems are operationsal.
Route optimization was briefly unavailable due to an outage at a partner provider. Their issues have now been resolved, and monitoring indicates that all features are once again available.
We experienced a brief 1-minute outage due to a system restart around 2:40 Pacific. We apologize for any inconvenience caused. The services have been fully restored shortly after the incident.
A misconfigured firewall rule briefly caused login failures. The rules have been adjusted, and this should now be resolved.
The incident has been resolved.
While monitoring indicates that Onfleet systems are running normally, we are receiving reports of service unavailability affecting users in Australia and Southeast Asia. Initial assessments suggest this may be due to a network issue in ISPs from this region. We apologize for the inconvenience and will provide updates once we have more information. Thank you for your patience.
Impacted APAC customers have confirmed that they can now access the Onfleet application without any issues.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved. We apologize for the disruption and appreciate your understanding.