Incidents reported on status page for Truvity B.V. https://status.truvity.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/d131793d9fd7ab0573296082f59b6e50.png https://status.truvity.cloud/ en https://status.truvity.cloud/ Thu, 02 Apr 2026 14:23:05 +0000 https://status.truvity.cloud/#a766ca15be4d3d8250ab248cce764c29b93da770cde394812870c9d22ad3bc57 Drafts recovered https://status.truvity.cloud/ Thu, 02 Apr 2026 14:21:45 +0000 https://status.truvity.cloud/#a766ca15be4d3d8250ab248cce764c29b93da770cde394812870c9d22ad3bc57 Drafts went down https://status.truvity.cloud/ Mon, 23 Mar 2026 10:21:03 +0000 https://status.truvity.cloud/#938db7ad081733b27b46963a88f92e429b788093f4a2bf2ab7043349660dcd14 DID Documents recovered https://status.truvity.cloud/ Mon, 23 Mar 2026 10:20:51 +0000 https://status.truvity.cloud/#17a375e3a018df10b7c4654445db5f05dd61e023b760c52cdf87ad0a210c622b Presentations recovered https://status.truvity.cloud/ Mon, 23 Mar 2026 10:15:31 +0000 https://status.truvity.cloud/#17a375e3a018df10b7c4654445db5f05dd61e023b760c52cdf87ad0a210c622b Presentations went down https://status.truvity.cloud/ Mon, 23 Mar 2026 10:13:17 +0000 https://status.truvity.cloud/#938db7ad081733b27b46963a88f92e429b788093f4a2bf2ab7043349660dcd14 DID Documents went down https://status.truvity.cloud/incident/597593 Thu, 05 Jun 2025 13:05:00 -0000 https://status.truvity.cloud/incident/597593#b0c60fff3aa0abd559f930d16f3739b06a22bf57537059ce559b4eccfe256ab0 🚀 To restore full access, please: - Sign out of your current session. - Sign back in with your credentials. This will generate a fresh token and resolve the issue. 🙏 We’re Sorry for the Hitch! We know small disruptions can be annoying—thank you for your patience while we improve things! ✨ Thank you for trusting us! https://status.truvity.cloud/incident/597593 Thu, 05 Jun 2025 12:15:00 -0000 https://status.truvity.cloud/incident/597593#480a8e9ff47b5a9d0e9b508c01af22fc74a82b2e648f52ce42f341f6c4ea8543 🔍 What Happened? During a recent system update, older login sessions were affected, causing errors in the background. You may have noticed issues like failed actions or console errors—but no need to worry! Your data is safe. https://status.truvity.cloud/incident/541230 Fri, 04 Apr 2025 12:19:00 -0000 https://status.truvity.cloud/incident/541230#bd056c0a3fdf6c50199b390bb44513fa824431a1f6f70dfefec35d1489687191 The missing resources were successfully recreated, and the affected monitors were unpaused on April 4, 2025. From that point onward, all monitoring systems resumed normal operation. We sincerely apologize for any confusion caused by the incorrect status indicators. https://status.truvity.cloud/incident/541882 Fri, 04 Apr 2025 09:13:00 -0000 https://status.truvity.cloud/incident/541882#850e4bd597d29cb9ecf328075bf8ccc7c950505d5dafec036e06761d63f89812 After adjusting how we use the BetterStack API, functionality was restored. In fact, there was no downtime on the Truvity side of the product. https://status.truvity.cloud/incident/541882 Thu, 03 Apr 2025 22:01:00 -0000 https://status.truvity.cloud/incident/541882#e51527c7e15d4ec82876d9564d95ba7b23d3ea8a197af906b73dda468cd9bf1c The BetterStack API was recently updated in such a way that our Cron job that updates temporary credentials for accessing destination servers stopped working. https://status.truvity.cloud/incident/541230 Sun, 23 Mar 2025 13:11:00 -0000 https://status.truvity.cloud/incident/541230#c933ac21d1d776f7eb4f1759100df54c8ca7b9501e13295547d2fd45d0c45af7 On March 23, 2025, during a routine database wipe of our staging environment, a few resources associated with some of our Better Stack "API" monitors were removed. As a result, those monitors appeared as if they were failing and displayed red status indicators. We want to assure our customers that **there was no actual downtime**. All the "stage" services remained fully operational and unaffected throughout the period. The monitoring alerts were false positives triggered solely by the internal environment changes. To avoid further confusion, we promptly paused the affected monitors while restoring the necessary resources. However, the red status remained visible for a few days, which may have caused unnecessary concern. We sincerely apologize for any confusion this may have caused.