Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 5, 2026

  1. CerebrasPartial Service Disruption on Cerebras Endpoints

    Between 7.30 PM PT and 11 PM PT, the inference service was partially disrupted by 502 Gateway errors across all endpoints. This issue is caused by an internal system dependency, the fix was rolled out and the service is operational across all endpoints.

    Resolved

  2. GrammarlyScheduled Maintenance: Subscription Management

    The scheduled maintenance related to subscription management has been successfully completed. All subscription-related functionality has been fully restored. Existing subscriptions and active users were not impacted during this maintenance. Thank you for your patience.

    Resolved

  3. BufferIssue Publishing Posts to TikTok

    We are seeing that TikTok posting success rates have returned to normal levels. TikTok have also confirmed that the issue has been resolved: https://usdsjv.tiktok.com/Technical-issues-impacting-TikTok-US-service. We appreciate your understanding and apologise for any disruption this may have caused.

    Resolved

  4. CerebrasPartial Service Disruption Qwen 235B

    Between 06:00 AM PT and 06:00 PM PT users experienced service disruption with Qwen 3 235B Instruct. We have taken action to address recent changes in traffic patterns and capacity, reducing the disruption. We plan to monitor this endpoint and evaluate restoring rate limits in the next week for Pay Go users.

    Resolved

  5. GitHubDelays in UI updates for Actions Runs

    On February 3, 2026, between 14:00 UTC and 17:40 UTC, customers experienced delays in Webhook delivery for push events and delayed GitHub Actions workflow runs. During this window, Webhook deliveries for push events were delayed by up to 40 minutes, with an average delay of 10 minutes. GitHub Actions workflows triggered by push events experienced similar job start delays. Additionally, between 15:25 UTC and 16:05 UTC, all GitHub Actions workflow runs experienced status update delays of up to 11 minutes, with a median delay of 6 minutes.<br /><br />The issue stemmed from connection churn in our eventing service, which caused CPU saturation and delays for reads and writes, with subsequent downstream delivery delays for Actions and Webhooks. We have added observability tooling and metrics to accelerate detection, and are correcting stream processing client configuration to prevent recurrence.

    Resolved

Feb 4, 2026

  1. RetoolOutage

    Between 12:00pm and 12:08pm, there was a partial outage across many of Retool's product surfaces. There should be no impact outside of that timeframe.

    Resolved

  2. GranolaDesktop transcription failure rates higher than normal

    We've released an update to Granola that should resolve this issue (v7.6.1). Your app should auto-update, or you can get the latest version from our website. If you're still having issues transcribing meetings after updating, get in touch at hey@granola.so "hey@granola.so": mailto:hey@granola.so.

    Resolved

  3. LovableErrors enabling lovable cloud

    Between 16:45 - 18:30 we observed a high rate of failure when enabling Lovable Cloud for new projects, but has since recovered and operations are back to normal.

    Resolved

  4. GitHubDisruption with some GitHub services

    From Feb 2, 2026 17:13 UTC to Feb 2, 2026 17:36 UTC we experienced failures on ~0.02% of Git operations. While deploying an internal service, a misconfiguration caused a small subset of traffic to route to a service that was not ready. During the incident we observed the degradation and statused publicly.<br /><br />To mitigate the issue, traffic was redirected to healthy instances and we resumed normal operation.<br /><br />We are improving our monitoring and deployment processes in this area to avoid future routing issues.

    Resolved

  5. GitHubIncident with Copilot

    On February 3, 2026, between 09:35 UTC and 10:15 UTC, GitHub Copilot experienced elevated error rates, with an average of 4% of requests failing.<br /><br />This was caused by a capacity imbalance that led to resource exhaustion on backend services. The incident was resolved by infrastructure rebalancing, and we subsequently deployed additional capacity.<br /><br />We are improving observability to detect capacity imbalances earlier and enhancing our infrastructure to better handle traffic spikes.

    Resolved

  6. JamfThreat detection notifications for App Store flagged as a sideloaded app

    This incident has been resolved. Actions: A fix has been applied for notifications of App Store app flagging as sideloaded. Customer Action Required: UEM Synchronization To remediate the side-loaded app events identified during this incident, please perform a UEM sync between Jamf Security Cloud and your MDM solution. This sync will also update device risk state used by Access policies. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If a UEM sync was previously performed and alerts still persist, please perform a full sync again. The issue has now been fully resolved and syncing will remediate the false positive events. Alternatively, you can manually archive the specific threat in Radar > Threats view. To synchronize: Navigate to Jamf Security Cloud > Integrations > UEM Connection > Settings > Actions > Synchronize If you have questions or need assistance, please contact Jamf Support.

    Resolved

  7. LovableMonthly credit refill is delayed

    We have completed our investigation and monitoring of the incident that occurred on February 1st. Our systems have been operating normally, and we have confirmed that all necessary backfill processes have completed successfully.

    Resolved

  8. DevinDevin repo setup experience degraded

    We are aware of an issue impacting the Devin session setup experience in production environments. Some users may experience delays or incomplete loading during repository setup. Our engineering team has identified the issue and is working on a fix. We will notify you once service is fully restored. Thank you for your patience.

    Resolved

  9. BufferIssue with Buffer Start Page not loading

    The issue with Start Page has been fully resolved, and it’s functioning as expected again. If you encounter any further problems, please don’t hesitate to reach out to our team.

    Resolved

  10. LeverIntermittent issues impacting Lever API

    The incident occurred from 3:30 am Pacific time until 5:00 am Pacific time. No further action will be required from impacted users to have restored functionality. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new

    Resolved

Older incidents