Onfleet kesinti geçmişi

1. 19 Ağustos 2026 19:00 UTCinvestigating

   Harita görünümünde yüklemeyen unsurların raporları aldık, özellikle görev atamalarını ve muhtemelen analizlerini etkileyen sürücü ekip elemanlarıyla ilgili. Ekibimiz şu anda araştırıyor.

2. 19 Ağustos 2026 20:05 UTCmonitoring

   Sıcak bir ek dağıtılır, elementler şimdi panoda görünmelidir. Şu anda her şeyin istikrarlı olduğundan emin olmak için düzeltmeyi izliyoruz.

3. 19 Ağustos 2026 20:42 UTCresolved

   Bu olay çözüldü, Map View sidebar normale döndü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 23 Temmuz 2026 22:45 UTCinvestigating

   Bazı müşteriler ortaya çıktığında hatalarla karşılaşırlar. Takım araştırıyor.

2. 23 Temmuz 2026 22:55 UTCidentified

   Sorun son bir altyapı değişikliği ile ilgili görünüyor. Bir düzeltme hazırlanır.

3. 23 Temmuz 2026 23:07 UTCmonitoring

   Bir düzeltme uygulandı ve ekip sorunu doğrulamak için izliyor.

4. 23 Temmuz 2026 23:14 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 22 Temmuz 2026 05:05 UTCinvestigating

   ABD müşterilerimizin alt kümesi bir SMS teslimat hatasıyla etkilenebilir. Şu anda bu sorunu çözmek için sağlayıcıları ile çalışıyoruz.

2. 22 Temmuz 2026 12:33 UTCmonitoring

   Bir düzeltme uygulandı ve sonuçları takip ediyoruz.

3. 22 Temmuz 2026 17:44 UTCmonitoring

   Güncelleme - ABD Müşteriler için SMS Teslimat Etkilenen SMS bildirimlerinin çoğu restore edilmiştir. Bu sabah erkenden, birincil sağlayıcımızın sayılarından birinde bir taşıyıcının kesintisi sonrasında bir yedek telefon sağlayıcı aracılığıyla trafiği geri aldık. Küçük sayıda ikamet süresiz teslimat başarısızlığı kalır, bildirimlerin sınırlı bir alt kümesini etkiler. Bir düzeltme planlandı ve bugün çözülmesini bekliyoruz. Bu sayfayı tam olarak çözdüğünde güncelleyeceğiz. Hata için özür dileriz ve sabrınızı takdir ediyoruz.

4. 22 Temmuz 2026 20:47 UTCresolved

   Olay çözüldü ve SMS işlevselliği tamamen restore edildi. Lütfen SMS mesajlarının birincil sağlayıcımızla sorunu çözinceye kadar farklı bir telefon numarasını gösterebileceğini unutmayın.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 10 Temmuz 2026 02:00 UTCinvestigating

   Onfleet'te Eksik Ekranda Upstream POS sonuçları ile entegrasyon Şu anda üçüncü taraf POS veya API entegrasyonu ile görevleri yaratan müşterileri etkileyen bir sorunu araştırıyoruz. Bu entegrasyonlar aracılığıyla yaratılan görevler Onfleet Dashboard'da görünmeyebilir, ancak başarıyla yaratıldılar. Ne etkilenir: API entegrasyonları (örneğin, POS sistemleri, üçüncü taraf platformları) aracılığıyla yaratılan görevler Dashboard bu görevlerin görünürlüğü Ne etkilenmez: Görev oluşturmanın kendisi – görevler başarıyla yaratılıyor Manually Dashboard'da görevleri yarattı Büyük nedeni tespit ettik ve bir düzeltme üzerinde çalışıyoruz. En kısa sürede bir güncelleme sağlayacağız. Bu rahatsızlıktan özür dileriz.

2. 10 Temmuz 2026 02:00 UTCidentified

   Sorun tespit edildi ve bir düzeltme uygulanır.

3. 10 Temmuz 2026 02:29 UTCresolved

   Bu olay çözüldü. API entegrasyonu aracılığıyla yaratılan görevler artık Onfleet Dashboard'da doğru gösterecektir. Etkilenen pencere sırasında yaratılan herhangi bir görevlerin hala eksik olduğuna inanıyorsanız, lütfen destek ekibimizle iletişime geçin ve remediasyona yardımcı olacağız.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

3. 19 Haziran 2026 00:02 UTCresolved

   Anonymized text service has been resolved for affected customers

1. 17 Haziran 2026 18:39 UTCinvestigating

   Kısacode tarafından servis edilen Kanadalı SMS şu anda teslimat başarısızlıklarını deneyimliyor. Bu sorunu çözmek için sağlayıcıları ile çalışıyoruz.

2. 17 Haziran 2026 21:55 UTCresolved

   Bir düzeltme uygulandı ve sistem şimdi tamamen operasyonel. Stabilite sağlamak için aktif olarak izliyoruz.

3. 10 Temmuz 2026 18:12 UTCpostmortem

   17 Haziran'da, paylaşılan Kanada SMS kısa kodu geçici olarak, Kanadalı alıcılar için SMS teslimat bildirimlerini kesintiye uğrattı. Aynı öğleden sonra bildirimleri geri yüklemek ve ertesi gün tamamen restore edilen sürücüyü tamamen restore etmek için alternatif bir sağlayıcı aracılığıyla trafiği geri aldık. Uyum incelemesi, cezalarla sonuçlanmamış olduğundan, kısa kod yeniden yürürlüğe girdi ve tüm hizmet normalde çalışıyor. Bu rahatsızlıktan özür dileriz. Herhangi bir sorunuz varsa, destek ekibimiz yardımcı olmaktan mutluluk duyuyor ve [[email protected]](mailto:[email protected]) ulaşılabiliyor

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 14 Mayıs 2026 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 Mayıs 2026 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 Nisan 2026 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 Nisan 2026 18:57 UTCmonitoring

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

3. 7 Nisan 2026 19:06 UTCresolved

   This incident has been resolved.

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

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

2. 3 Nisan 2026 01:15 UTCmonitoring

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

3. 3 Nisan 2026 01:27 UTCresolved

   This incident has been resolved.

4. 6 Nisan 2026 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 Mart 2026 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 Mart 2026 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 Mart 2026 21:34 UTCresolved

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

1. 3 Kasım 2025 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 Kasım 2025 21:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 Kasım 2025 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 Kasım 2025 21:49 UTCresolved

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

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

   The dashboard display behavior has returned to normal.

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

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

2. 15 Ekim 2025 18:38 UTCinvestigating

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

3. 15 Ekim 2025 19:12 UTCmonitoring

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

4. 15 Ekim 2025 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 Temmuz 2025 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 Temmuz 2025 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 Temmuz 2025 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 Temmuz 2025 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 Haziran 2025 18:22 UTCinvestigating

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

2. 30 Haziran 2025 18:23 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 Temmuz 2025 14:08 UTCresolved

   This incident has been resolved.

1. 9 Haziran 2025 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 Haziran 2025 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 Haziran 2025 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 Mayıs 2025 21:39 UTCinvestigating

   We are experiencing errors related to ETA calculations

2. 30 Mayıs 2025 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 Mayıs 2025 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 Mayıs 2025 23:56 UTCidentified

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

3. 21 Mayıs 2025 00:01 UTCmonitoring

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

4. 21 Mayıs 2025 00:13 UTCresolved

   This incident has been resolved.

1. 5 Mayıs 2025 16:54 UTCinvestigating

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

2. 5 Mayıs 2025 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 Mayıs 2025 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.