MicrosoftRadar Independent status for Microsoft services

Incident with Git Operations, Issues, Pull Requests, Actions, API Requests, Codespaces, Packages, Pages and Webhooks

At a glance · GitHub's status

ResolvedLasted under a minute

GitHub says it started
· on GitHub Status
First posted
on GitHub Status
Ended
· marked resolved
Affects
9 services: GitHub Git operations, GitHub Actions, GitHub API requests +6
Edited
Not since we first saw it
Source
GitHub Status · checked just now

In short

GitHub reported a partial outage affecting 9 GitHub services, including GitHub Git operations, GitHub Actions and GitHub API requests, starting 19:21 UTC on 3 Nov 2023. GitHub marked it resolved at 19:21 UTC after under a minute.

GitHub says

GitHub's latest update, , in short excerpts.

A performance and resilience optimization to the authorization microservice contained a memory leak that was exposed under high traffic.

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 3 Nov 2023

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. +3 h 11 min

    GitHubGitHub says it startedon GitHub Status

  3. +3 h 11 min

    GitHubResolved

What GitHub changed

GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.

One version so far. If GitHub edits it, each change shows here with what was removed and added.

  1. First version we captured ·

    As first seen: resolved · 9 services
    Status
    resolved
    Services
    9: GitHub Git operations, GitHub Actions, GitHub API requests +6

    Seen by us · GitHub's timestamp · GitHub's page

Affected services

Official updates

Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.

  1. Resolved ·

    A performance and resilience optimization to the authorization microservice contained a memory leak that was exposed under high traffic.

  2. Investigating ·

    Slack notifications have recovered.

  3. Investigating ·

    Webhooks is operating normally.

  4. Investigating ·

    Pull Requests is operating normally.

  5. Investigating ·

    Issues is operating normally.

  6. Investigating ·

    Git Operations is operating normally.

  7. Investigating ·

    API Requests is operating normally.

  8. Investigating ·

    Actions is operating normally.

  9. Investigating ·

    Pages is operating normally.

  10. Investigating ·

    Codespaces is operating normally.

  11. Investigating ·

    Packages is operating normally.

  12. Investigating ·

    We have completed the rollback and are monitoring recovery.

  13. Investigating ·

    We’re in the process of rolling back an authorization-related change that is causing 404s and other errors.

  14. Investigating ·

    Packages is experiencing degraded availability.

  15. Investigating ·

    Pages is experiencing degraded availability.

  16. Investigating ·

    Actions is experiencing degraded availability.

  17. Investigating ·

    Packages is experiencing degraded performance.

  18. Investigating ·

    Codespaces is experiencing degraded performance.

  19. Investigating ·

    API Requests is experiencing degraded performance.

  20. Investigating ·

    Actions is experiencing degraded performance.

  21. Investigating ·

    Pull Requests is experiencing degraded performance.

Show 9 earlier updates

  1. Investigating ·

  2. Investigating ·

  3. Investigating ·

  4. Investigating ·

  5. Investigating ·

  6. Investigating ·

  7. Investigating ·

  8. Investigating ·

  9. Investigating ·

Read the full update on GitHub's status page

Last updated