Incidents | Paragon Incidents reported on status page for Paragon https://status3.useparagon.com/ en Microservice: Connect recovered https://status3.useparagon.com/ Mon, 11 May 2026 19:52:09 +0000 https://status3.useparagon.com/#4582574c9c626d8272b494e5cc378514dc7a945bc840d210b53fe5d04dd37983 Microservice: Connect recovered Microservice: Connect went down https://status3.useparagon.com/ Mon, 11 May 2026 19:45:33 +0000 https://status3.useparagon.com/#4582574c9c626d8272b494e5cc378514dc7a945bc840d210b53fe5d04dd37983 Microservice: Connect went down Microservice: Cerberus recovered https://status3.useparagon.com/ Wed, 06 May 2026 15:57:29 +0000 https://status3.useparagon.com/#247a56fd7aac769899d6a33c708a296c4b011c100541d43878ab48bae8e70a7e Microservice: Cerberus recovered Microservice: Release recovered https://status3.useparagon.com/ Wed, 06 May 2026 15:49:18 +0000 https://status3.useparagon.com/#32fd9643df2b0892afb1d173146c93638f45b4e0195822eedad8e43ceb60c2d9 Microservice: Release recovered Microservice: Release went down https://status3.useparagon.com/ Wed, 06 May 2026 15:46:09 +0000 https://status3.useparagon.com/#32fd9643df2b0892afb1d173146c93638f45b4e0195822eedad8e43ceb60c2d9 Microservice: Release went down Microservice: Cerberus went down https://status3.useparagon.com/ Wed, 06 May 2026 15:44:49 +0000 https://status3.useparagon.com/#247a56fd7aac769899d6a33c708a296c4b011c100541d43878ab48bae8e70a7e Microservice: Cerberus went down Microservice: Hermes recovered https://status3.useparagon.com/ Mon, 04 May 2026 21:28:28 +0000 https://status3.useparagon.com/#579b02417033b56b67b50e87b462bdc01b63dd601a702ed3ca436fed94e5885b Microservice: Hermes recovered Microservice: Hermes went down https://status3.useparagon.com/ Mon, 04 May 2026 21:18:26 +0000 https://status3.useparagon.com/#579b02417033b56b67b50e87b462bdc01b63dd601a702ed3ca436fed94e5885b Microservice: Hermes went down Dashboard Login recovered https://status3.useparagon.com/ Tue, 28 Apr 2026 23:05:03 +0000 https://status3.useparagon.com/#d9eed16f9e18f793c609313b1fd47300d3b8099e3a5c5619bc30e0f317c36bae Dashboard Login recovered Dashboard Login went down https://status3.useparagon.com/ Tue, 28 Apr 2026 23:02:17 +0000 https://status3.useparagon.com/#d9eed16f9e18f793c609313b1fd47300d3b8099e3a5c5619bc30e0f317c36bae Dashboard Login went down Worker: Proxy recovered https://status3.useparagon.com/ Thu, 16 Apr 2026 15:01:03 +0000 https://status3.useparagon.com/#5089f9758832a522e24959b1b9c05631b6f214ce24c4847b9444783e47d471d7 Worker: Proxy recovered Worker: Proxy went down https://status3.useparagon.com/ Thu, 16 Apr 2026 14:58:05 +0000 https://status3.useparagon.com/#5089f9758832a522e24959b1b9c05631b6f214ce24c4847b9444783e47d471d7 Worker: Proxy went down Microservice: Embassy recovered https://status3.useparagon.com/ Tue, 31 Mar 2026 08:52:44 +0000 https://status3.useparagon.com/#f485ac24499082a42b333b8440d4abf061d2a9343324ea192ee757734eef9eb0 Microservice: Embassy recovered Microservice: Embassy went down https://status3.useparagon.com/ Tue, 31 Mar 2026 08:47:46 +0000 https://status3.useparagon.com/#f485ac24499082a42b333b8440d4abf061d2a9343324ea192ee757734eef9eb0 Microservice: Embassy went down Microservice: Embassy recovered https://status3.useparagon.com/ Mon, 30 Mar 2026 14:28:11 +0000 https://status3.useparagon.com/#53ed14d8f8fd570d28330f921185145331d558ddd6c4528bb566540e17777c6e Microservice: Embassy recovered Microservice: Embassy went down https://status3.useparagon.com/ Mon, 30 Mar 2026 14:22:11 +0000 https://status3.useparagon.com/#53ed14d8f8fd570d28330f921185145331d558ddd6c4528bb566540e17777c6e Microservice: Embassy went down Microservice: Embassy recovered https://status3.useparagon.com/ Mon, 30 Mar 2026 14:19:13 +0000 https://status3.useparagon.com/#d3f95f3245b8deae753e8908673586176237d1483315cf0bf9d952dcc18da883 Microservice: Embassy recovered Microservice: Embassy went down https://status3.useparagon.com/ Mon, 30 Mar 2026 14:08:57 +0000 https://status3.useparagon.com/#d3f95f3245b8deae753e8908673586176237d1483315cf0bf9d952dcc18da883 Microservice: Embassy went down