Postmortem: Content Violation Feature Temporarily Disabled
Date: March 26, 2026
Duration: ~24 hours (approx. 12:49 CET March 25 – resolved March 26)
Impact: Minor — Content Violation screening was temporarily disabled for affected clients. Users could post content without automated policy screening during this period.
Summary
Our Content Violation feature relies on Microsoft Azure's AI Content Safety service for automated content screening. On March 25, Azure experienced instability in this service, causing screening requests to fail intermittently.
Root Cause
Microsoft Azure's AI Content Safety service experienced an outage. Azure was initially slow to report the incident, which delayed our identification of the root cause.
Our Response
Once the issue was identified as Azure-side, we disabled Content Violation screening for affected clients to ensure users were not blocked from posting content. We monitored the situation and began re-enabling the feature once Azure confirmed the service was restored.
Going Forward
We are updating the Content Violation feature to automatically detect when the Azure Content Safety service is unavailable and gracefully handle the situation — reducing response time and minimizing the need for manual intervention in similar scenarios.