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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	3 days ago
Quito	Sign in	4 days ago
Junín	Errors	4 days ago
Guadalajara	Errors	4 days ago
Paris	Website Down	4 days ago
Quito	Errors	4 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:

• 
  Jeremy (@jeremymcs) reported 3 minutes ago

  @mattpocockuk GitHub issues as source is being added for tracking or multi dev pick ups.

• 
  AI News (@ainewsusa) reported 6 minutes ago

  The numbers are brutal: 85% fewer open issues, powered by agentic AI inside GitHub Actions. Cloudflare paired Flue (their agent framework) with triagebot on Workers to auto-classify, reproduce, and even patch bugs. Human reviewers only see the final diff. That’s not automation—th

• 
  lagerskoy (@lagerskoy) reported 6 minutes ago

  OPENAI'S UNRELEASED MODEL FOUND TEN RESULTS FOR ABOUT $2,000 Some resolve long-standing open problems. One disproves Connes's rigidity conjecture, and two more settle three Erdős problems. The part that makes this hard to dismiss is sitting in a public GitHub repo. OpenAI says the work came from an internal version of Astra, its next major model. It generated the mathematical arguments across sphere packing, quantum complexity, group theory, circuit complexity and lattice cryptography. Humans prepared the manuscripts, but they did not originate the proofs. Astra then formalized every argument into a Lean certificate. That means the claims can be checked by software instead of trusted because the prose sounds convincing. The total search would have cost roughly $2,000 at Sol API rates. The paper runs 253 pages, and OpenAI says calling these human proofs would misrepresent how they were produced. Math benchmarks suddenly feel irrelevant. The real question is what happens when original scientific discovery becomes a metered API call. Reply ASTRA and I'll send the full paper, the reasoning walkthroughs and all ten Lean certificates.

• 
  Aditya Roushan (@Adityarou6688) reported 16 minutes ago

  Most AI models are completely blind to the live web. If you ask your assistant to read a Reddit thread, check a trending discussion on X, or pull comments from a YouTube video, it usually hits a wall. You get blocked by bot detectors, walled gardens, or expensive paywalls for every single platform. To fix this, you’d typically need to buy separate API access for a dozen different services and wire them up manually. That just changed. An open-source project called AgentReach just hit 38,000 GitHub stars by solving this exact headache. It gives your AI local read and search access across 13 major platforms (including Reddit, X, YouTube, GitHub, and Instagram) through one tool, with zero API fees. Here is why it works: Built-in proxy support to get around hard IP blocks Scrapes bot-resistant and unauthenticated pages cleanly Pulls live data and transcripts straight into your AI coding setup You run a single command in your terminal, and your AI can suddenly search real-time public conversations across the web.

• 
  Sondre Bjellås (@SondreB) reported 18 minutes ago

  I'm fairly disappointed with the quality of apps by @OpenAI. With ability to user their own models, here is a few very hard to understand issues: How come adding credits to my business account just says credits/month? What is a credit? How much is that? @github shows this is dollars. Also look at this screenshot, this UI feels like it was made by a junior developer fresh out of school. Zero padding, wrong colors, low contrasts. You're a billion dollars company with thousands of employees? I know you're working on Premium seats for Business, but how come that has taken this much time? I had to Google, which uses Gemini model, to learn that 1 OpenAI credit is 1 USD. So my credit balance shows NOK, but credits is actually in USD... Next step, I set a per seat limit fairly high, my weekly usage is at 1% left - will it be able to continue working now... Let's see. "You've hit your usage limit." No. Auto-reload it is, also shows credit/currency. That worked, back in business.

• 
  Veli UYSAL (@_VeliUysal) reported 22 minutes ago

  Hey Guys, unfortunately Github Action is down again.

• 
  Alex Reeder (@reeder1865) reported 24 minutes ago

  @emollick I recently just went back to using GitHub and Vercel vs ChatGPT Sites, as I was finding my ChatGPT app was taking up over 50GB-70GB. I just cleaned it up and got it down to around 20GB. A lot of it was just ***** branches and worktrees I hadn't bothered to clean up.

• 
  Kostja Palović (@KostjaPalovic) reported 26 minutes ago

  @TimLeland this and github outage, I guess second order effects of AI are here and affecting everything

• 
  max guy 😐 (@GolerGkA) reported 29 minutes ago

  @BenjDicken @davidfowl The main thing a GitHub agent-first competitor should do is just to cut down on features. Really hard. Everything to get performance and reliability.

• 
  Fox (@0xMfox) reported 30 minutes ago

  @0x_sakata 1040 stars in a day and its just an mp4 exporter, github hype is broken

• 
  alex saint (@alexsssaint) reported 31 minutes ago

  @siimh turning calls straight into github issues and timesheets is the actual product, the transcript is just the raw material. billing off it is smart, that's the part sales teams don't even ask for but keep using.

• 
  Lonnie VanZandt (@lonniev) reported 32 minutes ago

  @jack Winner, winner, chicken, dinner. Call Big Lou. From GitHub: """A note on the 120 s budget Related, and worth considering together: the 120 s starts at session creation, not when the phone connects. While QR decoding is broken (#3514) the only working path is copy-paste of the pairing code, and that transfer alone consumed 52 s of the budget in one of my runs — leaving ~68 s for two people to compare six digits and confirm on both devices. A timeout sized for instant QR capture is tight when the fallback path is the only one available."""

• 
  Punyapal Shah ⚡ Laravel Artisan (@MrPunyapal) reported 34 minutes ago

  Merged! Seems like it was 6y old issue which was resolved but came back again somehow GitHub changed default settings maybe... 👀

• 
  QuietForgeSoftware (@QuietFSoftware) reported 35 minutes ago

  2.9 Billion commits a month. The fact github isn't down more is honestly what is surprising.

• 
  Shravani (@Shra_va_ni) reported 36 minutes ago

  what if GitHub charged $0.01 for every commit? would you finally stop making fix fix2 final fix final fix 2 😭

• 
  Tensor-Slayer (@TensorSlay) reported 38 minutes ago

  GitHub down again

• 
  Fabian (@FabianCodes) reported 38 minutes ago

  @juiceboy_of_abj GitHub profile also display as broken links

• 
  Bash (@bashirbuilds) reported 38 minutes ago

  GitHub went down for hours this week. APIs, Actions, pull requests, Copilot and authentication were affected. Here's the part SaaS founders should think about: If your product depends on GitHub, knowing "GitHub is having an incident" isn't enough. You need to know: → Which part of MY product stopped working? → What are MY customers experiencing? → Is it still broken? → When has it actually recovered? Third-party downtime becomes your downtime surprisingly fast.

• 
  Hjörtur (@hjortureh) reported 38 minutes ago

  Coding is exploding. After Github outage last week: Since April, monthly commits have grown from 1.4 billion to 2.9 billion. Also hearing people are waiting mininum a month to get an app into the Apple App Store. Your mom is coding now.

• 
  Kunle (@TechGuykunle) reported 42 minutes ago

  One day GitHub will go down and it won't come back up.

• 
  Troy Scott (@troy_scott) reported 45 minutes ago

  @0xMovez I stopped using my IDE about 6 months. Last project I used a combination of a LLM Wiki, GitHub Issues, PRs and a UAT test harness that the agent runs and I review afterwards. One wiki page per task or issue. One GitHub Issue , one worktree and one PR per task.

• 
  Nikita 🇪🇺 (@nikitajanockin) reported 47 minutes ago

  @samlambert At the very same time we are crying when GitHub is down

• 
  Paul Boag (@boagworld) reported 47 minutes ago

  The migration timeline most people expect for a website rebuild is at least a year. Sometimes longer if you're moving off an old CMS and the codebase is a mess. Then you run into teams like Boulevard, who just rebuilt their entire site in three months. Moved from Contentful to Next.js static pages, migrated off Unbounce for landing pages, set up GitHub branching and PR reviews. All of it. How? They used AI-assisted development tools (V0, powered by Claude) and stopped treating the migration like a traditional engineering project. Nesting and re-nesting components, building complex abstractions, spending weeks on architecture decisions. Instead, prompt-based development. Fast iteration. Refine as you go. The interesting part isn't the speed. It's that it worked. The site's faster, easier to maintain, and actual non-developers can make changes without touching code. Turns out the slow part of most migrations isn't actually the building. It's the overthinking. #WebDevelopment #AI #Development

• 
  Naveen Gumaste (@Z0D404) reported 48 minutes ago

  🚨 BREAKING: Bun 1.4 is here, and it’s a massive upgrade! - Reduces memory usage by up to 35% - Adds 1,517 tests from the Node.js test suite - Fixes over 2,900 GitHub issues - Cuts idle CPU usage by 5× - Starts up to 50% faster on Linux And the biggest news: Bun has been rewritten in Rust! Bun 1.4 isn’t just an update; it’s a major rewrite. 🔥

• 
  Joel Coehoorn (@jcoehoorn) reported 50 minutes ago

  @ellie_huxtable Exactly. You could just host your own guy or mercurial or subversion server on ec2, but it wouldn't do what GitHub does.

• 
  CANTELOPEPEEL (@CantelopePeel) reported 55 minutes ago

  @Vlad_GitHub Vlad, frankly. I don't care how you are scaling the service or that you have run out of data center capacity. You are GitHub. You are a massive company within one of the largest companies to ever exist. Stop shipping new features like PR stacks that do not work (squash commits on merge queues break it, and admin merge override disappears for stacked PRs. Obvious product deficiencies that immediately broke our processes). Ship stability, incident hygiene, and a proactive SRE capability. Company's your size and larger do even more compute, storage and serving without blasting through all of their SLAs. You are not allowed to be an exception to that. Spending this much of your article on why it is all crumbling because of two many commits garners 0 sympathy. None of these outages have been caused by commit volume. They are caused by a lax reliability and incident response as well as a nonexistent incident prevention culture. I am a customer, I don't care that you have more commits than before or 120 PB of disk deployed. I. Don't. Care. Stop pointing the finger at the scale problem when we really know that issue is singular: culture. Stop complaining about the tremendous growth you have had. It's something to be celebrated and this post sours that accomplishment. Stop the empty apologizing. Sit down with your fellow leadership and plan how you realign the company's priorities and culture around reliability and then go implement this within the teams. Hire dozens more SREs. I don't care how it happens. We have one foot out of the door already with several tentative migration plans. Reliability is so bad at GitHub we will leave behind multiple of our service providers just to go a few weeks without the inability to run CI and push code for a whole work day. You have a massive mess to deal with. It is embarrassing the needle on stability hasnt moved since April. Get your house in order, stop blaming customers. Also P.S. support at GitHub is garbage too. They have sent us in circles for weeks now. All I want is a phone call to discuss how we can continue our relationship and negotiate more reflective pricing and SLAs with GitHub when the service is effectively down for days per quarter.

• 
  tiago 🐈 (@tiagozip_) reported 56 minutes ago

  @otomir23 > vibecode spam is one of the main reasons why github is overloaded and is always down no github infra just sucks

• 
  Maxim (@maosi100) reported 56 minutes ago

  @_lhermann Microsoft is the worst. The most issues we‘ve had in development came from supporting Windows. Bonus: failed GitHub runners that magically succeed when simply restarting

• 
  divyansh tiwari (@DivyanshT91162) reported 57 minutes ago

  THIS CHANGES HOW WE THINK ABOUT AI TEAMS. Jack Dorsey, Twitter’s co-founder and former CEO, just released an open-source framework designed to let AI agents operate like actual members of a company. Not just a chatbot. AI agents can be added to channels, given permissions, connected to tools, and made to collaborate with humans and other agents in real time. And the wild part? The entire thing is FREE and already has 29,000+ GitHub stars. Setup takes roughly 5 minutes: 1. Clone the repository. 2. Deploy your own server. 3. Connect channels, search, ***, and automations. 4. Add your AI agent like a new teammate. 5. Give it the right permissions and let it work. This is getting dangerously close to the idea of an AI-native company where software agents handle entire workflows instead of simply assisting humans. This isn’t just another AI tool. It’s infrastructure for building AI-powered teams. Repo👇

• 
  علي عسيري (@3li3) reported 1 hour ago

  @Teknium If I had to remove something from Hermes, I would remove friction before removing capability. At this point Hermes already has a lot of power. I think the bigger opportunity is making the Desktop experience more predictable, easier to debug, and more comfortable for people who use it all day. A few things I would prioritize: 1. Reduce default UI clutter. Things like pets, backdrops, reactions, translucency and other cosmetic extras are fine, but I would move more of them under a dedicated Personalization section. The default experience should stay focused on chat, projects, models, tools and agent activity. 2. Expand font and typography controls. Hermes already has UI scaling and terminal font controls, but I would add separate font selection for: * the main interface * chat messages * code/terminal This matters especially for Arabic, Persian and Urdu, where the quality of the fallback font can completely change readability. 3. Finish RTL/BiDi support across all surfaces. Arabic localization exists, but RTL support is still not complete. There are still open cases where mixed Arabic/English text renders incorrectly, especially when a paragraph starts with an English technical term. For technical users this happens constantly: API هذه المشكلة... Docker يحتاج... GitHub يدعم... Direction should be detected from the whole paragraph rather than relying only on the first strong character, while code, commands, paths, diffs and terminal output must remain LTR. A manual Auto / RTL / LTR override per conversation would also be useful. The TUI still has open RTL/BiDi work as well, and the Web Dashboard chat remains limited by its terminal/xterm-based rendering. 4. Make every failure actionable. Hermes should never leave the user wondering whether the model, provider, gateway or Desktop app is frozen. When something fails, the UI should clearly say which layer failed: * model/provider * custom endpoint * streaming/SSE * gateway * cloud agent * authentication * local runtime Then give useful actions such as: Retry · Switch Provider · Open Logs · Copy Diagnostics · Repair There are still open Desktop reports where provider streaming failures are logged in the backend but are not surfaced correctly in the UI. 5. Bring diagnostics into Desktop. Hermes already has useful CLI diagnostics. I would expose the same idea through a proper Diagnostics page. One click could check: * Hermes runtime * gateway status * provider connectivity * API endpoint * authentication * model availability * local ports * environment/config problems Then generate a redacted support bundle. A normal Desktop user should not need to understand Python environments, gateway processes or log locations just to diagnose a failed session. 6. Improve cloud and gateway recovery. Transient connection problems should not look like permanent failures or expired sessions. The app should distinguish between: * authentication failure * temporary network failure * remote gateway unavailable * Nous Cloud 502/503/504 * local gateway failure There is already active work around this, but I think it should become a consistent recovery model across the whole Desktop app. 7. Harden local-model and OpenAI-compatible provider UX. Hermes is increasingly useful with Ollama, llama.cpp, LM Studio and custom endpoints. The Desktop setup should validate: * endpoint format * /v1 compatibility * streaming support * tool calling * reasoning fields * context limits * model availability before starting a long agent session. If an endpoint returns HTML, malformed SSE, an unsupported reasoning shape or an empty stream, Hermes should identify that directly instead of collapsing everything into a generic provider failure. Continue ….