GitLabDuo Agentic Chat intermittently fails to respondPartial Service Disruption
We are wrapping up our monitoring period and this incident is now resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We are wrapping up our monitoring period and this incident is now resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have fixed the issue
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between March 2, 21:42 UTC and March 3, 05:54 UTC project board updates, including adding new issues, PRs, and draft items to boards, were delayed from 30 minutes to over 2 hours, as a large backlog of messages accumulated in the Projects data denormalization pipeline.<br /><br />The incident was caused by an anomalously large event that required longer processing time than expected. Processing this message exceeded the Kafka consumer heartbeat timeout, triggering repeated consumer group rebalances. As a result, the consumer group was unable to make forward progress, creating head-of-line blocking that delayed processing of subsequent project board updates.<br /><br />We mitigated the issue by deploying a targeted fix that safely bypassed the offending message and allowed normal message consumption to resume. Consumer group stability recovered at 04:10 UTC, after which the backlog began draining. All queued messages were fully processed by 05:53 UTC, returning project board updates to normal processing latency.<br /><br />We have identified several follow-up improvements to reduce the likelihood and impact of similar incidents in the future, including improved monitoring and alerting, as well as introducing limits for unusually large project events.
Resolved
This degradation has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue.
Resolved
After further monitoring and some additional fixes deployed by engineering, we are considering this issue resolved.
Resolved
This is now resolved.
Resolved
On February 27, 2026, between 22:53 UTC and 23:46 UTC, the Copilot coding agent service experienced elevated errors and degraded functionality for agent sessions. Approximately 87% of attempts to start or interact with agent sessions encountered errors during this period.<br /><br />This was due to an expired authentication credential for an internal service component, which prevented Copilot agent session operations from completing successfully.<br /><br />We mitigated the incident by rotating the expired credential and deploying the updated configuration to production. Services began recovering within minutes of the fix being deployed.<br /><br />We are working to improve automated credential rotation coverage across all Copilot service components, add proactive alerting for credentials approaching expiration, and validate configuration consistency to reduce our time to detection and mitigation of issues like this one in the future.
Resolved
Issue is resolved.
Resolved
This incident has been resolved.
Resolved
We observed no issues for the past 1h. Closing the incident.
Resolved
On February 25, 2026, between 15:05 UTC and 16:34 UTC, the Copilot coding agent service was degraded, resulting in errors for 5% of all requests and impacting users starting or interacting with agent sessions. <br /><br />This was due to an internal service dependency running out of allocated resources (memory and CPU). We mitigated the incident by adjusting the resource allocation for the affected service, which restored normal operations for the coding agent service.<br /><br />We are working to implement proactive monitoring for resource exhaustion across our services, review and update resource allocations, and improve our alerting capabilities to reduce our time to detection and mitigation of similar issues in the future.
Resolved
This incident has been resolved.
Resolved
Migration to our new Logging Platform is now complete, and near real-time logs should be visible again. Unfortunately, we had to accelerate the migration timeline as our legacy platform began struggling much sooner than expected. Because of this, we made the difficult decision to complete the migration before fully backfilling the expected 3 days of retained logging history. At the moment, approximately 1.5 days of logs are available on the new platform. This will gradually increase and return to the full 3-day retention by Friday. The raw, unprocessed logs remain stored on the legacy logging platform. If you require access to these logs and have a valid justification, please submit a support ticket, and we will do our best to recover them on a case-by-case basis.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved.
Resolved
From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
From 10:52 - 11:35 UTC, User Data and Conversation Data would not load in the Helpdesk. There were also failures in Ticket Creation. This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour
Resolved
This turned out to be an issue with the alerting.
Resolved
Supabase have resolved their incident, and everything is back to being operational.
Resolved
Publishing success rates for TikTok posts have returned to normal levels over the past few hours, and it appears that TikTok has recovered. We apologize for any inconvenience this may have caused. If you’re still experiencing issues, please reach out to us at hello@buffer.com: mailto:hello@buffer.com.
Resolved
This incident has now been mitigated and services are back to normal.
Resolved
Business Account onboarding issues in Europe have now been resolved.
Resolved
This incident has been resolved.
Resolved
We identified that an unhealthy host was not properly evicted, which caused search failures and increased latency for some customers. The issue has now been resolved, and search performance has returned to normal.
Resolved
Per further log inspection on our side, we're no longer seeing the problem occurring. The incident is now resolved. Refer to https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21436 for details.
Resolved
We've deployed the fix and the issue is now resolved.
Resolved
We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.
Resolved
This incident has been resolved.
Resolved
We have resolved the issue.
Resolved
The temporary spike in queued redeployments has been cleared, and updates have returned to processing normally again. We will continue monitoring to redeployments.
Resolved
The incident is now resolved and the system is full operational after monitoring.
Resolved
Access to Supabase’s website has now been fully restored for all users across India. If you were previously affected, you should now be able to access your Supabase projects without interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Allow up to 24 hours for changes to propagate across providers. Thank you for your patience while we worked through this incident.
Resolved
On March 3, 2026, between 19:44 UTC and 21:05 UTC, some GitHub Copilot users reported that the Claude Opus 4.6 Fast model was no longer available in their IDE model selection. After investigation, we confirmed that this was caused by enterprise administrators adjusting their organization's model policies, which correctly removed the model for users in those organizations. No users outside the affected organizations lost access.<br /><br />We confirmed that the Copilot settings were functioning as designed, and all expected users retained access to the model. The incident was resolved once we verified that the change was intentional and no platform regression had occurred.
Resolved
This incident has been resolved.
Resolved