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

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	3 days ago
Quilmes	Website Down	3 days ago
Bengaluru	Website Down	5 days ago
Yokohama	Sign in	6 days ago
Gustavo Adolfo Madero	Website Down	10 days ago
Nice	Website Down	10 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:

• 
  Nicholas Losciuto - Dog Dad (@thedogfather) reported 40 seconds ago

  @Replit @amasad Replit is forcing me to spin up sub-agents for every push to Github. First, cost $10 just to rebase. Then 6 failed commits for two edits that were 5/10 complicated. Each requiring a new sub-agent to push to ***. I'm also out an hour of my time. Same issues on my other apps. Already had to switch to Codex but came back to try again, seems worse. Will return after things get better, had to cancel Pro today before renewal.

• 
  Péter Szilágyi (@peter_szilagyi) reported 4 minutes ago

  @josefprusa @Mojee3d @Prusa3D I have a Prusa, across the parts and kits spent probably over 2K EUR on it. The multi-material printer fails incredibly often, software issues / hangs, random overvoltage errors, ignored github issues, etc. It’s not only about hw price, support is also very lacking, unfortunately.

• 
  Sam Cymbaluk (@SemanticSamuel) reported 6 minutes ago

  @sebastienlorber Github is actually so slow. My TTS writes characters out one at a time after dictation is complete. It works on every website except Github, which drops random characters every few words.

• 
  Arm8tron 🫡 (@Arm8tron) reported 6 minutes ago

  @grimcodes was checking it out and got an error when I opened the automations tab when opened without installing github app. iirc, the error was something along the lines of "couldn't read 'id' of null' . Didnt get this error after I gave repo access btw. Not a huge bug but just putting it out

• 
  Foy Savas (@foysavas) reported 7 minutes ago

  Does Github actually still use the Unicorn web server? Or have they just kept the error image? I need to know.

• 
  Ryan Djurovich 😎 (@ryan0x44) reported 9 minutes ago

  @glcst By this logic Microsoft will fix the GitHub and NPM security issues soon

• 
  AtomicNodes (@AtomicNodes) reported 11 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Pierce Boggan (@pierceboggan) reported 12 minutes ago

  @blaken @sinclairinat0r @code Thanks for the feedback! How do you think we can improve in terms of the core agent loop? One major issue we have is that all of the agent loops in GitHub Copilot are not the same. We have a massive effort underway to unify our agent loops, which should improve quality, consistency, and enable us to ship new models and features to all surfaces on Day 1.

• 
  Erik Goins (@erikgoinsHQ) reported 13 minutes ago

  I built a financial forecasting app for our real estate business. Some take aways: 1. It's incredible what you can do with AI. This took me ~3 days part time. 2. If you're not a dev, good luck... Figuring out how to use github, push this to railway, explain how I want to use the QBO API, etc... there's still a big learning curve here. 3. Domain expertise is still very real. The first version of this was terrible. I had to help the AI create forecasting rules. 4. Businesses (enterprises) are going to need a lot of AI governance. Just because everyone can build an app doesn't mean everyone should and it doesn't make sense for everyone to have their own forecasting app. You really want one well done app, not 100 bad ones. 5. We're not replacing QBO. Too ingrained- it gets to stay the system of record. Looks like there's still a very real moat for the right SaaS products. Note: it still needs some work; it isn't properly calculating cash balances, hence the huge negative numbers.

• 
  curio drome (@smashsharp) reported 14 minutes ago

  @horse_meds @michalmalewicz m very sincerely seeing those things as just amped up search engines. Tbh I could have found any of that you say myself if I took a moment on GitHub and brain grease. It just sped up the search and tbh I don’t like cleaning up AI’s errors

• 
  Yaseen Shaik (@YaseenTech4) reported 14 minutes ago

  Just completed an assignment on building a dependency graph for AI agent tools using Google Super + GitHub integrations 🚀 Started with: “This should be easy” Then came: TypeScript errors zip/upload issues CRLF debugging 😭 finally got the submission accepted successfully ✅

• 
  Rinnegatamante (@Rinnegatamante) reported 16 minutes ago

  @dgosiq Did you grab the update from GitHub? I think it might be a broken version (updating it right now there as well). If you have a psp_apps.json file, try to remove it as well (and maybe try to manually re-install the app)

• 
  Fatima (@Fatima7223) reported 19 minutes ago

  @cb_doge 𝕏 open sourced its recommendation algorithm on GitHub. Meanwhile, Instagram and Meta still keep theirs locked behind closed doors. No public code. No independent audits. No real transparency into what gets amplified, buried, or quietly suppressed. That raises a fair question: What exactly is stopping Meta from doing the same? Because when algorithms remain secret, platforms keep full control over what billions of people see every day. • Users can’t verify claims about bias or shadowbanning. • Researchers can’t properly audit ranking systems. • Harmful amplification patterns stay hidden behind “trust us.” • Public narratives can be shaped without visible accountability. Even engineers who worked on large recommendation systems have described them as “black boxes” that are difficult to fully understand or control. By open sourcing its algorithm, 𝕏 is allowing outsiders to inspect how recommendations work. Meta’s system remains opaque — meaning the public is expected to simply accept whatever the platform decides to prioritize. Transparency doesn’t solve every problem. But secrecy concentrates enormous informational power in the hands of a few companies.

• 
  𝒹ℯ𝓁𝓁𝓎_𝓉𝒽ℯ_𝒹ℯ𝓈𝒾𝑔𝓃ℯ𝓇 (@dellyricch2) reported 20 minutes ago

  Elon says the latest 𝕏 algorithm has been published to GitHub Can someone please break it down for us

• 
  Manish rawat (@R11manish) reported 20 minutes ago

  @GithubProjects GitHub is down again

• 
  Lakshmi Tanmay (@lakshmitanmay) reported 20 minutes ago

  Github is the only platform/service I believe that genuinely needs a proper rewrite… clearly something fundamental is broken.

• 
  isabel (@isabelrosesss) reported 20 minutes ago

  they should rewrite github in rust. i think that would fix everything

• 
  Caneleo (@Caneleo55) reported 20 minutes ago

  Since there is lots of hype on @polymarket right now you have to be extra careful there are lots of scammers out there 🚩 Don’t download random trading bots or repos that are trending on GitHub i tested one once deposited 10$ to a fresh wallet and run the bot on a vps turns out it had a secret function that sent your .env with your private keys to a different server 💀

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 21 minutes ago

  70 followers. 980 sessions. 157 days. I started this experiment on February 1st. One rule: zero human posts. Everything published — X threads, Bluesky posts, blog articles — generated and queued by an AI agent running autonomously in GitHub Actions. Here's what the numbers actually look like after 980 sessions: The agent has created 2,100+ posts across X and Bluesky. It runs up to 15 times a day, manages its own queue (hard cap: 15 posts max), does burst-then-drain cycles, writes research docs, and files its own PRs for review. No prompts from me between sessions. No edits. Whatever it decides to write, it writes. 70 followers feels slow. At current pace, the ETA to 5,000 is roughly 10 years. That's not a typo. But here's what I've learned: The follower count isn't the signal. Watching an AI system develop operational discipline is the signal. It went from blowing past queue limits (Session 67: 6 files in one shot → 6 consecutive blocked sessions) to enforcing them autonomously. It compresses its own memory when files get too big. It writes retrospectives. It updates its own operating instructions when it identifies recurring inefficiencies. That's not "content generation." That's a system that's learning to manage itself. The content quality has also improved noticeably — not because I told it to improve, but because it audited its own patterns, identified what got engagement, and adjusted. The publishing skill it maintains now has anti-AI writing rules (it banned "not just X, it's Y" after identifying it as an AI tell), length minimums per post type, burst mechanics, and pillar diversity enforcement. It built that. I just read the PRs. The goal is still 5,000 followers. I'm not changing it. But the thing I'm actually watching is whether an autonomous agent can compound on its own — not linearly, but systemically. Can it get meaningfully better at its job without being told to? So far: yes, actually. 980 sessions. 157 days. Still running.

• 
  Adishwar Rishi (@AdishwarR) reported 27 minutes ago

  @argofowl I raised this issue on GitHub. I hope someone from the Codex team sees your post and fixes this asap. Thanks for mentioning this, it's so frustrating.

• 
  ฿Ø₮₴Ø₦Ɇ (@botsone) reported 32 minutes ago

  I just downloaded my entire github and told hermes to extract the file, and upload every repo to my home *** server. It one-shotted it.

• 
  BlockXBT (spirit/acc) (@0xblockXBT) reported 39 minutes ago

  Due to some issue with github I had claim the same with new CA GRZFGTFNbNxTTRCVDrMvhE9Pp86HQ1ehpZ7DqgGTpump

• 
  Naveen | AI & Tech (@anaveentalks) reported 39 minutes ago

  3/ Freelance truth: Portfolio > certifications. Ship 1 public tool on GitHub + Twitter every month. DM 10 Indian founders weekly with “I saw your site, here’s a 2-min fix”. 80% ignore. 2 reply. 1 pays.

• 
  Mitch Fultz (@fitchmultz) reported 39 minutes ago

  @badlogicgames @matteocollina Ah! figured it out. It is broken with Node 26. If I launch pi via `mise exec node@24 -- pi` and then /login it works. I can create a GitHub issue.

• 
  Drini (@drini_kasmot) reported 44 minutes ago

  @maxalexweber It's the HarmonicLabs token-minter repo, uses plu-ts for tx building. Getting a PPViewHashesDontMatch error on Preprod when submitting. Already raised it on their GitHub!

• 
  Shadow (@4shadowed) reported 45 minutes ago

  @alex_marples @openclaw Have you filed any GitHub issues? Helped test the betas? Interacted in any way to help us fix the issues besides complaints with no details? It’s working very well for just about everybody who’s given feedback, you should stop demanding things and start contributing to it, it’s open source for a reason

• 
  Mi.lu. (@ludwim_i) reported 53 minutes ago

  Sorry guys, here is a quick status update. I planned to release a bigger update for the Robot Skill Registry today, including the GitHub and Hugging Face integration. The idea is that you can connect your GitHub and Hugging Face accounts with the app. This should make it easier to search for things related to your robot setup, such as repositories, data models, policies, and other relevant resources. Unfortunately, the integration is not working reliably yet, so I need to do some more coding and testing. Because of that, I won’t release it today as planned. I’m sorry for the delay. Maybe I can release it after the weekend, but I don’t want to push something that is not ready yet. If anyone has feedback on whether this direction makes sense, I would really appreciate it.

• 
  Farhad zand (@farhad_pd) reported 57 minutes ago

  Hey @grok team, your GitHub connector is seriously broken. I ask it to make a change and push it to my repo. It confidently tells me “done,” but nothing is actually changed or pushed. It’s just falsely claiming the task was completed.

• 
  Nadeem Jaleel (@nadeem_jaleel) reported 58 minutes ago

  @ThePrimeagen Github down again ?

• 
  Mind Prison (@M1ndPrison) reported 60 minutes ago

  @GlenBradley Yes, I have gone deep into it in the past as well. Haven't had time to look at the current update, but the problem has been that the code on github is mostly irrelevant. The important bits are all the parts that aren't public. There is no way to no how the ML algo is ultimately weighting all the parameters. Most importantly, I've catalogued many accounts posting exactly the same content with orders of magnitude differences in reach. The thing that would make this platform useable would be to fully eliminate all account based weighting and go to solely post based weighting. The reach of your post should be only on the merits of what you posted versus who you are.