Some latency reported by users around 15:30 BST on @GerritCodeReview with a few 504s. The situation is back to normal and latency is back to normal thanks to the automatic healing we have in place. We are investigating the cause of the latency increase.
If your session has expired on #GerritCodeReview on https://t.co/BHzl36ATtN, you will have troubles logging back in, due to @github outage still in progress.
@GerritReview https://t.co/uPaeOLnwri production fix has been completed *IF* you failed to create a change this morning just reset to the remote branch amend the commit and push again for review
The root cause of the issue has been identified, software bug in Gerrit v2.15 during the migration process. Production is getting fixed shortly and changes will be available again very soon. Apologies for the disruption this morning.
"Starting online NoteDb migration" on https://t.co/Ab9cB7YjiY and thanks to @daveborowitz there will be no downtime, you can use @GerritReview as usual without limitations or delays
A significant % of new changes a getting rejected on https://t.co/uPaeOLnwri most likely as consequence of the #NoteDb migration. We are investigating the issue please bear with us