Service Disruption: GitHub Actions, Pull Requests, and Issues

This report details a technical incident affecting several core GitHub components. Users can stay informed by subscribing to various alert channels.

🔔 Subscription Options for Updates

To receive real-time notifications when incidents are created, modified, or resolved, please choose one of the following methods:

1. Email Alerts

Provide your email address and verify via a One-Time Password (OTP).

• Field: Email address
• Verification: Enter OTP
• Option: Resend OTP (available after a countdown)

2. SMS Notifications

Select your region and provide a mobile number.

• Supported Regions:
  • Afghanistan (+93), Albania (+355), Algeria (+213), American Samoa (+1), Andorra (+376), Angola (+244), Anguilla (+1), Antigua and Barbuda (+1), Argentina (+54), Armenia (+374), Aruba (+297), Australia/Cocos/Christmas Island (+61), Austria (+43), Azerbaijan (+994), Bahamas (+1), Bahrain (+973), Bangladesh (+880), Barbados (+1), Belarus (+375), Belgium (+32), Belize (+501), Benin (+229), Bermuda (+1), Bolivia (+591), Bosnia and Herzegovina (+387), Botswana (+267), Brazil (+55), Brunei (+673), Bulgaria (+359), Burkina Faso (+226), Burundi (+257), Cambodia (+855), Cameroon (+237), Canada (+1), Cape Verde (+238), Cayman Islands (+1), Central Africa (+236), Chad (+235), Chile (+56), China (+86), Colombia (+57), Comoros (+269), Congo (+242), Congo, Dem Rep (+243), Costa Rica (+506), Croatia (+385), Cyprus (+357), Czech Republic (+420), Denmark (+45), Djibouti (+253), Dominica (+1), Dominican Republic (+1), Egypt (+20), El Salvador (+503), Equatorial Guinea (+240), Estonia (+372), Ethiopia (+251), Faroe Islands (+298), Fiji (+679), Finland/Aland Islands (+358), France (+33), French Guiana (+594), French Polynesia (+689), Gabon (+241), Gambia (+220), Georgia (+995), Germany (+49), Ghana (+233), Gibraltar (+350), Greece (+30), Greenland (+299), Grenada (+1), Guadeloupe (+590), Guam (+1), Guatemala (+502), Guinea (+224), Guyana (+592), Haiti (+509), Honduras (+504), Hong Kong (+852), Hungary (+36), Iceland (+354), India (+91), Indonesia (+62), Iraq (+964), Ireland (+353), Israel (+972), Italy (+39), Jamaica (+1), Japan (+81), Jordan (+962), Kenya (+254), Korea, Republic of (+82), Kosovo (+383), Kuwait (+965), Kyrgyzstan (+996), Laos (+856), Latvia (+371), Lebanon (+961), Lesotho (+266), Liberia (+231), Libya (+218), Liechtenstein (+423), Lithuania (+370), Luxembourg (+352), Macao (+853), Macedonia (+389), Madagascar (+261), Malawi (+265), Malaysia (+60), Maldives (+960), Mali (+223), Malta (+356), Martinique (+596), Mauritania (+222), Mauritius (+230), Mexico (+52), Monaco (+377), Mongolia (+976), Montenegro (+382), Montserrat (+1), Morocco/Western Sahara (+212), Mozambique (+258), Namibia (+264), Nepal (+977), Netherlands (+31), New Zealand (+64), Nicaragua (+505), Niger (+227), Nigeria (+234), Norway (+47), Oman (+968), Pakistan (+92), Palestinian Territory (+970), Panama (+507), Paraguay (+595), Peru (+51), Philippines (+63), Poland (+48), Portugal (+351), Puerto Rico (+1), Qatar (+974), Reunion/Mayotte (+262), Romania (+40), Russia/Kazakhstan (+7), Rwanda (+250), Samoa (+685), San Marino (+378), Saudi Arabia (+966), Senegal (+221), Serbia (+381), Seychelles (+248), Sierra Leone (+232), Singapore (+65), Slovakia (+421), Slovenia (+386), South Africa (+27), Spain (+34), Sri Lanka (+94), St Kitts and Nevis (+1), St Lucia (+1), St Vincent Grenadines (+1), Sudan (+249), Suriname (+597), Swaziland (+268), Sweden (+46), Switzerland (+41), Taiwan (+886), Tajikistan (+992), Tanzania (+255), Thailand (+66), Togo (+228), Tonga (+676), Trinidad and Tobago (+1), Tunisia (+216), Turkey (+90), Turks and Caicos Islands (+1), Uganda (+256), Ukraine (+380), United Arab Emirates (+971), United Kingdom (+44), United States (+1), Uruguay (+598), Uzbekistan (+998), Venezuela (+58), Vietnam (+84), Virgin Islands, British (+1), Virgin Islands, U.S. (+1), Yemen (+967), Zambia (+260), Zimbabwe (+263).
• Field: Phone number
• Verification: Enter OTP (Resend available every 30s)

3. Slack Integration

Connect your Slack workspace to receive maintenance and incident status messages.

4. Webhook Notifications

For automated systems, configure a webhook to trigger on incident creation, updates, resolution, or component status changes.

• Webhook URL: The destination endpoint.
• Email address: Used for failure notifications if the endpoint is unreachable.

[!IMPORTANT] Legal Compliance: By subscribing, you agree to the Privacy Policy, Atlassian Terms of Service, and Atlassian Privacy Policy. All forms are protected by reCAPTCHA; therefore, Google's Privacy Policy and Terms of Service apply.

---

🛠 Incident Timeline & Resolution

The following event occurred on October 12, 2026.

Mitigation Progress Tracking

• Restore Pull Request functionality
• Resolve Issues degradation
• Resolve Actions degradation
• Resolve Projects degradation
• Apply notification mitigation
• Clear notification backlog

Event Log

Visual Workflow of Incident

Official Status Updates

The following excerpts were posted to the status page:

"Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications." — 19:28 UTC

"Notifications have resumed but will continue to be delayed as we work through a backlog." — 15:50 UTC

Technical Implementation (Example Webhook)

If you are using the webhook subscription, your payload might look like this:

{
  "incident": {
    "status": "recovering",
    "component": "notifications",
    "message": "Backlog processing in progress",
    "timestamp": "2026-10-12T19:28:00Z"
  }
}