Is GitHub down?

Last checked 3m ago
Current status
GitHub has degraded performance

Active incident: Incomplete pull request results in repositories

Get alerts when GitHub breaks →

Free · no credit card

Official status page: https://www.githubstatus.com · Polled every 5 minutes · 12 components tracked

Real-time GitHub status, recent outages, and incident history — pulled directly from GitHub's official status page at https://www.githubstatus.com every 5 minutes. Pingoru tracks 12 GitHub services and has captured 50 incidents in the last 90 days (93.52% uptime). Get email, Slack, Discord, or webhook alerts the moment GitHub reports a new incident — free for 5 monitors, no credit card.

Users who monitor GitHub also follow these DevOps services: Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems CloudAMQP View all 6,000+ providers
GitHub uptime 93.52% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Incomplete pull request results in repositories
    Ongoing ● 1d 2h
    Started Apr 28, 2026, 02:17 PM UTC
    Pull Requests
    6 updates · show timeline
    • investigating · Apr 28, 2026, 02:17 PM UTC

      We are investigating reports of degraded performance for Pull Requests

    • investigating · Apr 28, 2026, 02:51 PM UTC

      After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents. No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again.

    • investigating · Apr 28, 2026, 03:58 PM UTC

      We are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact.  We are taking a measured approach to safely backfill data and will share additional updates as progress continues.

    • investigating · Apr 28, 2026, 09:43 PM UTC

      Elastic search reindexing of pull requests is continuing. All data is preserved, but may not be available on pages relying on elasticsearch until the reindex is complete. Pages and APIs that do not rely on elasticsearch, including the GitHub CLI (gh pr list) and API (/repos/{owner}/{repo}/pulls), are not impacted and can be used to retrieve pull request data in the interim.

    • investigating · Apr 28, 2026, 10:46 PM UTC

      We have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress.

    • investigating · Apr 29, 2026, 12:40 AM UTC

      Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.

    Latest: Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.

  2. Disruption with some GitHub services
    Resolved 3h 9m
    Started Apr 28, 2026, 01:59 PM UTC · Resolved Apr 28, 2026, 05:09 PM UTC
    Actions
    9 updates · show timeline
    • investigating · Apr 28, 2026, 01:59 PM UTC

      We are investigating reports of impacted performance for some GitHub services.

    • monitoring · Apr 28, 2026, 01:59 PM UTC

      Actions is experiencing capacity constraints with hosted ubuntu-latest and ubuntu-24.02, leading to high wait times. Other hosted labels and self-hosted runners are not impacted.

    • investigating · Apr 28, 2026, 02:02 PM UTC

      Actions is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 28, 2026, 02:49 PM UTC

      We're still investigating the root cause for run start delays and failures for Actions hosted Ubuntu jobs, around 5% of jobs are impacted as of now.

    • investigating · Apr 28, 2026, 03:20 PM UTC

      We've applied a mitigation to unblock running Actions. We're continuing to monitor.

    • investigating · Apr 28, 2026, 03:41 PM UTC

      Currently less than 2% of hosted ubuntu-latest and ubuntu-24.04 runs are delayed or failing. We are continuing to monitor for full recovery.

    • investigating · Apr 28, 2026, 04:36 PM UTC

      Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.

    • monitoring · Apr 28, 2026, 05:08 PM UTC

      Actions is operating normally.

    • resolved · Apr 28, 2026, 05:09 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  3. Disruption with some GitHub services
    Resolved 2h 14m
    Started Apr 27, 2026, 04:48 PM UTC · Resolved Apr 27, 2026, 07:02 PM UTC
    5 updates · show timeline
    • investigating · Apr 27, 2026, 04:48 PM UTC

      We are investigating reports of impacted performance for some GitHub services.

    • investigating · Apr 27, 2026, 05:01 PM UTC

      Copilot Cloud Agent (CCA) jobs using the Codex agent are failing after starting. To avoid this issue, please choose a different agent. We are investigating the cause and working towards remediation

    • investigating · Apr 27, 2026, 05:26 PM UTC

      We've found the issue and are working on deploying a solution to get Codex agent runs working again.

    • monitoring · Apr 27, 2026, 07:01 PM UTC

      The degradation has been mitigated. We are monitoring to ensure stability.

    • resolved · Apr 27, 2026, 07:02 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  4. GitHub search is degraded
    Resolved 6h 15m
    Started Apr 27, 2026, 04:31 PM UTC · Resolved Apr 27, 2026, 10:46 PM UTC
    IssuesPull RequestsActionsPackages
    15 updates · show timeline
    • investigating · Apr 27, 2026, 04:31 PM UTC

      We are investigating reports of degraded performance for Actions

    • investigating · Apr 27, 2026, 04:33 PM UTC

      Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.

    • investigating · Apr 27, 2026, 04:36 PM UTC

      Issues is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 27, 2026, 04:39 PM UTC

      Packages is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 27, 2026, 04:53 PM UTC

      Pull Requests is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 27, 2026, 05:35 PM UTC

      Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.

    • investigating · Apr 27, 2026, 06:17 PM UTC

      We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause

    • investigating · Apr 27, 2026, 06:19 PM UTC

      Pull Requests is experiencing degraded availability. We are continuing to investigate.

    • investigating · Apr 27, 2026, 07:50 PM UTC

      We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery

    • investigating · Apr 27, 2026, 08:06 PM UTC

      Pull Requests is experiencing degraded performance. We are continuing to investigate.

    • investigating · Apr 27, 2026, 09:32 PM UTC

      We've applied a mitigation and continuing to monitor

    • monitoring · Apr 27, 2026, 09:33 PM UTC

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

    • monitoring · Apr 27, 2026, 10:35 PM UTC

      The degradation has been mitigated. We are monitoring to ensure stability.

    • monitoring · Apr 27, 2026, 10:44 PM UTC

      The degradation has been mitigated. We are monitoring to ensure stability.

    • resolved · Apr 27, 2026, 10:46 PM UTC

      This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Latest: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  5. Disruption with some GitHub services
    Resolved 35m
    Started Apr 27, 2026, 04:27 PM UTC · Resolved Apr 27, 2026, 05:03 PM UTC
    Actions
    1 update · show timeline
    • investigating · Apr 27, 2026, 04:27 PM UTC

      We are investigating reports of degraded performance for Actions

    Latest: We are investigating reports of degraded performance for Actions

See the full GitHub outage history

45 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 30 incidents
  • Incomplete pull request results in repositories Ongoing
    Started Apr 28, 2026, 02:17 PM UTC · ● 1d 2h
  • Disruption with some GitHub services Resolved
    Started Apr 28, 2026, 01:59 PM UTC · Resolved Apr 28, 2026, 05:09 PM UTC · 3h 9m
  • Disruption with some GitHub services Resolved
    Started Apr 27, 2026, 04:48 PM UTC · Resolved Apr 27, 2026, 07:02 PM UTC · 2h 14m
  • GitHub search is degraded Resolved
    Started Apr 27, 2026, 04:31 PM UTC · Resolved Apr 27, 2026, 10:46 PM UTC · 6h 15m
  • Disruption with some GitHub services Resolved
    Started Apr 27, 2026, 04:27 PM UTC · Resolved Apr 27, 2026, 05:03 PM UTC · 35m
  • Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region Resolved
    Started Apr 24, 2026, 07:02 PM UTC · Resolved Apr 25, 2026, 12:36 AM UTC · 5h 33m
  • Incident with Pull Requests Resolved
    Started Apr 23, 2026, 09:43 PM UTC · Resolved Apr 23, 2026, 09:43 PM UTC · —
  • Disruption with users unable to start Claude and Codex agent task from the web Resolved
    Started Apr 23, 2026, 07:28 PM UTC · Resolved Apr 23, 2026, 07:42 PM UTC · 13m

See GitHub in your Pingoru dashboard

Monitor GitHub alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add GitHub to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every GitHub incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just GitHub or see every provider at once.

Maintenance calendar

Scheduled GitHub maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every GitHub status change, one inbox

Pingoru watches GitHub's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

GitHub reports on 12 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route GitHub alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming GitHub maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy GitHub services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching GitHub from the same account, with per-user notification preferences for any monitor.

Get notified on GitHub status changes

Pingoru watches GitHub's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring GitHub free

Monitor GitHub along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add GitHub and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track GitHub uptime & incident history

See 90 days of GitHub uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See GitHub uptime history

Frequently asked questions

What is GitHub's uptime?
Over the last 90 days, GitHub reported 93.52% uptime on its official status page. That figure is calculated from the public incident timeline at https://www.githubstatus.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see GitHub's uptime history rolling forward in real time.
Has GitHub had outages in 2026?
Yes — GitHub has had 49 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last GitHub outage?
The most recent GitHub incident was "Disruption with some GitHub services", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://www.githubstatus.com. See the full incident card above for affected components and the update timeline.
How often does GitHub have outages?
Based on the last 90 days, GitHub averages 16.3 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is GitHub's status page?
GitHub's official status page is https://www.githubstatus.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is GitHub down right now?
GitHub has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment GitHub reports a change. Current status is based on 12 tracked services.
How does Pingoru know if GitHub is down?
We read https://www.githubstatus.com directly, using GitHub's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when GitHub has an outage?
Create a free Pingoru account and add GitHub as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
GitHub's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real GitHub incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real GitHub issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official GitHub status?
We use GitHub's own status page at https://www.githubstatus.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Degraded" mean?
GitHub is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch GitHub's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor GitHub free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →