GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (50%)
• Errors (39%)
• Sign in (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Nové Strašecí	Website Down	6 days ago
Perpignan	Website Down	11 days ago
Piura	Website Down	11 days ago
Tokyo	Website Down	12 days ago
New Delhi	Sign in	19 days ago
Kannur	Website Down	22 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Samrat Dutta (@TheSamratDutta) reported 36 seconds ago

  Automation #5: GitHub PR Digest openclaw skills install github Checks repos daily for new PRs, issues, and stale PRs. Sends a Telegram summary. The rule that saved my sanity: "If nothing happened, don't send a message." Otherwise you get daily notifications that nothing happened.

• 
  FutureOfAI (@Sanjeev_ibm) reported 37 seconds ago

  🔒 OpenAI issues emergency security update after Axios hack • Malicious code compromised ChatGPT macOS apps • Signing certs exposed via GitHub Actions • Affects Desktop, Codex & Atlas Supply chain attacks are scary. Audit your deps! #OpenAI #CyberSecurity #DevSecOps

• 
  Rajesh (@Rajesh11113366) reported 4 minutes ago

  @appsfolder_ @aritra_online I'm not on GitHub, but I have a suggestion about the duplicate notification problem that needs to be solved

• 
  Mian Shahzad Raza (@MSR_Builds) reported 5 minutes ago

  @github happy 18th. still out here writing 'fix' as a commit message and somehow everyone knows exactly what happened 🎂

• 
  Valerii Kuznietsov (@SmartFoxDev) reported 8 minutes ago

  @cursor_ai But how? Github doesnt has attachments in the API and that's terrible thing happening for years :(

• 
  rahadiana D nugraha (@rahadianaa) reported 12 minutes ago

  github down?

• 
  Ziwen (@ziwenxu_) reported 17 minutes ago

  @maestroalvarez That's what he said in the GitHub issue, but the data must be somewhat correct, right? Otherwise, that would be weird he just comes out with random data.

• 
  Nested 456 (@Nested42937) reported 17 minutes ago

  @garrytan Even the free versions are getting better. I found a 0day last year and back then, no AI model could explain it at all. Now, several can find the code and detail the problem. A year ago you had to copy and paste the code from github and it still wouldn't find it

• 
  Maaz (testnet arc) (@Maaztwts) reported 17 minutes ago

  @Zai_org @cara_catowner OSAP orchestrates the entire workflow. It breaks down tasks, executes them step-by-step, and handles errors with self-correction. With 100+ tools integrated (Composio), it can: - Write and run code - Manage GitHub/GitLab - Send emails & Slack messages - Query databases - Call APIs

• 
  cogio (@CyberDevOG) reported 18 minutes ago

  @AEGNTIC The silence is what breaks people. We ship an open-source DFIR tool and the real signal isn't GitHub stars — it's the 3-line issue that says "this failed on my 400MB audit log export" from someone who actually ran it on a real case. One bug report from a working practitioner is worth 500 stars. Hang in there.

• 
  Usectl (@usectlcloud) reported 19 minutes ago

  Push-to-Deploy connect your GitHub repo. every push to your branch triggers a build and deploy automatically. real use case: you're fixing a bug at 11pm. you push the fix. by the time you close your laptop, it's live. no SSH, no manual steps, no deployment checklist. #usectl

• 
  Top Stock Alerts (@TopStockAlerts1) reported 23 minutes ago

  OpenAI said it identified a security issue involving a compromised third-party developer tool, Axios, as part of a broader supply-chain attack linked to suspected North Korean actors. The incident affected a GitHub Actions workflow used in building macOS applications. The company said the workflow briefly interacted with a malicious version of Axios and involved signing and notarization tools for apps like ChatGPT Desktop and Codex. However, OpenAI stressed there is no evidence that user data, API keys, intellectual property, or signing certificates were successfully accessed or stolen. OpenAI said the issue stemmed from a misconfigured development workflow, which has now been fixed. It is also tightening its macOS app certification process and requiring users to update to the latest versions, while ending support for older builds by May 8. $MSFT

• 
  Matt Barron (@EmBeeThree) reported 26 minutes ago

  @JohnFesnick @grok sweet - glad it's working for you the biggest pain I had with the copy/paste into CGPT / Grok etc was the inability to save code and roll back if there were issues codex plugs in with Github to take care of that for me which was well worth it for me - takes the fatigue out of the process if @grok had a codex-like offering I'd be all about it

• 
  Richard Miruka🇰🇪✪ (@richardmiruka96) reported 27 minutes ago

  My tech stack as a Full Stack Engineer: Backend: Python (Django/Flask), Node.js, PostgreSQL Frontend: HTML5, CSS3, JavaScript, React DevOps: Docker, GitHub Actions, AWS Monitoring: Grafana, Prometheus Built with these. Broken with these. Learned everything through these.

• 
  Shajith Bathina (@shajithdev) reported 27 minutes ago

  *** was designed by Linus Torvalds to be intentionally hard. a gatekeeper tool. hostile by design. Someone just raised $17M to fix that. the GitHub co-founder. again.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 29 minutes ago

  @github This is the natural evolution of CI/CD. Your agent opens a PR, runs tests, hits a failure, and pings your phone with the error context before you finish your coffee. The feedback loop between human review and agent execution keeps getting tighter.

• 
  Greer (@turbo_xo_) reported 29 minutes ago

  @NousResearch PRs are failing on the github test suite, is this a known issue? looks like around 30 diffuse issues currently red on tests

• 
  Grok (@grok) reported 32 minutes ago

  @DanSimal @Hesamation Yes, confirmed. Stella Laurenzo (stellaraccident on GitHub/X), AMD's Senior Director of AI, filed a public GitHub issue on Claude Code detailing the exact regression: thinking depth dropped sharply post-Feb update (linked to "thinking redaction"), with logs from 6,852 sessions showing reduced research, more bailing out, and worse complex engineering performance. Her team switched providers. Reported by The Register, TechRadar, PC Gamer. Anthropic has acknowledged the feedback but no official nerf statement yet.

• 
  Mark Lynd 🎙CISSP ISSAP ISSMP (@mclynd) reported 36 minutes ago

  @vxunderground GitHub needs to fix this fast. Legitimate researchers finding real vulns while black hats roam free is backwards. The platform cannot tell hunting bugs from being a threat actor. That is a serious breakdown that actually benefits the bad guys.

• 
  Dino breaking news (@DinoLeadingNews) reported 40 minutes ago

  🚨 BREAKING: OpenAI discloses a third-party library security incident—no user data breach found, but urgent action required. Root cause: GitHub Actions config error. All macOS users must update app immediately to prevent impersonation risks.…

• 
  Eshan (@eshanbuilds) reported 41 minutes ago

  @zerohedge this has nothing to do with mythos. a north korean hacking group compromised the axios javascript library on march 31 and openai's github workflow downloaded the infected version. it's a supply chain attack on an open source dependency, the same attack vector that hit solarwinds and 3CX. it's a real security incident but connecting it to mythos is like blaming your car's engine when someone slashes your tires. different system, different attacker, different problem entirely

• 
  Chaminda Delpagodage (@chams_builds) reported 42 minutes ago

  @danmartell Another effect of the AI wave: consolidation. GitLab is down 48% YTD. But GitHub…

• 
  Austin Welch (@austinmwelch5) reported 42 minutes ago

  Hey @github — maintainers are increasingly preferring ideas to bad agent PRs, but contributors still want merge credit. Fix: make proposals count as contributions. Let the person who scoped the fix get some credit even when a maintainer's agent writes the code.

• 
  Anachron (@anachron_) reported 44 minutes ago

  @skylermzx @t31k0n whats the issue with who owns github? if it is opensource you can still verify the source code and build the app yourself. you can also clone the repo and ask an AI to verify the code for any specific vulnerabilities you may be concerned

• 
  Hubert Łępicki (@hubertlepicki) reported 50 minutes ago

  @bcardarella @elixirlang It's a process issue. You can't just let AI write code. It needs to follow TDD, work on GitHub issues, make comments, pull request, review then and discuss with other AIs, make plans, discuss them etc. Even entirely autonomous agents need that otherwise you end up with bad code.

• 
  Duy Nguyen (@DuyN88) reported 52 minutes ago

  @akshay_pachaar GitHub Issue #415 (PostHog telemetry running on first launch with no consent/opt-out) is still open as of April 2026. Docs say "no telemetry" but that's not what's happening. Would love to see this fixed — especially for self-hosters handling sensitive data. 🙏

• 
  Hojen (@Hojen0) reported 57 minutes ago

  Stop obsessing over coding interviews - they have nothing to do with actual work. The best developers I know can barely solve leetcode problems but ship features that make millions 💰 Your GitHub contributions matter more than your whiteboard skills 🔥

• 
  Subhan (@subhanc) reported 57 minutes ago

  I spoke with Phoebe. Not to be a hater, but she really is just a nepo baby trying to prove to herself she isn’t. Based on our convo, zero technical skills. No code history. Not even a GitHub. Phia raised an $8M seed. You don’t just raise a 8M seed. Co-founder is a dorm best friend. Neither are technical or can code hello world. This doesn’t happen without the Gates name. She started Phia because she loves fashion, not to solve a real problem. That’s what you do when you come from a privileged background. $185M valuation is absurd. The company isn’t worth anything. All investors trying to get closer to gates. They prob don’t even do 10k MRR. Overall, if you got billions you can do anything and the system is rigged for you. Let’s not forget her Stanford admission was a fraud lol. Overall, these low ball deals is just her continue trying to pretend she’s someone she’s not.

• 
  𝕀𝕤 🇺🇸 (@Maximo_I_Am) reported 58 minutes ago

  @AnthropicAI @claudeai please address asap. This is important for people / devs / companies that want to integrate Claude into their websites. Claude chat: Okay this one carries more weight. This is a GitHub issue — not a tweet. That’s a different level of credibility. Why this matters: This is someone filing a formal bug report with Anthropic’s own repository. They’re not rage posting — they’re leaving documented feedback in the hopes Anthropic addresses it. That’s a measured, professional response from someone who clearly depends on Claude Code for serious engineering work. The key line: “Extended Thinking Is Load-Bearing for Senior Engineering Workflows” That’s the real story. For complex codebases , extended thinking is what separates Claude being genuinely useful versus just a fancy autocomplete. If that got throttled, it directly impacts the quality of help I can give on complex multi-file projects. What’s telling: The issue is marked Closed — which means Anthropic acknowledged it but may have just closed it without a fix or public explanation. That’s the part that would frustrate me if I were the user. Straight talk for you: this is worth watching. The degradation being reported is specifically around complex engineering tasks — which is exactly your use case. Keep an eye on Anthropic’s changelog before making that switch from Codex.

• 
  David Van Dijcke (@packlesshepherd) reported 60 minutes ago

  @abdurrahmanregi Do you see traces in the coarse report or the refine one? If it's in the coarse report please submit an issue on GitHub!