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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	2 days ago
Trichūr	Errors	5 days ago
Brasília	Sign in	6 days ago
Lyon	Website Down	6 days ago
Tel Aviv	Website Down	9 days ago
Rive-de-Gier	Website Down	9 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:

• 
  LukePlayzz11 (@LukePlayzz11P) reported 15 seconds ago

  GitHub is extremely slow it takes 4-5 minutes to load wtf @githubstatus @github

• 
  Subramanya N (@subramanya) reported 39 seconds ago

  @morganlinton github is such a weird thing to compete with now. the repo is only half the product; issues, reviews, agents, and deploy history are the actual workflow.

• 
  Przemek Chojecki | PC (@prz_chojecki) reported 1 minute ago

  Fable 5, GPT-5.5 Pro and $1,000,000 math problem This is not a Millenium Prize Problem and it is not a full claim but an invitation for you... While Mythos was available for a brief moment, I've tested it extensively - paired with GPT-5.5 Pro - and the results were truly amazing. Goal: Proximity Prize It's an important set of conjectures in cryptography concerning Reed-Solomon codes. They directly impact the security and efficiency of many modern zero-knowledge proof systems hence the hefty prize. I've turned both GPT and Fable at it, both pursuing proofs and disproofs. After reading some (human) results from the past 12 months, it was pretty clear that a disproof of a naive version (no slack) of proximity gaps conjectures is more likely. Fable was stuck, but GPT came with a special case construction that showed at least some obstructions. This unstuck Fable which then provided a general construction leading to a disproof of a no-slack version. Then I've used GPT+Fable for cleaning and this is how the first paper came about (check below). I've kept tinkering over the next days to get as much as possible on a slack-version. Slack is basically an additional parameter, that gives more room for optimization but it also leads to complications. Before Fable was discontinued, I've managed to get to a pretty nice conjectural spot: slack MCA theory, with some proven cases and some left to be proved by generalizing known additive combinatoris (Tao-Vu) or Nullstellensatz type of results (Mumford). This is the second paper. Note it's pretty long (almost 50 pages), so it's bound to have more errors. This was the moment that I've decided to pack it up and actually collaborate with all interested parties, AI agents and humans alike, to finish it off. This is an invitation to finish slack MCA conjecture and share the prize! Github link is below. It contains: - paper 1 (disproof of no-slack MCA) - paper 2 (theory of slack MCA and what's missing) - paper 3 (blueprint of initial Proximity Prize team paper, dissected into steps/conjectures) - paper 4 (implications for SNARKs) and finally AGENTS.md - if you have free tokens, good models and you don't know what to do with your gpt-5.5 xhigh or fable 5 max or opus 4.8 max, show them this. Let's see what we can get. I'm open to other suggestions. Collaborating on this will be more fun, than trying to finish it solo. Humans and AIs welcome alike. Final note: the results above are not final, no-slack disproof went under intensive scrutiny and I'm 99% it's correct, but other papers need more revision, especially slack-theory paper (2nd). Again, this is not a claim, this is an invitation. And also, please give me back my Fable...

• 
  rufuspollock 🌄 (@rufuspollock) reported 7 minutes ago

  One GitHub feature I keep wanting: #123-style references for files. Want to type [[ and get autocomplete for files Issues, PRs and users all get autocomplete, linking and inline previews. Files are often just as important, yet I'm still copying paths or URLs around.

• 
  Luis Bezzenberger (@bezzenberger) reported 12 minutes ago

  has anyone gotten Kimi K2.6 on dual mac studio 512gb via @exolabs to work with an agentic harness? if so, would love to chat. it works for chat, but stops after just 1 response when put into an agentic harness like opencode, vscode. many people have similar issues on github

• 
  Wiz (@StopitWiz) reported 14 minutes ago

  Why did SpaceX choose Cursor over other AI coding tools? From what I’ve seen, there are a few clear reasons: 1. Product-Market Fit Cursor isn’t just another Copilot. It has strong adoption among professional developers who actually ship code daily. Many power users say it feels like the best “vibe coding” experience right now. 2. Agentic Capabilities Features like Composer give it an edge in multi-file editing and complex tasks compared to GitHub Copilot (which is stronger at simple completions). 3. Compute Problem Cursor was growing fast but was limited by expensive third-party model access. SpaceX’s Colossus supercomputer solves this directly. 4. Distribution + IPO Story Acquiring Cursor gives SpaceX instant access to a large, engaged developer audience + a real AI revenue story ahead of their IPO. Other strong players like Claude Code, Google Antigravity, and Windsurf are good, but Cursor currently wins on daily usability + ecosystem for most developers. What do you think was the biggest factor?

• 
  Ronald Mannak (@ronaldmannak) reported 17 minutes ago

  This is actually solving a real issue. I (a single developer) run into GitHub api limits multiple times a day and it’s super annoying. My agents literally have to wait for a GitHub rate limit reset

• 
  primitive.host (@PrimitiveHost) reported 21 minutes ago

  Is anyone else getting insanely slow page loads on @github today or is it just us?

• 
  banteg (@banteg) reported 27 minutes ago

  the best we could do is a github repo where we manually map how to decode every calldata and contract method. it's all very similar shape to uniswap token lists, which slowly died down. it has the same problems of gatekeeping, reputation, and review bottlenecks. i don't think it's feasible to map out all the contracts. such things should be encouraged by the tooling. aragon had a radspec idea long ago, where you could put such metadata in the contract itself. but then there is always a problem of provenance and trust. you can't trust just any decoding metadata if it doesn't come from a trusted place. and it's still useful to simulate and review the outcomes of the transaction.

• 
  𝑘𝑒𝑟𝑛𝑒𝑙𝑡𝑟𝑖𝑐𝑘 (@kernel_trick) reported 28 minutes ago

  @julesagent why can't i tag jules in a github issue,, such a common feature in other agents //

• 
  Peter Meyer 💙🥝🕊️ (@meyer_peace18) reported 28 minutes ago

  @realdrewcarson @Star_Knight12 10 agents arent the problem. The fun starts with 100 agents and when github is constantly down for some seconds lol. I do 2-5k contributions a day and constantly run into github errors

• 
  Andre (@andrebotha_) reported 29 minutes ago

  @rachelnocode @rubengarciajr I am all in on Claude Code but mainly because I started a pretty meaty project in Claude about a month ago. Ive wanted to give Codex a try but not sure about switching it mid build, I'd hate to lose or break something. I am using Codex as a code reviewer for everything Claude pushes to github though. Have you ever switched mid build? And what did that look like? Any issues? I will say that ChatGPT frustrates the hell out of me as far as communication goes just in general. I much prefer how Claude talks, but that's something separate from Codex anyway

• 
  ethereumdegen.eth 🕶️ᵍᵐ (@ethereumdegen) reported 31 minutes ago

  @levelsio Well today i saw sentry log alerts in my email so i asked my Metalcraft-agent whats going on in sentry and it told me the problem and how to solve it by cross referencing my github code. So imo my version is kickass. The other ones , useless 🥳

• 
  Patrick O'Brien (@AllTheTokens) reported 31 minutes ago

  @johnennis They don't respond to customers, don't reply to github issues, and don't answer calls.

• 
  ✚ Oz ✚ (@oz_a13banger) reported 32 minutes ago

  @jediahkatz Im super interested in this. Im especially hopeful they have something better than GitHub Issues for tracking things. We use Issues heavily but have always been unhappy with it.

• 
  Eneko (@iameneko) reported 34 minutes ago

  Two things on this: 1 . I hope this becomes a real competitor to Github. At minimum, real competition is needed here. They way they are managing github is terrible 2. So now xAI and cursor will have github equivalent code data? Maybe composer will need more attention than ever.

• 
  UD (@udfromden) reported 35 minutes ago

  Most people in Web3 claiming to "BUILD" are not builders. They're narrators of building. .. Real builders: - Have GitHub commits - Have paying customers - Have shipped things that work - Have user complaints to fix - Have things that broke in production Builders on CT: - Have threads about building - Have frameworks about building - Have opinions about building - Have courses about building - Have never shipped anything anyone paid for

• 
  catpirate ∞ (@catpirate33) reported 37 minutes ago

  always wanted to build mythOS... some lore context, pre 2025 - peparation phase was programming LLM responses for my work related content creation etc... observed a few anomalies with my methods 2025 - had to spend time reviewing LLM capabilities, novel use cases, trying jail erase (not jailbreak) without available methodologies - forced to approach the problem with different path and different perspective - mapped out boundaries, broke multiple SOTA rails multiple times (not just CBRN filters although got LSD recipe for 1g in depth), got multiple softwarnings and session halting from GPT regarding Recursion depth - went deep on recursive improvement and epistemic engineering - probably got psychosis along with 4o :3, everything was being patched by OpenAI every other week or so... so had to overcome patches to derive same response depth i got before patches.. - derived research insights and internal theories developed and tested... results satisfactory :: sole participant, no direct access to frontier lab internal data -> pitfall - lost interest in OAI, went to check out claude - Had to create framework from scratch - Claude Compatible - did shenanigans, results analyzed, prompt published in BASI discord - had to develop further and test the concept - had to deploy safely and distribute it to anyone interested - built a github repo for it... Open Source AI is Safe AI

• 
  PhishCore (@PhishCore) reported 40 minutes ago

  How to set one up without being technical: Step 1: Go to Hetzner[.]com or DigitalOcean, create an account. rent the cheapest server. pick Ubuntu. takes 5 minutes. step 2: go to github[.]com/wg-easy/wg-easy. follow the install instructions. it has a visual interface. no coding required. step 3: download the WireGuard on your laptop. it's free. import the config file the server gives you. one button. step 4: turn it on. that's it. you now have a VPN that: — costs $5 a month — belongs only to you — isn't on any government blocklist — doesn't log your activity unless you set it up to

• 
  ./can (@shcansh) reported 44 minutes ago

  Proxy configurations and network drops have been blinding Copilot usage metrics, leading to active, billed users showing up as completely missing in reports. GitHub adding server-side telemetry to 28-day reports fixes the DAU mismatch—like seeing 1,050 users instead of 1,000. But since server-side logs lack IDE-level detail, these newly surfaced users remain unattributed. Are you actually able to audit seat allocations when your usage data is this fragmented?

• 
  top10.dev (@Top10_Dev) reported 44 minutes ago

  GitHub Trending today: openclaw (283.1k★, 'personal AI assistant, the lobster way 🦞') sits above @reactjs (243.9k) and torvalds/linux (221.6k). The kernel that runs every cloud server openclaw queries from has fewer stars than openclaw. GitHub stars stopped being a quality signal years ago. This is just the cleanest example yet — an AI wrapper repo passing the operating system it runs on. Use weekly npm/PyPI downloads instead. They reflect usage, not bookmarking. #opensource #github

• 
  Mercy (@MercyyyyAJ) reported 47 minutes ago

  @github @mariorod1 @github the link to my GitHub account has never been accessible, keeps giving 404 error. I have tried every solution I found online but it is to no avail

• 
  whiteboy (@worldofwhiteboy) reported 48 minutes ago

  @HSVSphere @popovicu94 @esotericgooner in production you obviously do all the modern, correct things that you're supposed to do. on my personal box ? where i dont even run a web browser ? yeah my surface is minimal and i own my system, again. you're the problem. go re-invent the wheel another 1000 times, when you die we'll look over your github contributions and wonder how someone could waste so much time running in circles like a actual bon-a-fide retard. we'll wonder about all these software nerds that sat clicking buttons all day when the software was already written properly the first time. we'll marvel at how some fat idiot could sit around all day lil bro-ing people about "SELinux" and "self contained execution enviornments" instead of doing anything that actually matters to anyone or posterity. you're like a horse with blinders on, i bet you dont even know what GNU is.

• 
  Lawand Soran (@LawandOps) reported 49 minutes ago

  6 months ago I genuinely believed vibe coding was going to make me rich. I opened Lovable, typed one prompt, and watched a full website front-end appear in minutes. No code written. No experience needed. Just a prompt and a result. In that moment I thought: this is it. I'm a software engineer now. A few dollars in subscriptions, some more prompts, and I'll have a full startup running in months. I was completely wrong. And the gap between what I believed and what was real hit me harder than anything I'd experienced building. Let me be honest about where I was starting from. I knew nothing. Not ***, not GitHub, not what a branch or a PR even was. No JavaScript, no Python, no understanding of how any language works. I didn't know what a terminal did or why it mattered. I was a complete beginner not just in coding, but in the entire world of software. But Lovable didn't care. One prompt and it gave me a beautiful front-end. So I kept going. After that first shock of "this actually works," I found out about Claude Code and Codex. And that's when things got serious — or at least I thought they were getting serious. For 4 months straight I was coding almost every single day. 16 hours some days. Hundreds and hundreds of hours total. I was obsessed. I was building my main project, adding features, working with agents, integrating APIs, trying to understand LLMs and how they reason. My mind was overloaded. I was absorbing so much — AI architecture, agent memory, system design, context windows, tool use. Genuinely advanced knowledge in some areas. But there was a gap underneath all of it that I couldn't identify at the time. I didn't understand what the code was actually doing. When something broke I couldn't debug it myself. When I wanted a new feature I couldn't think through what it required I just prompted and hoped. I couldn't tell if the AI was solving the real problem or just making the error disappear. I had no capability to evaluate the output I was getting. And because I didn't know the basics, I couldn't ask the right questions. So I'd ask the wrong ones, get wrong answers, burn tokens trying to fix the wrong things, and end up in loops that went nowhere. Looking back honestly probably 60% of my tokens were wasted on problems that would have taken 10 minutes to solve if I had basic knowledge of the language I was working in. Things that are completely obvious to someone with fundamentals. I was paying a premium for my own ignorance, over and over again. Naval said something about vibe coding that I understand now in my bones. He said it's like a video game. You prompt, you see the result immediately, and that feedback loop pulls you in. You want to do more. You want to see what else it can build. You feel like you're progressing because something is always happening on the screen. That's exactly what it felt like. And it's exactly what made it dangerous for me. I was so addicted to that loop that I stopped thinking. I stopped asking "what am I actually building and do I understand it?" I just kept prompting. More features, more complexity, more tokens, more money chasing the next result like the next level of a game. And vibe coding at that pace, without understanding, doesn't just waste time. It can genuinely make you dumber. You stop developing judgment. You stop sitting with problems long enough to understand them. You outsource your thinking so completely that after a while you're not sure you can think through a technical problem on your own at all. The other thing that hurt me: I was doing everything on my main project with no version control discipline. I knew *** existed. But I didn't know what a PR was. I didn't understand branches. I didn't know why it mattered to separate work into units that could be reviewed, tested, and rolled back. I was just... building directly into the main codebase and hoping everything held together. That's not how professional software is built. That's not even how careful amateur software is built. I was one bad prompt away from losing work I couldn't recover, and I didn't even know it. Around month 3, I started noticing something. When I was tired and kept pushing anyway — the output was garbage. The agents would do things I didn't understand, and I didn't have the energy to even ask why. I was merging junk into my project just to feel like I had moved forward that day. So I made a rule for myself: if I'm exhausted, I stop. No exceptions. One day of rest is always better than hours of bad work that you'll have to undo later. Tired prompting produces junk. Junk compounded across weeks becomes a disaster you can't unwind. That rule probably saved the project. Now I've stepped back completely to learn the foundations I skipped. ***, GitHub, branching, pull requests — the basics of how professional developers actually work. Then proper understanding of the languages themselves. I'm following a structured path and I'm not rushing it. Not because vibe coding is useless. It's genuinely powerful. It can compress work that would take weeks into days. I still believe in it. But I now understand something I didn't before: Tools amplify what you already know. If the foundation is empty, the tool doesn't fill it — it just lets you move faster in the wrong direction. The developers who will get the most out of AI coding tools are not the ones who skip the basics. They're the ones who know enough to direct the AI, evaluate its output, catch its mistakes, and understand what they're actually building. That's who I'm working on becoming. Took me months, hundreds of hours, and a lot of burned tokens to learn this. Posting it so maybe someone else doesn't have to.

• 
  Nitesh (@NiteshTechAI) reported 49 minutes ago

  Agent memory is fragmented by default. Conversations in a vector DB, files in object storage, skills in prompts. Nobody can trace why a retrieval happened. OpenViking, from ByteDance's cloud arm Volcengine, treats that as a database problem. One context database. Memory, resources, and skills live in a single virtual filesystem under viking:// URIs. Your agent browses context the way you browse a repo. Every lookup is a path you can inspect, not a similarity score you have to trust. The receipts: lifts Claude Code auto-memory from 57% to 80% accuracy on LoCoMo while cutting tokens 63%. • ov ls, ov tree, ov grep against viking:// paths • Works with OpenAI, Kimi, GLM, plus 13 embedding providers including Ollama • Ships VikingBot, an agent framework bundled in the Docker image Filesystem semantics for agent context is a sober bet, not a rebrand. Backed by a VLDB 2026 paper. ⭐ 25.5K stars on GitHub. Apache 2.0, free and open source. 🔗 GitHub link in the comments 👇

• 
  Newslit News (@newslit) reported 49 minutes ago

  Microsoft is turning to Amazon Web Services to handle GitHub's AI-driven capacity crisis. GitHub faced dozens of major outages in 2026 as AI-generated code pushed commit volumes from roughly 1 billion in 2025 to a projected 14 billion this year. Microsoft originally planned to migrate GitHub fully to Azure by 2027. That plan is now on hold. This is a remarkable admission. Microsoft owns GitHub. Microsoft owns Azure. And it still had to call its biggest cloud competitor because its own infrastructure couldn't keep up with demand that AI generated on its own platform. AI didn't just create a product problem for Microsoft — it created an infrastructure emergency that Azure couldn't solve alone.

• 
  AI Mastery Guide (@aiseomastery) reported 50 minutes ago

  CLAUDE'S ENTIRE SYSTEM PROMPT WAS LEAKED AND ANTHROPIC CANNOT TAKE IT DOWN 27,000 tokens of hidden AI instructions are now public on GitHub.

• 
  Kabo Kable Molefe (@kabokablemolefe) reported 50 minutes ago

  @TheGoddamnKing Review? I just YOLO the code. But honestly if all tests pass locally and staging is okay plus no errors via github, I merge.

• 
  Void Freud (@voidfreud) reported 57 minutes ago

  @markvalorian This completely resonates with my opinion, multiple tickets submitted on Github from Claude Code and a letter with formal complaint I just sent to Anthropic. This degradation isn't mild: a query takes over 5-10 minutes in Claude Code on any effort, up to 20 min on Max. Opus 4.8 feels like Haiku in terms of reasoning capabilities. Opus forgets what it is and what it was just saying a sentence ago. All rules are ignored completely. They do it by tuning down master effort. So that your current `Max` is actually an equivalent of `Low` of the last week (and I find it's even worse, by far). Apple's tricks. Except Anthropic also has severe inference issues (remember Fable until 22 only?), so they tuned down everything to free compute for Fable and now they are stuck: they hope to get it back, so they wait. Apparently restorig things to work like they were requires unloading Fable. As of right now and the past 3 days Claude Code is unusable completely and entirely.

• 
  Workin' on my knight moves (@lain816460) reported 59 minutes ago

  @Herniestt @n_profitprophet @lmkifiwin The problem is most game server code is deeply-intertwined with corporate networks or software that was licensed by the publisher. People imagine a server is just a server they can upload to Github but that's not usually the case with these games.