The main domain has now been set back to patched.to
Access to patched.sh will be automatically redirected to patched.to
Access to patched.sh will be automatically redirected to patched.to
❤88💩22🖕17👍16👎6🤣6🏆5😘3💯2💔2🔥1
We are currently experiencing an issue on the datacenter side. The situation is being addressed, and we expect everything to be back to normal shortly. We appreciate your understanding and patience.
❤117💩50🖕24👎21😱11👍9💔7❤🔥6🤣6😘5👏4
We are currently experiencing a power outage at the data center hosting our services, which is causing service interruptions. The data center provider's team is working to restore services as quickly as possible.
We appreciate your understanding and patience during this time.
We appreciate your understanding and patience during this time.
🤬175❤146😢122🖕98💩59🕊51😭43👍9🐳8🌭7🍾7
Service Outage - One-Month Update
Today marks one month since the outage began, and we would like to explain what happened and where things stand.
On September 23, a Russian drone strike on telecommunications facilities in Ukraine damaged the data center hosting our servers. We later learned that the data center holding our backups had also been damaged. Our servers and backups were with two separate hosting providers, but the attack did not affect just one provider; several hosting companies in the region were impacted.
We kept backups in three places: two separate physical devices and one cloud storage service. According to our providers, the drives are in good condition and are waiting in the queue to be copied. Thousands of drives are being recovered, which is why the process has taken so long.
The forum scripts and files in our cloud backup are intact. However, the database backup could not connect to the database because its username had changed. About 11 months ago, at the start of the year, we moved to the p.to domain and changed the database username while moving the files. Because of this, the cloud backup has not saved the database since then, and the latest database backup there is about a year old. This was a serious mistake on our part: we failed to update the backup settings after the migration. We have learned an important lesson from this, and we will be far more careful with our backups going forward.
The full length of the outage will be added to all time-based services, including advertising periods, pinned threads, custom CSS and VIP memberships.
We apologize for the disruption and thank you for your patience. We will share further updates as the recovery progresses.
Today marks one month since the outage began, and we would like to explain what happened and where things stand.
On September 23, a Russian drone strike on telecommunications facilities in Ukraine damaged the data center hosting our servers. We later learned that the data center holding our backups had also been damaged. Our servers and backups were with two separate hosting providers, but the attack did not affect just one provider; several hosting companies in the region were impacted.
We kept backups in three places: two separate physical devices and one cloud storage service. According to our providers, the drives are in good condition and are waiting in the queue to be copied. Thousands of drives are being recovered, which is why the process has taken so long.
The forum scripts and files in our cloud backup are intact. However, the database backup could not connect to the database because its username had changed. About 11 months ago, at the start of the year, we moved to the p.to domain and changed the database username while moving the files. Because of this, the cloud backup has not saved the database since then, and the latest database backup there is about a year old. This was a serious mistake on our part: we failed to update the backup settings after the migration. We have learned an important lesson from this, and we will be far more careful with our backups going forward.
The full length of the outage will be added to all time-based services, including advertising periods, pinned threads, custom CSS and VIP memberships.
We apologize for the disruption and thank you for your patience. We will share further updates as the recovery progresses.
❤57😢33👍12🫡9🔥3🍾3💊3⚡2👏2💯2🎃1