GitHub first acknowledged the issue at 23:39 UTC on March 12. Around two hours later, it Xeeted news that it had found a mitigation and was 'currently monitoring systems for recovery.'
The issue was caused by a deployment of network related configuration that was inadvertently applied to the incorrect environment," states GitHub's error report.
[
add
]
[
|
|
...
]