Smartsheet driftsforstyrrelser

1. 27. august 2026 kl. 13.33 UTCinvestigating

   Vi undersøger et udfald, der påvirker login, pladeadgang, Control Center og Dynamic View. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 27. august 2026 kl. 13.52 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 27. august 2026 kl. 15.53 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. august 2026 kl. 13.28 UTCinvestigating

   Vi undersøger et problem, hvor nogle lagner i den amerikanske Smartsheet instans ikke kan indlæses. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 26. august 2026 kl. 14.39 UTCinvestigating

   Vi undersøger stadig et problem, hvor nogle lagner i det amerikanske Smartsheet-tilfælde ikke kan indlæses. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

3. 26. august 2026 kl. 15.17 UTCinvestigating

   Vi undersøger stadig et problem, hvor nogle lagner i det amerikanske Smartsheet-tilfælde ikke kan indlæses. Dette spørgsmål er også påvirke Rapporter og Dashboards, samt Premium Apps herunder Dynamic View, WorkApps, og Resource Management. Vores team er fortsat fuldt engageret i at tackle situationen. Vi vil fortsat give hyppige opdateringer, indtil vi når en overvågningsstatus.

4. 26. august 2026 kl. 15.47 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

5. 26. august 2026 kl. 16.08 UTCidentified

   Vi har implementeret en rettelse for at afbøde problemet forårsager ark i den amerikanske Smartsheet instans at undlade at indlæse, samt virkningen på rapporter, Dashboards, og Premium Apps (Dynamisk View, WorkApps, Resource Management, og Control Center). Systemmålinger viser i øjeblikket opsving, og vores team overvåger aktivt tjenesten for at sikre fuld stabilitet. Vi vil sende yderligere opdateringer indtil hændelsen er helt løst.

6. 26. august 2026 kl. 16.22 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

7. 26. august 2026 kl. 18.23 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. august 2026 kl. 20.45 UTCinvestigating

   Vi undersøger forsinkelser eller svigt påvirker Cell Links og Cross Sheet Referencer. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 25. august 2026 kl. 21.25 UTCinvestigating

   Vi undersøger stadig dette spørgsmål. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

3. 25. august 2026 kl. 22.09 UTCidentified

   Dette spørgsmål er blevet identificeret, og et fix er ved at blive gennemført.

4. 25. august 2026 kl. 22.23 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger tjenesten for at sikre stabilitet.

5. 26. august 2026 kl. 00.23 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. august 2026 kl. 19.51 UTCinvestigating

   Vi undersøger problemer med ark, rapporter og arbejdsgange. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 11. august 2026 kl. 20.26 UTCinvestigating

   Vi fortsætter med at undersøge dette og arbejder mod en afbødning, som vi forventer at have på plads snart.

3. 11. august 2026 kl. 21.02 UTCmonitoring

   En afbødning er nu på plads, og vi ser en stærk bedring. Vi holder nøje øje med, at problemet er løst.

4. 11. august 2026 kl. 23.20 UTCresolved

   Denne hændelse er blevet løst.

5. 19. august 2026 kl. 22.38 UTCpostmortem

   Den 11. august fra omkring 7: 00 til 4: 20 PM PDT, nogle kunder oplevede timeouts eller svigt, når du indlæser ark og rapporter, samt automatisering workflow fejl, der forårsagede nogle arbejdsgange til at deaktivere på grund af forhøjede fejlrater. Hændelsen var forårsaget af en database query- routing spørgsmål relateret til betingelserne bag de seneste service forstyrrelser, hvor visse læsning blev omdirigeret til primære skrive servere og en kant tilfælde involverer ark synkronisering forstærket den resulterende belastning. Vi stabiliserede tjenesten med 3: 20 PM PDT og bekræftede fuld inddrivelse med 4: 20 PM PDT efter skalering berørte tjenester og svigter over database servere til at øge kapaciteten. Vi har identificeret og indsat en permanent kode fix til at korrigere forespørgsel routing. Vi forbedrer også overvågning og sikkerhedsforanstaltninger for at opdage og afbøde lignende forhold tidligere.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 30. juli 2026 kl. 14.54 UTCinvestigating

   Vi undersøger langsommelighed og timeout fejl i Smartsheet, påvirker ark, premium apps, konnektorer og API. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 30. juli 2026 kl. 15.26 UTCidentified

   Vi har identificeret problemet ansvarlig for Smartsheets langsommelighed og timeout problem og er ved at gennemføre en rettelse. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

3. 30. juli 2026 kl. 15.40 UTCmonitoring

   Vi observerer stabilitet bliver genoprettet for Smartsheet, Premium Apps, Connectors, og API. Vi fortsætter med at overvåge det nøje for at bekræfte fuld service stabilitet. Vi vil give en opdatering, når resolution er bekræftet.

4. 30. juli 2026 kl. 15.42 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 30. juli 2026 kl. 17.41 UTCresolved

   Denne hændelse er blevet løst.

6. 20. august 2026 kl. 17.23 UTCpostmortem

   Den 30. juli 2026, mellem ca. 11: 00 og 15: 57 UTC, nogle kunder kunne ikke indlæse ark og erfarne API timeouts. Dette påvirkede også Control Center, Table View, Timeline og Board visninger, Rapporter, Dashboards, Forms, Dynamisk View, og Bridge integration. Årsagen var en backend service, der kom under tung CPU belastning under morgen trafik ramp-up. Dens automatiserede sundhedstjek begyndte at fjerne overbelastede tilfælde hurtigere end udskiftninger kunne komme online, og tjenestens minimumskapacitet indstilling var for lav til at absorbere tabet. Vores ingeniører løst problemet ved at hæve tjenestens kapacitet grænser, som genoprettet sund kapacitet og returneret ydeevne til normal inden for få minutter. Ingen data blev tabt. Vi har permanent hævet kapaciteten, og vi er ved at justere sundhedstjekket, tilføje tidligere infrastrukturniveau overvågning, og opbygge en runbook for at forhindre og fremskynde genopretning fra lignende spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 15. juli 2026 kl. 09.23 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem, der forhindrer Smartsheet US i at indlæse. Forsøg på at logge ind på Smartsheet US eller adgangspunkter kan resultere i indlæsning skærme, der ikke er komplet. Vi leverer en opdatering om 30 minutter.

2. 15. juli 2026 kl. 09.38 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 15. juli 2026 kl. 09.44 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 15. juli 2026 kl. 09.55 UTCresolved

   Denne hændelse er blevet løst.

5. 17. juli 2026 kl. 01.22 UTCpostmortem

   Fra omkring 1: 44 AM PT den 15. juli 2026, nogle kunder kan have oplevet fejl, når de udfører handlinger, der er afhængige af Smartsheets godkendelse kontrol, såsom adgang kontrol af aktiver. Dette skyldtes et midlertidigt problem under en rutinemæssig systemopdatering, der kort forårsagede, at en del af anmodningerne blev rettet mod en utilgængelig del af vores infrastruktur. I denne periode kan berørte anmodninger have slået fejl. Spørgsmålet blev identificeret og rettet, og normal drift blev genoprettet.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juni 2026 kl. 21.51 UTCinvestigating

   Vi undersøger rapporter om manglende eller forsinkede Opdatering / Godkendelse Anmodninger meddelelser og e-mails via Automated Workflows samt manuel udløser. Vores team er fuldt engageret i at løse situationen. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

2. 24. juni 2026 kl. 23.04 UTCidentified

   Problemet med manglende eller forsinkede opdaterings- / godkendelsesanmodninger er blevet identificeret. Vores hold laver et fix. Vi vil give hyppige opdateringer, indtil vi når en overvågningsstatus.

3. 25. juni 2026 kl. 00.43 UTCmonitoring

   En rettelse er blevet gennemført for at løse de manglende eller forsinkede Opdatering / Godkendelse Anmodninger meddelelser og e-mails, og vi overvåger resultaterne.

4. 25. juni 2026 kl. 05.45 UTCresolved

   Denne hændelse er blevet løst.

5. 17. juli 2026 kl. 23.16 UTCpostmortem

   Den 24. juni 2026, en automatiseret workflow genereret en usædvanlig stor mængde opdateringsanmodninger i en kort periode, som midlertidigt forstyrret den interne begivenhedsbehandling infrastruktur, der er ansvarlig for at levere anmeldelse e-mails og in-app advarsler. Dette medførte, at ca. 85% af opdateringsanmodninger og meddelelser om anmodninger om godkendelse blev forsinket i omkring 13 timer. Ingen data blev tabt - alle meddelelser blev i sidste ende leveret, når systemet inddrives. Vi har siden gennemført automatiske genopretningsmekanismer og tilføjer sikkerhedsforanstaltninger for at forhindre, at alt for store anmodninger påvirker anmeldelsesrørledningen i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. juni 2026 kl. 21.42 UTCidentified

   Vi er klar over, at nogle kunder modtager en øget mængde af uønskede spam indlæg gennem offentlige Smartsheet formularer, selv med reCAPTCHA aktiveret. Vores hold har aktivt undersøgt og udsendt yderligere beskyttelse. Vi observerer et fald i spam aktivitet, mens vi fortsætter med at anvende og evaluere yderligere lempelser. Hvem er påvirket: Kunder, der bruger offentlige formularer, der ikke kræver login.

2. 23. juni 2026 kl. 07.44 UTCmonitoring

   Vi har gennemført foranstaltninger til at håndtere den øgede spam aktivitet med Smartsheets offentlige formularer. Vi vil fortsat overvåge og foretage yderligere justeringer efter behov. Hvis du fortsætter med at se en høj sats af spam indlæg, bedes du kontakte vores support team, så vi kan undersøge yderligere.

3. 8. juli 2026 kl. 20.46 UTCresolved

   Det er nu løst. Vi overvåger stadig aktivt spam niveauer som en løbende og udviklende strategi. Vi opfordrer alle kunder til at indsende supportbilletter til eventuelle resterende spam kommer igennem, så vi kan fortsætte med at finjustere vores løsninger.

4. 17. juli 2026 kl. 23.14 UTCpostmortem

   Startende i slutningen af maj, vi observeret en markant stigning i volumen og raffinement af spam indlæg til offentlige Smartsheet Forms\ (formularer til rådighed for offentligheden og ikke kræver en Smartsheet login\), selv med Captcha indstilling aktiveret. Dette resulterede i, at nogle kunder oplever en stigning i uønsket spam indhold, der ofte indeholder cryptocurrency eller phishing links, leveret i deres ark. Aktiviteten blev genereret af automatiserede bots, der opererer via anonymiserede netværk og proxytjenester. Dette påvirkede primært, men var ikke begrænset til den amerikanske region. Da misbruget blev identificeret, evaluerede vi, udsendte, testede og afstemte en række beskyttelsesforanstaltninger i de følgende uger. Fordi automatiseret misbrug af denne art tilpasser sig over tid, at løse det kræver en iterativ tilgang: vi lagrede flere beskyttelsesforanstaltninger i begge former, captcha service, og den underliggende infrastruktur, vurderede deres effektivitet mod levende trafik, og raffineret dem som vi lærte mere, justere eller erstatte foranstaltninger, der viste sig mindre effektive. Under hele denne proces overvågede og arbejdede vi også på at korrigere eventuelle utilsigtede virkninger for legitime former for indlæg, som måtte have fundet sted i denne periode. Automatiseret spam er nu væsentligt blokeret ned til næsten nul passere gennem sats og med minimal eller ingen indvirkning på legitime indlæg. Vi bringer også aktivt lignende beskyttelse ind i Smartsheet Gov miljøet. Fra 1: 46PT den 8. juli markerede vi dette spørgsmål som løst. Hvis du stadig observerer spam indlæg, skal du først sikre dig at Captcha er aktiveret på formularen. Hvis Captcha er aktiveret, og du stadig ser spam, bedes du indsende en rapport ved hjælp af linket "rapportmisbrug" på din formular. Vi anbefaler altid at anvende den [højeste niveau af formularer sikkerhedsbegrænsning] (https: / / help.smartsheet.com / artikler / 2481836- manage- form- display- and -submission-options # toc- security) kompatibel med din løsning og om nødvendigt håndhæve [form sikkerhed fra admin center] (https: / / help.smartsheet.com / artikler / 2483290- apply- security- settings- forms). Vi vil fortsat overvåge, afstemme og styrke disse beskyttelsesforanstaltninger. Dette omfatter ændringer til at have Captcha aktiveret som standard for alle nye formularer og nye administrative kontroller rullende ud for systemadministratorer til at have mulighed for at håndhæve Captcha for formularer forvaltes af deres plan. Vi ved, hvor kritiske vores tjenester er for vores kunder og undskylde for enhver indvirkning denne hændelse kan have haft på dig og din virksomhed. Vi lover, at vi vil gøre alt, hvad vi kan, for at lære af denne begivenhed og bruge den til at drive forbedringer på tværs af vores tjenester for at sikre, at Smartsheet er en partner, der kan regnes med til at levere. Vi ved, at din succes - og din fortsatte tillid til Smartsheet - afhænger af det.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juni 2026 kl. 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. juni 2026 kl. 00.51 UTCidentified

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

3. 11. juni 2026 kl. 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. juni 2026 kl. 11.02 UTCresolved

   This incident has been resolved.

5. 14. august 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 20.37 UTCmonitoring

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

3. 27. maj 2026 kl. 20.39 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28. maj 2026 kl. 00.51 UTCresolved

   This incident has been resolved.

5. 23. juni 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 19.20 UTCresolved

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

5. 29. april 2026 kl. 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. april 2026 kl. 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. april 2026 kl. 19.35 UTCmonitoring

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

3. 18. april 2026 kl. 00.07 UTCresolved

   This incident has been resolved.

1. 13. april 2026 kl. 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. april 2026 kl. 17.52 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. april 2026 kl. 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. april 2026 kl. 20.46 UTCresolved

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

5. 14. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 19.35 UTCidentified

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

3. 31. marts 2026 kl. 20.11 UTCmonitoring

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

4. 31. marts 2026 kl. 22.01 UTCresolved

   This incident has been resolved.

5. 13. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 16.07 UTCidentified

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

3. 24. marts 2026 kl. 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. marts 2026 kl. 18.30 UTCresolved

   This incident has been resolved.

5. 3. april 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 17.47 UTCidentified

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

3. 3. marts 2026 kl. 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. marts 2026 kl. 18.19 UTCmonitoring

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

5. 4. marts 2026 kl. 23.42 UTCresolved

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

6. 13. marts 2026 kl. 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. februar 2026 kl. 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. marts 2026 kl. 15.55 UTCidentified

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

3. 9. marts 2026 kl. 16.38 UTCidentified

   We are continuing to work on restoring full service.

4. 12. marts 2026 kl. 21.08 UTCidentified

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

5. 16. marts 2026 kl. 19.05 UTCidentified

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

6. 24. marts 2026 kl. 15.02 UTCmonitoring

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

7. 24. marts 2026 kl. 17.57 UTCresolved

   This incident has been resolved.

8. 25. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 12.40 UTCmonitoring

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

3. 22. februar 2026 kl. 14.45 UTCresolved

   This incident has been resolved.

4. 7. marts 2026 kl. 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. februar 2026 kl. 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. februar 2026 kl. 16.29 UTCmonitoring

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

3. 17. februar 2026 kl. 18.55 UTCresolved

   This incident has been resolved.

4. 19. februar 2026 kl. 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.