Incidents reported on status page for BrandSSL - Mayzing https://status-mayzing.brandssl.io/ https://d1lppblt9t2x15.cloudfront.net/logos/f797c54b7f515461314d92a24e6ef291.png https://status-mayzing.brandssl.io/ en https://status-mayzing.brandssl.io/ Sun, 07 Jun 2026 10:45:35 +0000 https://status-mayzing.brandssl.io/#461a658a5b1662e2e9779d8a93ae231d6975f144a64c9566ec268bd87ddb9f0c Node recovered https://status-mayzing.brandssl.io/ Sun, 07 Jun 2026 10:42:44 +0000 https://status-mayzing.brandssl.io/#461a658a5b1662e2e9779d8a93ae231d6975f144a64c9566ec268bd87ddb9f0c Node went down https://status-mayzing.brandssl.io/ Fri, 22 May 2026 10:42:40 +0000 https://status-mayzing.brandssl.io/#50d8497ce442dcbdfcf1cf1f0548026c043159d781d190310f9f84a8cd9be2c2 Node recovered https://status-mayzing.brandssl.io/ Fri, 22 May 2026 10:39:37 +0000 https://status-mayzing.brandssl.io/#50d8497ce442dcbdfcf1cf1f0548026c043159d781d190310f9f84a8cd9be2c2 Node went down https://status-mayzing.brandssl.io/ Sat, 16 May 2026 05:21:32 +0000 https://status-mayzing.brandssl.io/#65fe4ff31caf25413a5b0cdb1aa59cceb6f6eb1f9d12057c8cb41c7115ce6e5f Node recovered https://status-mayzing.brandssl.io/ Sat, 16 May 2026 05:18:29 +0000 https://status-mayzing.brandssl.io/#65fe4ff31caf25413a5b0cdb1aa59cceb6f6eb1f9d12057c8cb41c7115ce6e5f Node went down https://status-mayzing.brandssl.io/ Thu, 26 Mar 2026 18:48:31 +0000 https://status-mayzing.brandssl.io/#8b93bf5a159e4c2d3746ce9a4f007b7e878357081581d656322e99d16acd5097 Node recovered https://status-mayzing.brandssl.io/ Thu, 26 Mar 2026 18:45:42 +0000 https://status-mayzing.brandssl.io/#8b93bf5a159e4c2d3746ce9a4f007b7e878357081581d656322e99d16acd5097 Node went down https://status-mayzing.brandssl.io/ Fri, 20 Mar 2026 10:27:38 +0000 https://status-mayzing.brandssl.io/#d2bb3047513a866a9ec4e469a193a5ce7e795def98b8e4942cbfd1af3c0f5909 Node recovered https://status-mayzing.brandssl.io/ Fri, 20 Mar 2026 10:24:48 +0000 https://status-mayzing.brandssl.io/#d2bb3047513a866a9ec4e469a193a5ce7e795def98b8e4942cbfd1af3c0f5909 Node went down https://status-mayzing.brandssl.io/ Thu, 19 Mar 2026 12:33:38 +0000 https://status-mayzing.brandssl.io/#a6de58b567e1b863789cd2d6c97995196b997bdf1ff07ca4fd90090562a55f39 Node recovered https://status-mayzing.brandssl.io/ Thu, 19 Mar 2026 12:31:02 +0000 https://status-mayzing.brandssl.io/#a6de58b567e1b863789cd2d6c97995196b997bdf1ff07ca4fd90090562a55f39 Node went down https://status-mayzing.brandssl.io/ Thu, 12 Mar 2026 00:21:40 +0000 https://status-mayzing.brandssl.io/#a841e5720106d99d4f1f145aee36712e0c40f2fa25b6052441500b3ec9a42f03 Node recovered https://status-mayzing.brandssl.io/ Thu, 12 Mar 2026 00:19:59 +0000 https://status-mayzing.brandssl.io/#a841e5720106d99d4f1f145aee36712e0c40f2fa25b6052441500b3ec9a42f03 Node went down https://status-mayzing.brandssl.io/incident/710799 Fri, 22 Aug 2025 22:50:00 -0000 https://status-mayzing.brandssl.io/incident/710799#84269a658bb6091552d38a0fb3f5082a63284baa07afc6e42f2d51bb6cd925de All impacted services have now fully recovered https://status-mayzing.brandssl.io/incident/710799 Fri, 22 Aug 2025 21:55:00 -0000 https://status-mayzing.brandssl.io/incident/710799#2ba821fd76e51f93eed83d244565aa6740d91c93bf712e5e2aafc859e596e588 Elevated errors and latencies