Incidents | Blox-Grow Incidents reported on status page for Blox-Grow https://status.bloxgrow.best/ https://d1lppblt9t2x15.cloudfront.net/logos/8a03a378e5cf782afe40996fa87cc88a.png Incidents | Blox-Grow https://status.bloxgrow.best/ en Withdrawal page down https://status.bloxgrow.best/incident/523440 Fri, 07 Mar 2025 03:21:00 -0000 https://status.bloxgrow.best/incident/523440#783bddc350fcb49f74a1852581bc4ca0cd01762bee7aa430aaf7bc178529c577 We have identified the root cause of the issue. All users should be able to access the withdrawal page now. Thanks for your patience! Withdrawal page down https://status.bloxgrow.best/incident/523440 Thu, 06 Mar 2025 02:31:00 -0000 https://status.bloxgrow.best/incident/523440#e70334fd023e7020448ee998704ab790369d8b3d9560e6f3be7cad5fe387d7b3 The withdrawal page is down for all users, the withdrawal system is not affected by this incident. We are not aware when this error started occurring. We are currently working on a solution, thank you for your patience. Dashboard unavailable https://status.bloxgrow.best/incident/500293 Thu, 23 Jan 2025 17:49:00 -0000 https://status.bloxgrow.best/incident/500293#65632c3508838d4e180eefa8c2b13b28ab4d7ef2391003f4af6fd0d4c2fef905 We have identified the root cause of all issues, the earn page should be stable and all features are operational. Thank you for your patience! Dashboard unavailable https://status.bloxgrow.best/incident/500293 Thu, 23 Jan 2025 05:20:00 -0000 https://status.bloxgrow.best/incident/500293#379d2a0914a3f2efffb6d507239edf6410e4756e18c2c459fc94391c7af8459c We’ve successfully identified and resolved the root cause of the issue, and users can now log in to their accounts without any problems. However, the Earn page is still not functioning as expected. Dashboard unavailable https://status.bloxgrow.best/incident/500293 Wed, 22 Jan 2025 23:29:00 -0000 https://status.bloxgrow.best/incident/500293#ab20673ccd43747ac17cceba7216d28d03ffc3c334d45cb4ac57b3b0721d6cf8 Dashboard is currently unavailable to all users. Please stay on hold while we resolve this issue.