GitHub logo
ALL SYSTEMS OPERATIONAL

GitHub systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Mar 2026 · 93 incidents caught

Last checked: 1 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    GitHub is up and running.

    Last incident resolved 3 days 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

  • 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%

Last 90 days

90-Day Health Summary

  • Total Incidents

    66

    Since Mar 2026

  • Major / Critical

    24

    24 high-impact incidents

  • Minor Incidents

    42

    Avg. 0.5 per day

  • Median Resolution

    1h 49m

    P95: 9h 17m

GitHub Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Delays starting Actions runs
Jul 9, 2026 · 4:34 AM 9h 17m
Critical
Resolved
Details →
Actions and Codespaces APIs experiencing partial failures
Jul 7, 2026 · 2:14 PM 2h 2m
Major
Resolved
Details →
Incident with Pages
Jul 2, 2026 · 4:54 PM 1h 31m
Minor
Resolved
Details →
Delays in copilot budget limits resets for some users
Jul 1, 2026 · 10:51 AM 2h 34m
Minor
Resolved
Details →
Disruption with some GitHub services - Signup Flow
Jun 30, 2026 · 3:38 PM 10m
Minor
Resolved
Details →
Disruption with some GitHub services
Jun 28, 2026 · 5:50 PM 3h 5m
Minor
Resolved
Details →
Disruption with some GitHub services
Jun 27, 2026 · 2:02 PM 6h 30m
Minor
Resolved
Details →
Degradation with Webhooks, Pull Requests and Actions
Jun 25, 2026 · 5:50 PM 37m
Major
Resolved
Details →
We are seeing elevated errors with Next Edit Suggestions and Completions
Jun 23, 2026 · 11:04 PM 24m
Minor
Resolved
Details →
Incident With Webhooks
Jun 17, 2026 · 7:00 PM < 1m
None
Resolved
Details →

How do they compare?

Alternatives to GitHub

Teams monitoring GitHub also watch

Other Monitored Services

Get alerted the moment GitHub goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is GitHub down today?

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

  • How often does GitHub go down?

    Based on our 90-day data, we've detected 66 incidents, of which 24 were major or critical. The median resolution time is 1h 49m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • 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 detected a real service disruption, confirmed by multiple user reports, 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.