Resolved: We are pleased to confirm that the issue has been successfully resolved, and all system functionalities have been restored to normal operation. https://t.co/wbN2vitolR
Investigating: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. https://t.co/dTejBwz6nV
Monitoring: We've restored the system, workspace starts and the dashboard experience are normal again.
We had to rollback a change that was putting excessive load on the system, it was causing API request duration to be too high. https://t.co/mv6tv4mHPl
Resolved: We are pleased to confirm that the issue has been successfully resolved, and all system functionalities have been restored to normal operation. https://t.co/bg35dHcj2H
Monitoring: We have identified and resolved the error. Workspace creation is now resuming as expected. We will continue to actively monitor the situation. https://t.co/fkpzyrYPKM
Resolved: A fix has been published (reference: https://t.co/j4CazLh9Aa). Please start a new workspace, if you you are still having trouble please rebuild your workspace image. https://t.co/Wh0UfcI3Ql
Identified: You may be experiencing trouble using Docker in Gitpod (feature reference: https://t.co/EakL2zuYjZ).
The issue was reported (https://t.co/YmZDABFeo1), we are producing a fix (https://t.co/uO37L4wXEZ), and there are a coup… https://t.co/aoEi5Izdhl
Resolved: Today, between 9:20 and 10:30 UTC, we saw elevated levels of "Content initialization failed" errors during the start of workspaces. The errors were caused by a malfunctioning VM. The VM has been removed and operations run sm… https://t.co/kAvbtr1Jdy
Monitoring: We continue monitoring the fix. In the meantime, if the sign-in issue persists, we recommend clearing Gitpod-related browser cookies as a workaround. https://t.co/oCZrzHSSmb
Resolved: We've found a possible image builder bug and logged relevant data. We'll continue this investigation offline. Meanwhile, all systems are operational. https://t.co/Hma1nT3KZy
Investigating: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. https://t.co/brWdLdvK3c
Resolved: The error spike was just a spike, and the service quickly recovered after the brief DB maintenance. Monitoring did not reveal any other issues. https://t.co/JxGBDlLw60
Monitoring: Gitpod's dashboard was briefly affected by an unplanned GCP database maintenance. Possible outage of user dashboard logins, starting/stopping workspaces, etc. The DB maintenance is now over, and error rates are recovering.… https://t.co/IOMR6O0W5s
Identified: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. https://t.co/CuPe1hqd8x
Investigating: We've spotted that something has gone wrong with our ports mechanism. We're currently investigating the issue, and will provide an update soon.
Ports visibility can't be set to public from the IDE-UI (e.g. vscode) or `… https://t.co/foKq5zk5VT