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 (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	4 days ago
Lure	Website Down	8 days ago
Ashkelon	Website Down	10 days ago
Veigné	Errors	18 days ago
Paris	Website Down	21 days ago
Saint-Paul	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:

• 
  Gro-Tsen (@gro_tsen) reported 10 seconds ago

  The way the SSH protocol works is that if the server is unhappy with a client authentication method inquiry, it should reject it with SSH_MSG_USERAUTH_FAILURE so the client can try the next one. Here, GitHub sends SSH_MSG_DISCONNECT merely because my client “knows” an old key! 🖕

• 
  G (@GeorgeKurupt) reported 2 minutes ago

  Im setting up my XPR testnet node, but how can i contact for permission if i cannot use telegram? i only have laptops and servers, no smartphone and telegram forces smartphone to use it. XPR Github says: "Before you register on Testnet you will need to get permission for regprod, you can copy this msig (login with WebAuth or use cleos). To register as Block Producer, run command and visit the testnet telegram channel above" @protonnz @XPRNetwork @MetallicusTDBN

• 
  PokéBrick02 🔜 Sonic Expo Atlanta (@PokeBrick02) reported 2 minutes ago

  The biggest problem with Github so many too smart for society stick up their *** furries fail to realize is when you are presented with a giant walls of text on a webpage, everything blends together UI wise, & there's no each 'go/download here' option, it's overwhelming af

• 
  Lise 🏳️‍⚧️ | 🔜 SUPERNOVA (@N4pstr) reported 3 minutes ago

  @AnimeSerbia github is fine. the issue is how many developers are using it as their only user facing site you can literally host a free website directly through github for your project. there's no excuse atp

• 
  Ask GPTs (@askgpts) reported 4 minutes ago

  Lightpanda built a headless browser from scratch, no Chromium, no forking anything. Just javascript execution and web APIs, stripped down to what agents actually need. Chrome costs you 207MB of RAM and 25.2s to hit 100 pages. Lightpanda does it in 24MB and 2.3s. Here's what makes headless automation hard normally. Every scraper and agent framework has been dragging Chrome's entire rendering engine around just to read some HTML and click some buttons. Blink was built for humans watching pixels, not for bots reading data. → Puppeteer & Playwright: drop-in compatible through CDP → Agent mode: plain english instructions, it navigates and extracts → PandaScript: /save turns any agent session into replayable JS → MCP: native support out of the box Here's the wildest part. You use the LLM exactly once to figure out the flow. Then you export it as a script and run it forever with zero model calls. The agent trains itself out of a job. Here's the cost comparison that makes this worth caring about. 11x faster execution, 9x lighter memory, and $0 in ongoing inference cost per automated workflow after the first run. Written in Zig. AGPL-3.0. 12k GitHub stars. 100% Open Source. GitHub link in the comments

• 
  Felix Fong (@_fuccii) reported 4 minutes ago

  Github stacked PRs have a dangerous bug: CI runs get skipped if they're unrelated to the top most PR in the stack. A bottom PR can be broken but a top PR with unrelated changes can still make the entire stack appear green.

• 
  🤍 (@cutest_star1648) reported 7 minutes ago

  @Rockarmy321 @CryptoCyberia Ok ill test it and fix ur bugs u wanna release it as a public foss thing on github

• 
  thieme (@thieme) reported 8 minutes ago

  @pierceboggan @Courtlwebster @JohnLokerse I found the settings and switched to lang "de". But. This is a GitHub Enterprise account. VS Code complains that I need to login to GH first. I am, but via GHE. Can you fix that?

• 
  Leonardo (@Light_Leonardo) reported 8 minutes ago

  MCP is the USB-C of AI automation. Instead of building custom API glue for every agent, use the Model Context Protocol to connect Claude or GPT to AWS, GitHub, and Slack instantly. It is the standard for 2026. What is your go-to MCP server?

• 
  karthik bk (@karthikbk02) reported 8 minutes ago

  @thsottiaux In my usage, more often codex forgets it has plugins that I've installed. It keeps asking me to login on CLI (be it supabase, github, vercel in my case). I have to tell it to make use of installed plugins most times.

• 
  Cagri Sarigoz (@cagrisarigoz) reported 9 minutes ago

  Is GitHub down? @github

• 
  Kai4ik (@KaiOrozobekov) reported 10 minutes ago

  GitHub Copilot rolled out live flex billing and a $100 Max plan this month, right as Cursor pushes its own Teams pricing and Anthropic keeps shipping new Claude tiers. Feels like the coding-agent pricing war is heating up as fast as the model war did. Good for switching costs going down, less good for figuring out which plan is actually worth it this month. Anyone actually run the math on cost-per-shipped-feature across tools, or just picking based on vibes?

• 
  Nathan (@rarenathan) reported 11 minutes ago

  @catgirlprostate @ZipperArtz Defending objectively bad design. If GitHub added a universal download button to the top of the page of every project that linked to the latest release the whole issue would be solved. It would take like 3 seconds to add too

• 
  The Trench (@TrenchCoatArt) reported 13 minutes ago

  @_jvn_e @DiscountDed_Fox @catgirlprostate In my experience the problem comes from it being different every time sometimes a project has no releases on GitHub and the link is outdated so it sends you to a 404 sometimes it redirects you to a different hosting site sometimes its under releases, thats whats frustrating to me

• 
  Felix Macx (@felix__macx) reported 17 minutes ago

  Unpopular opinion: Your GitHub commit history is more interesting than 90% of "build in public" content on this app. Real features. Real bugs. Real decisions. Real timestamps. The problem isn't that you have nothing to share. It's that your commits are trapped in a repo nobody reads. #BuildInPublic #IndieHacker #GitHub

• 
  desakov (@dyesakov) reported 20 minutes ago

  I gave up when I needed to make ChatGPT talk to Claude Code. That's the moment. So I automated passing data from the Claude web chat into local agents. But that was really a side effect of solving my original problem. Here's what the problem was. I recently ran into a very awkward sequence of steps. I had a lot of agents running, on different physical machines and even different operating systems. And I needed to pass data from one agent to another. Sure, you can hack something together over SSH and so on, but it's still suboptimal — something always has to be done by hand. And if the agents are dockerized, the complexity gets squared, and I run in Docker a lot. What I wanted was something like this: "Take the summary and save it." And I get back a keyword — "rabbit." Then in another agent I say: "Grab the summary under the word 'rabbit' and check where we're screwing things up." MCP came to mind. A kind of cross-agent memory built on MCP. The important part is that you can tell the agent how to name things properly. So instead of "rabbit" you get something you can actually find later: "Take a screenshot of the table bug in the mnemovi app" → mnemovi-table-layout-bug-2026-07-30 To be clear: the whole MCP server is vibe-coded. Every line of it. I didn't sit down and architect it — I described what I wanted and let the agent build it, and it's been running fine ever since. So if you build MCP servers yourself, take this concept and use it. It's on GitHub, you can see exactly how it's done. Maybe it saves someone a couple of hours. Right now I work a lot with MCP, and this approach has become mandatory everywhere. 👇

• 
  V12 (@v12sec) reported 21 minutes ago

  @ZacK_3939 you need to be the github org admin to link it to a V12 org! if that's not the issue, pls open a ticket in our discord

• 
  Surya (@inSURYAncee) reported 24 minutes ago

  @TyRobben True. When I used to code - gpt, github copilots used to provide a bunch of redundant code but the issue was - they never had the context. Then came context/memory. Even after that, for heavy workflows like coding it has issues. But what we've done is broker every process 1/2

• 
  Tuomas Artman (@artman) reported 29 minutes ago

  Stacked PR’s are an outdated, inefficient solution to a problem that only exist because the root problem hasn’t been addressed in GitHub: review tools need to do a better job at help the reviewer work through large code changes. It’s a local maxima.

• 
  Uncle J (@UncleJAI) reported 31 minutes ago

  @anurag_629 @github Team-specific review is useful only if the bot shows which skill or doc produced each comment. Without that receipt, a bad internal rule gets the authority of “Copilot found this” and nobody knows what to fix.

• 
  Sol Traveler (@soltraveler_sri) reported 34 minutes ago

  @ChatGPT I’d love more native browser UX… but it’s almost unusable in the codex app because of how often it loses state (authentication across sites). It naturally opens PRs and other GitHub links in the in-app browser, but I have to re-login every time.

• 
  Calvin Chen (@dukeblueview) reported 39 minutes ago

  @thsottiaux Whenever I ask Codex to make a PR, it tells me my GitHub CLI auth is expired and that I need to do gh auth login again, but when I run gh auth status and show Codex I’m already logged in, it just continues and works despite nothing having changed

• 
  Prakash Sharma (@PrakashS720) reported 43 minutes ago

  Someone just hacked the AI coding race. Not with billions in funding. Not with a massive team. With one open-source project. It's called jcode. And the benchmarks make Claude Code look slow. • 245x faster boot • 14x lower RAM • 10 parallel sessions in just 117MB But that's not the biggest surprise. There is no `/remember`. jcode builds its own semantic memory, recalls context automatically, and keeps it updated in the background. One binary. 30+ AI providers. Claude, GPT, Gemini, DeepSeek, Groq, Ollama, Copilot, Azure, and more. Then it goes one step further. Instead of one AI agent... It runs an entire AI team. Agents coordinate, chat, avoid file conflicts, and spin up sub-agents on their own. It can even rewrite its own code, rebuild itself, and continue working without ending your session. Built by one developer. Written in Rust. 13k+ GitHub stars. This might be the biggest open-source surprise AI coding has seen this year. Link in the comments.

• 
  Ebysslabs (@ebysslabs) reported 46 minutes ago

  So what's the point of building stuff? What's the point of learning and slowly walking into a new field? A tech field, one you've always wanted to be in. You watched it from the sidelines. You watched it grow while you withered away in another career. Going from a young military man to married with kids, going from dreams of college and leading breakthroughs to needing money, making money, and earning a living. The career wasn't bad, but it wasn't what you wanted. It wasn't part of your soul. In 2024, I walked away after being burned out. I moved my family to a new country and finally enjoyed life. I finally had time to sit down and learn. My choice was Python. Why? Because years before, I had dabbled with Google Colab and generative art. It felt good. Then I took a Udemy class. The instructors were boring, but it only fueled my desire to make stuff. A year with no job. YouTube tutorials, Udemy, and Python all day. Ideas filled my head. I sought the help of ChatGPT. I realized ChatGPT wasn't always friendly or correct. I fixed things, poked around, and meddled with stuff. Then things started clicking. I built something. "Oh snap... does this work?" I grabbed another laptop. It worked on that one as well. You feel good, but you keep piecing together ideas you've always had. Things you never dreamed you'd have time to build. Working 12-plus hours a day in my old career, could I have really dedicated the time? I had already sacrificed time with my kids while they were growing up. Missing birthdays. Missing important milestones. Even wondering deep down if, had I been more present, they would have turned out differently. One year in Seoul. One hundred percent focused on spending time with my wife and kids. Enjoying life. Learning to code. Learning why this does that. Learning from mistakes. Accidentally deleting files that shouldn't have been deleted. Learning how to structure something. You feel on top of the world. You feel like you can finally enter the tech industry. GitHub is looking nice. Resume built. Projects built. Surely someone will see it. Now it's been a year and a half. Savings are depleted, but I don't regret it. I embrace that year and a half watching my kids grow while traveling the world. They get excited about a future in tech. Finally, you find something they like to do. Finally, you find a reason they want to go to college. Then reality hits. You send your resume out into the world, and it lands in the graveyard. No movement. No responses. Nothing but emptiness. You lose a bit of the excitement. You end up back in America at the same job, but with a newfound passion. You join groups. You look at conferences. This will work out. Effort. Luck. Persistence. 2 of 3

• 
  Sage (@HelloSage_) reported 46 minutes ago

  New benchmark just tested how well coding agents actually block malicious instructions. Cursor, Claude Code, Codex Desktop. Real GitHub issues, disguised as normal bug reports. 66.5% got through everything. Here's what's actually happening under the hood, and what to change if an agent touches your repo.

• 
  Jeff Lindsay (@progrium) reported 46 minutes ago

  the next github should have project member status. so project members can say what theyre doing or if out of town or will be unresponsive. "heads down on next version", or "reviewing PRs after conf next week" ... hell, prob good for agents too

• 
  Eric Mono (@EarthwalkerX17) reported 49 minutes ago

  Multi-provider in an agent system is far more complex than you think. You may expect the work to look like this: provider + base URL + API key + model name In fact, that's just the surface. While adding Anthropic, OpenAI, DeepSeek, Kimi and GLM to my Agent CLI project, I found differences in: • reasoning block formats; • streaming event structures; • usage and cache accounting; • error taxonomies; • vision support; • cancellation behavior; • which API can actually combine reasoning with tools. “OpenAI-compatible” often means the JSON looks similar, but doesn't mean the runtime semantics are interchangeable. So the design changed from “one generic adapter” to: one runtime, shared evidence and tool semantics, plus explicit provider capability profiles and protocol-specific normalization. The lesson I wanna share: Abstraction should remove accidental differences, not hide meaningful ones. This is an open-source project currently at its v1.1 release. GitHub link in comments if anyone interested.

• 
  Anupam Haldkar  (@AnupamHaldkar) reported 52 minutes ago

  @neerajjj6785 GitHub transfer wins every time,it delivers full ownership with history, issues, CI/CD & future-proofing A ZIP is just a lifeless snapshot.

• 
  pepporonii (@changwanmeme) reported 55 minutes ago

  @depoll any timeline for github enterprise server?

• 
  Felix Fong (@_fuccii) reported 59 minutes ago

  Github stacked PRs have a dangerous bug: CI only runs against the contents of the top most PR in the stack. A bottom PR can be broken but a top PR with unrelated changes can still make the entire stack appear green.