Incidents reported on status page for cloro https://status.cloro.dev/ https://d1lppblt9t2x15.cloudfront.net/logos/57f72cce7337aff41123126cd6cd1903.png https://status.cloro.dev/ en https://status.cloro.dev/incident/846740 Fri, 13 Mar 2026 10:46:00 -0000 https://status.cloro.dev/incident/846740#e9ad5a74df9ee1ed8057a3d2dd3238e808eaf855fd96ba4a0ccc82a51e1c9b23 Grok seems to be back on track. https://status.cloro.dev/incident/846740 Fri, 13 Mar 2026 09:34:00 -0000 https://status.cloro.dev/incident/846740#1a9054a010afe792b291790326158a4f6a83ee7523f78dcbf5dca6adf0bd871e We're seeing some requests go through, but still heavily degraded. https://status.cloro.dev/incident/846740 Tue, 10 Mar 2026 18:11:00 -0000 https://status.cloro.dev/incident/846740#0833658216684791ae7273d125f2be6abfd993e3457e3f52d4694285da366ea8 Even though our scraping service is working, Grok is limiting access to its users. https://status.cloro.dev/incident/841532 Fri, 06 Mar 2026 04:31:00 -0000 https://status.cloro.dev/incident/841532#b9348db3b4eacc1cf7e1fe20aaed85ed1fdaf452f8531a898854e5ebc066df2c Gemini’s performance is back to regular levels. https://status.cloro.dev/incident/840844 Thu, 05 Mar 2026 19:47:00 -0000 https://status.cloro.dev/incident/840844#f2727b53fbe1eabdbb846748121256d3ad870cd20e352c100b7c5d2b33dd0a03 ChatGPT's performance is finally back to regular levels. https://status.cloro.dev/incident/841532 Thu, 05 Mar 2026 15:43:00 -0000 https://status.cloro.dev/incident/841532#e45dd9e24a3d61290b543264971684f5e5e7d2df204f7a066d3447be1cc8b976 We're seeing Gemini degrading in MX, BR, FR, IN and AU. https://status.cloro.dev/incident/840844 Thu, 05 Mar 2026 09:49:00 -0000 https://status.cloro.dev/incident/840844#8b5a4846e0fa4d1db6598e97f6c93b10dec5e10cda2ad2eef2e4e51d9fb161d1 Success rate is back to regular levels for most countries, except DE, FR and CA which remain degraded. https://status.cloro.dev/incident/840844 Thu, 05 Mar 2026 04:32:00 -0000 https://status.cloro.dev/incident/840844#8e52feb15827f273b008a914b400851d9b26fdc9ee1193ac36a631ec95ced09d Degradation is now spread across more countries. We're working on fixing it. https://status.cloro.dev/incident/840844 Wed, 04 Mar 2026 13:23:00 -0000 https://status.cloro.dev/incident/840844#1c27d35fb19a8a20fc479b7cb8e206cc3f49e2cdd1632b52e3e667e4225320f5 We are seeing degradation in a subset of countries: CA, DE, FR. The rest of the countries seem performant. https://status.cloro.dev/incident/839826 Wed, 04 Mar 2026 11:04:00 -0000 https://status.cloro.dev/incident/839826#8577441d6c194a553c5e8f0c08469618e1e6870b9ecd868a5a9e3eabb0d80380 ChatGPT is back to normal status. https://status.cloro.dev/incident/839826 Wed, 04 Mar 2026 04:16:00 -0000 https://status.cloro.dev/incident/839826#94c8c6d57b49d74c595ac4d75d1e6c4703e21581e5035bf507e365701874e546 ChatGPT's success rate has gone down from 99% to 92%, we are working on it. Make sure you retry 500 error responses. https://status.cloro.dev/incident/834944 Fri, 27 Feb 2026 08:12:00 -0000 https://status.cloro.dev/incident/834944#406c2d6985cdf6178c4a66cf750f66d3d47e4d6caa5c8197f5ceee4184b4d735 The database that services the dashboard logs has been recovered (even though the logs are lost). https://status.cloro.dev/incident/834944 Fri, 27 Feb 2026 00:11:00 -0000 https://status.cloro.dev/incident/834944#2ff04e834831e6eb989ee8a2e2477e56d6defbde5021aee1da58d074f4fece72 The database which services the dashboard logs crashed in the past 8 hours. You won't see the logs in your dashboards, however the billing and credits are counted correctly. https://status.cloro.dev/incident/832678 Wed, 25 Feb 2026 05:40:00 -0000 https://status.cloro.dev/incident/832678#def7dc74511b69dd673df192d96de110094e9d1e8b40b4d21ac1b06b33739229 Copilot is back up. https://status.cloro.dev/incident/832678 Wed, 25 Feb 2026 04:31:00 -0000 https://status.cloro.dev/incident/832678#2c698fa593f9d056f8870684192301bdbcc20a6dd984a882eaeb0d046a494205 Our service is fully functional, but the underlying Copilot service appears not to be working in some countries. https://status.cloro.dev/incident/828704 Thu, 19 Feb 2026 23:00:00 -0000 https://status.cloro.dev/incident/828704#06ea21e2da9ceff27dc9377dd4419845b29baec8dd0bb5a6c287204278646361 Maintenance completed https://status.cloro.dev/incident/828704 Thu, 19 Feb 2026 18:00:00 -0000 https://status.cloro.dev/incident/828704#ba6f230d7fd5bbe50174b852e46aab7cbe725e2a973b054fd8b899235556db6f We will be upgrading our log database, so you might see disruption in the dashboard logs. https://status.cloro.dev/incident/826308 Mon, 16 Feb 2026 06:31:00 -0000 https://status.cloro.dev/incident/826308#856c4729af47ee62517168b709757ddc23e05aa6bf1b61b9cf96b855def5c3c7 Both are back up. https://status.cloro.dev/incident/826308 Mon, 16 Feb 2026 02:14:00 -0000 https://status.cloro.dev/incident/826308#9de4c4a60df2ba2633b8952590a7270996d8d7e03e8f21fc44c8a8e5d765b493 We’re investigating https://status.cloro.dev/incident/825526 Sat, 14 Feb 2026 22:36:00 -0000 https://status.cloro.dev/incident/825526#88fbd5a08ed1259a17a7567e6a07cd9b98a3f9f8a2767a4db42e7546424a3252 Performance back to normal. https://status.cloro.dev/incident/825526 Sat, 14 Feb 2026 21:28:00 -0000 https://status.cloro.dev/incident/825526#eb12bcc702063dea2452c2b830ea01cd8a6d56473d39b8296a667e7a161e3267 Success rate has gone up, but latency is still high. https://status.cloro.dev/incident/825526 Sat, 14 Feb 2026 18:34:00 -0000 https://status.cloro.dev/incident/825526#9de09a123a477e18c2378812ec703e51990b0bd1082d8e453b4db28aa4773490 We are working on fixing it. https://status.cloro.dev/incident/824712 Fri, 13 Feb 2026 09:59:00 -0000 https://status.cloro.dev/incident/824712#e7cee135d923779497e2e33fdcb43f4d6c15c3fd9b4469dccf3b4fae0927b011 Everything back up. https://status.cloro.dev/incident/824712 Fri, 13 Feb 2026 09:52:00 -0000 https://status.cloro.dev/incident/824712#31ec35b837a7e9c35c8b089af0e2221b1980da95efd32ee33174ebb6131fa161 We're working on understanding what happened. https://status.cloro.dev/incident/823257 Wed, 11 Feb 2026 12:08:00 -0000 https://status.cloro.dev/incident/823257#1a3fe671b9166c8092a73f6c8ce9b21dad116ed88cb5defb44f5fda1e9ab48f5 It's back on. https://status.cloro.dev/incident/823257 Wed, 11 Feb 2026 12:03:00 -0000 https://status.cloro.dev/incident/823257#2ebfddce8fdf7846647556a83168240618f728463a1ace11d145dbab3e20611c We are working on fixing this. https://status.cloro.dev/incident/820490 Mon, 09 Feb 2026 12:51:00 -0000 https://status.cloro.dev/incident/820490#8795bc78b2e53a66e50664978e42410804c55fc536b452ea03e3795889a1a68c The ChatGPT endpoint is back at its regular performance. https://status.cloro.dev/incident/820490 Sat, 07 Feb 2026 13:31:00 -0000 https://status.cloro.dev/incident/820490#72c487a0c8f12bc3b112d706f7e3157f60ac9471cdbf632cef90fde3ccd41017 The success rate is back to normal levels, even though the latency is still higher than usual. https://status.cloro.dev/incident/820490 Sat, 07 Feb 2026 07:52:00 -0000 https://status.cloro.dev/incident/820490#f591c5bdffb39a2893d4c3228239f9c9d47a198620b75cd07011417e1d1fd186 We're seeing lower success rate (~85% vs. 99% as usual). We're actively working on improving it. https://status.cloro.dev/incident/816148 Tue, 03 Feb 2026 09:20:00 -0000 https://status.cloro.dev/incident/816148#ec381d173592d0bf2f45d2cfeeb48e94730faa21094827389fa6c91ab938b318 We have fixed the degradation in ChatGPT, you can now use it to the full extent. Thank you for your patience! https://status.cloro.dev/incident/816148 Tue, 03 Feb 2026 06:25:00 -0000 https://status.cloro.dev/incident/816148#ef4bfc4ee9307c3067cd2c0c5af07dfbf9754a13797a599de665948a43d17eb5 We continue working on the degradation. We’re seeing better success rates, but far from ideal. We will continue to keep you posted. https://status.cloro.dev/incident/816150 Sat, 31 Jan 2026 16:00:00 -0000 https://status.cloro.dev/incident/816150#bdd8e7979eba4a83f69370a6db7c543057ca3ad1163880fa345347522d238118 The dashboard logs are now being populated. https://status.cloro.dev/incident/816148 Sat, 31 Jan 2026 13:45:00 -0000 https://status.cloro.dev/incident/816148#7e8ee8a43582a2f3d48a95029206d84bf58d00e3ef1bc0ac59eadafb7ba32f98 We're working on fixing the errors, until then retry your 5xx error responses. https://status.cloro.dev/incident/816150 Sat, 31 Jan 2026 04:00:00 -0000 https://status.cloro.dev/incident/816150#d7d05bfdbd85fe967d5dcb0360f3def5075cbaa42d177afb1a08e5726746369c Our database instance had issues writing during 12h, so you won't see these records in your dashboard's logs. https://status.cloro.dev/incident/814582 Thu, 29 Jan 2026 17:58:00 -0000 https://status.cloro.dev/incident/814582#3d6ec82e4abfe21d5cf7dd49bb57d1db040e0d42312d53c62fce54ae5c6127bc The downtime is now over, back to processing your requests! https://status.cloro.dev/incident/814582 Thu, 29 Jan 2026 17:43:00 -0000 https://status.cloro.dev/incident/814582#0ade7214a0d2f9b3832a4cf59ab1b7b5e6dcaf4f312cf7c7cbf9fdb21fd8a7ee When upgrading our queue engine there was a 10-minute downtime. https://status.cloro.dev/incident/812915 Tue, 27 Jan 2026 22:24:00 -0000 https://status.cloro.dev/incident/812915#97f9f5181ef81b3bb435a2993bd285b79fc66e27376b69e6385f41e159bf702c The Grok interface seems to be back. https://status.cloro.dev/incident/812915 Tue, 27 Jan 2026 16:58:00 -0000 https://status.cloro.dev/incident/812915#0ed1a5bd121f69b19086533b96569aba34585b03160ac935c9efa2e51c69bdc0 Grok is experiencing server-related issues on their website, claiming to be working on restoring service as quickly as possible. https://status.cloro.dev/ Fri, 16 Jan 2026 09:45:08 +0000 https://status.cloro.dev/#51bbbe18a24d2e605137938998ecfeb5903489f25d9c27c5776156b6f4bf9e21 Backend recovered https://status.cloro.dev/ Fri, 16 Jan 2026 09:40:00 +0000 https://status.cloro.dev/#51bbbe18a24d2e605137938998ecfeb5903489f25d9c27c5776156b6f4bf9e21 Backend went down