Authentication Issue with MCP
OutageMajor incident
Componentes afetados
Shortcut MCP
- identified
The issue has been identified and a fix is being implemented.
57 Shortcut incidents · Ebrel 2022 — official updates, affected components, duration and resolution details.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
This incident has been resolved.
A questão foi identificada e está a ser implementada uma solução.
Foi implementada uma correção e estamos monitorando os resultados.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do incidente.
O Atalho MCP não estava disponível por aproximadamente 6 minutos devido a uma má configuração. A causa raiz foi identificada, fixa e implementada para evitar uma recorrência futura.
Traduzido automaticamente da atualização oficial do incidente.
A autenticação com o Atalho MCP está falhando para alguns clientes MCP. Estamos a investigar a causa.
A questão foi identificada e está a ser implementada uma solução.
Este incidente foi resolvido.
Traduzido automaticamente da atualização oficial do incidente.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Korey did not respond to user messages.
The Shortcut web app is slow to load and many pages are unresponsive.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We have observed an increase in errors. Response times have increased as well. We are monitoring the situation and working to increase capacity.
We have identified the issue and have taken actions to mitigate the issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Currently investigating processing delays for Gitlab events.
This incident has been resolved.
We are currently investigating an issue where some sessions aren't connecting as expected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
Slack link unfurl events are working as expected.
We're seeing more authentication errors from a cloud provider, causing Korey login issues and disrupting user invitations. Workos has been identified as the root cause: https://status.workos.com/incidents/rdz189wnjhyn.
This incident has been resolved.
From approximately 3:12am EDT until 5:35am EDT, Shortcut was unavailable. We identified the cause to be the widespread AWS outage occurring at that time. During that time, StatusPage's administrative interface was also inaccessible, so we are adding a historical incident here to record the event. AWS states that the services which Shortcut relies on have recovered and we are seeing no further errors in our observability dashboards.
From approximately 3:12am EDT until 5:35am EDT, Shortcut was unavailable. We identified the cause to be the widespread AWS outage occurring at that time. During that time, StatusPage's administrative interface was also inaccessible, so we are adding a historical incident here to record the event. AWS states that the services which Shortcut relies on have recovered and we are seeing no further errors in our observability dashboards.
We are currently investigating an issue with our search system, resulting in many search requests failing.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our async processing infrastructure is running behind. Actively monitoring and investigating the root cause.
We are continuing to investigate this issue.
Notifications for integrations should have caught up. Google Sheet processing has been disabled for the moment, we're working on a fix that will resume processing.
Google Sheets processing has been re-enabled but is still behind. We're monitoring it's progress.
GSheet processing should have caught up. A few integrations had been disabled during investigation, we're looking to restore those integrations.
This incident has been resolved.