GitHub logo
ALL SYSTEMS OPERATIONAL

GitHub systems
are operational.

Pulsetic can detect an outage before the provider officially reports it. 160 incidents on record since Mar 2026

Last updated: 1 min ago · 0 user reports (24h)

  • ALL SYSTEMS OPERATIONAL

    GitHub is up and running.

    Last incident resolved 13 hours ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked GitHub. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds on the Team plan, so the next answer arrives by email.

10 monitors free, checked every 5 minutes, with email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

90-Day Health Summary

  • Total Incidents

    69

    Jul 4 to Oct 2, 2026

  • Major / Critical

    26

    38% of the total

  • Minor Incidents

    43

    Avg. 0.5 per day

  • Median Resolution

    1h 19m

    P95: 10h 27m

Across all 4,379 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 2h 4m, and 35% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for GitHub above.

Source: The State of Uptime 2026, figures as of .

GitHub Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Actions Job Delays
Oct 1, 2026 · 2:47 PM 3h 9m
Minor
Resolved
Details →
Elevated request latency
Oct 1, 2026 · 1:37 PM 20m
Minor
Resolved
Details →
[Retroactive] Actions workflow run failures after deployment gate approvals
Oct 1, 2026 · 2:00 AM < 1m
Minor
Resolved
Details →
Copilot Code Review is unable to complete reviews
Sep 28, 2026 · 9:16 PM 51m
Critical
Resolved
Details →
Disruption with billing information updates
Sep 24, 2026 · 4:51 PM 3h 49m
Minor
Resolved
Details →
Incident across several services
Sep 23, 2026 · 10:11 AM 18h 44m
Minor
Resolved
Details →
Incident with Pull Requests
Sep 20, 2026 · 10:13 PM 1h 8m
Minor
Resolved
Details →
Elevated rate of errors for OpenAI models provided by Copilot
Sep 17, 2026 · 8:59 PM 49m
Minor
Resolved
Details →
Degradation with Gemini 3.8 Flash
Sep 16, 2026 · 7:20 AM 10h 27m
Major
Resolved
Details →
Disruption with some GitHub services
Sep 15, 2026 · 7:11 PM 49m
Minor
Resolved
Details →

How do they compare?

Alternatives to GitHub

More in Developer platform

Other Monitored Services

Common questions

Frequently Asked Questions

  • Is GitHub down today?

    Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.

  • How often does GitHub go down?

    Based on our 90-day data, we've recorded 69 incidents, of which 26 were major or critical. The median resolution time is 1h 19m.

  • How are outages detected?

    Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.