GitHub incident: [Retroactive] Actions workflow run logs delayed

1. resolvedOct 13, 2026, 20:30 UTC

   On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Shippo: Elevated error rate on Canada post Shipment APIMajor · Oct 13, 2026, 08:58 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object Storage S3 incident notificationMinor · Oct 8, 2026, 15:14 UTC
• Twilio: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• Cloudflare: Elevated Errors in China Network ColosMinor · Oct 10, 2026, 04:13 UTC
• Twilio: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Supabase: Realtime latencyMinor · Oct 12, 2026, 22:59 UTC
• Snyk: GitLab Cloud Integration DegradedMinor · Oct 13, 2026, 07:32 UTC

How often does GitHub have incidents?

GitHub reported 63 incidents in the last 90 days, 23 of them major or critical. A typical incident lasted 1h 11m. See GitHub's uptime and incident history