Incidents reported on status page for wrexbe https://status.wrexbe.dev/ en https://status.wrexbe.dev/ Sun, 22 Jun 2025 18:14:40 +0000 https://status.wrexbe.dev/#f3dadedc4a5b5db3f75e9a2cc104e1191fe9b546475dd9d8e074c94274a43c6f backend went down https://status.wrexbe.dev/ Sun, 22 Jun 2025 18:14:30 +0000 https://status.wrexbe.dev/#b29b73dc1ec72543b6d94aec282f2c650c81a28c67565a2b44d5a48be05f0198 Main Website went down https://status.wrexbe.dev/ Mon, 09 Jun 2025 12:29:16 +0000 https://status.wrexbe.dev/#89405a7f44ed2cbe82473c39ac5fb24db88d38e463ea523fa81ba0ca6f9eb664 Auth Server went down https://status.wrexbe.dev/ Sun, 01 Jun 2025 09:12:10 +0000 https://status.wrexbe.dev/#52cf1c8145cbdbe0758ef060bd1ec3a264bd7c621027b54467caa18d53e875f1 Main Website recovered https://status.wrexbe.dev/ Sun, 01 Jun 2025 09:09:10 +0000 https://status.wrexbe.dev/#52cf1c8145cbdbe0758ef060bd1ec3a264bd7c621027b54467caa18d53e875f1 Main Website went down https://status.wrexbe.dev/ Sun, 01 Jun 2025 00:27:30 +0000 https://status.wrexbe.dev/#fab9acd7b7678d0d6bd123ab952411dd5e3c88a7a80418a3fe95ab3ba1e7034d backend recovered https://status.wrexbe.dev/ Sun, 01 Jun 2025 00:26:59 +0000 https://status.wrexbe.dev/#9c6eb30a9a1ccf71f15b1d6b7687f5d97fa1589ece8adc1e02bfe04acdb51beb Main Website recovered https://status.wrexbe.dev/ Sat, 31 May 2025 22:18:33 +0000 https://status.wrexbe.dev/#fab9acd7b7678d0d6bd123ab952411dd5e3c88a7a80418a3fe95ab3ba1e7034d backend went down https://status.wrexbe.dev/ Sat, 31 May 2025 22:18:01 +0000 https://status.wrexbe.dev/#9c6eb30a9a1ccf71f15b1d6b7687f5d97fa1589ece8adc1e02bfe04acdb51beb Main Website went down https://status.wrexbe.dev/ Wed, 28 May 2025 05:32:31 +0000 https://status.wrexbe.dev/#619120fb3d49a8f06b1943470dc9324ebd2d7afbeae9083972a4ec9e4329fa2d backend recovered https://status.wrexbe.dev/ Wed, 28 May 2025 05:30:07 +0000 https://status.wrexbe.dev/#619120fb3d49a8f06b1943470dc9324ebd2d7afbeae9083972a4ec9e4329fa2d backend went down