2024-08-02: Duo Chat getting A1000 / Bad Gateway error on gitlab.com
Exec summary
GitLab team members reported intermittent errors using Duo Chat, receiving A1000 errors.
On further investigation the impact appears to be low, and intermittent.
We believe this is related to https://status.anthropic.com/incidents/nly5s6zbcvg5 Elevated rate limiting errors on the API
We downgraded to severity 3, and monitored.
Anthropic resolved their incident and we noted a drop in errors. After 30min of no relevant errors in the logs, we marked this as Resolved.
Customer Impact
The Anthropic API errors impacted a small number of Duo Chat requests, and Code Generation requests.
Initial report:
My user @jay_mccure is getting A1000 error when using Duo Chat on gitlab.com (@elwyn-gitlab / @tmike is getting the same)
UPDATE: getting some responses now, but still seeing some A1000's, also getting them on my private account
Sometimes I see the bad gateway page in the response:
Current Status
The incident is resolved.
📝 Summary for CMOC notice / Exec summary:
- Customer Impact: A small percentage of Duo Chat and Code Generation users impacted due to a third party API incident.
- Service Impact: Intermittent - many team members reported no issues using these features, some reported occasional errors.
- Impact Duration: 01:46 UTC - 03:46 UTC ( 120 minutes )
- Root cause: Third party API partial outage
📚 References and helpful links
Recent Events (available internally only):
- Feature Flag Log - Chatops to toggle Feature Flags Documentation
- Infrastructure Configurations
- GCP Events (e.g. host failure)
Deployment Guidance
- Deployments Log | Gitlab.com Latest Updates
- Reach out to Release Managers for S1/S2 incidents to discuss Rollbacks, Hot Patching or speeding up deployments. | Rollback Runbook | Hot Patch Runbook
Use the following links to create related issues to this incident if additional work needs to be completed after it is resolved:
- Corrective action ❙ Infradev
- Incident Review ❙ Infra investigation followup
- Confidential Support contact ❙ QA investigation
Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in our handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.
Security Note: If anything abnormal is found during the course of your investigation, please do not hesitate to contact security.