GitHub logo
ALL SYSTEMS OPERATIONAL

GitHub systems
are operational.

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

Last checked: just now · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    GitHub is up and running.

    Last incident resolved 1 day 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, so the next answer arrives by email.

10 monitors free, 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%

Last 90 days

90-Day Health Summary

  • Total Incidents

    76

    Since Mar 2026

  • Major / Critical

    29

    29 high-impact incidents

  • Minor Incidents

    47

    Avg. 0.5 per day

  • Median Resolution

    1h 19m

    P95: 9h

GitHub Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Intermittent failures creating agent tasks
Aug 20, 2026 · 2:43 PM 9h 54m
Critical
Resolved
Details →
Incident with Actions
Aug 18, 2026 · 9:36 AM 46m
Major
Resolved
Details →
Intermittent failures in runner group and runner-related permissions pages
Aug 18, 2026 · 7:40 AM 4h 2m
Minor
Resolved
Details →
Incident with GitHub.com
Aug 17, 2026 · 1:40 PM 7h 35m
Critical
Resolved
Details →
Disruption with GHEC Team Sync
Aug 13, 2026 · 4:21 PM 2h 6m
Minor
Resolved
Details →
Incident with Webhooks
Aug 13, 2026 · 2:45 PM 50m
Minor
Resolved
Details →
Errors with the Fable 5 Model in Copilot
Aug 13, 2026 · 2:43 PM 1h 3m
Minor
Resolved
Details →
Disruption with Login and Release Asset downloads
Aug 12, 2026 · 9:39 PM 1h 17m
Major
Resolved
Details →
Incident with Pull Requests and Issues
Aug 12, 2026 · 4:16 PM 25m
Minor
Resolved
Details →
Incident with GraphQL API Requests
Aug 11, 2026 · 2:50 PM 5h 16m
Minor
Resolved
Details →

How do they compare?

Alternatives to GitHub

Teams monitoring GitHub also watch

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 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 76 incidents, of which 29 were major or critical. The median resolution time is 1h 19m.

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