WhatBrokeToday
Today's Trends
minorResolvedGitHub

GitHub: Elevated 404s for GitHub App s2s tokens in git/API

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(current)

Executive summary

Between 0655 and 0801 UTC on 10/27, GitHub experienced increased failure rates for API requests authenticated with server-to-server tokens. During this window, authenticated git operations mistakenly returned 404 for 1.24% of requests on average and up to 2.49% at peak.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Elevated 404s for GitHub App s2s tokens in git/API(opens official status page in a new tab)

    Resolved: Between 0655 and 0801 UTC on 10/27, customers experienced increased failure rates for API and git requests authenticated with server-to-server tokens for GitHub Apps (excluding Actions tokens). During this window, authenticated git operations mistakenly returned 404 for 1.24% (2.6x) of requests on average and 2.49% (5.3x) at peak. These failures were caused by a scheduled maintenance event where GitHub migrated 7 tables between two MySQL clusters in our IAD and Azure Central US…

    by github status

Timeline

  1. First report on status page

    Elevated 404s for GitHub App s2s tokens in git/API

    Source
  2. Official statement

    Resolved: Between 0655 and 0801 UTC on 10/27, customers experienced increased failure rates for API and git requests authenticated with server-to-server tokens for GitHub Apps (excluding Actions tokens).

    Source
  3. Status changed

    Status changed: new → resolved (official status page reports resolution).