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/ Mon, 09 Feb 2026 00:03:25 +0000 https://status.truvity.cloud/#0301195b89b5a26d100718365221285c2cf3aaf2042d67da446ad3ca5ab70850 DID Method Universal Resolver recovered https://status.truvity.cloud/ Sun, 08 Feb 2026 23:59:10 +0000 https://status.truvity.cloud/#0301195b89b5a26d100718365221285c2cf3aaf2042d67da446ad3ca5ab70850 DID Method Universal Resolver went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:31:05 +0000 https://status.truvity.cloud/#5630cf2f358b1334fc5f8ba79af315ec4ccd99f1d04d3a3ad48fd7cfecc616f7 Credentials recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:31:05 +0000 https://status.truvity.cloud/#09a5f3a161f026c21992232a97a566880e2450f1dc5d3e9f449c9f529e5550fe Files recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:31:02 +0000 https://status.truvity.cloud/#438415f0221f412e53bc9b0987b4d1c472a4866f55ccd2c74774a135cc397147 DIDComm Messages recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:30:51 +0000 https://status.truvity.cloud/#f315f0e1a14c7211b6decc9ab6e8bfdc727a9b6c9ce639ca54b755dc398a2214 Presentations recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:30:50 +0000 https://status.truvity.cloud/#aafa77a12e47d28326771646850b45768dd9a52a95355f4801985db5b1ddc619 Drafts recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:30:43 +0000 https://status.truvity.cloud/#36d4bf7fe75a90238d28149647e1228692c279d2ae541b6b2ecbd8994a32f684 DIDs recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:25:11 +0000 https://status.truvity.cloud/#aafa77a12e47d28326771646850b45768dd9a52a95355f4801985db5b1ddc619 Drafts went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:24:00 +0000 https://status.truvity.cloud/#36d4bf7fe75a90238d28149647e1228692c279d2ae541b6b2ecbd8994a32f684 DIDs went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:23:58 +0000 https://status.truvity.cloud/#5630cf2f358b1334fc5f8ba79af315ec4ccd99f1d04d3a3ad48fd7cfecc616f7 Credentials went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:23:58 +0000 https://status.truvity.cloud/#438415f0221f412e53bc9b0987b4d1c472a4866f55ccd2c74774a135cc397147 DIDComm Messages went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:23:58 +0000 https://status.truvity.cloud/#09a5f3a161f026c21992232a97a566880e2450f1dc5d3e9f449c9f529e5550fe Files went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:23:51 +0000 https://status.truvity.cloud/#f315f0e1a14c7211b6decc9ab6e8bfdc727a9b6c9ce639ca54b755dc398a2214 Presentations went down https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:24 +0000 https://status.truvity.cloud/#0b3f9d9859fb703e8b477941a65a6be259bce1c4240438294aabf667b3d658c2 DIDs recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:24 +0000 https://status.truvity.cloud/#e9c607e3a182427e754ea5c6935bdbb335f230ea1f79b9cc53a75bf217b43bc9 DIDComm Messages recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:22 +0000 https://status.truvity.cloud/#97ec2ccfbb44960d230f76194231b97c58539611824dee53e119dd0213be6bc2 Files recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:22 +0000 https://status.truvity.cloud/#7c238eb9c3a647ef30fe12004d34a570e269b074261149da15ce19b2ee233c98 Credentials recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:17 +0000 https://status.truvity.cloud/#e18f00f87b25a06571f95e5f0c9e4385de05b541af807ba4ec4200d5e1d7e364 Presentations recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 13:06:12 +0000 https://status.truvity.cloud/#8d99cd922b0007090c6a82b9429c8c32a574d2ca35a0de64e0ea2018b9989c94 Drafts recovered https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:40 +0000 https://status.truvity.cloud/#7c238eb9c3a647ef30fe12004d34a570e269b074261149da15ce19b2ee233c98 Credentials went down https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:22 +0000 https://status.truvity.cloud/#e9c607e3a182427e754ea5c6935bdbb335f230ea1f79b9cc53a75bf217b43bc9 DIDComm Messages went down https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:11 +0000 https://status.truvity.cloud/#e18f00f87b25a06571f95e5f0c9e4385de05b541af807ba4ec4200d5e1d7e364 Presentations went down https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:10 +0000 https://status.truvity.cloud/#97ec2ccfbb44960d230f76194231b97c58539611824dee53e119dd0213be6bc2 Files went down https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:09 +0000 https://status.truvity.cloud/#8d99cd922b0007090c6a82b9429c8c32a574d2ca35a0de64e0ea2018b9989c94 Drafts went down https://status.truvity.cloud/ Tue, 20 Jan 2026 12:59:00 +0000 https://status.truvity.cloud/#0b3f9d9859fb703e8b477941a65a6be259bce1c4240438294aabf667b3d658c2 DIDs 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 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/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/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/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/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/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/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 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/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. 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. 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. 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. 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. 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.