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	7 days ago
Quito	Sign in	8 days ago
Junín	Errors	8 days ago
Guadalajara	Errors	8 days ago
Paris	Website Down	8 days ago
Quito	Errors	8 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:

• 
  Arham (@arhamsai) reported 1 minute ago

  @yoimkonrad This was on a PR that contained an entire build which was about 15,000 lines. From the initial commits CodeRabbit gave the most findings, almost 2x more than Greptile and Codex, however after 2-3 rounds of fixes it didn't find anything while Codex kept giving 2-3 findings per round. Codex kept doing this for about ~20 further rounds and CodeRabbit did give findings on a handful of those commits as well, but what I have majorly noticed is that after a fix Codex tends to find other things that came up elsewhere because of the fix. I'm not sure if this is because CodeRabbit has an incremental review system and Codex maybe does it differently, but it does feel like it rereviews everything again. On the experience side however CodeRabbit is much much better, Codex does not give a prompt and doesn't even use GitHub checks, also been loving the autofix feature in CodeRabbit.

• 
  Alexander Cranga (@alexandercranga) reported 3 minutes ago

  *** is solved. GitHub outages are not. Fix is not incoming

• 
  Joel Wohlhauser (@joelwohlhauser) reported 7 minutes ago

  For the last few weeks I've completely switched from VS Code to Blackbird, my personal fork of T3 Code. I was a die-hard VS Code user for years. I even built my own extension to push it further, but eventually hit too many limits. T3 Code had most of what I wanted, so I forked it and added the missing pieces: - a right sidebar for files, local changes, and PR changes - tabs in the main chat area, with tabs for the Linear issue and GitHub PR opening automatically - better flows for existing and new worktrees, with automatic .env linking and cleanup - smaller things I missed, like fast keyboard switching between chats Why call it Blackbird? the SR-71 is the most impressive airplane ever built. easy.

• 
  ZYN (@XboxSignOut999_) reported 10 minutes ago

  @Narf_ios Tbh I just use GitHub actions and Tailscale with ssh on my iPad and I have chat gpt connect to it and I have it fully debug my iPad like that and fix it remove any tweaks that cause safe mode

• 
  m4rio (@m4rio_eth) reported 11 minutes ago

  and we wonder why github goes down so often

• 
  Femi Akinyemi (@akinyemi_t) reported 11 minutes ago

  @syrokomskyi @PafCore Reasonable concern. It's plain JavaScript, nothing compiled. Read all of it before running anything: npm pack @pafcore/cli Two dependencies, lighthouse and chrome-launcher. No calls to my server. Repo goes public this week. After that every release publishes straight from CI with npm provenance, so the registry verifies the tarball against the commit rather than you verifying me. A GitHub Action is built and ships with it. Same check on every pull request, and it only fails the build when the drop is bigger than the page moves on its own.

• 
  Simon Skinner (@vultuk) reported 12 minutes ago

  @Rames_Jusso Nope. I have a Mac mini that just runs codex. It’s just sat there dealing with things for me. Runs scheduled tasks to work on GitHub issues and I connect through remote to start it working on things. It’s more than enough. No usage issues, no need for anything more. There seems to be a whole batch of people that seem to “need” all these special agents, yet they aren’t shipping anything that benefits from it. (That I’ve seen at least)

• 
  M.S (@MrMSpencer) reported 14 minutes ago

  @evntylr @blbraner @thekitze Interesting. Being free for Cursor members makes it compelling for small new projects. I still wouldn’t want the repo parked with the same company providing the AI, if your AI use gets falsely flagged as security work, consultancy, or something similar, you don’t want your *** access going down with it. Some separation is handy. GitHub is established, understood and reasonably resourced if msft could kindly buy them more servers yesterday.

• 
  Franklin Solum (@FranklinSolum) reported 15 minutes ago

  Storing long-lived cloud credentials (AWS_ACCESS_KEY_ID, GCP_SA_KEY) in your repository secrets is a massive security liability. Use OpenID Connect (OIDC): Your CI runner (GitHub Actions / GitLab CI) exchanges a cryptographically signed identity token with your cloud provider The cloud provider issues a temporary, short-lived IAM session token valid for only 15 to 60 minutes Zero static credentials stored in your *** settings

• 
  Joe Guardino (@JoeGuardino88) reported 17 minutes ago

  @NFL_Blitz_Rez I think this link is broken. Can you post on GitHub?

• 
  Vet (@Vet_X0) reported 17 minutes ago

  @Kirjakulov @daniel_wwf Let's not apply sarcasm on one of the few persons who in recent times put out a proper solution for this on github. We can all drive a change we want to see it's an open source project, especially by (FH) node operators if this is a cost burden. Definitely in favor or a solution personally, looks like this discussion goes back to 2019 with Nik B. The only thing i'd add here is that existing services would become tiny more expensive. The memo field is heavily used by Flare and Axelar for interoperability, and potentially other integrations in the future. At the same time, it's also good to know none of this would solve the issue of FH nodes needing to store this stuff and they will not get paid to do that. That's a general blockchain problem. Solana FH is hundreds of TBs for example.

• 
  Juraj Bednar🏴💛🌘 (@jurbed) reported 19 minutes ago

  @marttimalmi I'll switch to it too, with github mirrors. I've sent an issue to nostr vpn to it, so I have minimal experience. It's much better for agent work than github, Nostr events for issues are better than centralized accounts. Although there will be spam. Just curious if they don't have more features, using their frontend with hashtree backend.

• 
  Artes (@Artemwkz5) reported 20 minutes ago

  Your agent isn’t failing. It’s on payroll in the wrong building. Busy chat. Dead output. Same disease. This 11-second video is ByteByteGo’s floor plan for LangChain, AutoGen, CrewAI, LlamaIndex, and Semantic Kernel. Same model logos on the right. Five jobs on the left, in those yellow boxes. X keeps voting for a winner. The video is the org chart they should have used before they cloned a repo. Don’t listen to the captions. Watch the arrows. See the llama row? Hard hat at the bottom. Query up. Response down. That’s a librarian. Load → parse → index → ask your PDFs, DBs, APIs. If you dumped 400 internal docs into a generic “agent” and spent a month on retrieval, you hired a plumber to run the library. The weekend version is already drawn. See writer and editor, then three clipboards? That’s a newsroom. Process in the middle. Tools under the floor. If you needed draft → edit → three tasks and opened a group chat, you staffed a committee. Committees debate the assignment. Newsrooms file it. That’s why one path ships by Friday and the other still has “alignment.” LangChain is pipes: prompts, tools, vector stores, chains. AutoGen is a meeting: humans can cut in, code can run, tools can fire. Semantic Kernel is a socket wall: C#, Python, Java, then a plug into the model. None of that is a personality. It’s a department. One person who pauses on the right box looks like a 7-agent company. One person with five GitHub tabs open looks like they work in AI. Open the video. Find your yellow box. Fire the other four.

• 
  catman (@catmanyau) reported 23 minutes ago

  @godwinbabu how are you preventing the operator from filing noisy GitHub issues for symptoms it can’t reproduce? the handoff between the monitoring agent and the separate dev agent is where i’d want to see

• 
  Satyam Gupta (@skg_twt) reported 25 minutes ago

  github is down again 🥀🥲

• 
  Joey (@joeyjurjens) reported 25 minutes ago

  @fuolpit @Cloudflare Maybe make a Github issue? :)

• 
  Umar Bashir Rather (@umar_who_code) reported 26 minutes ago

  @orcdev @grok @bot This seems very interesting. Now I have a question: Does it post these posts as well, or does it write somewhere for you and then you post them? If he's doing the work on Github issues and PR's then are you reviewing them or you have created somekind of guardrails and checks to pass the PR review and auto approve.

• 
  Robert (@Rrrrrobertanium) reported 28 minutes ago

  This is the way. If you don't meter usage with people blowing up their weekly so fast they're going to be sitting idle wondering about continuing their work with a competitor... And then they leave your ecosystem. Again thank you for helping to introduce me to the Chinese models. I got qwen 3.8 now working and fixing 5.6 Sol outputs. Let's see how the changes go because right now I still burned 40% overnight with little to show for it. That and it really ****** up with GitHub. So many CI actions we're running and unnecessarily running from my sol chats got to shut it down because it was going to bill me $60 a day.

• 
  Grey Ledger (@Airdrops_one) reported 29 minutes ago

  This one is bad. Cosmos EVM had a critical vulnerability. The fix existed. The issue was public and then multiple chains running the stack were hit or are being forced to halt. The v0.7.2 release told chains to upgrade "as soon as possible using a coordinated upgrade." Coordinated with whom? If attackers can read GitHub, downstream teams need something better than GitHub. Bugs happen. Enterprise infrastructure is judged by everything that happens after the bug: who is exposed, who gets warned, who gets patched, and whether the customer or the attacker acts first. We need the full postmortem from @cosmoslabs_io But there’s no sugar coating this one: the coordination failed pretty bad.

• 
  John Crickett (@johncrickett) reported 32 minutes ago

  I recently ran a hackathon sponsored by Kiro. The goal was simple: use Kiro to build something useful. As a judge, I couldn’t officially take part. But I still wanted to build alongside everyone else. I originally planned to work on a screen recording app. Then, towards the end of the hackathon, I realised there was something I wanted even more: a voice dictation app. Like a lot of people, I’ve been experimenting with using voice to drive AI, and increasingly other parts of my workflow, rather than typing everything. The problem is that I hadn’t quite found the right app for it. There are some good options out there, but many of them, particularly on mobile, come with privacy trade-offs I wasn’t comfortable with. So I decided to build my own, with one important constraint: Everything must stay on-device. I started by looking at existing apps and pulling out the features I actually cared about. I wrote those down as rough requirements in my notes. Then I gave those notes to an agent and asked it to rewrite them as requirements using the EARS format. That became my high-level spec, saved as Markdown. From there, I started a new session in Kiro Crew, pointed it at a fresh GitHub repo and the spec, and gave it a fairly simple instruction: “Review the spec and advise me how we can build it.” A few hours later, I had a working first version of the app. There are still a few things to tidy up, but the next step is to release an alpha and get it into people’s hands for feedback. This was a fun project to build with an AI agent. It lets me have the tool I want and I simply wouldn’t have had the time to build it without AI. But with AI, I could build it alongside chatting to people as they wrapped up their hackathon submissions. This is where AI coding agents shine! @kirodotdev

• 
  Lord Bean (@lifeisameeme) reported 33 minutes ago

  Every 'AI research assistant' out there sends your queries to someone else's server. Local Deep Research doesn't. → Runs fully on-device - arXiv, PubMed, SearXNG and 10+ sources searched locally → Plug in Ollama, OpenAI, or Anthropic - your model, your choice → ~𝟵𝟱% accuracy on SimpleQA, in the same range as the cloud tools For competitive intel, legal research, or anything you don't want logged - there's no privacy policy to trust here, because the data never leaves your machine to begin with. 🔗 GitHub in the reply

• 
  MoStandard (@TheMoYouKnow13) reported 36 minutes ago

  @witcheer Never had this issue. Tell it your everyday routine and ask how it can help. Explain your job. Your jobs expectations, tasks and processeses and how it can assist, streamline or elevate. Find repos on GitHub. Inexperienced? Don't know how to download/install? Tell Hermes. Hermes will oblige. Desktop app sticking during updates on the desktop app because you have an AMD GPU while it hangs on CUDA? No sweat. Ask Hermes. In terminal. On desktop. It does it all

• 
  aria (@aria__han) reported 37 minutes ago

  don’t write md files, write github issues. saving me immense time and cognitive load to coordinate through issues rather than files or messages, especially for cross human coordination

• 
  djSoniQ (@djsoniq) reported 39 minutes ago

  We'd have major data security issues with the way this NIN / NIMC thing is being used. Nigerians' PII just flying all over the place to anyone with a github account& enough tokens. Why are non-regulated sectors plugging into national identity infra in order to book kabu kabu???

• 
  Ramtin (@ramtinrhmti) reported 40 minutes ago

  Day 2/180 UPDATE yesterday I asked if I should build or validate. did some digging today but not the kind that actually counts yet killed the clinic booking idea, a funded competitor already does exactly what I wanted to build. glad I checked before sinking a month into it pivoted to something I deal with myself, AI agents saying a task is done when it isnt. before touching code I checked 5 real PRs an AI coding agent made against the actual github issues they were supposed to fix, just to see if the problem is even real 2 were legit. 3 got closed without merging even though they looked fine on paper. so the problem seems real at least on paper but I havent talked to a single person about this. no dms, no "would you use this," nothing. that's still the actual next step, not more building scaffolded it anyway bc I wanted to know if it was technically doable. a github app + a small action, both build and run. broke something mid way, fixed it properly not attached to this yet. could easily be wrong, just havent found out yet

• 
  Nav Toor (@heynavtoor) reported 41 minutes ago

  The Composio breach in May 2026 exposed every credential stored on their platform. That's the risk of closed-source integration platforms. Your customers' OAuth tokens, API keys, and credentials sit on servers you can't inspect, running code you can't read. Nango is the open source alternative. 11600+ GitHub stars. 900+ APIs. Every line of code is public. The auth layer, the credential store, the proxy, the execution runtime. All inspectable. All self-hostable. Replit, Ramp, and Mercor already run it in production. 600+ B2B companies total. Here's why developers are switching: You describe an integration in plain English. "Sync GitHub issues to my database every 5 minutes." The Nango AI Builder skill, along with a coding agent such as Claude, Cursor, or Codex, can write code and test it against a real account. You read it. You edit it. You own it. It's not a black box. It's code in your repo. The runtime handles everything production needs: OAuth for 900+ APIs, automatic token refresh, rate limit handling, per-tenant isolation, retries, and scaling. SOC 2 Type II, HIPAA, GDPR compliant. And you can self-host the entire thing for $0. The "unified API" vendors charging $40K-$100K/year for the same capability are selling you a hosted version of what Nango ships publicly. After Composio, the question isn't whether open source integrations are good enough. It's whether you can afford to trust closed source with your customers' credentials.

• 
  Denson Ngumo (@denson_ngumo) reported 47 minutes ago

  @CloudStack Which release has a fix for the bug with reference #13233 on Github?

• 
  RaoulDuke (@RaoulDukeDegen) reported 55 minutes ago

  @levelsio saw that black hat demo where a github issue triggered rce on ai agents

• 
  PADRE🏝️ (@0xpadre) reported 59 minutes ago

  Cursor is coming for GitHub and it's not subtle anymore. GitHub went down for 7 and a half hours. Copilot, Actions, merges, all of it. 15,000 devs hit the outage. Every minute of downtime is a migration notice. AI-native tools take the code layer next.

• 
  Jaseci Labs (@Jaseci_Org) reported 59 minutes ago

  @Prathkum The diffs-to-outcomes shift is right, but it doesn't need a whole new agent-first GitHub to happen. It can happen at the function level today. If a function's contract is a type signature instead of a human reading every line of implementation, grading the outcome is just checking whether the return value matches the contract, no diff review needed for that piece at all. The reason people are bolting agents onto GitHub isn't inertia, it's that most code still doesn't have a machine-checkable definition of correct, so a human has to eyeball the diff because there's nothing else to check against. Fix that at the language level and a lot of what GitHub was built for stops being the bottleneck, even without replacing GitHub itself.