Incidents and maintenance reported on status page for StackGuardian https://status.stackguardian.io/ https://d1lppblt9t2x15.cloudfront.net/logos/51e512cef8b92b317afc16c356fbea12.png https://status.stackguardian.io/ en https://status.stackguardian.io/incident/1091228 Fri, 09 Oct 2026 15:40:00 -0000 https://status.stackguardian.io/incident/1091228#e29c8079a9d728527d9abc1c4903d6b09c300b19d776291542c498701b23759a Incident ## Summary Occasionally, a small number of requests to the StackGuardian API timed out. The cause was an intermittent software fault that, from time to time, left one of our API servers unable to finish some requests until it was automatically restarted. Our other servers kept handling requests normally. The permanent fix went live in production on October 8, 2026 at 17:55 UTC. The incident on October 8, 2026 is one example. Between 07:36 and 08:45 UTC that day, 112 requests that create or change resources timed out. The problem cleared on its own when the affected server was restarted. This report uses that incident to explain what happened. Nothing was wrong with your Terraform code or your configuration. ## What you may have seen - **Occasional timeouts, mostly on create, update and delete requests.** The affected requests ended with a 504 Gateway Timeout. Requests handled by our other servers succeeded as normal, so most requests worked while a few failed. In the October 8 example, requests that only read data were not affected. - **A "400 Bad Request" error in Terraform.** The StackGuardian Terraform provider reported the timeout as a 400 Bad Request, for example "Error reading Role Assignment". Running the plan again worked. - **Changes that were made although an error was returned.** The requests that timed out had already done their work before they got stuck. If a request timed out for you, the resource may still have been created or updated. ## Cause A fault in a third-party library we use could leave a request stuck after it had saved its changes but before it replied. Our own code triggered the fault through the way it handled some connections. Once one request was stuck, later create, update and delete requests on the same server waited behind it and received no reply until the server was restarted. The server kept responding to other requests, so it was not detected and replaced sooner. The 400 Bad Request in Terraform was a second, separate fault. When the provider retried a timed-out request, it sent an incomplete request, which the API rejected as invalid. ## What we fixed The two changes that stop the server fault went live in production on October 8, 2026 at 17:55 UTC: - **We upgraded the affected library** to a version without the fault. We could reproduce the fault on the old version and cannot on the new one. - **We changed how our API handles these connections**, which removes the trigger. The Terraform provider now sends the full request when it retries, so a brief server error is retried properly and no longer shows up as a 400 Bad Request. This fix is done in code and ships in the next provider release after v1.12.4. We have not seen the fault recur since the fix went live. ## How we are preventing it from happening again The fixes above remove the fault we found. Two further measures guard against the same kind of problem from any other cause. - **A time limit on every API request.** A request that runs too long will be stopped, so one stuck request can no longer hold up others, whatever made it stick. This is built and tested and is in review; it is not live yet. - **Automated tests for both fixes.** Tests now check the connection handling in our API and that the Terraform provider's retry sends the full request. We apologize for the disruption this caused. https://status.stackguardian.io/incident/1085775 Fri, 09 Oct 2026 09:54:41 -0000 https://status.stackguardian.io/incident/1085775#2f738fe878952178ec7d8b6fff8cde77627861d080795db9d5cd6bb7d8d1248a Incident API recovered. https://status.stackguardian.io/incident/1085775 Fri, 09 Oct 2026 09:50:00 -0000 https://status.stackguardian.io/incident/1085775#243366b476c5f89288a78615176f96a9fee73248f3eca9c9a39c3cead633952c Incident API went down. Please read the RCA here: https://status.stackguardian.io/incident/1091228 https://status.stackguardian.io/incident/927831 Thu, 18 Jun 2026 14:03:53 -0000 https://status.stackguardian.io/incident/927831#c8937af87fd6f5eaf078ee442231a8c1270d2273688d10dbff51e87d98931188 Incident AI model provider recovered. https://status.stackguardian.io/incident/927831 Thu, 18 Jun 2026 13:59:00 -0000 https://status.stackguardian.io/incident/927831#4b3a8676965eeb18694c5de2486cfbc041554fb1c5e82374fc02e91901f3424d Incident AI model provider went down. https://status.stackguardian.io/incident/925902 Tue, 16 Jun 2026 19:07:00 -0000 https://status.stackguardian.io/incident/925902#fade17a35ee2f65b0dabed31aa79f0b321c09d844efd8c1a56ccdc2713388b68 Incident # Incident Report: Degraded AI-Powered Features Due to AI Provider Service Disruption **Incident Status:** Resolved / Monitoring **Incident Date:** 16 June 2026 **Affected Services:** AI-powered capabilities within StackGuardian **Root Cause Category:** Third-party AI provider service disruption ## Summary On 16 June 2026, StackGuardian experienced degraded performance across some AI-powered features due to elevated error rates from an upstream AI model provider. During the incident, users may have experienced failed AI requests, increased response times, or incomplete AI-generated outputs when using AI-assisted capabilities such as code generation, AI agents, compliance assistance, and related model-driven workflows. Core StackGuardian platform functionality, including infrastructure workflow execution, policy enforcement, private runners, Terraform/OpenTofu runs, and platform operations, remained operational and unaffected. ## Impact The incident affected AI-assisted functionality that depends on external model provider availability. Potential user impact included: * Failed or delayed AI-generated responses * Increased latency for AI-powered requests * Intermittent failures in AI-assisted workflows * Incomplete outputs from model-driven features There was no impact to customer infrastructure, workflow execution, policy enforcement, stored configurations, or customer data. ## Root Cause The degradation was caused by an upstream service disruption at one of our AI model providers, which resulted in elevated error rates across multiple models. This was not caused by StackGuardian infrastructure or a failure within the core StackGuardian platform. ## Response Our team identified the issue as originating from an external AI provider and monitored provider status, request failure rates, and platform health throughout the incident. We continued to verify that non-AI StackGuardian functionality remained healthy and that infrastructure orchestration and automation capabilities were not affected. ## Current Status The affected AI provider has implemented mitigations, and StackGuardian has observed recovery in AI request success rates and latency. We are continuing to monitor AI-powered functionality to ensure service stability. ## Preventive Actions and Future Improvements We understand that AI-powered workflows are becoming increasingly important to our customers’ day-to-day operations. To improve resilience, StackGuardian is actively working on strengthening the AI provider layer. This includes building capabilities that will allow us to support fallback options when an AI provider experiences an outage or degradation. Our goal is to make AI-assisted functionality more resilient by enabling provider-level failover, so that where technically possible, requests can be routed to an alternative AI model provider during upstream disruptions. These improvements are part of our broader commitment to platform reliability, operational resilience, and minimizing customer impact from third-party service interruptions. ## Closing Note We apologize for the disruption to AI-powered functionality and appreciate your patience while the upstream provider issue was being resolved. StackGuardian remains committed to delivering a reliable platform for infrastructure orchestration, automation, compliance, and AI-assisted engineering workflows. https://status.stackguardian.io/incident/925902 Tue, 16 Jun 2026 15:30:00 -0000 https://status.stackguardian.io/incident/925902#51579e9565609ee7a317e4328925878cde48497bafc9a0c82b8458e3504ceb64 Incident Monitoring The upstream AI provider has implemented mitigation measures and service recovery is underway. We are monitoring request success rates, latency, and overall platform health before declaring the incident resolved. https://status.stackguardian.io/incident/925902 Tue, 16 Jun 2026 14:20:00 -0000 https://status.stackguardian.io/incident/925902#2e66cce483236527922db6c8a2bbb5a55fb7114d6a6248e105a09513cefa94d1 Incident StackGuardian is currently experiencing degraded performance and elevated error rates affecting AI-powered features. Users may encounter: - Failed AI requests - Increased response times - Incomplete AI-generated outputs Infrastructure orchestration, workflow execution, policy enforcement, and platform operations remain unaffected. We are actively monitoring an issue with one of our AI model providers and working to restore normal service. https://status.stackguardian.io/incident/925902 Tue, 16 Jun 2026 13:50:00 -0000 https://status.stackguardian.io/incident/925902#92dff2e288e4d61e1d894c55b6165a74e3efbd204031a0144aa1c8cba6f7feda Incident Identified We have identified the issue as a service disruption affecting one of our AI model providers. Users may continue to experience intermittent failures, increased latency, or reduced functionality across AI-assisted features while the provider works toward resolution. Core StackGuardian platform functionality, including workflow execution, policy enforcement, and infrastructure automation, remains operational. https://status.stackguardian.io/incident/901689 Thu, 21 May 2026 12:24:43 -0000 https://status.stackguardian.io/incident/901689#67f8b272e958d69f13997131bb6cd9780c2db792ea15be0685242fe4e1cbb475 Incident API recovered. https://status.stackguardian.io/incident/901689 Thu, 21 May 2026 12:18:46 -0000 https://status.stackguardian.io/incident/901689#2644a2dabd84507d30b5bcf5fa7134247741be11b40bb7b2c53440950c082b03 Incident API went down. https://status.stackguardian.io/incident/894030 Tue, 12 May 2026 12:15:18 -0000 https://status.stackguardian.io/incident/894030#9687d5532804e38e5c230f6761858befcd8a5c2173b07715507cbe76a0159488 Incident API recovered. https://status.stackguardian.io/incident/894030 Tue, 12 May 2026 12:12:56 -0000 https://status.stackguardian.io/incident/894030#b2aa48ea85d137d65e2f53c550104793ecf0daf95a8d1f826a426b6c6bfa17e4 Incident API went down. https://status.stackguardian.io/incident/848283 Fri, 13 Mar 2026 06:40:03 -0000 https://status.stackguardian.io/incident/848283#036c6a715de3ac9debf1877286ffd6381efd9830080b378be0c3e9f29bf29a21 Incident API recovered. https://status.stackguardian.io/incident/848283 Fri, 13 Mar 2026 06:37:17 -0000 https://status.stackguardian.io/incident/848283#273cec382bc985c71bdb2f19ba760deb142a00114250204a3a3e4c47d41f658b Incident API went down.