Opened on Wednesday 3rd March 2021, last updated
Resolved — This is apparently a know bug in mongoDB 4.4, we'll now work with them to help fix the issue in https://jira.mongodb.org/browse/SERVER-53566. Sorry for the trouble 🙇
Monitoring — The problem has been identified, it's a database crash (mongoDB) in chain on 2 out of the 3 database servers, so we ended up with a read-only database. This was apparently triggered by the network maintenance, even though it was only impacting one of them. The situation has been fixed and monitoring is resuming. We'll try to find more informations about this crash and help the mongoDB team fix it.
Investigating — Since 4am UTC this morning the monitoring service is down. This is following a planned maintenance from our hosting provider, we're currently investigating to restore the service and find what went wrong. The website, status pages and API are still accessible in degraded (read-only) mode.