Authentifizierungsproblem mit MCP
OutageSchwerwiegender Vorfall
Betroffene Komponenten
Shortcut MCP
- identified
The issue has been identified and a fix is being implemented.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
57 Shortcut incidents · April 2022 — official updates, affected components, duration and resolution details.
The issue has been identified and a fix is being implemented.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
We are currently investigating this issue.
This incident has been resolved.
Das Problem wurde identifiziert und ein Fix wird implementiert.
Ein Fix wurde implementiert und wir überwachen die Ergebnisse.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Der Shortcut MCP war aufgrund einer Fehlkonfiguration etwa 6 Minuten lang nicht verfügbar. Die Ursache wurde identifiziert, behoben und Schritte implementiert, um ein zukünftiges Wiederauftreten zu verhindern.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Die Authentifizierung mit dem Shortcut MCP scheitert bei einigen MCP-Clients. Wir untersuchen die Ursache.
Das Problem wurde identifiziert und ein Fix wird implementiert.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
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.