Updated
Jun 25, 2026 at 2:32pm UTC
Incident has been triggered by a faulty monitor configuration. Unfortunately, proper incident authority hasn’t been setup yet and the incident cannot be resolved manually. This can be safely ignored, and will be resolved soon.