Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Oct 28, 2026

  1. GranolaGranola app services down

    We should be back up and running again. If you're still having problems, get in touch at hey@granola.so "hey@granola.so": mailto:hey@granola.so.

    Resolved

  2. CursorMultiple services degraded

    Services have recovered and we're monitoring to make sure everything stays stable. If you're still seeing errors, please try again. We'll post another update once we've confirmed the issue is fully resolved.

    No longer active

  3. GitHubDelayed Actions status check results

    On October 23, 2026, between 07:06 UTC and 07:27 UTC, GitHub Actions workflow run results were delayed. Job status, check run updates, and logs in the GitHub UI and API updated with an average delay of about 2 minutes, and some updates were delayed by up to about 7 minutes. <br /><br />During this window, a storage dependency that Actions uses to process workflow logs and artifacts throttled our requests. This slowed result processing, causing updates to queue up. The queue was fully processed by 07:27 UTC, shortly after the throttling stopped. <br /><br />To reduce the risk of recurrence, we have added several storage accounts to increase capacity, and we are working on additional steps to continue to scale. We are also working with our storage provider to understand why the throttling occurred, and improving how result processing handles storage throttling and how quickly we detect it.

    Resolved

  4. StripeElevated Issuing errors from 17:13 - 20:41 UTC

    From 17:15 - 20:41 UTC, Stripe Issuing cards that were created or updated between 17:15–17:54 UTC experienced elevated error rates for API requests. The majority of errors subsided by 19:32 UTC, with full resolution occurring at 20:41 UTC. We have corrected the affected card data, and this issue is now resolved.

    Resolved

  5. SnowflakeINC20000301

    Current status: We've implemented the fix for this issue and monitored the environment to confirm that service was restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features. Affected users may have been unable to sign in, use Snowsight, execute queries, resume virtual warehouses, or ingest files using Snowpipe or Snowpipe Streaming. Scheduled tasks and other automated workloads may also have failed to run or may not start as expected. Impact start time: 17:50 UTC October 21, 2026 Impact end time: 21:25 UTC October 21, 2026 Preliminary root cause: A configuration change applied to the cloud services layer in the specified region interacted with existing settings in a way that caused a significant number of instances to be taken out of service. This led to cascading failures across sign-in, query execution, data ingestion, and other dependent services. A root cause analysis (RCA) will be conducted and a summary will be made available within 5 business days.

    Resolved

  6. LinearSome Slack integrations have been unexpectedly archived

    "We’ve deployed a fix for the issue that unexpectedly disconnected Slack integrations in some workspaces. If your integration remains disconnected, reconnect it in Linear under Settings → Integrations → Slack, then add Linear back to affected channels using /invite @Linear. Your notification settings and project channel links will return automatically. We’re sorry for the disruption and the extra steps needed to restore your integration. "

    Resolved

  7. SendGridPossible 503 Errors for Messaging Traffic in the Australia Region

    Our engineers have deployed a fix, and are monitoring to confirm that affected customers in the Australia Region are no longer encountering 503 Errors for Messaging Traffic. We expect to provide another update in 30 minutes or as soon as more information becomes available.

    No longer active

  8. HarnessIntermittent CI Pipeline using VM Runner slowness and errors

    Starting 10/28/2026 10:10 AM CI jobs on internal VM runners intermittently hung or expired without logs, affecting some customers in prod1/2. The resolution is to upgrade the new runner version https://github.com/drone-runners/drone-runner-aws/releases/tag/v1.0.0-rc.318 (Docker image: drone/drone-runner-aws:1.0.0-rc.318)

    Resolved

  9. SendGridMMS Delivery Delays from a Subset of Twilio Long Codes to GCI United States

    We have identified that GCI is a small network in the US and doesn't always return delivery receipts. Because of this, an affected message can stay at "sent" in your Message Logs instead of changing to "delivered" or "undelivered." Our connectivity partner is building a new connection to GCI to improve messaging reliability and we expect it to be ready between mid-November and late November. We will proceed with the resolution of this post.

    Resolved

  10. TwilioMMS Delivery Delays from a Subset of Twilio Long Codes to GCI United States

    We have identified that GCI is a small network in the US and doesn't always return delivery receipts. Because of this, an affected message can stay at "sent" in your Message Logs instead of changing to "delivered" or "undelivered." Our connectivity partner is building a new connection to GCI to improve messaging reliability and we expect it to be ready between mid-November and late November. We will proceed with the resolution of this post.

    Resolved

  11. SendGridSMS Delivery Delays and Failures from Twilio to MTC Namibia

    Twilio customers may be experiencing SMS delivery delays and delivery failures from Twilio to MTC network subscribers in Namibia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

    No longer active

  12. SendGridTwilio Console Errors

    Twilio Console was degraded for 90 minutes between 28 October 2026 7:45 AM and 9:15 AM Pacific Time. During this period of time customers may have experienced errors when loading some pages in One Console. The issue has now been resolved.

    Resolved

Older incidents