https://www.githubstatus.com/incidents/z3c6q056q332 Help Community Status GitHub.com Twitter GitHub header GitHub header x Get email notifications whenever GitHub creates, updates or resolves an incident. Email address: [ ] [Subscribe via Email] By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get text message notifications whenever GitHub creates or resolves an incident. Country code: [United States (+1) ] Phone number: [ ] [Subscribe via Text Message] Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy. Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: [ ] The URL we should send the webhooks to Email address: [ ] We'll send you email if your endpoint fails [Subscribe] By subscribing you agree to our Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Follow @githubstatus or view our profile. Visit our support site. Get the Atom Feed or RSS Feed. Incident with Actions, Codespaces and Pages Incident Report for GitHub Resolved This incident has been resolved. Posted Mar 29, 2023 - 19:03 UTC Update Codespaces is operating normally. Posted Mar 29, 2023 - 18:18 UTC Update We are still working towards full recovery. Actions jobs still experience delays when being queued. Posted Mar 29, 2023 - 18:13 UTC Update Pages is operating normally. Posted Mar 29, 2023 - 18:10 UTC Update We are still working towards full recovery. Actions jobs still experience delays when being queued. Posted Mar 29, 2023 - 17:41 UTC Update Codespaces is experiencing degraded performance. We are continuing to investigate. Posted Mar 29, 2023 - 17:29 UTC Update Actions workflows have started running again. We're continuing to work towards full recovery. Posted Mar 29, 2023 - 16:56 UTC Update Actions is now experiencing degraded performance. We are still investigating and will provide an update when we have one. Posted Mar 29, 2023 - 16:47 UTC Update We are seeing signs of recovery for Actions and continue to monitor closely. We will continue to post updates about progress as soon as we have them. Posted Mar 29, 2023 - 16:22 UTC Update We continue to work on mitigating the problems with Actions and Pages with high urgency. We will continue to post updates about our progress. Posted Mar 29, 2023 - 15:42 UTC Update Pages is experiencing degraded performance. We are continuing to investigate. Posted Mar 29, 2023 - 15:29 UTC Update We are still investigating the cause of Actions degradation, we will provide an update when we have one. Posted Mar 29, 2023 - 14:56 UTC Update Actions is now experiencing degraded availability. We are still investigating and will provide an update when we have one. Posted Mar 29, 2023 - 14:43 UTC Investigating We are investigating reports of degraded performance for Actions. Posted Mar 29, 2023 - 14:21 UTC This incident affected: Actions, Pages, and Codespaces. - Current Status Powered by Atlassian Statuspage GitHub footer Product * Features * Security * Business * Case studies * Pricing * Resources Platform * Developer API * Partners * Atom * Electron * GitHub Desktop Support * Help * Community Forum * Training * Status * Contact Company * About * Blog * Careers * Press * Shop * * * * * * (c) 2023 GitHub, Inc. * Terms * Privacy x Subscribe to Incident Subscribe to updates for Incident with Actions, Codespaces and Pages via email and/or text message. You'll receive email notifications when incidents are updated, and text message notifications whenever GitHub creates or resolves an incident. Email address: [ ] Country code: [United States (+1) ] Phone number: [ ] Subscribe to Incident Message and data rates may apply. By subscribing you agree to our Privacy Policy, the Atlassian Terms of Service, and the Atlassian Privacy Policy. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.