Incidents reported on status page for Smasher Network https://status.smasher.to/ https://d1lppblt9t2x15.cloudfront.net/logos/1286ad8f34313d2135f64c84e29f899f.svg https://status.smasher.to/ en https://status.smasher.to/incident/477168 Fri, 13 Dec 2024 13:00:12 -0000 https://status.smasher.to/incident/477168#6bd36eafe23c4a847b42c7e75b3d6a7b38fbefba1c2f371048f8752de8c8e4e3 Our proxy performance has been severely degraded, we're working on a fix https://status.smasher.to/incident/430724 Mon, 16 Sep 2024 21:38:00 -0000 https://status.smasher.to/incident/430724#691869e7b86e6021db302694cfca7f38ca5f47a861f3484f5a48ae71da78881d Whole API and network will be inaccessible during maintenance. https://status.smasher.to/incident/383747 Thu, 13 Jun 2024 10:00:00 -0000 https://status.smasher.to/incident/383747#6781c3ca9d5abefd6ab872c436e6d9cf12442d68d53cb24f07ca1039a792732c Reliability issues on IOS tokens is being investigated and resolved. I apologize for the potential longer downtime. https://status.smasher.to/incident/372746 Tue, 21 May 2024 19:55:00 -0000 https://status.smasher.to/incident/372746#c3a6710adfbd9261f5cf0a2c2008d5951b50e48f05ff945e89677a5397085228 Currently investigating elevated number of "no device token" errors. https://status.smasher.to/incident/372083 Mon, 20 May 2024 13:00:00 -0000 https://status.smasher.to/incident/372083#3c60a255e0589b8eb519fd1b4de5d3ace1a8f3af0856651e3c7134ae34ca4782 A new JP patch was released which requires a bot update. https://status.smasher.to/incident/328194 Sat, 17 Feb 2024 19:15:52 -0000 https://status.smasher.to/incident/328194#87e85e5852cf69831f264a0e6dcd8504b39bff99cf9364f4b9479eede28bca68 Maintenance completed https://status.smasher.to/incident/328194 Sat, 17 Feb 2024 15:30:00 -0000 https://status.smasher.to/incident/328194#de37a5023f272f3f0350a19536764043bc86638c94c7f48e44dc4231625ff5bd Updating the network protocol to utilize a much more precise approach to minimize routing. https://status.smasher.to/incident/236135 Sat, 22 Jul 2023 20:00:00 -0000 https://status.smasher.to/incident/236135#974b54f58bb60bf419a10b497bd8a1256680a5d38c834fd750ab86daf7cb4c24 This downtime will bring much needed system upgrades to the internal handlers and subsequently improve performance and reliability. This update will take longer as we're going to do a health inspection on all of the interlinked systems. https://status.smasher.to/incident/204218 Sat, 06 May 2023 16:05:00 -0000 https://status.smasher.to/incident/204218#86f850452ae959dc5382362b2a6734a1ae5a85e94b039da12058f7c5a35a978d https://youtu.be/OgZzUJud3Q4 https://status.smasher.to/incident/195000 Tue, 11 Apr 2023 06:00:00 -0000 https://status.smasher.to/incident/195000#bb31ba39d35a491a58e2dbbe27da47049913286c08f3b32ab11740bc5b95b009 Updating our services, to comply with the latest patch released by Google. https://status.smasher.to/incident/181356 Sat, 04 Mar 2023 11:00:00 -0000 https://status.smasher.to/incident/181356#e2ec4a7e940d01362d20c8be3f081015216420e1b24db123261ff8e550a4b096 We are writing to inform you that our system will be undergoing scheduled maintenance at 12:00 (UTC+1) to 12:15 PM (UTC+1). During this period, our Android JP system will be temporarily offline to adopt new firmware to strengthen the reliability of our service. https://status.smasher.to/incident/176649 Sat, 18 Feb 2023 18:09:00 -0000 https://status.smasher.to/incident/176649#c9c6939af0e172dec219ae6b7ce1e6c9b6f28fce0694b7052fb2b072966259a2 We've collected a lot of error critical data the past week to finally put a nail in the multiple origins of the frequent errors. The service is going offline as of now until a stable solution that can handle the load without causing network wide errors is achieved.