• If this is your first visit You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Sign up today to get the latest PS4 GameSaves, Game Mods and much more!
  • If you've previously logged in via Google or Discord and are now unable to do so you'll need to request a password reset which will be emailed to you via the link here: Lost password
  • If you've previously used Two-step verification you'll need to re-enable it via the link here: Password and security

Outage Report: April 2nd, 2021

Status
Not open for further replies.

JB

Remember, no Russian.
FOUNDER
November 29, 2018
265
287
UK
24
Welcome back all!

I think DNS should now be fully re-propagated so it seems like an ideal time to talk about what happened yesterday, and how we're going to avoid any similar issues going forwards.

Yesterday, a glitch at our domain registrar resulted in the nameservers for playersquared.com being reset to an incorrect value, which lead to the site going offline. As DNS caches around the world, we were unable to immediately understand the issue, and initially put it down to a global DNS outage that affected numerous sites including a bunch of Microsoft services. By the time DNS had fully updated to reflect the new nameservers, it was late UK time. We got the issue resolved a very short amount of time later.

So what have we done to prevent this happening again in the future? We've finished transferring the domain to another registrar where myself, Vince and Tustin all have access in the extremely unlikely instance that something like this happens again. This means that regardless of who's online/offline, someone should be available to resolve such an issue quickly going forwards.

During the outage, I also took the time to run some upgrades across the site and server and perform some general maintenance.

Apologies from all of us for the inconvenience caused yesterday, rest assured it will not happen again!
 
Status
Not open for further replies.