56 Onfleet incidents · 2023年1月 — official updates, affected components, duration and resolution details.
マップビューにロードされていない要素のレポートを受け取りました。特に、タスクの割り当ての表示に影響を及ぼすドライバーチーム要素や、おそらく分析に関連しています。 弊社チームでは、現在調査中です.
Hotfix がデプロイされ、ダッシュボードに要素が表示されるようになりました。 現在、すべてのものが安定していることを確認するために修正を監視しています.
このインシデントは、マップビューのサイドバーが正常に戻りました.
公式のインシデント更新を自動翻訳しています。
マニフェストを作成するときに、一部の顧客はエラーに遭遇しています。 チームは調査しています.
最近のインフラ変更に関連した問題が現れます。 修正準備中です.
修正が適用され、チームは問題が解決されることを確認するために監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
米国の顧客のサブセットはSMS配達欠陥によって影響されるかもしれません。 私たちは、この問題を解決するためにプロバイダと協力しています.
修正を実装し、結果を監視しています.
更新 -- 米国顧客のためのSMS配達 影響を受けたSMS通知の大部分は復元されています。 早朝に、第一次プロバイダーのナンバーワンでキャリア・サイドの割込みが発生した後、バックアップ・テレフォニー・プロバイダーによるトラフィックを再ルートしました。 残留配送障害が少なく、通知の限られたサブセットに影響します。 修正は予定されており、今日は解決する予定です。 このページを完全に解決したときに更新します。 皆様のお越しを心よりお詫び申し上げます.
事件は解決され、SMS機能は完全に復元されます。 SMS メッセージは、主要なプロバイダーの問題を解決するまで、異なる電話番号を表示することがあります.
公式のインシデント更新を自動翻訳しています。
OnfleetのMissing DisplayのUpstream POS結果との統合 現在、サードパーティのPOSまたはAPI統合を介してタスクを作成する顧客に影響を与える問題を検討しています。 これらの統合によって作成されたタスクは、正常に作成されているにもかかわらず、Onfleetダッシュボードには表示されません。 影響を受けるもの: 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
ショートコードで提供されているカナダのSMSは、現在配達障害を経験しています。 私たちは、この問題を解決するためにプロバイダと協力しています.
修正が適用され、システムが完全に操作できるようになりました。 安定性確保のため、積極的にモニタリングを行っています.
6 月 17 日、カナダの SMS ショート コードは、カナダの受信者に SMS 配信通知を中断したキャリアのコンプライアンスレビューに一時的に停止されました。 同午後の代替プロバイダによるトラフィックを再ルートし、通知を復元し、次の日を完全に復元しました。 コンプライアンス・レビューは、ペナルティなしで締結したので、ショート・コードは再定義され、すべてのサービスは正常に動作しています。 大変申し訳ございません。 ご不明な点がございましたら、サポートチームにご連絡ください。[[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.