Incidents reported on status page for Shadey https://status.shadey.dev/ en https://status.shadey.dev/ Sat, 16 May 2026 17:05:53 +0000 https://status.shadey.dev/#3e5a88343bed6543c4ca106695c4dad03d27db3f99202bdc78bcb1e87592d0f2 API (api.shadey.dev) recovered https://status.shadey.dev/ Sat, 16 May 2026 16:56:36 +0000 https://status.shadey.dev/#3e5a88343bed6543c4ca106695c4dad03d27db3f99202bdc78bcb1e87592d0f2 API (api.shadey.dev) went down https://status.shadey.dev/ Tue, 05 May 2026 10:30:08 +0000 https://status.shadey.dev/#2113c8e8fa6e2e8bdef8fb21f1e52204a9998a317576426c1d9fbf38e8910d5e API (api.shadey.dev) recovered https://status.shadey.dev/ Tue, 05 May 2026 10:26:57 +0000 https://status.shadey.dev/#2113c8e8fa6e2e8bdef8fb21f1e52204a9998a317576426c1d9fbf38e8910d5e API (api.shadey.dev) went down https://status.shadey.dev/ Wed, 29 Apr 2026 03:35:39 +0000 https://status.shadey.dev/#6b6cfc79e7d60583b13d0c39dff4e785c22352e920826aea872d923892d259b4 API (api.shadey.dev) recovered https://status.shadey.dev/ Wed, 29 Apr 2026 03:32:30 +0000 https://status.shadey.dev/#6b6cfc79e7d60583b13d0c39dff4e785c22352e920826aea872d923892d259b4 API (api.shadey.dev) went down https://status.shadey.dev/ Mon, 27 Apr 2026 04:11:37 +0000 https://status.shadey.dev/#bf958415d13967197e4232479b6c9eb19f4465b4b77ed28aeb4ee28cc15e1fa2 API (api.shadey.dev) recovered https://status.shadey.dev/ Mon, 27 Apr 2026 04:08:33 +0000 https://status.shadey.dev/#bf958415d13967197e4232479b6c9eb19f4465b4b77ed28aeb4ee28cc15e1fa2 API (api.shadey.dev) went down https://status.shadey.dev/ Mon, 27 Apr 2026 01:05:43 +0000 https://status.shadey.dev/#dceabc959ce1fd287b9b62634cbfb1d36754cef17e91e1e2f2b9b254e873ca7d API (api.shadey.dev) recovered https://status.shadey.dev/ Mon, 27 Apr 2026 01:02:40 +0000 https://status.shadey.dev/#dceabc959ce1fd287b9b62634cbfb1d36754cef17e91e1e2f2b9b254e873ca7d API (api.shadey.dev) went down https://status.shadey.dev/ Fri, 27 Mar 2026 02:14:50 +0000 https://status.shadey.dev/#d0bbc86ea8395d00a4f0ec212ecc6514db70c6e13e3ec33b6ba2c224f088b63c API (api.shadey.dev) recovered https://status.shadey.dev/ Fri, 27 Mar 2026 02:00:04 +0000 https://status.shadey.dev/#d0bbc86ea8395d00a4f0ec212ecc6514db70c6e13e3ec33b6ba2c224f088b63c API (api.shadey.dev) went down https://status.shadey.dev/ Fri, 27 Mar 2026 01:32:32 +0000 https://status.shadey.dev/#3970b984c02a1e333028b701d5f86752a301107c83161379a257c1d24eeec46d API (api.shadey.dev) recovered https://status.shadey.dev/ Fri, 27 Mar 2026 01:20:59 +0000 https://status.shadey.dev/#3970b984c02a1e333028b701d5f86752a301107c83161379a257c1d24eeec46d API (api.shadey.dev) went down https://status.shadey.dev/ Fri, 27 Mar 2026 01:17:40 +0000 https://status.shadey.dev/#6486d9acb28e0705a2f760c1b6120a9d2ecd4cf29b9b582dbfda20dd1c48b52d API (api.shadey.dev) recovered https://status.shadey.dev/ Thu, 26 Mar 2026 23:54:06 +0000 https://status.shadey.dev/#6486d9acb28e0705a2f760c1b6120a9d2ecd4cf29b9b582dbfda20dd1c48b52d API (api.shadey.dev) went down https://status.shadey.dev/ Thu, 26 Mar 2026 23:50:44 +0000 https://status.shadey.dev/#aa99e9011e30ea31bb504b06b76e309a4c1535f2fee809e08e744ec9062bbad4 API (api.shadey.dev) recovered https://status.shadey.dev/ Thu, 26 Mar 2026 11:36:03 +0000 https://status.shadey.dev/#aa99e9011e30ea31bb504b06b76e309a4c1535f2fee809e08e744ec9062bbad4 API (api.shadey.dev) went down