Gitlab.com is down(about.gitlab.com) |
Gitlab.com is down(about.gitlab.com) |
Where else do people go for confirmation of problems?
UPDATE: status.gitlab.com is now acknowledging the incident, so that was fairly quick. My question still stands, but I guess it's less urgent now
> Where else do people go for confirmation of problems?
You are using it already :) https://status.gitlab.com/ or if you prefer tweets, the updates are also posted to https://twitter.com/gitlabstatus
A more general approach I use - search on Twitter for the project name. If many users say that something does not work, it usually is not a "me" problem. Another strategy is to use websites which do connectivity tests from different locations (example: https://tools.keycdn.com/ping). You can use SSL scanning sites for that matter too.
Any reason why "Google Compute Engine" is highlighted in red on that page? Other entries seems fine that are also using it, but not the one where the service is currently broken. Makes it seem like the problem is Google Compute Engine is at fault, when that's obviously not true.
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... is the query I use normally, replace `query=gitlab` with the service you're wondering about.
Maybe the best status page we could have would be a status page that just queries the HN Algolia API for "$SERVICE + DOWN" and checks if there is any hits in the last hour.
We believe we have mitigated the incident, but continue the work to monitor and make additional corrective measures: https://twitter.com/gitlabstatus/status/1462838897499508737
The current selection for the affected component automatically selects the `locations` entry. The `website` component selects the Google Compute Engine in this case.
Agreed that this can be confusing, we'll have to check whether the status page interface allows for more fine granular selections.