显示板/图像问题
Pending
受影响的组件
MapsDashboard
- investigating
我们收到关于未装入地图的内容的报告,具体涉及影响任务分配和可能分析的司机团队要素。 我们的团队正在调查.
- monitoring
安装了热接器 元素现在应该出现在仪表板上 我们目前正在监测修复工作,以确保一切稳定.
- resolved
这一事件已经解决,"地图视图"侧边栏已恢复正常.
自动翻译自官方事件更新。
56 Onfleet incidents · 2023年1月 — official updates, affected components, duration and resolution details.
我们收到关于未装入地图的内容的报告,具体涉及影响任务分配和可能分析的司机团队要素。 我们的团队正在调查.
安装了热接器 元素现在应该出现在仪表板上 我们目前正在监测修复工作,以确保一切稳定.
这一事件已经解决,"地图视图"侧边栏已恢复正常.
自动翻译自官方事件更新。
一些客户在创建货单时遇到错误. 调查组正在调查.
这个问题似乎与最近的基础设施变化有关。 正在准备解决.
已经采取了补救措施,该小组正在进行监测,以确认这一问题已经解决.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们的美国客户可能会受到短信发送故障的影响。 我们正在同提供方合作,以解决这一问题.
一项措施已经执行,我们正在监测结果.
更新 - 为美国客户发送短消息 大多数受影响的短信通知已经恢复。 今天清晨,我们通过一个备用电话供应商调整了交通路线,因为航母侧中断影响到我们主要供应商之一的交货。 少数剩余交付失败依然存在,影响到有限的部分通知。 计划进行补救,我们期望这些办法今天得到解决。 我们会更新这个页面 当完全解决。 我们为干扰道歉 并感谢你的耐心.
该事件已经解决并全面恢复了短信功能. 请注意,在与我们的主要提供者解决问题之前,短信可能显示不同的电话号码.
自动翻译自官方事件更新。
在 Onfleet 上缺失显示中与上游 POS 集成 我们正在调查一个影响到通过第三方POS或API集成创造任务的客户的问题。 通过这些集成创建的任务可能不会出现在Onfleet Dashboard上,尽管它们已经成功创建. 受影响的因素: 通过API集成(如POS系统,第三方平台)创建的任务 这些任务的可视性 未受影响者: 任务创建本身——任务正在成功创建中 在 Dashboard 中手工创建任务 我们已经查明了可能的原因,并正在设法解决问题。 一旦有最新资料,我们将立即提供。 我们为不方便而道歉.
这一问题已经确定,一个解决办法正在实施之中.
这一事件已经得到解决。 通过API集成创建的任务现在将在Onfleet Dashboard中正确显示. 如果您认为在受影响的窗口中创建的任何任务仍然缺失,请联系我们的支援团队,我们将协助补救.
自动翻译自官方事件更新。
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.
We have deployed a fix and are monitoring the results. Affected users should now see normal service restored.
Anonymized text service has been resolved for affected customers
加拿大短码服务短信目前出现发送故障. 我们正在同提供方合作来解决这个问题.
已采用了一个固定系统,该系统现已全面运作。 我们正在积极监测,以确保稳定.
6月17日,我们共享的加拿大短信短码在承运人履约审查后被暂时中止,中断了向加拿大收件人发送短信的通知. 我们于同日下午通过另一家供应商调整了交通路线,以恢复通知,并于次日全面恢复司机到接收者的通讯. 合规审查自此结束,没有处罚,恢复了短码,所有服务正常运行. 我们为中断道歉。 如果您有任何问题,我们的支援团队很乐意帮忙,可以在[[email protected]](mailto:[email protected])上联系
自动翻译自官方事件更新。
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.
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.
We are seeing system latency normalizing after putting some mitigations in place. Our infrastructure and database teams are continuing to monitor this situation.
System responsiveness is returning to normal. Our engineering teams will continue to work on root causes to avoid latency spikes in the future.
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.
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.
Monitoring indicates increased response times overall. Our infrastructure teams are investigating the issue.
The team has identified some changes to database queries to alleviate this issue, and will be publishing these changes as soon as possible.
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.