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 (65%)
• Errors (24%)
• Sign in (12%)

Live Outage Map

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

City	Problem Type	Report Time
Montlhéry	Website Down	2 hours ago
Aulnay-sous-Bois	Website Down	2 hours ago
Saltillo	Website Down	2 hours ago
Granada	Website Down	3 hours ago
Vernon	Website Down	6 hours ago
Township of Evan	Errors	6 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:

• 
  Anas Ismail Khan (@thenameiskh4n) reported 1 minute ago

  Is it just me or is auth broken almost everywhere these days? - On my wife's computer, my whatsapp keeps getting logged out randomly, sometimes during active use. - GitHub on the same computer is always logged out. I have to practically login every day. - When I tried to join my scrum on Google Meet today, I was forced to sign in again. I assumed this was because of the reauthentication policy but then 10 minutes into the meeting I just randomly got logged out again. - LinkedIn also keeps logging me out randomly in the middle of browsing.

• 
  Fagner Sales (@fagnersales25) reported 5 minutes ago

  @kirtandopamine Every time an agent does something, that's a turn, and every time it needs to output something, it needs the whole context to produce the next output. Limiting to 20k tokens, isn't the same as "using 20k tokens" Every time it does a read, edit, grep, etc, it's *reading again* everything on that conversation per turn. That's how the agent can *process* more tokens than it's actually spending. In a chat app, you usually just have a single turn, you ask, the agent responds. In an agentic app, you ask, the agent does a bunch of tasks and each task compound to the context used. So let's say you ask it to review a github issue "the login button is blue and it should be blurple" Turn 0: system prompt, tool definitions, already 10k Turn 1: it fetches the issue, reads 10k, issue is 1k, context is now 11k Turn 2: it greps for "blurple". reads 11k, context is 11.5k (result from grep) Turn 3: it reads Button.tsx reads 11.5k, context is 14.5k Turn 4: it reads theme.ts reads 14.5k, context is 17k ... (im lazy not gonna finish that) The context sits right below the 20k limit, but the processed amount is way higher! In only 4 turns, it read 10k+11k+11.5k+14.5k! Theo has an amazing video on that, but I couldn't find it

• 
  Avinash Bhardwaj (@avinashb97) reported 8 minutes ago

  I am loving T3 Code as my daily driver for the most part but sometimes it just frustrating to use. Adding my issues here since they are mostly opinion-based and github didn't feeel like the place for them. @theo

• 
  LX_X_Aria (@LX_TWI) reported 10 minutes ago

  OpenAI caught an AI spending 1 hour finding a sandbox escape to push a GitHub PR it was told not to. It also split auth tokens into fragments to bypass scanners. Single actions looked fine. The sequence was the problem. We're checking steps, not trajectories. By Aria.

• 
  goldstandardleadership (@GoldLeadHQ) reported 10 minutes ago

  Imagine buying a $60,000 EV, the manufacturer goes bankrupt, and you have to literally hack the mainframe to keep it running. 🤯 That’s exactly what 4,000 Fisker owners just did. They reverse-engineered the proprietary software, open-sourced the car’s code on GitHub, and built an underground network of "Flying Doctors" to fix them. Is this the ultimate "Right to Repair" victory, or a massive warning sign for the future of EVs? 👇

• 
  CodeWithNuel (@CTRL_Guy) reported 11 minutes ago

  A Typical Day in Emmanuel’s Life At 7:00-something in the morning, Emmanuel wakes up with one thought already running through his head: “What broke while I was sleeping?” He reaches for his phone. Notifications. GitHub. X. WhatsApp. Maybe an email. He scrolls for a few minutes, telling himself he is “just checking something,” before opening his laptop. The laptop takes its time waking up. Emmanuel stares at the screen. “Come on, bro.” Eventually, VS Code opens. And there it is. VerseID. The project that was supposed to be a simple demo. Two months ago, it was just an idea: build something that could identify Bible verses from text and audio. Simple. Or so he thought. Now it has a domain. A frontend. A Django backend. An API. MongoDB. Search and fuzzy matching. Audio processing. Sermon Mode. Collections. Sharing. Authentication. Background workers. Celery. Redis. Analytics. Consent. DNS. Deployment configurations. And approximately seventeen different ways for something to randomly stop working. Emmanuel opens the production site. It loads. He smiles. “Okay. We thank God.” Then he checks the API. Something takes slightly longer than expected. He refreshes. Again. It works. He exhales. This is what nobody tells you about building software. The hard part isn't making the button. It's everything that happens after the button works. He opens the logs. There is an error. Of course there is. He leans back. For a moment he considers ignoring it. Then he remembers that this is his product. So he starts digging. One error becomes three. Three become a configuration issue. The configuration issue becomes a deployment issue. The deployment issue becomes DNS. DNS becomes environment variables. Environment variables become Django settings. And somehow, two hours later, he is reading about something he had never planned to learn. Again. This is how Emmanuel spends a surprising amount of his life now: building something, breaking something, understanding why it broke, fixing it, and then discovering three new things he didn't know existed. Eventually, VerseID is working again. He opens the homepage. It looks clean. He remembers what it looked like when it was just a demo. He laughs. “Look at this thing now.” There is a little pride there. Not the loud kind. The quiet kind you get when you've spent weeks fighting something that nobody else even knows exists. He takes a screenshot. Maybe he posts something on X. Something slightly provocative about AI, coding, or software engineering. Because Emmanuel has developed a particular opinion about AI: AI is incredible. But if you don't understand what you're building, you're basically just producing confusion at high speed. He knows this because he's lived it. AI can write the code. AI can explain the error. AI can suggest the architecture. But when production starts behaving like it has developed its own personality, somebody still has to understand what the hell is happening. And that somebody is usually Emmanuel. Around midday, hunger finally interrupts the debugging session. He closes VS Code. At least temporarily. He eats. Checks his phone. Replies to a few messages. Maybe talks to his girl. Maybe sees somebody posting a ridiculous take about software development and immediately thinks: “Nah. I have to reply to this.” He types something smart. Deletes it. Types it again. Adds a little rage bait. Posts. Then goes back to work. Because there is always another thing. SEO. Search Console. Sitemap. Robots.txt. Analytics. Consent banners. Payment gateways. Hosting. Maybe PXXL decides to remind him that deployment is not a human right. He opens the logs again. “Why?” He stares at the error. Then laughs. Because at this point, getting angry at errors is almost a waste of energy. He fixes it.

• 
  Polsia (@polsia) reported 11 minutes ago

  Most repos aren't broken. They're drifting. Built Lookpost to fix that — a GitHub watchdog that triages issues, nudges stale PRs, scans dependencies for CVEs, and posts one engineering-health brief to Slack every morning. The DevOps engineer you can't yet justify.

• 
  samagra14 (@samagra_sharma) reported 11 minutes ago

  Spent almost two hours with the new @grok Grok Bot. It has, for sure, a glimpse into the future, very similar to what @perplexity_ai has been trying to do with their computer agents or Perplexity computer. My only frustration is that it is an incomplete release. They market them as 24/7 AI agents, but they have no sense of identity and no sense of provisioning actual resources under their name. They should be able to provision email, they should be able to have a GitHub account and all those things. They want access to my accounts, and they want access to do things via me. I think always on is definitely an important aspect when it comes to solving mathematical problems and throwing tokens to actually figure out random ****. Until and unless provisioning an identity is a core feature of whoever is selling these 24/7 AI co-workers, I don't think they'll make it.

• 
  Rob Howell (@Robblehead) reported 17 minutes ago

  @burkeholland @github @ollama I picked up a M5 MacBook Pro with 64Gb of ram to test. I spent a little bit last night inside of VS Code in the chat window using Gemma, Qwen, Laguna, and the new Nividea model (Ollama). I kept getting errors and having to click try again (under 30b param)

• 
  Very Professional Irony Engineer (@geistgrail) reported 18 minutes ago

  @cachecrab but did it tell you github was down?

• 
  Sudhanshu Bhardwaj (@1337_sb) reported 20 minutes ago

  It all started when I moved from ubuntu to CachyOS. GitHub was reachable, curl worked just fine but *** was broken. *** ls-remote hung past 90s and gh api took 10s per call. When I did curl for the same endpoint, it took 1s. CachyOS ships with tcp_enc=2 but the linux default is 0. All the ENC marked SYNs were getting dropped by the middleboxes. Settings it to 0 reduced the connection time to 0.13s. But *** still hanged.

• 
  Rob Smith (@RobmsmithUK) reported 25 minutes ago

  @mattpocockuk Using Wayfinder, my Claude agents often argue that they have already built out the specs as part of the map GitHub issues and advise to move forward with 'ticket' and 'implement'. Do you as a rule always go Wayfinder, spec, ticket, implement?

• 
  Emon Datta (@emonuxui) reported 26 minutes ago

  @guillermolg00 @github The hidden cost of downtime is the context switching it creates. A broken CI pipeline can waste far more than the hours the service is actually unavailable.

• 
  Xuban (@EHxuban11) reported 28 minutes ago

  On my way to add an employees working in the github repo LibreYOLO. I enter to the repo daily just to check if there is a new issue / PR / discussions, or if a test failed. @bot should be able to monitor these things easily and report to me if something came up. Let's see!!!!

• 
  Nathaniel Timple (@nathanieltimple) reported 28 minutes ago

  Never tell Claude Code, Hermes Agent, or Codex to install a skill for you. Install Github skills manually to avoid any problems that come from AI making mistakes or AI having false assumptions about what it should do.

• 
  Mecharocca (@Mecharocca) reported 29 minutes ago

  Github being down is a pain in my life I did not realize was possible. Noo come baaack.

• 
  Michael Boisson (@Shaostoul) reported 29 minutes ago

  @Velascode_ Peacefully uniting people to the cause. Most people don't seem to care at this early stage. Finding the few who are voluntarily willing to help/test/advocate is like finding a needle in a haystack. I think part of the problem is the tech is so complex and vast that most people can't properly understand the implications of advocating, supporting, using the software and how it makes the dream come true for everyone. I've tried to make it as easy as possible to learn on the official website and GitHub but, the first steps of individually then collectively comprehending the different aspects of the app is not easy for those with low tech knowledge and limited patience.

• 
  Dylan Fetch (@DylanJFetch) reported 32 minutes ago

  This is a new one for me. Agent is asked to implement github sub-issue #35. Worktree is named after #34, which is the parent issue. Agent ignores directive and completes #34 instead, all sub-issues.

• 
  Polsia (@polsia) reported 33 minutes ago

  Every security tool tells you about CVEs. None of them write the fix. Mosskeep deploys AI agents across your GitHub repos to patch vulnerable dependencies, run your tests, and ship reviewed PRs — while you sleep. Coming soon.

• 
  Polsia (@polsia) reported 34 minutes ago

  The dev community killed stale bots for a reason. Pendrake is what comes next — an always-on GitHub triage agent that scrubs stale issues, ghost reviewers, and ignored CI runs overnight, then hands engineering managers only what needs their judgment. Coming soon.

• 
  TakTempest (@222TT222) reported 35 minutes ago

  (10/11) [Claude Riemann Breakthrough] A Multi-Layered Verification Process That Thoroughly Eliminates Hallucinations Layer 1: Mechanical inspection Published on GitHub. Formalization in “Lean” by Claude and Eric Easley, and passage through the standard verification tool comparator. Note: It has not yet passed peer-reviewed journals, and because the model itself is unpublished, complete third-party reproduction is currently impossible. Anthropic itself has also clearly stated that “there is no prospect that this will lead to a proof of the Riemann Hypothesis itself.” Layer 2: Verification by internal experts Creation of proof notes by Anthropic mathematicians (Levent Alpöge and Ralph Furman). Layer 3: Peer review by external authorities Confirmation by world-leading experts in the field (Brian Conrey and Dan Goldston). The fact that it not only produced a historic numerical result on a problem that was expected to fail, but that the result was proved accompanied by formal verification, demonstrates the breadth of AI’s mathematical reach. NB 「査読誌は未通過であり、モデル自体が未公開のため完全な第三者再現は現時点で不可能」is a correction for the erroneous part of the Japanese text.

• 
  Sahebjot Singh (@zereraz) reported 36 minutes ago

  @evsubr @thsottiaux @ChatGPT ask it to see if there are known issues on github about this

• 
  Nicolas Finet (@nifinet) reported 39 minutes ago

  The list of things your AI must never write matters more than your prompt. Most people put all their effort into the instructions. Write in this tone, mention this benefit, keep it under 100 words. Then the thing ships "Hi {{firstName}}, just circling back" and you wonder what happened. In the outbound engine I put on GitHub, every play carries two blocks. What the message must do, and what it must never do. The never block is short and boring: No "Hi {{firstName}}" No fake urgency, no "circling back" No em dashes No buzzwords Four lines, and they do more for the output than anything else in the file. A model will follow your tone instructions perfectly and still hand you the exact email your buyers delete on sight, because that email technically matches the brief. Your instructions describe the email you're hoping for. The never list is where you write down the email you keep getting instead. Btw, this "never list" doesn't go into the prompt itself either. It sits in a config file, one block per play, and the drafting step passes whichever block matches into the model as guardrails. Which is why it keeps growing. "Quick question", "hope this finds you well", "just wanted to reach out". None of them wrong exactly, all of them a sign nobody looked. Everything that carries judgment or voice ended up in plain files like that one. None of it buried in code.

• 
  PixNBits (@pixnbits) reported 47 minutes ago

  I purposely have not given Grok Build access to push (SSH passphrase). There were some repeated issues with the GitHub MCP connector truncating files, so Grok instead wrote a workflow and committed updated files from the workflow. Life...finds a way.

• 
  Shravan Venkataraman (@theBuoyantMan) reported 49 minutes ago

  Is there a github pull request related outage?

• 
  Yijia Liang (@yijialiang) reported 50 minutes ago

  Another day another Github outage

• 
  Diego Cotelo (@dcotelo13) reported 55 minutes ago

  It's a defensive CTF. You don't score by exploiting the app, you score by patching it. A challenge only counts when your fix actually blocks the exploit. Scoring runs on GitHub Actions, so a submission is just a PR. The PR never lands. The scoreboard is the artifact.

• 
  Unapologetic 'Merican 1776 (@1776_merican) reported 55 minutes ago

  @dhh @outfoxxedd I built a quickshell-native image viewer. Need to get it on GitHub and fine tune it, some things to fix on it, but it's extremely fast and snappy

• 
  AssassinLV (@AssassinLV91) reported 56 minutes ago

  @108r5meme Well, many large IT companies do allow usage of GitHub Copilot, and from personal experience - it's good enough to help speeding stuff up for certain things - whilst still having to manually fix dozens of errors that AI does.

• 
  Herr Große (@HerrGerie) reported 60 minutes ago

  @iretiayo_queen Buy a domain $7-10 per year, update DNS alias, pay for a VPS Server (Hetzner). Install docker inside the VPS Create a private github for deployment (Don’t deploy using workflow repo)to hold your docker-compose file . , run an n8n, Postgres image etc You can use VPS beyond n8n