ALL SYSTEMS OPERATIONAL

GitHub systems
are operational.

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

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

Report an outage
  • ALL SYSTEMS OPERATIONAL

    GitHub is up and running.

    Last incident resolved 17 hours ago


    No active incidents at this time. Noticed something? Let us know →
  • 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

    Updating in real-time

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

    Report an outage
  • 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

    65

    Since Mar 2026

  • Major / Critical

    22

    22 high-impact incidents

  • Minor Incidents

    43

    Avg. 0.5 per day

  • Median Resolution

    1h 22m

    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
Delays with Code Scanning and Billing
Jun 1, 2026 · 3:17 PM 9h
Minor
Resolved
Details →
Elevated error rates across multiple services
May 28, 2026 · 7:07 PM < 1m
None
Resolved
Details →
Disruption with OpenAI Models
May 28, 2026 · 7:01 PM 1h 40m
Critical
Resolved
Details →
Webhook APIs and UI Degraded
May 28, 2026 · 1:13 AM 18m
Minor
Resolved
Details →
Incident with Pull Requests, Issues, Git Operations and API Requests
May 27, 2026 · 12:10 PM 1h 6m
Minor
Resolved
Details →
Disruption with some GitHub services
May 26, 2026 · 3:44 PM 51m
Minor
Resolved
Details →
Incident with Actions and Pages
May 26, 2026 · 10:57 AM 2h 21m
Critical
Resolved
Details →
Intermittent errors with app installation token authentication
May 23, 2026 · 4:00 PM 3h 31m
Minor
Resolved
Details →
Incident with Actions
May 20, 2026 · 4:58 PM 3h 15m
Minor
Resolved
Details →
Incident with Copilot
May 19, 2026 · 5:30 AM < 1m
None
Resolved
Details →

Teams monitoring GitHub also watch

Other Monitored Services

Get alerted the moment GitHub goes down.

No credit card · free plan · 2-minute setup

Start Free Trial

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

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

  • Monitor GitHub and 2,000+ services from one dashboard.

    2-minute setup · Cancel any time

  • Create Free Account

    No credit card needed

Hey there 👋  Friends from designmodo are here to help!