Archived:February 2023 lag incident: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
RandomUser34 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
The '''February 2023 lag incident''' began when [[Attempt2]] suddenly began to experience extreme TPS lag, to the point of rendering the server entirely unplayable. As no solutions, up to and including wiping the entire server | The '''February 2023 lag incident''' began when [[Attempt2]] suddenly began to experience extreme TPS lag, to the point of rendering the server entirely unplayable. As no solutions, up to and including wiping the entire server failed to resolve the issue, it was believed by the server administration that it was caused by a fault on the host's end. This was later confirmed on February 7th, 2023, when the server host's technical support team confirmed that the server was running on a node that was experiencing high resource usage, and moved the server to a different node, upon which the issue was immediately resolved. | ||
Revision as of 02:32, 8 February 2023
The February 2023 lag incident began when Attempt2 suddenly began to experience extreme TPS lag, to the point of rendering the server entirely unplayable. As no solutions, up to and including wiping the entire server failed to resolve the issue, it was believed by the server administration that it was caused by a fault on the host's end. This was later confirmed on February 7th, 2023, when the server host's technical support team confirmed that the server was running on a node that was experiencing high resource usage, and moved the server to a different node, upon which the issue was immediately resolved.