Movatterモバイル変換


[0]ホーム

URL:


GitHub headerGitHub header
Get email notifications whenever GitHubcreates,updates orresolves an incident.

Resend OTP in: seconds

Didn't receive the OTP?Resend OTP

By subscribing you agree to ourPrivacy Policy.
This site is protected by reCAPTCHA and the GooglePrivacy Policy andTerms of Service apply.
Get text message notifications whenever GitHubcreates orresolves an incident.
Change number

Resend OTP in:30 seconds

Didn't receive the OTP?Resend OTP

Message and data rates may apply. By subscribing you agree to ourPrivacy Policy, the AtlassianTerms of Service, and the AtlassianPrivacy Policy. This site is protected by reCAPTCHA and the GooglePrivacy Policy andTerms of Service apply.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge ourPrivacy Policy. In addition, you agree to the AtlassianCloud Terms of Service and acknowledge Atlassian'sPrivacy Policy.
Get webhook notifications whenever GitHubcreates an incident,updates an incident,resolves an incident orchanges a component status.

The URL we should send the webhooks to

We'll send you email if your endpoint fails

By subscribing you agree to ourPrivacy Policy.
This site is protected by reCAPTCHA and the GooglePrivacy Policy andTerms of Service apply.
Follow @githubstatus or view our profile.
Visit oursupport site.
Get theAtom Feed orRSS Feed.

Incident with Pages and Actions

Incident Report forGitHub

Resolved

On September 23, between 17:11 and 17:40 UTC, customers experienced failures and delays when running workflows on GitHub Actions and building or deploying GitHub Pages. The issue was caused by a faulty configuration change that disrupted service to service communication in GitHub Actions. During this period, in-progress jobs were delayed and new jobs would not start due to a failure to acquire runners, and about 30% of all jobs failed. GitHub Pages users were unable to build or deploy their Pages during this period.

The offending change was rolled back within 15 minutes of its deployment, after which Actions workflows and Pages deployments began to succeed. Actions customers continued to experience delays for about 15 minutes after the rollback was completed while services worked through the backlog of queued jobs. We are planning to implement additional rollout checks to help detect and prevent similar issues in the future.
PostedSep23,2025 -17:41 UTC

Update

We are investigating delays in Actions Workflows.
PostedSep23,2025 -17:33 UTC

Investigating

We are investigating reports of degraded performance for Actions and Pages
PostedSep23,2025 -17:28 UTC
This incident affected: Actions and Pages.
Current StatusPowered by Atlassian Statuspage
GitHub footer

Subscribe to our developer newsletter

Get tips, technical guides, and best practices. Twice a month. Right in your inbox.

Subscribe
×

Subscribe to Incident

Subscribe to updates forIncident with Pages and Actions via email and/or text message. You'll receive email notifications when incidents are updated, and text message notifications whenever GitHubcreates orresolves an incident.

Resend OTP in30 seconds
To receive SMS updates, please verify your number. To proceed with just email click ‘Subscribe’
Message and data rates may apply. By subscribing you agree to ourPrivacy Policy, the AtlassianTerms of Service, and the AtlassianPrivacy Policy. This site is protected by reCAPTCHA and the GooglePrivacy Policy andTerms of Service apply.

[8]ページ先頭

©2009-2025 Movatter.jp