As part of our “Respect the Community” value, we will continue to be transparent in our post-mortem. In addition, we will implement a policy to make our creator community economically whole as a result of this outage. We will publish a post-mortem with more details once we’ve completed our analysis, along with the actions we’ll be taking to avoid such issues in the future. We were able to fully restore service as of this afternoon.
Upon successfully identifying this root cause, we were able to resolve the issue through performance tuning, re-configuration, and scaling back of some load. The result was that most services at Roblox were unable to effectively communicate and deploy.ĭue to the difficulty in diagnosing the actual bug, recovery took longer than any of us would have liked. Rather the failure was caused by the growth in the number of servers in our datacenters. This was not due to any peak in external traffic or any particular experience. A core system in our infrastructure became overwhelmed, prompted by a subtle bug in our backend service communications while under heavy load. This was an especially difficult outage in that it involved a combination of several factors. Teams began working around the clock to identify the source of the problem and get things back to normal. This immediately became our highest priority. On Thursday afternoon, October 28th, users began having trouble connecting with our platform. A key value at Roblox is “Respect the Community,” and in this case, we apologize for the inconvenience to our community.
We are sorry for the length of time it took us to restore service.
As most of the Roblox community is aware, we recently experienced an extended outage across our platform.
0 kommentar(er)
