Resolved -
We identified an issue with a synthetic check that temporarily reported an incorrect system status. The underlying services remained operational throughout. The check has since been corrected, and we’re monitoring to ensure continued accuracy.
May 14, 19:24 UTC