Smartsheet kesinti geçmişi

1. 27 Ağustos 2026 13:33 UTCinvestigating

   Giriş, sayfa erişimi, Kontrol Merkezi ve Dinamik View'i etkileyen bir etkisi araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 27 Ağustos 2026 13:52 UTCmonitoring

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

3. 27 Ağustos 2026 15:53 UTCresolved

   Bu olay çözüldü.

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

1. 26 Ağustos 2026 13:28 UTCinvestigating

   ABD Smartsheet örneğindeki bazı çarşafların yüklemediği bir sorunu araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 26 Ağustos 2026 14:39 UTCinvestigating

   Hala ABD Smartsheet örneğindeki bazı çarşafların yüklemediği bir sorunu araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

3. 26 Ağustos 2026 15:17 UTCinvestigating

   Hala ABD Smartsheet örneğindeki bazı çarşafların yüklemediği bir sorunu araştırıyoruz. Bu konu aynı zamanda Raporları ve Dashboardları da dinamik View, WorkApps ve Kaynak Yönetimi dahil olmak üzere Premium Apps'i de etkiliyor. Ekibimiz durumu ele almak için tamamen meşgul kalır. İzleme durumuna ulaşıncaya kadar sık güncelleme yapmaya devam edeceğiz.

4. 26 Ağustos 2026 15:47 UTCinvestigating

   Bu konuyu araştırmaya devam ediyoruz.

5. 26 Ağustos 2026 16:08 UTCidentified

   ABD Akıllı Sayfa örneğindeki çarşafları kaldırmak için bir düzeltme yaptık, aynı zamanda Raporlar, Dashboards ve Premium Uygulamaları (Dynamic, WorkApps, Resource Management ve Control Center). Sistem ölçümleri şu anda kurtarma gösteriyor ve ekibimiz tam istikrarı sağlamak için hizmeti aktif olarak izliyor. Olay tamamen çözülinceye kadar daha fazla güncelleme yayınlayacağız.

6. 26 Ağustos 2026 16:22 UTCmonitoring

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

7. 26 Ağustos 2026 18:23 UTCresolved

   Bu olay çözüldü.

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

1. 25 Ağustos 2026 20:45 UTCinvestigating

   Hücre Bağlantılarını ve Cross Sheet Referanslarını etkileyen gecikmeleri veya başarısızlıkları araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 25 Ağustos 2026 21:25 UTCinvestigating

   Hala bu konuyu araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

3. 25 Ağustos 2026 22:09 UTCidentified

   Bu konu tespit edilmiştir ve bir düzeltme uygulanır.

4. 25 Ağustos 2026 22:23 UTCmonitoring

   Bir düzeltme uygulandı ve garanti edilen stabilite için hizmeti izliyoruz.

5. 26 Ağustos 2026 00:23 UTCresolved

   Bu olay çözüldü.

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

1. 11 Ağustos 2026 19:51 UTCinvestigating

   Dokümanlar, Raporlar ve Workflows ile ilgili sorunları araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 11 Ağustos 2026 20:26 UTCinvestigating

   Buna bakmaya devam ediyoruz ve yakında yerinde olmasını beklediğimiz bir tazminata doğru çalışıyoruz.

3. 11 Ağustos 2026 21:02 UTCmonitoring

   Bir mitigation şimdi yerinde ve güçlü bir kurtarma görüyoruz. Sorunu doğrulamak için yakından takip edeceğiz tamamen çözülebilir.

4. 11 Ağustos 2026 23:20 UTCresolved

   Bu olay çözüldü.

5. 19 Ağustos 2026 22:38 UTCpostmortem

   11 Ağustos'ta yaklaşık 7:00 AM'den 4:20 PM PDT'ye kadar, bazı müşteriler yükleme çarşafları ve raporları yüklediğinde zaman veya başarısızlıklar yaşadılar ve bazı iş akışlarının yüksek hata oranları nedeniyle devre dışı bırakmalarına neden olan otomasyon iş başarısızlıkları gibi. Olay, son hizmet kesintilerinin arkasındaki koşullarla ilgili bir veritabanı sorgu-routing sorunu nedeniyle neden oldu, bazı okurların birincil yazma sunucularına yol açtığı ve ortaya çıkan yükleri içeren bir kenar vakası. Hizmeti 3:20 PM PDT ile stabilize ettik ve etkilenen hizmetleri ölçeklendirmeden sonra 4:20 PM PDT tarafından tam iyileşmeyi doğruladık ve veri tabanı sunucularının kapasitesini artırmak için başarısız oldu. Sorgu routing düzeltmek için kalıcı bir kod düzeltmesini tespit ettik ve kullandık. Ayrıca daha önce benzer koşulları tespit etmek ve azaltmak için izleme ve korumaları geliştiriyoruz.

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

1. 30 Temmuz 2026 14:54 UTCinvestigating

   Smartsheet'de yavaşlığı ve zaman hataları araştırıyoruz, çarşafları, premium uygulamaları, konektörleri ve API'leri araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 30 Temmuz 2026 15:26 UTCidentified

   Smartsheet yavaşlığı ve zamanout sorunundan sorumlu olan sorunu tespit ettik ve bir düzeltme uyguluyoruz. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

3. 30 Temmuz 2026 15:40 UTCmonitoring

   Akıllı tablo, Premium Uygulamalar, uygulamalar ve API için stabiliteyi gözlemliyoruz. Tam hizmet istikrarını doğrulamak için yakından takip etmeye devam ediyoruz. Bir güncellemeyi bir kez çözüm onaylayacağız.

4. 30 Temmuz 2026 15:42 UTCmonitoring

   Daha fazla sorun için izlemeye devam ediyoruz.

5. 30 Temmuz 2026 17:41 UTCresolved

   Bu olay çözüldü.

6. 20 Ağustos 2026 17:23 UTCpostmortem

   30 Temmuz 2026, yaklaşık 11:00 ve 15:57 UTC arasında, bazı müşteriler çarşafları yükleyemez ve deneyimli API zamanlarını deneyimleyemezdi. Bu aynı zamanda Kontrol Merkezi, Masa View, Zaman Çizelgesi ve Kurul görüşleri, Raporlar, Dashboards, Forms, Dynamic View ve Bridge entegrasyonları etkilemiştir. Sebep sabah trafik rampası sırasında ağır CPU yükü altında gelen bir arka uç hizmetti. Otomatik sağlık kontrolleri, yedeklerden daha hızlı aşırı yüklemeye başladı ve hizmetin minimum kapasite ayarı kaybı absorbe etmek için çok düşüktü. Mühendislerimiz, hizmetin kapasite sınırlarını yükselterek sorunu çözdüler, bu da sağlıklı kapasiteyi restore etti ve birkaç dakika içinde normale döndü. Hiçbir veri kaybedilmedi. Kapasite zeminini kalıcı olarak yükselttik ve sağlık kontrollerini ayarlarız, daha önceki altyapı düzeyinde izleme ekliyoruz ve benzer konularda kurtarmayı önlemek için bir runbook inşa ediyoruz.

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

1. 15 Temmuz 2026 09:23 UTCinvestigating

   Şu anda Smartsheet ABD'nin başarıyla yüklenmesini engelleyen bir sorunu araştırıyoruz. ABD'ye giriş yapmak veya erişim öğeleri, tamamlanmayan yükleme ekranlarına neden olabilir. 30 dakika içinde bir güncelleme sağlayacağız.

2. 15 Temmuz 2026 09:38 UTCidentified

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

3. 15 Temmuz 2026 09:44 UTCmonitoring

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

4. 15 Temmuz 2026 09:55 UTCresolved

   Bu olay çözüldü.

5. 17 Temmuz 2026 01:22 UTCpostmortem

   15 Temmuz 2026'da yaklaşık 1:44 AM PT'ye başlayın, bazı müşteriler Smartsheet'in yetki kontrollerine güvenen eylemleri gerçekleştirirken deneyimli hataları yaşayabilirler. Bu, rutin bir sistem güncellemesi sırasında geçici bir sorun nedeniyle, kısa bir süre önce altyapımızın mevcut olmayan bir parçasına yönlendirilmesi için taleplerin bir kısmını neden oldu. Bu dönemde etkilenen istekler başarısız olabilir. Sorun tespit edildi ve düzeltildi ve normal operasyon restore edildi.

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

1. 24 Haziran 2026 21:51 UTCinvestigating

   Eksik veya gecikmiş Update / Onay İstekleri bildirimleri ve e-postaları otomatik İş akışları ile de manuel tetikler yoluyla araştırıyoruz. Ekibimiz durumu ele almak için tamamen meşgul. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

2. 24 Haziran 2026 23:04 UTCidentified

   Kayıp veya gecikmiş Güncelleme / Onay İsteklerine ve e-postalara neden olan sorun tespit edilmiştir. Ekibimiz bir düzeltme uyguluyor. İzleme durumuna ulaşıncaya kadar sık güncellemeler sağlayacağız.

3. 25 Haziran 2026 00:43 UTCmonitoring

   Kayıp veya gecikmiş Update / Onay İstekleri bildirimleri ve e-postaları çözmek için bir düzeltme uygulandı ve sonuçları takip ediyoruz.

4. 25 Haziran 2026 05:45 UTCresolved

   Bu olay çözüldü.

5. 17 Temmuz 2026 23:16 UTCpostmortem

   24 Haziran 2026'da, otomatik bir iş akışı, bildirim e-postalarını ve uygulama uyarılarını sunmadan sorumlu iç olay işleme altyapısını geçici olarak kesintiye uğrattı. Bu, güncelleme talebinin yaklaşık% 85'ine ve onay talebi bildirimlerinin yaklaşık 13 saat gecikmesine neden oldu. Hiçbir veri kaybedilmedi – tüm bildirimlerin sonunda sistem kurtarıldı. Otomatik kurtarma mekanizmaları uyguladığından ve gelecekteki bildirim borusunu etkileyen büyük talepleri önlemek için korumalar ekliyoruz.

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

1. 18 Haziran 2026 21:42 UTCidentified

   Bazı müşterilerin kamu Smartform formları aracılığıyla istenmeyen spam tekliflerin daha yüksek bir hacmi aldığını biliyoruz, hatta reCAPTCHA etkinleştirildi. Takımlarımız aktif olarak ek korumaları araştırıyor ve dağıtıyor. Uygulamaya devam ettikçe spam aktivitelerinde azalma gözlemliyoruz ve daha fazla işlem değerlendirmeye devam ediyoruz. Kim etkilenir: Kayıt gerektirmez kamu formlarını kullanan müşteriler.

2. 23 Haziran 2026 07:44 UTCmonitoring

   Akıllı tablo halk formları ile artan spam aktivitesini ele almak için önlemler aldık. İzlemeye devam edeceğiz ve ihtiyaç olduğu gibi daha fazla ayarlama yapacağız. spam tekliflerinin yüksek bir oranını görmeye devam ederseniz lütfen destek ekibimizle iletişime geçin, böylece daha fazla araştırabiliriz.

3. 8 Temmuz 2026 20:46 UTCresolved

   Bu şimdi çözüldü. Hala devam eden ve gelişen bir strateji olarak spam seviyelerini aktif bir şekilde izliyoruz. Tüm müşterileri, herhangi bir oturma spam için destek biletlerini göndermeye teşvik ediyoruz, böylece çözümlerimizi iyi ayarlamaya devam edebiliriz.

4. 17 Temmuz 2026 23:14 UTCpostmortem

   Geç Mayıs ayında başlayarak, hacimde belirgin bir artış gözlemledik ve spam teslimlerinin kamu Smartsheet Forms \(forms available to the general public and not require a Smartform login\), Captcha setting ile bile. Bu, istenmeyen spam içeriğinde bir artış yaşayan bazı müşteriler, sık sık sık sık kriptolama bağlantıları içeren, çarşaflarına teslim edilmiştir. Faaliyet anonim ağlar ve proxy hizmetleri aracılığıyla çalışan otomatik botlar tarafından oluşturuldu. Bu öncelikle etkiledi, ancak ABD bölgesi ile sınırlı değildi. Tedavi tespit edildikten sonra, değerlendirildik, test edildik ve sonraki haftalarda bir dizi koruyucu önlemi topladık. Çünkü bu tür otomatik istismar zamanla uyum sağlar, bir iteratif bir yaklaşım gerektirir: her iki formda birden fazla koruma katmanız, captcha hizmeti ve alt altyapı, canlı trafiğine karşı etkinliğini değerlendirir ve daha az etkili olan önlemleri değiştiririz. Bu süreç boyunca, bu dönemde meydana gelebilecek meşru form tekliflerinin herhangi bir olumsuz etkisini düzeltmeye çalıştık. Otomatik spam şu anda neredeyse sıfır geçişe büyük ölçüde engelleniyor ve meşru teslimlere etkisi yok. Aynı zamanda Smartsheet Gov ortamına benzer korumalar da getiriyoruz. 1:46PT olarak, 8 Temmuz, bu konuyu çözdük. spam gönderimlerini hala gözlemliyorsanız lütfen önce Captcha'nın formda etkinleştirilmesini sağlayın. Captcha etkinleştirilirse ve spam'ı hala görüyorsunuz, lütfen formunuzda “report istismarı” bağlantısını kullanarak bir rapor gönderin. Her zaman en yüksek form güvenlik kısıtlamasını uygulamanızı tavsiye ederiz) (https://help.smartsheet.com/articles/2481836-manage-form-display-and-submission-options #toc-security) Çözümünüzle uyumlu ve gerekirse [eski güvenlik] Bu korumaları takip etmeye, ayarlamaya ve güçlendirmeye devam edeceğiz. Bu, Captcha'nın tüm yeni formlar ve yeni yönetim kontrolleri için varsayılan olarak etkinleştirilmesi gereken değişiklikleri içerir ve planlarından yönetilen formlar için Captcha'yı uygulama yeteneğine sahip olmak. Hizmetlerimizin müşterilerimiz için ne kadar eleştirel olduğunu ve bu olayın size ve işinize sahip olabileceğini biliyoruz. Bu olaydan öğrenmek için elimizden gelen her şeyi yapabileceğimize ve Smartsheet'in teslim edilmesi için sayılabilecek bir ortak olduğundan emin olmak için hizmetlerimizde iyileşme sağlamak için kullanacağımıza söz veriyoruz. Başarınızın - ve Akıllı Sayfaya devam eden güveninizin - buna bağlı olduğunu biliyoruz.

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

1. 10 Haziran 2026 22:21 UTCinvestigating

   We are investigating the Smartsheet add-ons for Google which is currently not available. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 11 Haziran 2026 00:51 UTCidentified

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

3. 11 Haziran 2026 03:30 UTCmonitoring

   The Smartsheet and Brandfolder add-ons for Google Docs, Sheets, and Slides were unavailable due to a Google platform change that required all affected add-ons to be redeployed. Our team has applied the necessary fixes and we are currently monitoring to confirm full stability.

4. 11 Haziran 2026 11:02 UTCresolved

   This incident has been resolved.

5. 14 Ağustos 2026 18:51 UTCpostmortem

   **The Smartsheet Merge add-on for Google Docs stopped working after Google removed support for an older runtime environment that the add-on depended on, causing the add-on to fail entirely for all users \(~234,000 affected\).** The issue was resolved on June 11, 2026, by updating the add-on's code and deployment configuration to be compatible with Google's current platform — no customer data was lost.

1. 3 Haziran 2026 20:28 UTCinvestigating

   We are investigating an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 3 Haziran 2026 21:41 UTCidentified

   We have identified the issue responsible for the assets unexpectedly moved from Folders to the Parent Workspace and implemented a fix. We will provide frequent updates until we reach a monitoring status.

3. 3 Haziran 2026 22:16 UTCidentified

   We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status. Components: Core App - Sheets, Reports, Dashboards - Degraded

4. 3 Haziran 2026 22:59 UTCinvestigating

   We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

5. 4 Haziran 2026 00:06 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users, and we are diligently working to restore them to their original location. We will provide frequent updates until we reach a monitoring status.

6. 4 Haziran 2026 02:14 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide frequent updates until we reach a monitoring status.

7. 4 Haziran 2026 12:25 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide updates until we reach a monitoring status.

8. 4 Haziran 2026 15:44 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work on restoring assets to their original location, and some customers should begin to see assets restored to their original locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

9. 4 Haziran 2026 21:26 UTCidentified

   We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We are continuing to restore assets to their original location, and some customers should begin to see assets in the correct folder structure. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

10. 4 Haziran 2026 23:01 UTCidentified

    We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We have restored some assets to their original locations, and some customers should begin to see assets in the correct folder structure. We are continuing to restore assets to their previous locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

11. 5 Haziran 2026 02:07 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users will be unable to move affected assets until we restore them to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We continue to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.

12. 5 Haziran 2026 10:15 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We are continuing to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.

13. 5 Haziran 2026 12:34 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed the majority of affected assets, and the customers will see they have been restored to their prior locations. We are continuing to work on restoring the remaining assets to their original locations, and we will provide updates until we reach a monitoring status.

14. 5 Haziran 2026 19:53 UTCmonitoring

    We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.

15. 5 Haziran 2026 23:53 UTCresolved

    We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.

16. 9 Haziran 2026 23:07 UTCpostmortem

    On Wednesday, June 3, beginning at approximately 11:15 AM PDT, a platform configuration change caused sheets, reports, dashboards, and folders to be unexpectedly moved from their original folder locations to the top level of the workspace. Affected assets could not be manually moved by users during this period. The issue was identified at 1:28 PM PDT and the root cause was isolated and remediated at 2:10 PM PDT, stopping any further impact. The issue affected customers across North America, European Union, and Australia regions. Our engineering team worked to identify and restore all affected assets back to their original folder structure. The restoration process was completed on June 5, at 12:53 PM PDT, with 99.98% of affected assets successfully returned to their correct locations. For any remaining items that may still appear out of place, they can safely be moved manually as needed. If you encounter issues when attempting to move items, need guidance, or if the volume is too large to address manually, please open a Support case at [https://supportportal.smartsheet.com](https://supportportal.smartsheet.com) referencing "INC-1089" and our team will assist with restoration directly. We sincerely apologize for the disruption this caused. We are making improvements based on our learnings from this incident to prevent similar issues in the future.

1. 27 Mayıs 2026 17:50 UTCinvestigating

   We are currently investigating reports of sheets failing to open and displaying the error "We're having trouble reaching Smartsheet right now." Our team is actively working to resolve the issue and will provide frequent updates until we reach a monitoring status.

2. 27 Mayıs 2026 20:37 UTCmonitoring

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

3. 27 Mayıs 2026 20:39 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 Mayıs 2026 00:51 UTCresolved

   This incident has been resolved.

5. 23 Haziran 2026 23:35 UTCpostmortem

   On May 27, 2026, from approximately 8:30 AM to 2:00 PM PDT, some customers were unable to load sheets, receiving the error, "We're having trouble reaching Smartsheet right now." This was caused by an unexpectedly high volume of simultaneous database requests triggered when loading configuration data for sheets with forms containing numerous column options. Under elevated traffic, this pattern generated hundreds of parallel queries, overwhelming the affected database cluster's read capacity. We resolved the issue by scaling database read capacity and routing traffic away from the affected infrastructure. To prevent recurrence, we are implementing changes to: * Redesign how column option data is fetched to reduce load. * Better distributing database traffic and protecting database capacity during periods of high usage. * Improving monitoring and tooling to detect and respond to issues faster. We know how critical our services are to our customers and apologize for any impact this incident may have had on you and your business. We promise that we will do everything we can to learn from this event and use it to drive improvement across our services to ensure that Smartsheet is a partner that can be counted on to deliver. We know that your success—and your continued trust in Smartsheet—depends on it.

1. 22 Nisan 2026 16:45 UTCinvestigating

   We are investigating reports of the Workspace panel not opening or closing unexpectedly. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 22 Nisan 2026 17:01 UTCidentified

   We have identified the issue responsible for the Workspace panel not opening or closing unexpectedly and are implementing a fix. We will provide frequent updates until we reach a monitoring status.

3. 22 Nisan 2026 17:09 UTCmonitoring

   We are observing stability being restored for Workspace panel not opening or closing unexpectedly. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.

4. 22 Nisan 2026 19:20 UTCresolved

   Workspace panel functionality has been fully restored and is operating normally. The incident is now resolved.

5. 29 Nisan 2026 15:48 UTCpostmortem

   Between 22:40 UTC on April 21 and 19:21 UTC on April 22, the Workspace Panel was not rendering consistently for users. Regardless of whether they had toggled it on or off, the panel did not appear. The issue was particularly present for non-Enterprise users \(Business and Pro accounts\). The impact was limited to the panel and did not affect any other UI flows within the Smartsheet app. The incident was resolved by rolling back the affected Workspace Panel to a previous known good version.

1. 17 Nisan 2026 19:23 UTCinvestigating

   We are currently experiencing intermittent loading issues with the Resource Management module within Smartsheet. Please note that the standalone site at rm.smartsheet.com is working normally and can be used as a workaround while we resolve the integration issues.

2. 17 Nisan 2026 19:35 UTCmonitoring

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

3. 18 Nisan 2026 00:07 UTCresolved

   This incident has been resolved.

1. 13 Nisan 2026 16:33 UTCinvestigating

   We are currently investigating an issue affecting Smartsheet Forms where a subset of users are experiencing failures when submitting forms.

2. 13 Nisan 2026 17:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 Nisan 2026 18:31 UTCmonitoring

   The issue has been identified, Form submissions are operating normally now. Our team will continue to monitor the service and implement the necessary changes to prevent recurrence.

4. 13 Nisan 2026 20:46 UTCresolved

   Forms Submissions are operating normally. The incident is now resolved.

5. 14 Nisan 2026 14:26 UTCpostmortem

   On Monday, April 13, between 7:00 AM and 11:30 AM PST, some users experienced failures when submitting Smartsheet forms. The issue was isolated to CAPTCHA-enabled forms and was caused by a problem with our reCAPTCHA verification endpoint. Error rates declined significantly by mid-morning and the incident was fully resolved by 11:30 AM PST. All form submissions are operating normally.

1. 31 Mart 2026 18:53 UTCinvestigating

   We are currently investigating an issue causing 'EVALUATION MODE' watermarks and slow loading on proofs. We will provide an update in 30 minutes.

2. 31 Mart 2026 19:35 UTCidentified

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

3. 31 Mart 2026 20:11 UTCmonitoring

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

4. 31 Mart 2026 22:01 UTCresolved

   This incident has been resolved.

5. 13 Nisan 2026 23:13 UTCpostmortem

   On March 30, 2026, at approximately 10:55 PM PDT, the Proofing service encountered issue where users encountered watermarks on all legacy proofs. The outage was caused by a licensing issue and was also compounded by an internal configuration issue causing a full proofing outage. The incident was mitigated by March 31, 2026 at 1:15PM PDT To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for licensing issues as well bolstering deployment stability.

1. 24 Mart 2026 15:16 UTCinvestigating

   We are investigating blank results showing on User & Group Management pages in Admin Center. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 24 Mart 2026 16:07 UTCidentified

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

3. 24 Mart 2026 16:08 UTCmonitoring

   We are observing stability being restored for the User & Group Management pages in Admin Center. A page refresh or clearing of cache from this page from your browser might be necessary for full resolution. We are continuing to monitor it closely to confirm full service stability.

4. 24 Mart 2026 18:30 UTCresolved

   This incident has been resolved.

5. 3 Nisan 2026 23:20 UTCpostmortem

   On March 24, 2026, at approximately 07:55 UTC, the Admin Center Client experienced an issue where users were unable to view user groups in the Group Management view and users in the User Management page in certain cases — instead seeing an infinite loading screen. The issue was caused by a recent update to a shared part of the Admin Center interface that controls how loading indicators are shown during searching. In the Group Management area and UserView, this change accidentally made the page think it was always still loading, so users saw a never-ending loading screen and couldn't view groups \(and in some cases users\). The problem was fixed by rolling back that change, which finalized at 09:06 UTC. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for failed page renders in key Admin Center views, adding automated synthetic tests, and documenting recovery runbooks to reduce future resolution time.

1. 3 Mart 2026 17:16 UTCinvestigating

   We've investigating an issue with Form Submissions propagating to the sheet. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 3 Mart 2026 17:47 UTCidentified

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

3. 3 Mart 2026 17:52 UTCidentified

   This issue has been identified and a fix has been implemented for new form submissions. For previous form submissions that failed in this window, a manual replay will be ran. Please do not re-submit these form submissions.

4. 3 Mart 2026 18:19 UTCmonitoring

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

5. 4 Mart 2026 23:42 UTCresolved

   Forms Submissions has been fully restored and is operating normally. The incident is now resolved.

6. 13 Mart 2026 23:53 UTCpostmortem

   On 4:47PM Pacific Standard Time, March 2nd, 2026, a code regression impacted a subset of Form Submissions to propagate to the underlying sheets and some API requests. Service was restored by rolling back to the last known stable deployment. A manual scale up was applied to meet the demands of the queues. Issue was successfully resolved by 9:53AM PST March 3rd, 2026. All previously failed form submissions were successfully replayed by 12:20PM PST, March 4th, 2026.

1. 27 Şubat 2026 21:55 UTCidentified

   We have proactively paused the release of our February reports to ensure the highest level of data accuracy. Our team is currently resolving a synchronization issue, and we expect the corrected reports to be available shortly. We apologize for the inconvenience and appreciate your patience while we ensure your data is 100% correct.

2. 3 Mart 2026 15:55 UTCidentified

   We are continuing to work on a fix for this issue.

3. 9 Mart 2026 16:38 UTCidentified

   We are continuing to work on restoring full service.

4. 12 Mart 2026 21:08 UTCidentified

   A fix is being implemented. An update will be shared once completed.

5. 16 Mart 2026 19:05 UTCidentified

   We are finalizing the fix for this issue and will have an update shortly.

6. 24 Mart 2026 15:02 UTCmonitoring

   We have implemented the fix fully and we are monitoring for stability.

7. 24 Mart 2026 17:57 UTCresolved

   This incident has been resolved.

8. 25 Mart 2026 03:05 UTCpostmortem

   On February 25, 2026, a data synchronization issue was identified in Brandfolder's reporting infrastructure. The logical replication pipeline between the production database and the analytics data layer fell out of sync, which caused stale or missing data in Insights dashboards, subscription page metrics, and the Insights Data Connector. Standard monthly reports were proactively paused on February 27 to prevent delivery of inaccurate data, and a partial outage was posted to the status page. Engineering began rebuilding the replication pipeline, but encountered multiple failures during the data catch-up process due to the volume of data \(~5TB\) and recurring initialization errors. The replication pipeline was stabilized on March 16 and data began flowing to the analytics layer. The team then identified and resolved gaps in session data for specific dates, re-ran the affected data pipeline jobs, and verified data parity between the production database and analytics systems. Standard reporting was resumed on March 24, 2026, and the incident was resolved the same day. All previously missed reports have been generated and delivered. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for the replication pipeline, adding automated data health checks, and documenting recovery runbooks to reduce future resolution time.

1. 22 Şubat 2026 12:17 UTCinvestigating

   We are investigating the home page error message "Something went wrong". Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 22 Şubat 2026 12:40 UTCmonitoring

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

3. 22 Şubat 2026 14:45 UTCresolved

   This incident has been resolved.

4. 7 Mart 2026 01:02 UTCpostmortem

   Approximately on 3:15AM Pacific Standard Time February 22nd, 2026 in our Australia region, a deployment was performed to resolve a performance issue. However, a configuration required to validate session cookies was incorrectly specified, which caused the web app to become inaccessible after successful login. The issue was mitigated within 80 minutes by toggling a feature flag to reroute traffic back to a stable service and full functionality was restored by 4:35AM Pacific Standard Time February 22nd, 2026.

1. 17 Şubat 2026 16:08 UTCinvestigating

   We are investigating Advanced Reports not being able to create new ones and also failing to refresh. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 17 Şubat 2026 16:29 UTCmonitoring

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

3. 17 Şubat 2026 18:55 UTCresolved

   This incident has been resolved.

4. 19 Şubat 2026 13:49 UTCpostmortem

   On February 17th, 2026, a failure in the service linking Resource Management Workflows to the main Data Shuttle engine resulted in a service disruption for the Resource Management Advanced Reporting feature in the US Production environment. Service was restored by rolling back the most recent Data Shuttle deployment \(originally released five days prior\). While this action immediately resolved the issue, preliminary analysis indicates the root cause was likely a memory exhaustion issue within the service, rather than a defect in the deployment itself. The rollback effectively reset the service state, clearing the error. A comprehensive RCA is currently underway to pinpoint the source of the outage.