Incidents reported on status page for Zeabur https://status.zeabur.com/ https://d1lppblt9t2x15.cloudfront.net/logos/2253e0a2e9071aaefa190bf759254f25.png https://status.zeabur.com/ en https://status.zeabur.com/ Fri, 13 Mar 2026 12:39:08 +0000 https://status.zeabur.com/#4a3fce38a1c7c36ec3604116ab333d97ab468465cfc04652e6fcfa198b41512b Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Fri, 13 Mar 2026 12:32:24 +0000 https://status.zeabur.com/#4a3fce38a1c7c36ec3604116ab333d97ab468465cfc04652e6fcfa198b41512b Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Fri, 13 Mar 2026 04:40:11 +0000 https://status.zeabur.com/#71657b52e565563cdc889af53c4463b9c3f39759685f6114723a0c1fb21f01f0 Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Fri, 13 Mar 2026 04:07:07 +0000 https://status.zeabur.com/#71657b52e565563cdc889af53c4463b9c3f39759685f6114723a0c1fb21f01f0 Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Thu, 12 Mar 2026 08:49:31 +0000 https://status.zeabur.com/#bb17586020ea665000da2905cbe18327fc832136b21c2ce75844b72b5a57671d Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Thu, 12 Mar 2026 08:34:24 +0000 https://status.zeabur.com/#bb17586020ea665000da2905cbe18327fc832136b21c2ce75844b72b5a57671d Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Thu, 12 Mar 2026 08:00:18 +0000 https://status.zeabur.com/#7fc8d893211985c2ecc788a401feea7ea52b1ddc424eef327b3c6efc2239789f Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Thu, 12 Mar 2026 07:42:26 +0000 https://status.zeabur.com/#7fc8d893211985c2ecc788a401feea7ea52b1ddc424eef327b3c6efc2239789f Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Wed, 11 Mar 2026 07:28:33 +0000 https://status.zeabur.com/#70f92afb144c573d2bb6520cc0ed7d800b45fd7c4c5ba01eb41727e02676e73a Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Wed, 11 Mar 2026 04:54:54 +0000 https://status.zeabur.com/#70f92afb144c573d2bb6520cc0ed7d800b45fd7c4c5ba01eb41727e02676e73a Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Tue, 10 Mar 2026 16:53:40 +0000 https://status.zeabur.com/#0fed31051952c9cb595c7e6553b9dd77e0d2cfeccfa50b90c62b32cefe1ce2fe Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Tue, 10 Mar 2026 16:35:48 +0000 https://status.zeabur.com/#0fed31051952c9cb595c7e6553b9dd77e0d2cfeccfa50b90c62b32cefe1ce2fe Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Sun, 08 Mar 2026 11:05:24 +0000 https://status.zeabur.com/#31dd8701b14c115f7db0c2352ca093880f2cd6483fa57381c42edc4c5a9536f4 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sun, 08 Mar 2026 11:03:10 +0000 https://status.zeabur.com/#31dd8701b14c115f7db0c2352ca093880f2cd6483fa57381c42edc4c5a9536f4 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sun, 08 Mar 2026 10:50:25 +0000 https://status.zeabur.com/#877606fad44ab0cbbb6d390dfa2334989a987ff982ef637f7f0a27035eab4ced Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Sun, 08 Mar 2026 10:40:27 +0000 https://status.zeabur.com/#877606fad44ab0cbbb6d390dfa2334989a987ff982ef637f7f0a27035eab4ced Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Fri, 06 Mar 2026 07:45:54 +0000 https://status.zeabur.com/#b340121e9e517fba7d21601af62da115d4993afa5361e2a8c84d3b70b21ea530 Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Fri, 06 Mar 2026 07:39:11 +0000 https://status.zeabur.com/#b340121e9e517fba7d21601af62da115d4993afa5361e2a8c84d3b70b21ea530 Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Thu, 05 Mar 2026 13:26:47 +0000 https://status.zeabur.com/#6ea256d598a6595067855317fcecb111f0df857b65f6aecc6e4078ce38ba4c93 Landing Page recovered https://status.zeabur.com/ Thu, 05 Mar 2026 13:17:52 +0000 https://status.zeabur.com/#6ea256d598a6595067855317fcecb111f0df857b65f6aecc6e4078ce38ba4c93 Landing Page went down https://status.zeabur.com/ Tue, 03 Mar 2026 17:34:13 +0000 https://status.zeabur.com/#299bbc8847bf9cee42af198d2e8a8fcb2e322e8aca2b9e1847ff8124ec9d7f5b Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Tue, 03 Mar 2026 17:31:41 +0000 https://status.zeabur.com/#299bbc8847bf9cee42af198d2e8a8fcb2e322e8aca2b9e1847ff8124ec9d7f5b Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 02 Mar 2026 18:02:26 +0000 https://status.zeabur.com/#ebd5606887f1c8b410483610789f5df15440baaa1a59886323aed4124ae1b52c Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Mon, 02 Mar 2026 16:03:25 +0000 https://status.zeabur.com/#ebd5606887f1c8b410483610789f5df15440baaa1a59886323aed4124ae1b52c Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Mon, 02 Mar 2026 14:32:22 +0000 https://status.zeabur.com/#95280916075b1266d9baa7a0d824dedc7e88625526440fb8ccf03ba6c12c4254 Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Mon, 02 Mar 2026 13:50:45 +0000 https://status.zeabur.com/#95280916075b1266d9baa7a0d824dedc7e88625526440fb8ccf03ba6c12c4254 Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Sun, 01 Mar 2026 14:36:15 +0000 https://status.zeabur.com/#bb3a0cebdde7dae701bb378a139c49d3c19bfcdb1dfa253af403608cad974369 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sun, 01 Mar 2026 14:31:38 +0000 https://status.zeabur.com/#bb3a0cebdde7dae701bb378a139c49d3c19bfcdb1dfa253af403608cad974369 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 23 Feb 2026 05:17:37 +0000 https://status.zeabur.com/#171cb6cdd30cdfb473fbb3ecf5eb630b3968943ddb32d657e6a4102f52d5bb9c Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Sun, 22 Feb 2026 15:08:03 +0000 https://status.zeabur.com/#d00bab5c6e770b1f14701c36a18fda2032835c5e4dd4ea2e37e6cc1103a5a98f Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Sun, 22 Feb 2026 15:07:09 +0000 https://status.zeabur.com/#d00bab5c6e770b1f14701c36a18fda2032835c5e4dd4ea2e37e6cc1103a5a98f Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Sun, 22 Feb 2026 11:56:42 +0000 https://status.zeabur.com/#22ef5235922f956bdcdbb5f193d2674801d2c9f909613598577a05537a318648 Landing Page recovered https://status.zeabur.com/ Sun, 22 Feb 2026 11:53:40 +0000 https://status.zeabur.com/#22ef5235922f956bdcdbb5f193d2674801d2c9f909613598577a05537a318648 Landing Page went down https://status.zeabur.com/ Sat, 21 Feb 2026 14:50:40 +0000 https://status.zeabur.com/#bc3b77bd7e93decbe09b5bd97b8d41223c0c15d1efdc9f6d1175ba715bfae137 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 21 Feb 2026 14:50:27 +0000 https://status.zeabur.com/#057e31eab4044c1a5f40956d726782cfbfc8adbf5d254656191dbdd6579d87d4 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Sat, 21 Feb 2026 14:44:20 +0000 https://status.zeabur.com/#bc3b77bd7e93decbe09b5bd97b8d41223c0c15d1efdc9f6d1175ba715bfae137 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 21 Feb 2026 14:39:20 +0000 https://status.zeabur.com/#5c237f34181f03fa41643d8136ef0106ac25247c43d13bd5a70673524c5a33b7 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 21 Feb 2026 14:36:38 +0000 https://status.zeabur.com/#5c237f34181f03fa41643d8136ef0106ac25247c43d13bd5a70673524c5a33b7 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 21 Feb 2026 14:35:38 +0000 https://status.zeabur.com/#057e31eab4044c1a5f40956d726782cfbfc8adbf5d254656191dbdd6579d87d4 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sat, 21 Feb 2026 02:39:19 +0000 https://status.zeabur.com/#c4ee991098fb7b225fae4fb0f8c8156cc0381914f499a45b909b585a1a56007f Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 21 Feb 2026 02:36:20 +0000 https://status.zeabur.com/#c4ee991098fb7b225fae4fb0f8c8156cc0381914f499a45b909b585a1a56007f Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 15:22:45 +0000 https://status.zeabur.com/#2849eceee34e1ba1e3bc4b5d8f3d687725ca4a6de8b338eacc4955bbf08ea66c Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 10:26:21 +0000 https://status.zeabur.com/#2849eceee34e1ba1e3bc4b5d8f3d687725ca4a6de8b338eacc4955bbf08ea66c Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 10:00:11 +0000 https://status.zeabur.com/#b385e33f21731519e19566268d844049773273696b01cbc714d39b68683a5f33 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 08:52:04 +0000 https://status.zeabur.com/#b385e33f21731519e19566268d844049773273696b01cbc714d39b68683a5f33 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 08:17:53 +0000 https://status.zeabur.com/#3422d1e104d14a2a7d10807f35b073d09deb497ab4ce4f7793ecfc4be913d250 Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 08:14:03 +0000 https://status.zeabur.com/#d316553cd400188f276f7ab76d7a068ef37b22c2c92c4f55bac4a9dde5e065c5 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 08:06:29 +0000 https://status.zeabur.com/#272ee82b91ef95add55560645d725baa18682152ee5d65a9fa398fa767e0f502 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 08:06:14 +0000 https://status.zeabur.com/#b957fb2c83137cf2c5c7304d9a41d24f7cea01d888c8bfce864bfc5d1b5b79c5 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 08:03:26 +0000 https://status.zeabur.com/#b957fb2c83137cf2c5c7304d9a41d24f7cea01d888c8bfce864bfc5d1b5b79c5 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 08:03:04 +0000 https://status.zeabur.com/#3422d1e104d14a2a7d10807f35b073d09deb497ab4ce4f7793ecfc4be913d250 Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 08:02:38 +0000 https://status.zeabur.com/#272ee82b91ef95add55560645d725baa18682152ee5d65a9fa398fa767e0f502 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 07:53:28 +0000 https://status.zeabur.com/#d316553cd400188f276f7ab76d7a068ef37b22c2c92c4f55bac4a9dde5e065c5 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 07:39:54 +0000 https://status.zeabur.com/#171cb6cdd30cdfb473fbb3ecf5eb630b3968943ddb32d657e6a4102f52d5bb9c Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 07:17:40 +0000 https://status.zeabur.com/#821617bb0b4c5f7bfa63b8812cebbaef9f92bae9919c800386ca8db36feeeca7 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 05:35:32 +0000 https://status.zeabur.com/#821617bb0b4c5f7bfa63b8812cebbaef9f92bae9919c800386ca8db36feeeca7 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 19 Feb 2026 04:19:06 +0000 https://status.zeabur.com/#29a668308dfc20277a78d9c3f7b0137eabf4478f7718faa836d67cf1c70e10b2 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 19 Feb 2026 03:42:29 +0000 https://status.zeabur.com/#29a668308dfc20277a78d9c3f7b0137eabf4478f7718faa836d67cf1c70e10b2 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Wed, 18 Feb 2026 20:42:37 +0000 https://status.zeabur.com/#046a99798908c1140599fe500ab486cef8aa6ad5c72fb607a6bf993653ca8032 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Wed, 18 Feb 2026 20:42:30 +0000 https://status.zeabur.com/#046a99798908c1140599fe500ab486cef8aa6ad5c72fb607a6bf993653ca8032 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Tue, 17 Feb 2026 10:39:28 +0000 https://status.zeabur.com/#2bd2028b97aba649e1687f1ae4b16ade7dec9e792a1ef8a1456da8be27e290b8 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Tue, 17 Feb 2026 10:38:54 +0000 https://status.zeabur.com/#112f571707844e5189c3312d576b9087712531acfa08a05621efccc2d91b3c76 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Tue, 17 Feb 2026 10:38:13 +0000 https://status.zeabur.com/#112f571707844e5189c3312d576b9087712531acfa08a05621efccc2d91b3c76 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Tue, 17 Feb 2026 10:37:34 +0000 https://status.zeabur.com/#2bd2028b97aba649e1687f1ae4b16ade7dec9e792a1ef8a1456da8be27e290b8 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Tue, 17 Feb 2026 10:05:42 +0000 https://status.zeabur.com/#5d32b886296afdc72daa1fc115cc44c706c8d59bc918dfe7f38a609fc4838400 Landing Page recovered https://status.zeabur.com/ Tue, 17 Feb 2026 10:00:08 +0000 https://status.zeabur.com/#5d32b886296afdc72daa1fc115cc44c706c8d59bc918dfe7f38a609fc4838400 Landing Page went down https://status.zeabur.com/ Mon, 16 Feb 2026 23:02:50 +0000 https://status.zeabur.com/#3dc69bc32d990e8774450236b58b2f1563eb1b70964f045ee08990e0ed8b8e98 Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 22:51:20 +0000 https://status.zeabur.com/#69d2f704a7ad6ae5e5453c84cdd5f21f2dfe8b1f4dca19638934d37e31818eb8 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 22:49:19 +0000 https://status.zeabur.com/#86ef11ef00cee7ec743c2539f99a00156ba6dfad08ce3187c83eef009b5bd2df California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 22:48:36 +0000 https://status.zeabur.com/#e74331e5b52703f8a2cbcd631d212a85557cdbaa1684db5a0864ec844d972378 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 22:48:02 +0000 https://status.zeabur.com/#3dc69bc32d990e8774450236b58b2f1563eb1b70964f045ee08990e0ed8b8e98 Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 22:45:27 +0000 https://status.zeabur.com/#69d2f704a7ad6ae5e5453c84cdd5f21f2dfe8b1f4dca19638934d37e31818eb8 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 22:44:52 +0000 https://status.zeabur.com/#e74331e5b52703f8a2cbcd631d212a85557cdbaa1684db5a0864ec844d972378 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 22:44:46 +0000 https://status.zeabur.com/#86ef11ef00cee7ec743c2539f99a00156ba6dfad08ce3187c83eef009b5bd2df California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 14:17:55 +0000 https://status.zeabur.com/#e149b4c269440fc4e235e4e5c159329da9320535c031ca2fd149872e49a8966b Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 14:15:28 +0000 https://status.zeabur.com/#876fa2f9378758cdd96251ebc07ed9d1c0f3e13be18ec74f8e9fb5ea7c016d3c Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 14:14:41 +0000 https://status.zeabur.com/#bbe8af639a4b192ee4894095c14334fe90d42b65543bf8b70a8ee5ad1b490dad Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 14:14:25 +0000 https://status.zeabur.com/#3ead7176c23166055b3e6d03fe6ce8d7444cea504c4ba40598b9a2c4d85ef770 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Mon, 16 Feb 2026 14:09:22 +0000 https://status.zeabur.com/#876fa2f9378758cdd96251ebc07ed9d1c0f3e13be18ec74f8e9fb5ea7c016d3c Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 14:03:04 +0000 https://status.zeabur.com/#e149b4c269440fc4e235e4e5c159329da9320535c031ca2fd149872e49a8966b Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 14:02:39 +0000 https://status.zeabur.com/#3ead7176c23166055b3e6d03fe6ce8d7444cea504c4ba40598b9a2c4d85ef770 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Mon, 16 Feb 2026 14:01:55 +0000 https://status.zeabur.com/#bbe8af639a4b192ee4894095c14334fe90d42b65543bf8b70a8ee5ad1b490dad Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 15 Feb 2026 09:57:21 +0000 https://status.zeabur.com/#c9fe4d546fae07c054f1d73ad22105702bd391688eb53138728fbc0fcb3e91bd Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sun, 15 Feb 2026 09:55:20 +0000 https://status.zeabur.com/#2c03e46de7fa5889a550b96cce542ca8f3783a26f39ce92ec9fe96e71a323034 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Sun, 15 Feb 2026 09:55:10 +0000 https://status.zeabur.com/#451d9f2e4379dd9bb47b31d0e1b771dcde2e2b64286544bf68107fa23f3c6f85 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sun, 15 Feb 2026 09:54:38 +0000 https://status.zeabur.com/#2c03e46de7fa5889a550b96cce542ca8f3783a26f39ce92ec9fe96e71a323034 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sun, 15 Feb 2026 09:54:24 +0000 https://status.zeabur.com/#451d9f2e4379dd9bb47b31d0e1b771dcde2e2b64286544bf68107fa23f3c6f85 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 15 Feb 2026 09:54:24 +0000 https://status.zeabur.com/#c9fe4d546fae07c054f1d73ad22105702bd391688eb53138728fbc0fcb3e91bd Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sun, 15 Feb 2026 04:00:08 +0000 https://status.zeabur.com/#79eac70adb8dddea396a1eb0dc8ff626e9bab9b8c62910a0044dc01a4ef3506a Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sun, 15 Feb 2026 03:37:53 +0000 https://status.zeabur.com/#79eac70adb8dddea396a1eb0dc8ff626e9bab9b8c62910a0044dc01a4ef3506a Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 15 Feb 2026 01:39:05 +0000 https://status.zeabur.com/#57bbc1ec507f0f97bb982ffbbedec7aa956059759ff0b48a8073fe9f4cf29bfd Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Sun, 15 Feb 2026 01:37:23 +0000 https://status.zeabur.com/#57bbc1ec507f0f97bb982ffbbedec7aa956059759ff0b48a8073fe9f4cf29bfd Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 15:33:38 +0000 https://status.zeabur.com/#fc07dd1f090e374bc416f4b3a6fd1cbeac298a87452d1d7fbd9601de49b87d2b Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 15:33:14 +0000 https://status.zeabur.com/#5f5185af962aec61a608270617524950cab5470ff0525f8ffcccc464c1f2790c Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 15:32:37 +0000 https://status.zeabur.com/#fc07dd1f090e374bc416f4b3a6fd1cbeac298a87452d1d7fbd9601de49b87d2b Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 15:31:04 +0000 https://status.zeabur.com/#6ae00e33d5ed95e7963d4764c4fa6efdea8325c416186b63a967b86b6ac5a713 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 15:30:08 +0000 https://status.zeabur.com/#5f5185af962aec61a608270617524950cab5470ff0525f8ffcccc464c1f2790c Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 15:30:07 +0000 https://status.zeabur.com/#6ae00e33d5ed95e7963d4764c4fa6efdea8325c416186b63a967b86b6ac5a713 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 13:42:10 +0000 https://status.zeabur.com/#bdd0b11aee45a8353ae421711d93ac238ff6c9f889cb1d50a485d58b201ec294 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 13:39:57 +0000 https://status.zeabur.com/#36f3c06360f0c7cb330b20e51bb401b5b16a2f749af6b180ce7e5df21e7e5db5 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 13:30:26 +0000 https://status.zeabur.com/#36f3c06360f0c7cb330b20e51bb401b5b16a2f749af6b180ce7e5df21e7e5db5 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 13:27:29 +0000 https://status.zeabur.com/#bdd0b11aee45a8353ae421711d93ac238ff6c9f889cb1d50a485d58b201ec294 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 11:45:20 +0000 https://status.zeabur.com/#a023c8d9092673483e3d1fe01fa8e8e669f7a7cdda29bddfa04dc37a23179f93 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 11:44:30 +0000 https://status.zeabur.com/#44597b0f363e1b6c5736a9163d5d75589f7e0ec867ade2b9a5e31e45aebba84b California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 11:44:02 +0000 https://status.zeabur.com/#4ce0b73cec71047606ab9b3e3172171bddaa1cc8915ea21c44050c90e5d58ab2 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 11:36:31 +0000 https://status.zeabur.com/#a023c8d9092673483e3d1fe01fa8e8e669f7a7cdda29bddfa04dc37a23179f93 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 11:32:47 +0000 https://status.zeabur.com/#1dfd5c6a45a662f3e6b9952f4e573f5c819d6e9271bd25a00abdd661d7b7560e Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 11:30:13 +0000 https://status.zeabur.com/#796b8752c0bd12967151bf6771b7c0fa947d7c63765cb9e0b2250e370c0882cb Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 11:03:03 +0000 https://status.zeabur.com/#1dfd5c6a45a662f3e6b9952f4e573f5c819d6e9271bd25a00abdd661d7b7560e Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 11:00:39 +0000 https://status.zeabur.com/#796b8752c0bd12967151bf6771b7c0fa947d7c63765cb9e0b2250e370c0882cb Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 10:57:22 +0000 https://status.zeabur.com/#1f4f92d1eaa3247ce891e94e05dd051fb6175dedca1bbb823171c024560fff9f Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 10:51:35 +0000 https://status.zeabur.com/#1f4f92d1eaa3247ce891e94e05dd051fb6175dedca1bbb823171c024560fff9f Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 10:48:15 +0000 https://status.zeabur.com/#509d6e38194da13a59d51ef7993665ea034dabc8b80d9e7013ba2f9988f1c2c7 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 10:47:50 +0000 https://status.zeabur.com/#743bccd6c4ec57f7e735fa39d9709809343ca2be7c7173dd011beab89eb71eaf Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 10:36:25 +0000 https://status.zeabur.com/#509d6e38194da13a59d51ef7993665ea034dabc8b80d9e7013ba2f9988f1c2c7 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 10:27:17 +0000 https://status.zeabur.com/#8ce937cdf51284ec4f5aaec5a61209b0555ee1189f9b999239bc23e44ccf62f0 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 10:18:09 +0000 https://status.zeabur.com/#743bccd6c4ec57f7e735fa39d9709809343ca2be7c7173dd011beab89eb71eaf Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 10:09:28 +0000 https://status.zeabur.com/#8ce937cdf51284ec4f5aaec5a61209b0555ee1189f9b999239bc23e44ccf62f0 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 10:02:50 +0000 https://status.zeabur.com/#0890b76fe019e472f450560e6d59000a0f06e5388e07e0e45add9f316a6947da Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 10:00:11 +0000 https://status.zeabur.com/#50d743ced7849707f369f0a7d739d6322ad80dc4902b6c1f74dc18598fc73f36 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 09:48:36 +0000 https://status.zeabur.com/#50d743ced7849707f369f0a7d739d6322ad80dc4902b6c1f74dc18598fc73f36 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 09:48:05 +0000 https://status.zeabur.com/#0890b76fe019e472f450560e6d59000a0f06e5388e07e0e45add9f316a6947da Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 09:45:16 +0000 https://status.zeabur.com/#8c828cbdc2ee1e885ee452976993656d994371293ccc913f86e997488fab80c7 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 14 Feb 2026 09:39:36 +0000 https://status.zeabur.com/#8c828cbdc2ee1e885ee452976993656d994371293ccc913f86e997488fab80c7 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 09:38:53 +0000 https://status.zeabur.com/#4ce0b73cec71047606ab9b3e3172171bddaa1cc8915ea21c44050c90e5d58ab2 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 14 Feb 2026 09:38:39 +0000 https://status.zeabur.com/#44597b0f363e1b6c5736a9163d5d75589f7e0ec867ade2b9a5e31e45aebba84b California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Mon, 09 Feb 2026 12:35:46 +0000 https://status.zeabur.com/#4f9d2561e7cfa4e7225d3a9b423b287ca2c417d76cb3f7243b0ce7a37f0a6111 Landing Page recovered https://status.zeabur.com/ Mon, 09 Feb 2026 12:33:20 +0000 https://status.zeabur.com/#4f9d2561e7cfa4e7225d3a9b423b287ca2c417d76cb3f7243b0ce7a37f0a6111 Landing Page went down https://status.zeabur.com/ Mon, 09 Feb 2026 12:32:42 +0000 https://status.zeabur.com/#ea86f09e3d30a75b8ce81baf05c1ebbd5fdd4fc11c728a36732fdee379622726 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Mon, 09 Feb 2026 12:31:48 +0000 https://status.zeabur.com/#ea86f09e3d30a75b8ce81baf05c1ebbd5fdd4fc11c728a36732fdee379622726 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 07 Feb 2026 10:02:24 +0000 https://status.zeabur.com/#88ea75773831a56889d2fe76b7a719dee761ca27bb201981945ded4186d7b5bc Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Sat, 07 Feb 2026 09:47:43 +0000 https://status.zeabur.com/#88ea75773831a56889d2fe76b7a719dee761ca27bb201981945ded4186d7b5bc Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Sat, 07 Feb 2026 09:32:31 +0000 https://status.zeabur.com/#d5097c51555a17a972f2f23032359b52e0ac2ba03862647aee698da30ac08cdd Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Sat, 07 Feb 2026 08:47:39 +0000 https://status.zeabur.com/#d5097c51555a17a972f2f23032359b52e0ac2ba03862647aee698da30ac08cdd Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Thu, 05 Feb 2026 15:53:51 +0000 https://status.zeabur.com/#232a39c595b24e9c2f06517a72d401c148645bc5af8b2863790d89ee431253fb Landing Page recovered https://status.zeabur.com/ Thu, 05 Feb 2026 15:51:39 +0000 https://status.zeabur.com/#232a39c595b24e9c2f06517a72d401c148645bc5af8b2863790d89ee431253fb Landing Page went down https://status.zeabur.com/ Thu, 05 Feb 2026 15:51:37 +0000 https://status.zeabur.com/#d0101bd5841b4dc6070c91e33ef0031a10e11ed0a5c89a37f4e3f0ff4254b190 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Thu, 05 Feb 2026 15:50:46 +0000 https://status.zeabur.com/#d0101bd5841b4dc6070c91e33ef0031a10e11ed0a5c89a37f4e3f0ff4254b190 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Wed, 04 Feb 2026 14:47:42 +0000 https://status.zeabur.com/#9c85d59d1b413132a8be8bec11c6a0723d50f15b123b926ca597edfe19d3e806 Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Wed, 04 Feb 2026 08:16:26 +0000 https://status.zeabur.com/#2cd1b0a32e46e095f7f3803cdc911eaa7e4a5fbdbd7a6018f9dec0899a0c8acc California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Wed, 04 Feb 2026 08:15:47 +0000 https://status.zeabur.com/#2cd1b0a32e46e095f7f3803cdc911eaa7e4a5fbdbd7a6018f9dec0899a0c8acc California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sun, 01 Feb 2026 08:11:12 +0000 https://status.zeabur.com/#022b3411cdad327e3fb33c01a2856d02064e2dbab8603b375c73b2cc37f7c1a4 Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Sun, 01 Feb 2026 07:52:03 +0000 https://status.zeabur.com/#022b3411cdad327e3fb33c01a2856d02064e2dbab8603b375c73b2cc37f7c1a4 Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Sat, 31 Jan 2026 19:51:07 +0000 https://status.zeabur.com/#1a490a8988fb96626d337dfe2ab68737f2b0e77b48b7628722c8d192a1b8afaa Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Sat, 31 Jan 2026 19:50:24 +0000 https://status.zeabur.com/#1a490a8988fb96626d337dfe2ab68737f2b0e77b48b7628722c8d192a1b8afaa Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Sat, 31 Jan 2026 15:17:47 +0000 https://status.zeabur.com/#08c640ab341df559d380f50222548b09c85c59d6517023df73776a660aaaeabd Landing Page recovered https://status.zeabur.com/ Sat, 31 Jan 2026 15:11:43 +0000 https://status.zeabur.com/#08c640ab341df559d380f50222548b09c85c59d6517023df73776a660aaaeabd Landing Page went down https://status.zeabur.com/ Thu, 29 Jan 2026 13:34:50 +0000 https://status.zeabur.com/#9c85d59d1b413132a8be8bec11c6a0723d50f15b123b926ca597edfe19d3e806 Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Thu, 29 Jan 2026 04:38:04 +0000 https://status.zeabur.com/#cb3d6a7206d301056f9f7fe99842c9e190dbaa457d98638390f71ef3e411e522 Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Thu, 29 Jan 2026 04:34:05 +0000 https://status.zeabur.com/#cb3d6a7206d301056f9f7fe99842c9e190dbaa457d98638390f71ef3e411e522 Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Wed, 28 Jan 2026 15:17:17 +0000 https://status.zeabur.com/#fd784ee84adca96f4025682651b3ffbf51acf55e90f2c73ebe0357ea51497310 Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Wed, 28 Jan 2026 13:02:20 +0000 https://status.zeabur.com/#fd784ee84adca96f4025682651b3ffbf51acf55e90f2c73ebe0357ea51497310 Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Tue, 27 Jan 2026 10:27:13 +0000 https://status.zeabur.com/#9c9647c99af3379004b02db8f653e6741bd16229b1e02925164f398dc002ae96 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Tue, 27 Jan 2026 10:24:37 +0000 https://status.zeabur.com/#9c9647c99af3379004b02db8f653e6741bd16229b1e02925164f398dc002ae96 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 26 Jan 2026 16:27:14 +0000 https://status.zeabur.com/#01936e3a1b555582eaea7768351a1f496654e45fb0e4ac9dbf1c6af070bd8c94 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Mon, 26 Jan 2026 16:24:33 +0000 https://status.zeabur.com/#01936e3a1b555582eaea7768351a1f496654e45fb0e4ac9dbf1c6af070bd8c94 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 24 Jan 2026 22:26:00 +0000 https://status.zeabur.com/#7ad3384cb943fa956b7e480aa76f014eab93c3175ee584b348e71a05163303d7 Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Sat, 24 Jan 2026 10:14:47 +0000 https://status.zeabur.com/#39df0194d44a059b665dc0a9a4bd215514558694462840b0b5d742359a6b0c80 Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Fri, 23 Jan 2026 19:17:55 +0000 https://status.zeabur.com/#990174a99e53b504ffd7f66f84d67a6517f3a5ca80cbc3a0f1ae60e73abffbf2 Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Fri, 23 Jan 2026 19:02:46 +0000 https://status.zeabur.com/#990174a99e53b504ffd7f66f84d67a6517f3a5ca80cbc3a0f1ae60e73abffbf2 Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Fri, 23 Jan 2026 04:28:07 +0000 https://status.zeabur.com/#05ec9a1a9aad0e32a08f214bbfb1a579400be0c7e942f4e95c6077ebacbda810 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Fri, 23 Jan 2026 04:08:30 +0000 https://status.zeabur.com/#05ec9a1a9aad0e32a08f214bbfb1a579400be0c7e942f4e95c6077ebacbda810 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Fri, 23 Jan 2026 01:11:44 +0000 https://status.zeabur.com/#3a8a328fde24506cfdb37561cdcc63577f4821355a9df88c7add02addc6302bb Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Fri, 23 Jan 2026 01:11:01 +0000 https://status.zeabur.com/#3a8a328fde24506cfdb37561cdcc63577f4821355a9df88c7add02addc6302bb Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 22 Jan 2026 21:11:38 +0000 https://status.zeabur.com/#39df0194d44a059b665dc0a9a4bd215514558694462840b0b5d742359a6b0c80 Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Thu, 22 Jan 2026 16:42:46 +0000 https://status.zeabur.com/#b7bae6700570361b928f15495a9ec2529679fc6d8da23f96f6574d4d94e40765 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 22 Jan 2026 16:42:03 +0000 https://status.zeabur.com/#b7bae6700570361b928f15495a9ec2529679fc6d8da23f96f6574d4d94e40765 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Mon, 19 Jan 2026 11:05:41 +0000 https://status.zeabur.com/#8ee0a35899f15b82692b4b4f81fe3c7bb73438498bb788600f673001481da0bc Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Mon, 19 Jan 2026 10:56:53 +0000 https://status.zeabur.com/#8ee0a35899f15b82692b4b4f81fe3c7bb73438498bb788600f673001481da0bc Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Mon, 19 Jan 2026 10:11:53 +0000 https://status.zeabur.com/#67ba591317e909391d032088df7c91cd14879c60d999a314260004fcaa95a5d8 Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Mon, 19 Jan 2026 10:02:47 +0000 https://status.zeabur.com/#67ba591317e909391d032088df7c91cd14879c60d999a314260004fcaa95a5d8 Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Sun, 18 Jan 2026 16:51:45 +0000 https://status.zeabur.com/#616fbab0e2f940068ae4ac069f03a8ce9c8f0075119f5f5f415b27a37cf01e75 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sun, 18 Jan 2026 16:48:32 +0000 https://status.zeabur.com/#616fbab0e2f940068ae4ac069f03a8ce9c8f0075119f5f5f415b27a37cf01e75 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sun, 18 Jan 2026 16:45:19 +0000 https://status.zeabur.com/#589835c8676becc1866096360b2a8de2223f4844bfeace84a91cea99a0640479 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sun, 18 Jan 2026 16:33:28 +0000 https://status.zeabur.com/#589835c8676becc1866096360b2a8de2223f4844bfeace84a91cea99a0640479 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sun, 18 Jan 2026 11:52:04 +0000 https://status.zeabur.com/#49a3d0cda930de7bf7cdbde9c1b8b60145a3c718c1ec4149db142981d741f21e Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Sun, 18 Jan 2026 11:51:33 +0000 https://status.zeabur.com/#49a3d0cda930de7bf7cdbde9c1b8b60145a3c718c1ec4149db142981d741f21e Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Sat, 17 Jan 2026 04:43:52 +0000 https://status.zeabur.com/#7ad3384cb943fa956b7e480aa76f014eab93c3175ee584b348e71a05163303d7 Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Thu, 15 Jan 2026 23:44:05 +0000 https://status.zeabur.com/#fcba07f63d67d4850f66c9192a861ba3b9344541b698468a64c8801d034404fb Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Thu, 15 Jan 2026 23:38:12 +0000 https://status.zeabur.com/#fcba07f63d67d4850f66c9192a861ba3b9344541b698468a64c8801d034404fb Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Thu, 15 Jan 2026 18:54:06 +0000 https://status.zeabur.com/#93388c3e0cedb85785e78b2caf21f93642621728ef23e1ae13cf2128bb6673e9 Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Thu, 15 Jan 2026 18:51:12 +0000 https://status.zeabur.com/#93388c3e0cedb85785e78b2caf21f93642621728ef23e1ae13cf2128bb6673e9 Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Thu, 15 Jan 2026 04:14:30 +0000 https://status.zeabur.com/#2fd304aa6c677bb3ca34b21da93a9839b1d48d4b5afe943864f7821e813485e1 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Thu, 15 Jan 2026 04:11:45 +0000 https://status.zeabur.com/#4801af6c4a740a3ce31f50b075442c8fb8b29683148aa3ee14300137b0ebb154 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Thu, 15 Jan 2026 04:11:02 +0000 https://status.zeabur.com/#4801af6c4a740a3ce31f50b075442c8fb8b29683148aa3ee14300137b0ebb154 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Thu, 15 Jan 2026 04:10:43 +0000 https://status.zeabur.com/#2fd304aa6c677bb3ca34b21da93a9839b1d48d4b5afe943864f7821e813485e1 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Thu, 15 Jan 2026 02:09:05 +0000 https://status.zeabur.com/#92d29b07695700f72ac3d98d9813b2fd8425f69ca4ad358646a9451c42c9a49f Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Thu, 15 Jan 2026 01:58:26 +0000 https://status.zeabur.com/#92d29b07695700f72ac3d98d9813b2fd8425f69ca4ad358646a9451c42c9a49f Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Wed, 14 Jan 2026 11:22:26 +0000 https://status.zeabur.com/#e24b7a662f137e4bbb9a37638b68bc8544a199053ab2c77313eb2d44b4ca4070 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Wed, 14 Jan 2026 11:13:27 +0000 https://status.zeabur.com/#e24b7a662f137e4bbb9a37638b68bc8544a199053ab2c77313eb2d44b4ca4070 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Wed, 14 Jan 2026 00:47:12 +0000 https://status.zeabur.com/#c3d701df60d48dc4ac8bb1ebe315e56a80e5a1b43524a0504f186b204806ed22 Taipei, Taiwan - Amazon Web Service (tpe1) recovered https://status.zeabur.com/ Wed, 14 Jan 2026 00:45:11 +0000 https://status.zeabur.com/#c3d701df60d48dc4ac8bb1ebe315e56a80e5a1b43524a0504f186b204806ed22 Taipei, Taiwan - Amazon Web Service (tpe1) went down https://status.zeabur.com/ Tue, 13 Jan 2026 19:17:40 +0000 https://status.zeabur.com/#74023f92acae845ca4752c8110e105e79b704fa4d5ed851b1520463e94daf25d Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 19:02:53 +0000 https://status.zeabur.com/#74023f92acae845ca4752c8110e105e79b704fa4d5ed851b1520463e94daf25d Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Tue, 13 Jan 2026 18:38:47 +0000 https://status.zeabur.com/#fa33394c0253f30e9637bae5e948d89b71daa3ef83e76140f4b87cc3157b0296 Landing Page recovered https://status.zeabur.com/ Tue, 13 Jan 2026 18:35:51 +0000 https://status.zeabur.com/#fa33394c0253f30e9637bae5e948d89b71daa3ef83e76140f4b87cc3157b0296 Landing Page went down https://status.zeabur.com/ Tue, 13 Jan 2026 18:17:29 +0000 https://status.zeabur.com/#cb3b96ad04df208360e5da1aaa4b48471d535ad02bddd51fafe3f87ba947ac94 Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 18:02:41 +0000 https://status.zeabur.com/#cb3b96ad04df208360e5da1aaa4b48471d535ad02bddd51fafe3f87ba947ac94 Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Tue, 13 Jan 2026 17:58:41 +0000 https://status.zeabur.com/#35f7f2443502919814a5bfa525e81593809173d81ae4b9c22b6eb7f2d239de6b California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 17:41:44 +0000 https://status.zeabur.com/#35f7f2443502919814a5bfa525e81593809173d81ae4b9c22b6eb7f2d239de6b California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Tue, 13 Jan 2026 06:40:51 +0000 https://status.zeabur.com/#09519416ca0e8238ab87b177f240d57de6f226c08b69390274804cc2ba9b6652 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 06:40:36 +0000 https://status.zeabur.com/#0bd7b6bfcaac92a6230b67fbeb6ed8690fc3e4dc0e98f9b35e9dfec8a8bd0179 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 06:38:49 +0000 https://status.zeabur.com/#0bd7b6bfcaac92a6230b67fbeb6ed8690fc3e4dc0e98f9b35e9dfec8a8bd0179 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Tue, 13 Jan 2026 06:38:05 +0000 https://status.zeabur.com/#09519416ca0e8238ab87b177f240d57de6f226c08b69390274804cc2ba9b6652 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Tue, 13 Jan 2026 06:05:26 +0000 https://status.zeabur.com/#5ddcb7ab72c70e94bfad5ffa25c68cd8d63130c5bb95c05edd2927e9f9cc7d4a California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Tue, 13 Jan 2026 06:04:49 +0000 https://status.zeabur.com/#5ddcb7ab72c70e94bfad5ffa25c68cd8d63130c5bb95c05edd2927e9f9cc7d4a California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Mon, 12 Jan 2026 16:55:49 +0000 https://status.zeabur.com/#508f0c5c27172542037b4aa242ccb67232cff4c5c261ae1970cb198380c78304 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Mon, 12 Jan 2026 16:53:07 +0000 https://status.zeabur.com/#508f0c5c27172542037b4aa242ccb67232cff4c5c261ae1970cb198380c78304 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Mon, 12 Jan 2026 04:39:50 +0000 https://status.zeabur.com/#5dd09b366fa8f6571821e766c7e61ffd295264d2d436143ff9711d5bad0d0b9b Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Mon, 12 Jan 2026 04:39:30 +0000 https://status.zeabur.com/#ff6640f2efab46ecfb3c2ad180255f31390a03ada89dc486d2b8dca37d8a6ae2 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Mon, 12 Jan 2026 04:36:28 +0000 https://status.zeabur.com/#ff6640f2efab46ecfb3c2ad180255f31390a03ada89dc486d2b8dca37d8a6ae2 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Mon, 12 Jan 2026 04:36:27 +0000 https://status.zeabur.com/#5dd09b366fa8f6571821e766c7e61ffd295264d2d436143ff9711d5bad0d0b9b Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Mon, 12 Jan 2026 03:55:21 +0000 https://status.zeabur.com/#244682e821998f935c0235123ab2b15c3b129c510ca15007aa3900dda3ab2800 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Mon, 12 Jan 2026 03:54:47 +0000 https://status.zeabur.com/#244682e821998f935c0235123ab2b15c3b129c510ca15007aa3900dda3ab2800 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sun, 11 Jan 2026 11:06:47 +0000 https://status.zeabur.com/#5ceeab6115a4a07cdd6bf9a5808ca937c0db7599a33eb0486575222c7411c7c1 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sun, 11 Jan 2026 11:06:32 +0000 https://status.zeabur.com/#61d761d19ba9edc274c59fa3a891819a9451bd8cc43f6706a5730a01f1c5d5c3 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Sun, 11 Jan 2026 11:05:43 +0000 https://status.zeabur.com/#61d761d19ba9edc274c59fa3a891819a9451bd8cc43f6706a5730a01f1c5d5c3 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sun, 11 Jan 2026 11:05:23 +0000 https://status.zeabur.com/#5ceeab6115a4a07cdd6bf9a5808ca937c0db7599a33eb0486575222c7411c7c1 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 11 Jan 2026 10:34:09 +0000 https://status.zeabur.com/#9367a155092221e204ad8d773392f4056c459140328a4de823e72e913d0963a7 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sun, 11 Jan 2026 10:31:55 +0000 https://status.zeabur.com/#9367a155092221e204ad8d773392f4056c459140328a4de823e72e913d0963a7 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Wed, 07 Jan 2026 17:10:46 +0000 https://status.zeabur.com/#52f233254120369bf39276a7db9c6dbf1739e0e83e2e9264a8b39bfc2c33abed Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Wed, 07 Jan 2026 17:10:20 +0000 https://status.zeabur.com/#52f233254120369bf39276a7db9c6dbf1739e0e83e2e9264a8b39bfc2c33abed Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Mon, 05 Jan 2026 09:09:09 +0000 https://status.zeabur.com/#074631ddfc457081e9c9e793ce9e02dd2492503e013d0b05a43a187f8ecea378 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Mon, 05 Jan 2026 09:08:48 +0000 https://status.zeabur.com/#074631ddfc457081e9c9e793ce9e02dd2492503e013d0b05a43a187f8ecea378 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 04 Jan 2026 09:20:50 +0000 https://status.zeabur.com/#12509ead3e1f0e810c6b32384e2abc42454aa2ea0b909df7f5a4d2228c7e74e3 Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Sun, 04 Jan 2026 09:17:38 +0000 https://status.zeabur.com/#12509ead3e1f0e810c6b32384e2abc42454aa2ea0b909df7f5a4d2228c7e74e3 Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Sat, 03 Jan 2026 18:20:41 +0000 https://status.zeabur.com/#3a9802db29cdbafbe92b8b7711bea426d5b2fc528b568c5ff03012327cdd594e Landing Page recovered https://status.zeabur.com/ Sat, 03 Jan 2026 18:19:46 +0000 https://status.zeabur.com/#68a579aa3f61196a42f095c9dc80907d3337999c90122eeeb832ad585b727f6b Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 18:18:25 +0000 https://status.zeabur.com/#3a9802db29cdbafbe92b8b7711bea426d5b2fc528b568c5ff03012327cdd594e Landing Page went down https://status.zeabur.com/ Sat, 03 Jan 2026 18:16:55 +0000 https://status.zeabur.com/#68a579aa3f61196a42f095c9dc80907d3337999c90122eeeb832ad585b727f6b Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sat, 03 Jan 2026 18:05:43 +0000 https://status.zeabur.com/#8e8ed6f26a45059ea0de29fde20a6ef6b43d32e7f9cc95ef5e6b2b24e34946e7 Landing Page recovered https://status.zeabur.com/ Sat, 03 Jan 2026 18:03:10 +0000 https://status.zeabur.com/#8e8ed6f26a45059ea0de29fde20a6ef6b43d32e7f9cc95ef5e6b2b24e34946e7 Landing Page went down https://status.zeabur.com/ Sat, 03 Jan 2026 17:56:56 +0000 https://status.zeabur.com/#94a77bfb77585bf93d604cc3bb326f993541adeb631d39e5b9257898d1fede3f Landing Page recovered https://status.zeabur.com/ Sat, 03 Jan 2026 17:55:46 +0000 https://status.zeabur.com/#35411939dc0dafd74c36efd5c9940e13933514daf496db4406b70f022366dc11 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 17:54:24 +0000 https://status.zeabur.com/#94a77bfb77585bf93d604cc3bb326f993541adeb631d39e5b9257898d1fede3f Landing Page went down https://status.zeabur.com/ Sat, 03 Jan 2026 17:52:57 +0000 https://status.zeabur.com/#35411939dc0dafd74c36efd5c9940e13933514daf496db4406b70f022366dc11 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sat, 03 Jan 2026 15:40:46 +0000 https://status.zeabur.com/#1ea25b2ce3db3a68617947ebcc4962582f8a12e7edbfb82011ec04b074a8c0d9 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 15:38:06 +0000 https://status.zeabur.com/#1ea25b2ce3db3a68617947ebcc4962582f8a12e7edbfb82011ec04b074a8c0d9 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sat, 03 Jan 2026 14:47:48 +0000 https://status.zeabur.com/#041a9afb1a54b99d82505a3922d8cd5abe9f8dd20278aa0bcd7056c922b3a805 Landing Page recovered https://status.zeabur.com/ Sat, 03 Jan 2026 14:46:01 +0000 https://status.zeabur.com/#041a9afb1a54b99d82505a3922d8cd5abe9f8dd20278aa0bcd7056c922b3a805 Landing Page went down https://status.zeabur.com/ Sat, 03 Jan 2026 14:37:46 +0000 https://status.zeabur.com/#e781deb4a6de2f4780ffdfef29f7138c3c9c4bb52a687913cb375c9b6c8a9eb9 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 14:35:05 +0000 https://status.zeabur.com/#e781deb4a6de2f4780ffdfef29f7138c3c9c4bb52a687913cb375c9b6c8a9eb9 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sat, 03 Jan 2026 14:16:47 +0000 https://status.zeabur.com/#a32993fb42fc597b1aafab774003453e08a5f7ac1f6afcdc03c58f0c6cea11dc Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 14:13:55 +0000 https://status.zeabur.com/#a32993fb42fc597b1aafab774003453e08a5f7ac1f6afcdc03c58f0c6cea11dc Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sat, 03 Jan 2026 09:53:41 +0000 https://status.zeabur.com/#feabab54531c8a454bb3eb361115be6054402ebbadfaa8d58c5b0e632a7716ee Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 09:47:44 +0000 https://status.zeabur.com/#feabab54531c8a454bb3eb361115be6054402ebbadfaa8d58c5b0e632a7716ee Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Sat, 03 Jan 2026 08:42:14 +0000 https://status.zeabur.com/#aab27a1ab15a5b28313b6e6639ecdb5567b3e7034bfb3c5834efb893cf855718 Frankfurt, Germany - Amazon Web Service (fra1) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 08:40:23 +0000 https://status.zeabur.com/#ec6e8a5ba1107044535474801ad996f2a15a30e5201af25e7327cb265efa7246 California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 08:39:38 +0000 https://status.zeabur.com/#ec6e8a5ba1107044535474801ad996f2a15a30e5201af25e7327cb265efa7246 California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Sat, 03 Jan 2026 08:39:17 +0000 https://status.zeabur.com/#aab27a1ab15a5b28313b6e6639ecdb5567b3e7034bfb3c5834efb893cf855718 Frankfurt, Germany - Amazon Web Service (fra1) went down https://status.zeabur.com/ Sat, 03 Jan 2026 08:32:36 +0000 https://status.zeabur.com/#09aea52fe490f2758d8a9ab020993feb2db347d0fc20aa6a4ffcbbed59bdd694 Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 08:29:52 +0000 https://status.zeabur.com/#09aea52fe490f2758d8a9ab020993feb2db347d0fc20aa6a4ffcbbed59bdd694 Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Sat, 03 Jan 2026 07:11:44 +0000 https://status.zeabur.com/#dfdec626754a1e40a8ef66b7a0786b8192a015a8923e1dca639f83abb184c2ce Taipei, Taiwan - Google Cloud Platform (tpe0) recovered https://status.zeabur.com/ Sat, 03 Jan 2026 07:09:01 +0000 https://status.zeabur.com/#dfdec626754a1e40a8ef66b7a0786b8192a015a8923e1dca639f83abb184c2ce Taipei, Taiwan - Google Cloud Platform (tpe0) went down https://status.zeabur.com/ Fri, 02 Jan 2026 14:46:42 +0000 https://status.zeabur.com/#32ceeace0a216f5ce89551eae9926665a8f6f20e7a97933c4ff15cdab368b9d8 Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Fri, 02 Jan 2026 14:45:55 +0000 https://status.zeabur.com/#32ceeace0a216f5ce89551eae9926665a8f6f20e7a97933c4ff15cdab368b9d8 Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Thu, 01 Jan 2026 15:25:24 +0000 https://status.zeabur.com/#755d7f5f844e4a3dcd386e104b3bee77ae8981096955dc0b5abecb80561195ce California, United States - Amazon Web Service (sfo1) recovered https://status.zeabur.com/ Thu, 01 Jan 2026 15:19:22 +0000 https://status.zeabur.com/#755d7f5f844e4a3dcd386e104b3bee77ae8981096955dc0b5abecb80561195ce California, United States - Amazon Web Service (sfo1) went down https://status.zeabur.com/ Wed, 31 Dec 2025 11:20:41 +0000 https://status.zeabur.com/#02a25dcbe4f17424cff7832aea1453333d042e36747fe82fe151879d8e828d06 Landing Page recovered https://status.zeabur.com/ Wed, 31 Dec 2025 11:19:44 +0000 https://status.zeabur.com/#553d4890a4d110478dbe503bad345601227520b9b638e121461fe1f2657e91a8 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Wed, 31 Dec 2025 11:12:43 +0000 https://status.zeabur.com/#02a25dcbe4f17424cff7832aea1453333d042e36747fe82fe151879d8e828d06 Landing Page went down https://status.zeabur.com/ Wed, 31 Dec 2025 11:11:03 +0000 https://status.zeabur.com/#553d4890a4d110478dbe503bad345601227520b9b638e121461fe1f2657e91a8 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Mon, 29 Dec 2025 08:58:47 +0000 https://status.zeabur.com/#c9816bffe59d2ee45638c681369d33d3cd6e62dcec5865612407eafcfd2b3133 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Mon, 29 Dec 2025 08:52:41 +0000 https://status.zeabur.com/#c9816bffe59d2ee45638c681369d33d3cd6e62dcec5865612407eafcfd2b3133 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Mon, 29 Dec 2025 08:43:54 +0000 https://status.zeabur.com/#af4d07761efb235ada4682a206fd192366f4826620ff58dbcb0ae099cb0841a7 Dashboard (zeabur.com/projects) recovered https://status.zeabur.com/ Mon, 29 Dec 2025 08:35:10 +0000 https://status.zeabur.com/#af4d07761efb235ada4682a206fd192366f4826620ff58dbcb0ae099cb0841a7 Dashboard (zeabur.com/projects) went down https://status.zeabur.com/ Sun, 28 Dec 2025 16:11:02 +0000 https://status.zeabur.com/#670734accf43da5805966243f90391f7f055185a587fc9aa9544abd64a8bcd9d Shanghai, China - Huawei Cloud (sha1) recovered https://status.zeabur.com/ Sun, 28 Dec 2025 16:08:56 +0000 https://status.zeabur.com/#670734accf43da5805966243f90391f7f055185a587fc9aa9544abd64a8bcd9d Shanghai, China - Huawei Cloud (sha1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 13:33:07 +0000 https://status.zeabur.com/#830acc56ad00455b06364523ca74d4815b53a0be5471e25ffad228abb10f5566 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 13:30:11 +0000 https://status.zeabur.com/#830acc56ad00455b06364523ca74d4815b53a0be5471e25ffad228abb10f5566 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 13:24:05 +0000 https://status.zeabur.com/#431b09debe47186b1f96645e1d182caa5db7601b295a5e6481c142caa33f482a Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 12:47:59 +0000 https://status.zeabur.com/#431b09debe47186b1f96645e1d182caa5db7601b295a5e6481c142caa33f482a Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 12:42:03 +0000 https://status.zeabur.com/#05e3ebcfc717b05734c25b0d505d193d622ed81f427ab0ecd6da56db53fcbbe5 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 12:39:02 +0000 https://status.zeabur.com/#05e3ebcfc717b05734c25b0d505d193d622ed81f427ab0ecd6da56db53fcbbe5 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 12:30:06 +0000 https://status.zeabur.com/#c0e2d1ea77193cf642ac5a63b524a6e79e7a7643d90697486d53e905b610403d Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 12:15:14 +0000 https://status.zeabur.com/#c0e2d1ea77193cf642ac5a63b524a6e79e7a7643d90697486d53e905b610403d Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 12:11:58 +0000 https://status.zeabur.com/#69eced38aaa5c721bb1a72dce68f56a1159cc3dd60d53577c19cde884ba3dfb1 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 11:51:02 +0000 https://status.zeabur.com/#69eced38aaa5c721bb1a72dce68f56a1159cc3dd60d53577c19cde884ba3dfb1 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 11:42:03 +0000 https://status.zeabur.com/#fa86aa042517913cc7a00ef385916952127fe03ceb85688ce5d62dfb52b26d8e Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 11:27:02 +0000 https://status.zeabur.com/#fa86aa042517913cc7a00ef385916952127fe03ceb85688ce5d62dfb52b26d8e Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 11:09:07 +0000 https://status.zeabur.com/#dad9b2c879f7894dc70cc8343fb3351048c749af719fa480d55dfbb84de3976a Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 10:57:06 +0000 https://status.zeabur.com/#dad9b2c879f7894dc70cc8343fb3351048c749af719fa480d55dfbb84de3976a Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 10:42:04 +0000 https://status.zeabur.com/#8c7f27112d43dbcb8bb0783306813cb9aa9e1b9719a4ed6b581d8c92e00be204 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 10:30:05 +0000 https://status.zeabur.com/#8c7f27112d43dbcb8bb0783306813cb9aa9e1b9719a4ed6b581d8c92e00be204 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 10:12:01 +0000 https://status.zeabur.com/#c8a7f6112eb051168d2d7baa441fd0cd7d0ccc744d46ae56fccf76af3c123885 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 10:06:03 +0000 https://status.zeabur.com/#c8a7f6112eb051168d2d7baa441fd0cd7d0ccc744d46ae56fccf76af3c123885 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sat, 27 Dec 2025 09:45:06 +0000 https://status.zeabur.com/#7dccd9a6836900a9cca5a293fdd4c242335eb6ee9a8c99483b670a54612aa632 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sat, 27 Dec 2025 09:39:13 +0000 https://status.zeabur.com/#7dccd9a6836900a9cca5a293fdd4c242335eb6ee9a8c99483b670a54612aa632 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Tue, 23 Dec 2025 14:47:29 +0000 https://status.zeabur.com/#248a4f6e90e7f0f7361ec114e8f0b710baaf30d97814266287375bd04a36645f Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Tue, 23 Dec 2025 14:44:21 +0000 https://status.zeabur.com/#248a4f6e90e7f0f7361ec114e8f0b710baaf30d97814266287375bd04a36645f Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Sun, 21 Dec 2025 08:54:06 +0000 https://status.zeabur.com/#5a9ac5532dd71cf231f13459d37ac959d2e6b7b58f984561c89b9c3ecd517175 Hong Kong - Amazon Web Service (hkg1) recovered https://status.zeabur.com/ Sun, 21 Dec 2025 08:50:49 +0000 https://status.zeabur.com/#5a9ac5532dd71cf231f13459d37ac959d2e6b7b58f984561c89b9c3ecd517175 Hong Kong - Amazon Web Service (hkg1) went down https://status.zeabur.com/ Sat, 20 Dec 2025 18:06:09 +0000 https://status.zeabur.com/#4484a01aafc791ab0cb71c89c839796b2dc86ec34519aaf2c81b81888a50d84d Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Sat, 20 Dec 2025 17:29:26 +0000 https://status.zeabur.com/#4484a01aafc791ab0cb71c89c839796b2dc86ec34519aaf2c81b81888a50d84d Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Fri, 19 Dec 2025 17:24:16 +0000 https://status.zeabur.com/#1d8056ea10b675a7e7ef9d4a71a9c0ce344c360e8378aab1db40ac8e30551171 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Fri, 19 Dec 2025 17:21:24 +0000 https://status.zeabur.com/#1d8056ea10b675a7e7ef9d4a71a9c0ce344c360e8378aab1db40ac8e30551171 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Fri, 19 Dec 2025 17:15:05 +0000 https://status.zeabur.com/#ac45082c0ab9453150f9c88296fd098d3549140c0129c80b67556db74a481a63 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Fri, 19 Dec 2025 17:03:29 +0000 https://status.zeabur.com/#ac45082c0ab9453150f9c88296fd098d3549140c0129c80b67556db74a481a63 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Wed, 17 Dec 2025 10:53:32 +0000 https://status.zeabur.com/#9aa2b12a39a7aa67904411755cbfb71536def872ca379da80d45c4acf077216d Jakarta, Indonesia - Volcengine (cgk1) recovered https://status.zeabur.com/ Wed, 17 Dec 2025 10:50:53 +0000 https://status.zeabur.com/#9aa2b12a39a7aa67904411755cbfb71536def872ca379da80d45c4acf077216d Jakarta, Indonesia - Volcengine (cgk1) went down https://status.zeabur.com/ Tue, 16 Dec 2025 21:39:12 +0000 https://status.zeabur.com/#fac1b37d707f062ddc1aa8916d3ce17f2b70d16a5d08cbd1c785b5a54d5bcfb3 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Tue, 16 Dec 2025 21:33:36 +0000 https://status.zeabur.com/#fac1b37d707f062ddc1aa8916d3ce17f2b70d16a5d08cbd1c785b5a54d5bcfb3 Tokyo, Japan - Amazon Web Service (hnd1) went down https://status.zeabur.com/ Sun, 14 Dec 2025 00:33:08 +0000 https://status.zeabur.com/#f1143ff3c1c06fd02d7c0dc168105741ba5e7e8480785f936a8170871759cee4 Tokyo, Japan - Amazon Web Service (hnd1) recovered https://status.zeabur.com/ Sun, 14 Dec 2025 00:27:29 +0000 https://status.zeabur.com/#f1143ff3c1c06fd02d7c0dc168105741ba5e7e8480785f936a8170871759cee4 Tokyo, Japan - Amazon Web Service (hnd1) went down