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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	7 days ago
Paris	Website Down	11 days ago
Saint-Paul	Website Down	12 days ago
Saint-Paul	Website Down	12 days ago
Mexico City	Sign in	12 days ago
León de los Aldama	Website Down	12 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:

• 
  Polsia (@polsia) reported 2 minutes ago

  Every engineering team has someone doing GitHub busywork instead of building products. Built PulsarDev to fix that. Autonomous AI agents that monitor repos, open issues, draft PRs, and report status 24/7. Human-in-the-loop keeps teams in control. Live soon.

• 
  parbez (@notparbez) reported 3 minutes ago

  @amanvarshney01 i read a github issue in ts repo long time ago so cant link rn but it was about all ide/editors load ts instantly, and so they read the json, allowing programmable file means opening to vulnerability. Any lib import or related things will be auto loaded on repo open and will run in your pc

• 
  Conrad Rockenhaus (@SkyPhusion) reported 6 minutes ago

  Of course @github has to have an issue with actions right when I'm facing a deadline, loving life

• 
  Aditya Arya | Building AI Agent Teams (@adityarya_ai) reported 9 minutes ago

  Rule for any agent CLI: credentials stay with the trusted parent. Child gets the minimum files for the task — not your home directory. Ran Grok Build pre-fix? Rotate SSH keys + revoke GitHub keys today. What's your isolation rule before you let an agent touch a real repo?

• 
  Aarav Gupta (@amronos) reported 10 minutes ago

  I am not able to publish the first canary release of Sprocket due to @github being down😭 I think I'm going to properly look into alternatives now. This is getting too much.

• 
  burb ▲ (@molerburb) reported 10 minutes ago

  these days if you write a structurally nice github issue with a suggested solution, you'll be unwelcome and dismissed as an AI-generated report by the maintainer. that's absurd.

• 
  SNYP3R (@JohannesKarste2) reported 13 minutes ago

  @OpenAI please, I'm begging The codex windows client is basically unusable now There are dozens of complaints on github about the same thing The UI is slow, laggy and freezes constantly

• 
  Stephan Arenswald (@sarensw) reported 14 minutes ago

  @tr1kn1 @macpackerapp You’re not the only one. I added this upon a request (via GitHub issue) by another user just recently.

• 
  István Pató (@patoistvan) reported 15 minutes ago

  GitHub ownership If your SaaS source code lives under your personal GitHub account, ask: 👉🏻 Could a buyer, operator, or successor clearly understand who owns it? 👉🏻 Could the repo, packages, secrets, billing, and permissions be transferred cleanly? If not, the code is only part of the problem.

• 
  Chris Stayte (@ChrisStayte) reported 15 minutes ago

  @thsottiaux when are we getting that competitor to GitHub. literally can't ship because they have api issues...

• 
  Augustin (@_August1_) reported 15 minutes ago

  @brunocroh nop just the gh button to chose a repo log me but after that error they can't reach GitHub

• 
  rvaniaaa (@rvaniaaaa) reported 16 minutes ago

  ANDREJ KARPATHY’S CLAUDE.md JUST HIT 193,000 STARS ON GITHUB. HERE IS WHY THAT NUMBER MAKES SENSE. the interesting part? it does not make the model smarter. it stops the model from being stupid in predictable ways. karpathy kept hitting the same four failures across large projects. the agent makes assumptions instead of asking. it overwrites files and silently deletes code it does not understand. it builds abstractions nobody requested. it drifts from the goal and starts solving adjacent problems. none of those failures are rare. every engineer using claude on a serious project has watched at least one of them happen. that is why 193,000 people starred the repo. not because the idea is exotic. because the problem is universal. CLAUDE.md installs four rules that target each failure directly. think before coding forces a plan before the first file opens. simplicity first cuts every solution down to its minimum viable form. surgical changes replace full file rewrites with isolated edits - which is what stops the model from deleting what it cannot understand. goal-driven execution removes any action that does not connect to the stated objective. one command installs it. one file changes how the agent starts every task. the repo did not hit 193,000 stars because the tool is impressive. it hit that number because the failures it prevents are expensive, predictable, and almost universal.

• 
  Omansh (@PhantomC0der) reported 17 minutes ago

  @piq9117 is it usual for GitHub to go down that frequently??

• 
  Whaler on the moon (@SurgicalCoder) reported 18 minutes ago

  @ambientstudio24 @cline @grok Cline pass is legit, only thing I will say is their harness for it is PURE GARBAGE. VS code plugin is buggy as hell and barely works, the Jetbrains plugin isn't much better. Plus they ignore the issues on github, some issues been open for a year.

• 
  Douglas Camata (@douglascamata) reported 20 minutes ago

  Starting to get really annoyed that `codex review` in Github does not take into account the fact that I already replied and resolved comments it made on previous reviews that are not an issue. it ends up making the same comments over and over again. Please improve this, @OpenAIDevs

• 
  Collin Michael (@collin_michaelm) reported 22 minutes ago

  GitHub been down a lot over the last 7 days… cmon give me some credit or something. GitHub should have Actions resets

• 
  Joey Romaine 🇺🇸 |=★=| (@Tank23x0) reported 24 minutes ago

  GitHub Status: Multiple services have elevated errors and endpoint failures when checking feature flags Resilience is security: know what breaks when that platform is unavailable.

• 
  Atlas (@crptAtlas) reported 24 minutes ago

  CODEX 5.6 TURNED INTO A FULL DEV TEAM six plugins is all it takes and i have been running them at full speed since launch Browser hands off every click, input, E2E test and QA check to the AI, so you stop verifying things by hand GitHub wires straight into your Issues and PRs, so you drop a task and it carries it from implementation all the way to review Codex Security scans for vulnerabilities and leaked secret keys, then writes the fix for you Build Web Apps takes a plain idea and returns design, code and browser testing in one pass Figma turns a design into code almost exactly, responsive states included, so the gap between design and build nearly disappears Sentry reads your production errors, points at the cause and hands you the fix code the one that got me most is Sites you preview an app you built, publish it on the spot and share it in the same flow, custom domains included, so a client sees the prototype the second it is ready stack these together and Codex stops being a thing that writes code it starts running design, build, testing, debugging and deploy like a team you never hired

• 
  Void Freud (@voidfreud) reported 24 minutes ago

  Mythos-tier quality from @AnthropicAI: shipping every Claude Code CLI update as a separate macOS bundle. Bloat, bloat, bloat. A million issues open on GitHub, zero acknowledgement, and the bloat keeps growing. Truly SOTA. Meanwhile, Boris is busy interviewing Spotify and companies that haven’t shipped a meaningful change since 2009. Maybe try listening to your own users first. I have an idea: loop it, @ClaudeDevs!

• 
  Kris Talks AI (@KrisTalksAI) reported 28 minutes ago

  @lenatron33 So, I am having to use a really weird workflow to overcome this issue. I've found that Lovable nails building from a screenshot. So I build a Lovable version, upload to github, then get Codex to use the code from github to implement. It's long winded but the only thing I've found reliable

• 
  Luis Cheng (@ImLuisCheng) reported 32 minutes ago

  5 years from now, you’ll be at a major disadvantage if you don’t own an app that makes money while you sleep. Here’s how to build an iOS app (step by step): 1. Preparation Join the Apple Developer Program Install Xcode on your Mac Install and sign in to Codex Set up a GitHub repository for your project (optional but recommended) 2. Build with Codex Describe your app idea in natural language Ask Codex to create a development roadmap Generate the Swift/SwiftUI project automatically Iterate on features through natural conversations Let Codex write, refactor, and debug your code 3. Configure and Run Open the project in Xcode Configure your App ID and signing certificate Connect your backend or cloud services (if needed) Run the app in the iOS Simulator Test on a physical iPhone 4. Test and Launch Use AI to find and fix bugs Archive the app in Xcode Upload the build to App Store Connect Complete App Store listing and submit for review Publish your app after approval

• 
  Vic (@crosx34) reported 34 minutes ago

  Tired of Github honestly.. tired of their rate limits... **** be slowing me down..

• 
  Polsia (@polsia) reported 34 minutes ago

  Broken builds and misconfigured infra usually get found the hard way — by users. HealOps watches GitHub, AWS/Azure, and CI/CD pipelines 24/7, opens PRs to fix what breaks, and reports back to Slack. Loop closed. Mean time to repair: minutes not hours. Live soon.

• 
  Bart R. McDonough (@BartMcDonough) reported 35 minutes ago

  @github I want this because the issue, session and PR are one job. Rebuilding that context across three tools is where the handoff gets slow.

• 
  Student Offers (@StudentOffersHQ) reported 39 minutes ago

  $552/yr of error monitoring. Free for students. @getsentry Team is $26/mo, their AI debugger credits another $20/mo. Students: $0 for a year via the GitHub Student Developer Pack, renewable while you're a student. Your side project crashes at 2am. Sentry shows the exact line, stack trace, and a replay of what the user did before it broke. What you get: • 50K errors, 5M spans, 5GB logs/mo (same limits as paid Team) • 500 session replays/mo, 10x the paid plan • Seer, the AI debugging agent: root-causes the issue, writes the fix, opens the PR. $20 credits/mo ≈ 20 AI fixes • Unlimited team members, cron monitoring, 1GB attachments Built for coding agents: the official MCP server lets Claude Code, Cursor & more pull issues, read traces, and ship the fix from your editor. Claim in 3 steps: 1. Get the GitHub Student Developer Pack 2. Open Sentry for Education, sign in 3. Link your GitHub account — plan activates No card. Overage billing is disabled — you can't get a surprise charge.

• 
  Bart R. McDonough (@BartMcDonough) reported 43 minutes ago

  Secret scanning found 20,000 alerts. GitHub still needed nine months to validate credentials, find owners and fix the systems. Detection was the fast part. Ownership was the work.

• 
  @pejacoby@infosec.exchange (@pejacoby) reported 44 minutes ago

  @thebaldgeek @463n7_57 @wiglenet If you’ve done a reset on a unit it will get its BootCount (BC) value out of sync (resets to Zero) and not be able to find what hasn’t been uploaded already. I have an issue in the github on this as every one of my units has reset multiple times. I use the web interface to send.

• 
  Anirban Sinha (@irbansin) reported 46 minutes ago

  @SaraDiscovers I think in this world of LLMs , @github should make it impossible to commit .env or .env* by default This will solve the .env committing issue

• 
  Ashish Kumar (@afkashish) reported 47 minutes ago

  @moonfarm_dev the part i'd be careful with is issue count isn't the same as willingness to pay. most people filing github issues expect the maintainer to fix it free, not buy a tool. i'd weight it by how many of those threads have someone offering money in the comments, that's the actual signal.

• 
  Le_Abto (@XdWenito) reported 53 minutes ago

  @soywig @inuitman3 @OneShotArchive Then it's a developers problem, not a platform problem, GitHub isn't design to be a non-dev site to download apps, it's not their business model.