Incidents reported on status page for Wezel https://status.wezel.build/ en https://status.wezel.build/ Fri, 05 Jun 2026 20:38:46 +0000 https://status.wezel.build/#237cf0360811dc0875547dd9c36c8bda21317dc1d6de92c8bf17055e2418cc41 api.wezel.build recovered https://status.wezel.build/ Tue, 02 Jun 2026 05:39:03 +0000 https://status.wezel.build/#237cf0360811dc0875547dd9c36c8bda21317dc1d6de92c8bf17055e2418cc41 api.wezel.build went down https://status.wezel.build/ Tue, 02 Jun 2026 05:37:57 +0000 https://status.wezel.build/#a5e3d7b8b4ad11ba5edaac27edf7a5db566402a831bcae54a8cc44834f03c5ed api.wezel.build recovered https://status.wezel.build/ Tue, 02 Jun 2026 05:36:02 +0000 https://status.wezel.build/#a5e3d7b8b4ad11ba5edaac27edf7a5db566402a831bcae54a8cc44834f03c5ed api.wezel.build went down https://status.wezel.build/incident/906556 Tue, 02 Jun 2026 05:35:00 -0000 https://status.wezel.build/incident/906556#a010ed332d4dd03a5262c29b95a91a64c6a7a13ede333af5ed834a6ab43adc0a All systems operational https://status.wezel.build/ Tue, 02 Jun 2026 05:32:29 +0000 https://status.wezel.build/#47d0f8874ef2b2c5c008f080a9a5cc57bff5490de868b6b69677b74432309d04 api.wezel.build recovered https://status.wezel.build/ Tue, 02 Jun 2026 05:32:25 +0000 https://status.wezel.build/#804fab72ac1d537cd697431be5b13eba438297d5ce91473de32d6d6b285f2e3e app.wezel.build recovered https://status.wezel.build/ Wed, 27 May 2026 14:38:17 +0000 https://status.wezel.build/#804fab72ac1d537cd697431be5b13eba438297d5ce91473de32d6d6b285f2e3e app.wezel.build went down https://status.wezel.build/incident/906556 Wed, 27 May 2026 14:38:00 -0000 https://status.wezel.build/incident/906556#374c050dfbcf470e11cf141b51459765aa39c81755d25ff001604263776bec49 Yeah https://status.wezel.build/ Wed, 27 May 2026 14:35:45 +0000 https://status.wezel.build/#47d0f8874ef2b2c5c008f080a9a5cc57bff5490de868b6b69677b74432309d04 api.wezel.build went down