Incidents reported on status page for hzmi's Lab https://status.hzmi.xyz/ en https://status.hzmi.xyz/incident/380763 Fri, 07 Jun 2024 03:29:10 -0000 https://status.hzmi.xyz/incident/380763#cd253101a7ed27138e5d13f54cc4033fdafda0d4a076a19eb6ddd6e72bf55656 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/380763 Fri, 07 Jun 2024 03:29:10 -0000 https://status.hzmi.xyz/incident/380763#cd253101a7ed27138e5d13f54cc4033fdafda0d4a076a19eb6ddd6e72bf55656 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/380763 Fri, 07 Jun 2024 03:23:09 -0000 https://status.hzmi.xyz/incident/380763#95a6035b0956ed43b41ca7f45064b8776c726c8c91ec9a84dff09b2b66af9451 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/380763 Fri, 07 Jun 2024 03:23:09 -0000 https://status.hzmi.xyz/incident/380763#95a6035b0956ed43b41ca7f45064b8776c726c8c91ec9a84dff09b2b66af9451 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 09:58:40 -0000 https://status.hzmi.xyz/incident/378976#c5e88c03f602de613352e45ce1e4a24e4a7694bdbacf8b171b827c598db2a26b hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 09:58:40 -0000 https://status.hzmi.xyz/incident/378976#c5e88c03f602de613352e45ce1e4a24e4a7694bdbacf8b171b827c598db2a26b hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 09:52:36 -0000 https://status.hzmi.xyz/incident/378976#4e21f4fd67a59cbd7a318968ba9c2efd373449112081ba08e989c76d6186c1b4 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 09:52:36 -0000 https://status.hzmi.xyz/incident/378976#4e21f4fd67a59cbd7a318968ba9c2efd373449112081ba08e989c76d6186c1b4 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 00:28:29 -0000 https://status.hzmi.xyz/incident/378976#7e14dd1bbd09ed5be155035d935cbc83e83e87a60af5179e957b04177d6da1c7 hzmi.dev recovered. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 00:28:15 -0000 https://status.hzmi.xyz/incident/378976#7098292997ec04448b306cbc3199d75b212bea62ba4a66a14e1adf0e31b5873e bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 00:13:25 -0000 https://status.hzmi.xyz/incident/378976#e5ad4cf508b154d9ef82355b124ad8ddfc78b6920ac4a1a61553a98661424375 hzmi.dev went down. https://status.hzmi.xyz/incident/378976 Tue, 04 Jun 2024 00:13:14 -0000 https://status.hzmi.xyz/incident/378976#958706d157cbe4ab9c79dd67e02e8e79250a8f8581ea7c0e2cd929f7c39b58e4 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/378325 Sun, 02 Jun 2024 15:23:03 -0000 https://status.hzmi.xyz/incident/378325#2045880d4255df22856e519ff7215e9d19d3411865e4fc7172c69e9bfbb70ac7 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/378325 Sun, 02 Jun 2024 15:23:03 -0000 https://status.hzmi.xyz/incident/378325#2045880d4255df22856e519ff7215e9d19d3411865e4fc7172c69e9bfbb70ac7 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/378325 Sun, 02 Jun 2024 14:47:02 -0000 https://status.hzmi.xyz/incident/378325#2a404da26fd3bbc25f0690502c3258e287115e5f7b007d08d0f14a7ecfe17b3f bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/378325 Sun, 02 Jun 2024 14:44:16 -0000 https://status.hzmi.xyz/incident/378325#33c3ac1e68ae6bdd7a4c060ee7a4e5ab93387f80c08e8cb11e4929b7749a3ff3 hzmi.dev went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 07:02:23 -0000 https://status.hzmi.xyz/incident/377242#23537e5a3019ad44eecc430abffc3ac4c9faa74e98115720c226883f6bf56315 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 07:02:23 -0000 https://status.hzmi.xyz/incident/377242#23537e5a3019ad44eecc430abffc3ac4c9faa74e98115720c226883f6bf56315 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 06:56:33 -0000 https://status.hzmi.xyz/incident/377242#0d092a33156b05d69e50106fe7ae59c6b36b828ecce66ab7b855a0bc1f8b41be hzmi.dev went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 06:56:21 -0000 https://status.hzmi.xyz/incident/377242#b7195c64ceb9abf33e620caea1303a1f9ed60844c7d58953d53990c2f8c0e9bb bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 06:38:36 -0000 https://status.hzmi.xyz/incident/377242#a97f09724d0b9589dcff7d4523a9faecb04c53a693285860c9036ce682978c41 hzmi.dev recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 06:38:22 -0000 https://status.hzmi.xyz/incident/377242#87617dfc69305476969efaab11bbffa8c1e0f066b3203da587803ee798dc1406 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 05:53:23 -0000 https://status.hzmi.xyz/incident/377242#569fa8a1405bc966a9d23702addc9e4f60014e549e60f823f441fe43aa10823b hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 05:53:23 -0000 https://status.hzmi.xyz/incident/377242#569fa8a1405bc966a9d23702addc9e4f60014e549e60f823f441fe43aa10823b hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 02:47:26 -0000 https://status.hzmi.xyz/incident/377242#fb54d42ebcb15443cd73e9f4154aefd0e2b4c77ebdc99680be0a42cd67d45223 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 02:47:26 -0000 https://status.hzmi.xyz/incident/377242#fb54d42ebcb15443cd73e9f4154aefd0e2b4c77ebdc99680be0a42cd67d45223 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 02:24:59 -0000 https://status.hzmi.xyz/incident/377242#c368c3960c155584c01863b02061d8ac0f451bdb61792222ea632e8a73224b1c bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/377242 Fri, 31 May 2024 02:23:37 -0000 https://status.hzmi.xyz/incident/377242#a8586499bb0c546820b30114e5edc7a2664ed5627bd6dfb5b385ab7dcebd2cde hzmi.dev went down. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 10:48:25 -0000 https://status.hzmi.xyz/incident/376716#f467b781699b7f2f0b953dbcf746af82f7ef3b287efe3f19a8a38e513464245f hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 10:48:25 -0000 https://status.hzmi.xyz/incident/376716#f467b781699b7f2f0b953dbcf746af82f7ef3b287efe3f19a8a38e513464245f hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 10:42:19 -0000 https://status.hzmi.xyz/incident/376716#d71dbb6bc10f529142eab0ec6122513cf8f9848e918a2183d836aad9d3a19e69 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 10:42:19 -0000 https://status.hzmi.xyz/incident/376716#d71dbb6bc10f529142eab0ec6122513cf8f9848e918a2183d836aad9d3a19e69 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 03:58:53 -0000 https://status.hzmi.xyz/incident/376716#9ee0c8489edbd74115687880a15bcffa4b6760b26243072f8c21da0b8e865d73 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/376716 Thu, 30 May 2024 03:52:18 -0000 https://status.hzmi.xyz/incident/376716#75b99651d9ed3451125011d5960aea570f0633a58d3e177a49e12c0af723e51a bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 22:49:25 -0000 https://status.hzmi.xyz/incident/375708#15ecae17f5b12bf79319ec86542ff6e3e6138a45707d108bec4e27155d9380d5 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 22:49:25 -0000 https://status.hzmi.xyz/incident/375708#15ecae17f5b12bf79319ec86542ff6e3e6138a45707d108bec4e27155d9380d5 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 22:43:23 -0000 https://status.hzmi.xyz/incident/375708#268bed35c0b90e1c378b5ac99166092346ec8de25aaeaca8df4fc0306257cac4 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 22:43:23 -0000 https://status.hzmi.xyz/incident/375708#268bed35c0b90e1c378b5ac99166092346ec8de25aaeaca8df4fc0306257cac4 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 20:43:25 -0000 https://status.hzmi.xyz/incident/375708#2600520e7c134e3c9b4dab462cfa05c6578edf6ca28114944b05cfd1fb963878 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 20:43:25 -0000 https://status.hzmi.xyz/incident/375708#2600520e7c134e3c9b4dab462cfa05c6578edf6ca28114944b05cfd1fb963878 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 19:58:27 -0000 https://status.hzmi.xyz/incident/375708#8aa50d069c00801c05ffa6b82fff843ec12b028bc347a5acbd977315306d10f0 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 19:58:27 -0000 https://status.hzmi.xyz/incident/375708#8aa50d069c00801c05ffa6b82fff843ec12b028bc347a5acbd977315306d10f0 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 13:55:09 -0000 https://status.hzmi.xyz/incident/375708#22c45689fe8657afeaaf4000dd1f452f3dd714e8bb8cf7207cfdbaf409d50622 hzmi.dev recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 13:51:50 -0000 https://status.hzmi.xyz/incident/375708#c54b617d8b7bfc20c373496b1450c9337cda27641c747177d94b438a3cd7836c bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 13:45:58 -0000 https://status.hzmi.xyz/incident/375708#b70cb17bb6e7349527e1ce3c539ba2ba6afbddf22920241cfd498ba038f01bed hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 13:45:58 -0000 https://status.hzmi.xyz/incident/375708#b70cb17bb6e7349527e1ce3c539ba2ba6afbddf22920241cfd498ba038f01bed hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 04:59:44 -0000 https://status.hzmi.xyz/incident/375708#b646230e6ea1b58ea145a8c95649f642e91e8760034325e266343f33a5e77e96 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 04:59:44 -0000 https://status.hzmi.xyz/incident/375708#b646230e6ea1b58ea145a8c95649f642e91e8760034325e266343f33a5e77e96 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 04:53:36 -0000 https://status.hzmi.xyz/incident/375708#9af17cb617f10e971ac67dc7a0a6d480873fd099ff6cd8df6cee62ffebead60d hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/375708 Tue, 28 May 2024 04:53:36 -0000 https://status.hzmi.xyz/incident/375708#9af17cb617f10e971ac67dc7a0a6d480873fd099ff6cd8df6cee62ffebead60d hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/374574 Sun, 26 May 2024 08:29:41 -0000 https://status.hzmi.xyz/incident/374574#75fbb6ac636264048238647f8b4b4ffe0275fb660ac21c041196335823db9c7a hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/374574 Sun, 26 May 2024 08:29:41 -0000 https://status.hzmi.xyz/incident/374574#75fbb6ac636264048238647f8b4b4ffe0275fb660ac21c041196335823db9c7a hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/374574 Sat, 25 May 2024 10:40:47 -0000 https://status.hzmi.xyz/incident/374574#cd926162da00b350ff86f0fbcd4e1342fdeff9001d9eff58f7e25070cbeef8ef hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/374574 Sat, 25 May 2024 10:40:47 -0000 https://status.hzmi.xyz/incident/374574#cd926162da00b350ff86f0fbcd4e1342fdeff9001d9eff58f7e25070cbeef8ef hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/365930 Tue, 07 May 2024 07:37:46 -0000 https://status.hzmi.xyz/incident/365930#bca5d8ea9f5f3a0337fc9251d931b399998503113a335c14e236b93435efe702 hzmi.dev recovered. https://status.hzmi.xyz/incident/365930 Tue, 07 May 2024 07:37:26 -0000 https://status.hzmi.xyz/incident/365930#8599e8eb0b54b0c826a670251a19eaf6d37b19857c504fd704f9a2bacc202044 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/365930 Tue, 07 May 2024 07:31:41 -0000 https://status.hzmi.xyz/incident/365930#113c9bafc9af67126cad3ca3756426799e3fce1db6e2beb3475fdae5199cb3f8 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/365930 Tue, 07 May 2024 07:31:41 -0000 https://status.hzmi.xyz/incident/365930#113c9bafc9af67126cad3ca3756426799e3fce1db6e2beb3475fdae5199cb3f8 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/365005 Sun, 05 May 2024 06:14:49 -0000 https://status.hzmi.xyz/incident/365005#12ed4a9382a2dc46f637e272413780ea1faa54a3e54cffb4435be307a78645fb hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/365005 Sun, 05 May 2024 06:14:49 -0000 https://status.hzmi.xyz/incident/365005#12ed4a9382a2dc46f637e272413780ea1faa54a3e54cffb4435be307a78645fb hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/365005 Sun, 05 May 2024 06:08:47 -0000 https://status.hzmi.xyz/incident/365005#8e5e22f46f24708b0f38d7a6cb2bab733d10a7cf1e5ca2bba27dd79088c46bed hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/365005 Sun, 05 May 2024 06:08:47 -0000 https://status.hzmi.xyz/incident/365005#8e5e22f46f24708b0f38d7a6cb2bab733d10a7cf1e5ca2bba27dd79088c46bed hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/364510 Sat, 04 May 2024 01:08:54 -0000 https://status.hzmi.xyz/incident/364510#2021b796ecd6383832338c922db65fda87ca3f1bee574857cb0ae5bf8ee159e0 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/364510 Sat, 04 May 2024 01:06:03 -0000 https://status.hzmi.xyz/incident/364510#e1274b43f39a27ed5b86158428ecc4ee04b90b7903e2439957c71109f02cbfe1 hzmi.dev recovered. https://status.hzmi.xyz/incident/364510 Sat, 04 May 2024 00:59:46 -0000 https://status.hzmi.xyz/incident/364510#a471a4323bb1e5545bb28344a774718441ab7100331e11ef6d55082ea7acb2b3 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/364510 Sat, 04 May 2024 00:59:46 -0000 https://status.hzmi.xyz/incident/364510#a471a4323bb1e5545bb28344a774718441ab7100331e11ef6d55082ea7acb2b3 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/363023 Tue, 30 Apr 2024 23:58:16 -0000 https://status.hzmi.xyz/incident/363023#b018d5405997fb2eb089a204647875f710f2bc3de0ecb8883aa58f699f17c8a8 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/363023 Tue, 30 Apr 2024 23:58:16 -0000 https://status.hzmi.xyz/incident/363023#b018d5405997fb2eb089a204647875f710f2bc3de0ecb8883aa58f699f17c8a8 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/363023 Tue, 30 Apr 2024 23:52:13 -0000 https://status.hzmi.xyz/incident/363023#e858aaf3f235a83886036acd978cc08bea667051fc10a009a9630489211c1db8 hzmi.dev went down. https://status.hzmi.xyz/incident/363023 Tue, 30 Apr 2024 23:52:01 -0000 https://status.hzmi.xyz/incident/363023#8de63aea9d90842fdd852365c619869a248388cbdc4e34c168d297339eca7b15 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 10:45:04 -0000 https://status.hzmi.xyz/incident/361783#6a8e8d988c6b212417b5b530618b6964bb4b6beb7ea5afbf7ee8af24b8516efe hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 10:45:04 -0000 https://status.hzmi.xyz/incident/361783#6a8e8d988c6b212417b5b530618b6964bb4b6beb7ea5afbf7ee8af24b8516efe hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 10:38:58 -0000 https://status.hzmi.xyz/incident/361783#779f3a5c2b8987bce0a11df6d2dc43968fd5b6540de5dfe85b81626573a1a734 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 10:38:58 -0000 https://status.hzmi.xyz/incident/361783#779f3a5c2b8987bce0a11df6d2dc43968fd5b6540de5dfe85b81626573a1a734 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 06:59:52 -0000 https://status.hzmi.xyz/incident/361783#64a1f3c8a9abee09f21c9133aeeb3189ee490ccf601527ff22b08e95d4d18e95 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 06:59:52 -0000 https://status.hzmi.xyz/incident/361783#64a1f3c8a9abee09f21c9133aeeb3189ee490ccf601527ff22b08e95d4d18e95 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 06:23:49 -0000 https://status.hzmi.xyz/incident/361783#ee9eec21a7d65d9a4277a215ee4ae1c1bc92db5ad0f993e0d8e666862f14ea33 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/361783 Sun, 28 Apr 2024 06:23:49 -0000 https://status.hzmi.xyz/incident/361783#ee9eec21a7d65d9a4277a215ee4ae1c1bc92db5ad0f993e0d8e666862f14ea33 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/360889 Fri, 26 Apr 2024 00:29:45 -0000 https://status.hzmi.xyz/incident/360889#19d79b5b0f4aa286486c51f3794355eb393cd472e82fe9dc4111a715528d5663 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/360889 Fri, 26 Apr 2024 00:29:45 -0000 https://status.hzmi.xyz/incident/360889#19d79b5b0f4aa286486c51f3794355eb393cd472e82fe9dc4111a715528d5663 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/360889 Fri, 26 Apr 2024 00:20:36 -0000 https://status.hzmi.xyz/incident/360889#639399d6c21ef5f02fb28c2969286c0ce33b50cd06ec08f553fcd8dead1291c2 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/360889 Fri, 26 Apr 2024 00:20:36 -0000 https://status.hzmi.xyz/incident/360889#639399d6c21ef5f02fb28c2969286c0ce33b50cd06ec08f553fcd8dead1291c2 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/360771 Thu, 25 Apr 2024 18:35:38 -0000 https://status.hzmi.xyz/incident/360771#28ab0edb948f74f90ddfd297179e0b6de508f4eaf61a8735a4a7a51167dba132 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/360771 Thu, 25 Apr 2024 18:35:38 -0000 https://status.hzmi.xyz/incident/360771#28ab0edb948f74f90ddfd297179e0b6de508f4eaf61a8735a4a7a51167dba132 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/360771 Thu, 25 Apr 2024 18:29:35 -0000 https://status.hzmi.xyz/incident/360771#ad8b6976670ea72859d4c69570fd0137fbf2b3521530771a919b6ebd826a9a8a hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/360771 Thu, 25 Apr 2024 18:29:35 -0000 https://status.hzmi.xyz/incident/360771#ad8b6976670ea72859d4c69570fd0137fbf2b3521530771a919b6ebd826a9a8a hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:33:57 -0000 https://status.hzmi.xyz/incident/356931#a0011a657667add9b698595b689608b218f018e3f720f9f142166723768fe91c hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:33:57 -0000 https://status.hzmi.xyz/incident/356931#a0011a657667add9b698595b689608b218f018e3f720f9f142166723768fe91c hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:27:54 -0000 https://status.hzmi.xyz/incident/356931#8bb5b4c9d2d9b969d8e463312f606c542c00ac718e70d205f3245716c1c33af1 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:27:54 -0000 https://status.hzmi.xyz/incident/356931#8bb5b4c9d2d9b969d8e463312f606c542c00ac718e70d205f3245716c1c33af1 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:25:01 -0000 https://status.hzmi.xyz/incident/356931#6a7b335b2f76e085d68ccb5d4c107c86c4b199d22755a10859238fa151a1138e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:25:01 -0000 https://status.hzmi.xyz/incident/356931#6a7b335b2f76e085d68ccb5d4c107c86c4b199d22755a10859238fa151a1138e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:18:57 -0000 https://status.hzmi.xyz/incident/356931#7970d4ee1db67e989ba99d157f7e2b398a2ec55d3326f4e458b5825832369b15 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/356931 Wed, 17 Apr 2024 18:18:57 -0000 https://status.hzmi.xyz/incident/356931#7970d4ee1db67e989ba99d157f7e2b398a2ec55d3326f4e458b5825832369b15 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/348285 Sat, 30 Mar 2024 15:15:14 -0000 https://status.hzmi.xyz/incident/348285#bceac78b6087ae84e6a26d38a819554c889dfcd3ed73ee5d0a02e231229a81b0 hzmi.dev recovered. https://status.hzmi.xyz/incident/348285 Sat, 30 Mar 2024 15:09:09 -0000 https://status.hzmi.xyz/incident/348285#3caf5f2e16150c1232f518ba5eb6acfe64a3689af1c59edf6f5447cf7df8b04c hzmi.dev went down. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:38:49 -0000 https://status.hzmi.xyz/incident/347769#130a65bd1be14ea2664b3f37cdd512072e674571af13a20e22316a1c213c4854 hzmi.dev recovered. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:38:31 -0000 https://status.hzmi.xyz/incident/347769#41a19e26a633186427edd472987ae62861bca75abf1660188cf3bbab2aff5209 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:32:35 -0000 https://status.hzmi.xyz/incident/347769#d4aedf7536d9327fc4d68624d51a5032e17b78f267a00917340f31398a4443a0 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:32:35 -0000 https://status.hzmi.xyz/incident/347769#d4aedf7536d9327fc4d68624d51a5032e17b78f267a00917340f31398a4443a0 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:08:46 -0000 https://status.hzmi.xyz/incident/347769#ab11e54eca714e475a584e0d3450a8761cffd34f4968580c08b5c84da0139faf hzmi.dev recovered. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 06:08:32 -0000 https://status.hzmi.xyz/incident/347769#9c9ac486c3a9d19af2dd7f56a6ad7bf519afeef4bfe1abff4f9cdc643ce6bece bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 05:53:49 -0000 https://status.hzmi.xyz/incident/347769#80da98d14c91b61cd18c5b17ada1b1112dc3d60d6282c03bbb027c3f287fe366 hzmi.dev went down. https://status.hzmi.xyz/incident/347769 Fri, 29 Mar 2024 05:53:26 -0000 https://status.hzmi.xyz/incident/347769#f95b36418924fddf062a791cb6811cc7a38d1df4b882b7bdca3a514d9f2e3f0d bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 11:23:56 -0000 https://status.hzmi.xyz/incident/346091#5d386e0551630be3ca6846411aa58ef402fbcbc7e54cda438b1b5e2e6c84758f hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 11:23:56 -0000 https://status.hzmi.xyz/incident/346091#5d386e0551630be3ca6846411aa58ef402fbcbc7e54cda438b1b5e2e6c84758f hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 11:14:51 -0000 https://status.hzmi.xyz/incident/346091#021964471fe59746b536d02c5da619ee8befaf5fa31fe729c1ff6b6b94a474aa hzmi.dev went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 11:14:38 -0000 https://status.hzmi.xyz/incident/346091#f206ec0972fd8c036db28f9b2c5b4a1a3b8beb214d171b52cb9faa58a6a0a7bc bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 07:44:30 -0000 https://status.hzmi.xyz/incident/346091#4dbd4c71a8d239e247034784bf3770f97af9e675606fd287cd2824e54b276737 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 07:41:31 -0000 https://status.hzmi.xyz/incident/346091#73e62b2888525444fc03d2655a5b753b42a0a1de58e365907f751b20b1556b50 hzmi.dev recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 07:20:14 -0000 https://status.hzmi.xyz/incident/346091#1807999bce2284ba4d4d13df1d5e89aa34da55c389faeb4c4d1085060acf5f73 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 07:20:14 -0000 https://status.hzmi.xyz/incident/346091#1807999bce2284ba4d4d13df1d5e89aa34da55c389faeb4c4d1085060acf5f73 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 03:53:11 -0000 https://status.hzmi.xyz/incident/346091#9af9e18425236aaa12064585682cd8f02fc31ab000a8533c674e893e8229818b hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 03:53:11 -0000 https://status.hzmi.xyz/incident/346091#9af9e18425236aaa12064585682cd8f02fc31ab000a8533c674e893e8229818b hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 03:38:09 -0000 https://status.hzmi.xyz/incident/346091#2ffbf65ef04718f0db97a1bb3f1900f50e16c01a2ee269a641529330ed65a423 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/346091 Tue, 26 Mar 2024 03:35:19 -0000 https://status.hzmi.xyz/incident/346091#492cea7d77bf5cabf0b72923a6e8801cd1405fc41f325e10343f4b69009a4c53 hzmi.dev went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 20:08:14 -0000 https://status.hzmi.xyz/incident/345522#3e8d0d68d4cf8e5b94cea1e0c9dffe09403c7f9905b3140619023efca9fd70d6 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 20:08:14 -0000 https://status.hzmi.xyz/incident/345522#3e8d0d68d4cf8e5b94cea1e0c9dffe09403c7f9905b3140619023efca9fd70d6 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 20:02:19 -0000 https://status.hzmi.xyz/incident/345522#557b0c56d68e5ea84ffe601ea727adfd3e19301bf31411abaf3d26fa0dfd31b0 hzmi.dev went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 20:02:06 -0000 https://status.hzmi.xyz/incident/345522#a0a7827c85a7c6cef0e0e403af69e1dc703e6d7c6eb699ff8e1176b806553d60 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 07:51:31 -0000 https://status.hzmi.xyz/incident/345522#b77c17d4e9c396156741bd7af5ce33fa918cea5bec0faec299cbe4b5717e1853 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 07:48:47 -0000 https://status.hzmi.xyz/incident/345522#d52ab7267cd69db5d11a3adaf5d9505efc2d0c1945a827a45430df49adbca4f4 hzmi.dev recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 07:30:26 -0000 https://status.hzmi.xyz/incident/345522#ffd4a90a7d94347fa8516c39cbdb3ac25631f849b0e390debd6e24905bb355c9 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 07:30:26 -0000 https://status.hzmi.xyz/incident/345522#ffd4a90a7d94347fa8516c39cbdb3ac25631f849b0e390debd6e24905bb355c9 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 02:03:33 -0000 https://status.hzmi.xyz/incident/345522#6529396858216ae0005464d179c08bc2090068e8ad31c5e6cf668b941480d6f0 hzmi.dev recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 02:03:23 -0000 https://status.hzmi.xyz/incident/345522#71a46673c1ca533ce77028c71cbc0b7f8b1e1ded72f0321cf5f1fbf57d3143e1 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 01:36:20 -0000 https://status.hzmi.xyz/incident/345522#cbd67be5d516920f77b401b374a401f6f6a5936c339ed2f49e01d36b9de73eb3 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345522 Mon, 25 Mar 2024 01:36:20 -0000 https://status.hzmi.xyz/incident/345522#cbd67be5d516920f77b401b374a401f6f6a5936c339ed2f49e01d36b9de73eb3 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345055 Sat, 23 Mar 2024 19:05:45 -0000 https://status.hzmi.xyz/incident/345055#fd7e98626e152a63a479ad7e6cbca270fbbeb3ec224fdf277cec55773f561ba8 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345055 Sat, 23 Mar 2024 19:05:45 -0000 https://status.hzmi.xyz/incident/345055#fd7e98626e152a63a479ad7e6cbca270fbbeb3ec224fdf277cec55773f561ba8 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/345055 Sat, 23 Mar 2024 18:23:36 -0000 https://status.hzmi.xyz/incident/345055#b02e638950e0fac45734159752175d1fc5778c51b9a502aed7880fec32efb0e2 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/345055 Sat, 23 Mar 2024 18:20:51 -0000 https://status.hzmi.xyz/incident/345055#32d41b452cdf238bce99825a0b942ed09672156e9062baa9e7e4304e21839aeb hzmi.dev went down. https://status.hzmi.xyz/incident/343815 Thu, 21 Mar 2024 00:29:14 -0000 https://status.hzmi.xyz/incident/343815#9901a5275b3c42115636f333de6661c0db67e2fc8315c5b7be22a30b2b51585e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/343815 Thu, 21 Mar 2024 00:29:14 -0000 https://status.hzmi.xyz/incident/343815#9901a5275b3c42115636f333de6661c0db67e2fc8315c5b7be22a30b2b51585e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/343815 Thu, 21 Mar 2024 00:23:17 -0000 https://status.hzmi.xyz/incident/343815#e6eae5ac10e93b6ba21aa8930a6dc92743a405a23fc1fa033f9d3a73e146ea68 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/343815 Thu, 21 Mar 2024 00:23:17 -0000 https://status.hzmi.xyz/incident/343815#e6eae5ac10e93b6ba21aa8930a6dc92743a405a23fc1fa033f9d3a73e146ea68 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341912 Sun, 17 Mar 2024 05:12:16 -0000 https://status.hzmi.xyz/incident/341912#031fb31c462d0b96ebf87a63ee3dfb5b9c535a34a4fd2de865505421da32585e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341912 Sun, 17 Mar 2024 05:12:16 -0000 https://status.hzmi.xyz/incident/341912#031fb31c462d0b96ebf87a63ee3dfb5b9c535a34a4fd2de865505421da32585e hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341912 Sun, 17 Mar 2024 03:21:17 -0000 https://status.hzmi.xyz/incident/341912#7f01e8525c12038fad668ce1c022ebc75961010a37b8d4aacc576946d9437d1c hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341912 Sun, 17 Mar 2024 03:21:17 -0000 https://status.hzmi.xyz/incident/341912#7f01e8525c12038fad668ce1c022ebc75961010a37b8d4aacc576946d9437d1c hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341641 Sat, 16 Mar 2024 12:12:25 -0000 https://status.hzmi.xyz/incident/341641#09f611b118c796c05eecb5f55813072928215ac7bdfcb5cc32070dd84a0454b7 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341641 Sat, 16 Mar 2024 12:12:25 -0000 https://status.hzmi.xyz/incident/341641#09f611b118c796c05eecb5f55813072928215ac7bdfcb5cc32070dd84a0454b7 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341641 Sat, 16 Mar 2024 09:36:18 -0000 https://status.hzmi.xyz/incident/341641#a5cec3dcc148a6f3a25a1eb149b95877648c1e5bedfb07a8ed4ff90f78f84687 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341641 Sat, 16 Mar 2024 09:36:18 -0000 https://status.hzmi.xyz/incident/341641#a5cec3dcc148a6f3a25a1eb149b95877648c1e5bedfb07a8ed4ff90f78f84687 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 15:00:11 -0000 https://status.hzmi.xyz/incident/341100#59aa79add4e0abd8b5f12c4d85f67c576f521afa958e6021ed40c0b544696d84 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 15:00:11 -0000 https://status.hzmi.xyz/incident/341100#59aa79add4e0abd8b5f12c4d85f67c576f521afa958e6021ed40c0b544696d84 hzmi.dev and bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 14:54:14 -0000 https://status.hzmi.xyz/incident/341100#1441a21518433b2ad0d573f507dd783e00cac5ddaa65ea8c5aa106b2e940624a hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 14:54:14 -0000 https://status.hzmi.xyz/incident/341100#1441a21518433b2ad0d573f507dd783e00cac5ddaa65ea8c5aa106b2e940624a hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 13:42:07 -0000 https://status.hzmi.xyz/incident/341100#11d776aede0b2419357807e8488d74c752b5163093060ed4abccab6d509938ab bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 13:36:09 -0000 https://status.hzmi.xyz/incident/341100#90569fbb3ad340e48b4ba5612223c2d66ad030731d1840adff114b7fd4f42f6a bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 13:33:21 -0000 https://status.hzmi.xyz/incident/341100#a9d0932b8bbb6b4d383d8d6418586c6474788d7c67d9bb011123ee7c2adddf48 hzmi.dev recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 13:33:08 -0000 https://status.hzmi.xyz/incident/341100#8019b804d9fd9f97761d07bd152176ce358eb029ffa9178e5966b2808719782d bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:44:27 -0000 https://status.hzmi.xyz/incident/341100#c461a7d7e90c2a88f1f9b716ff21899eae9e0f2a7a0fa0c21a63c82523f8f8ac bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:41:35 -0000 https://status.hzmi.xyz/incident/341100#200830b49ebbf3a41d0b51acf574877e4d03632fe91520a64ca66c8c76449903 hzmi.dev went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:26:29 -0000 https://status.hzmi.xyz/incident/341100#c07fa02f9e4f6eee39abdeaa014b016e04f67d25fa48bf4c32758e68fe01fb19 hzmi.dev recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:26:16 -0000 https://status.hzmi.xyz/incident/341100#db01e009da859aa9c5d688e4fad0df53768e85008bb30b73ccb2ee626509f9bc bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:20:16 -0000 https://status.hzmi.xyz/incident/341100#35bfe3de3ed4c933a374fd26aed22597dac06cb0e7929c8a813c0f15dd051020 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 10:20:16 -0000 https://status.hzmi.xyz/incident/341100#35bfe3de3ed4c933a374fd26aed22597dac06cb0e7929c8a813c0f15dd051020 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 05:33:49 -0000 https://status.hzmi.xyz/incident/341100#b153fdd0c7f43e5f36abe9bc558fc97de3c4af537149e1b462d2e57172f6ed24 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/341100 Fri, 15 Mar 2024 05:27:46 -0000 https://status.hzmi.xyz/incident/341100#5e623ffb5f8bd18784c587237077016c80971448c8e8e796d306d6096b239102 bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/339413 Mon, 11 Mar 2024 18:59:42 -0000 https://status.hzmi.xyz/incident/339413#2f6be971410a815297e526fbc19b0c66a728c9623a11c4ed30b2d9611d991087 hzmi.dev recovered. https://status.hzmi.xyz/incident/339413 Mon, 11 Mar 2024 18:54:16 -0000 https://status.hzmi.xyz/incident/339413#90cc6ea0c9b64723415013641b2dd10a2cc2f38020af9bcd1fe9e83f833e3a16 hzmi.dev went down. https://status.hzmi.xyz/incident/336967 Wed, 06 Mar 2024 08:16:50 -0000 https://status.hzmi.xyz/incident/336967#91a67006d6ba93e56771f8a2ac5fd0a5b16f8539d35dff7acb3ffd2b16cd099e bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/336967 Wed, 06 Mar 2024 08:14:03 -0000 https://status.hzmi.xyz/incident/336967#c170ce74ce006f18617f04a12ca3954f98b99e86999573b64b50c58d2e876d17 hzmi.dev recovered. https://status.hzmi.xyz/incident/336967 Wed, 06 Mar 2024 08:01:49 -0000 https://status.hzmi.xyz/incident/336967#9b49ca59c0381d08778a7470d49b9c2e2f8708f16eb62f96afce8258b4cdfb16 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/336967 Wed, 06 Mar 2024 08:01:49 -0000 https://status.hzmi.xyz/incident/336967#9b49ca59c0381d08778a7470d49b9c2e2f8708f16eb62f96afce8258b4cdfb16 hzmi.dev and bin.hzmi.xyz went down. https://status.hzmi.xyz/incident/333530 Thu, 29 Feb 2024 05:01:15 -0000 https://status.hzmi.xyz/incident/333530#442794df40a0274bea9b6a6bbd6fe929fc77f87eaa2998fbdc82987b6f2385fb hzmi.dev recovered. https://status.hzmi.xyz/incident/333530 Thu, 29 Feb 2024 05:00:52 -0000 https://status.hzmi.xyz/incident/333530#f24c9919d10e1d8ff06e99933783c7cc946bf5e5fd7dcf2b54328aaa5f5d63b5 bin.hzmi.xyz recovered. https://status.hzmi.xyz/incident/333530 Thu, 29 Feb 2024 04:54:02 -0000 https://status.hzmi.xyz/incident/333530#336f32383f7c383479b913ad1f89ab9c5bed8bc06c804b33db38c88e26747438 hzmi.dev went down. https://status.hzmi.xyz/incident/333530 Thu, 29 Feb 2024 04:53:50 -0000 https://status.hzmi.xyz/incident/333530#fd04074b06bab638d69f438ff604cf6e363a8a2037909465fe17aa0529c2c038 bin.hzmi.xyz went down.