Guardrails Service Disruption Impacting Customers
Summary
Our Engineering team has fully implemented and confirmed the effectiveness of the fix for the increased guardrail latency. System performance has returned to normal, and all affected services are operating as expected. We have observed stable metrics during extended monitoring and have not detected any further latency or interruptions. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Impact
minor
Timeline
[identified] As of 20:07 UTC on December 2, 2025, our Engineering team has detected increased guardrail latency which may produce long response times for agents with attached guardrails. Engineering is working on a fix. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.
via statuspage[investigating] Our Engineering team is currently investigating increased guardrail latency, which may cause long response times for agents with attached guardrails. We apologize for the inconvenience and will share an update once we have more information. Thank you for your patience and understanding as we work to resolve this issue.
via statuspage[monitoring] Our Engineering team has implemented a fix that has significantly reduced the impact of the issue, largely mitigating the outage. Although the situation has improved, some users may still experience intermittent latency issues. We are closely monitoring the results and will continue to work towards full resolution. We will provide another update once we have confirmed the issue is fully resolved.
via statuspage[resolved] Our Engineering team has fully implemented and confirmed the effectiveness of the fix for the increased guardrail latency. System performance has returned to normal, and all affected services are operating as expected. We have observed stable metrics during extended monitoring and have not detected any further latency or interruptions. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
via statuspageLessons Learned
⚠DigitalOcean has experienced 46 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network have occurred 48 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Network / Routing. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Ubuntu/Debian Package Mirror Failure
DigitalOcean · Mar 9, 2026
HTTP 522 Error on App Platform
DigitalOcean · Mar 6, 2026
Intermittent connectivity issues in Ashburn, VA
Cloudflare · Mar 6, 2026
Elevated TCP three-way handshake failures on api.anthropic.com
Anthropic · Mar 6, 2026
Disruption with some GitHub services
GitHub · Mar 5, 2026