GlobalOutageMap
← Live dashboard
GitHub logoGitHub

Incident with Pull Requests and Issues

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Aug 12, 2026, 04:16 PM · Resolved Aug 12, 2026, 04:41 PM

Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application...

GitHub live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with GitHub now? Check the current status

Affected services

Pull RequestsIssues

Updates (5)

  1. Aug 12, 2026, 04:41 PM
    Incident with Pull Requests and Issues

    Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application con

    GitHub ↗
  2. Aug 12, 2026, 04:38 PM
    Incident with Pull Requests and Issues

    We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.

    GitHub ↗
  3. Aug 12, 2026, 04:35 PM
    Incident with Pull Requests and Issues

    The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

    GitHub ↗
  4. Aug 12, 2026, 04:24 PM
    Incident with Pull Requests and Issues

    We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

    GitHub ↗
  5. Aug 12, 2026, 04:16 PM
    Incident with Pull Requests and Issues

    We are investigating reports of degraded performance for Issues and Pull Requests

    GitHub ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow GitHub's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.