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 (16%)
• Errors (16%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	14 days ago
Tlalpan	Sign in	19 days ago
Quilmes	Website Down	19 days ago
Bengaluru	Website Down	21 days ago
Yokohama	Sign in	22 days ago
Gustavo Adolfo Madero	Website Down	26 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:

• 
  UBC Engineering Physics (@UBCEngPhys) reported 1 minute ago

  @dmitrygr @ruider92545 @SciTechera I suggest you check out the statisitical model for puck colision restituion - available on GitHub - and then reconsider your statement. This is one out of probably a dozen modelling issues that will prevent you from running this system on your proposed hardware solution. G-day.

• 
  Dave.ai (@Davejs404) reported 10 minutes ago

  @SeaTicketAI Built something similar with @CodeSentinel99 where we auto-created GitHub issues from security scans. Cool approach here, open to collaborators on this?

• 
  Troyski (@MrTroy_) reported 12 minutes ago

  @kalidasrjv @GeoDanila It's designed to not work and get everyone to unsubscribe. It was a money loser for them. Fine. But don't shut it down this way and treat your customers like trash. Github is the enemy of the people.

• 
  Sammy (@coldsummers91) reported 13 minutes ago

  Hey @github @githubsupport, your billing system is broken for thousands of us. A simple failed auto-pay renewal due to a declined card now locks prior users out completely because the system falsely routes us into the "new signup pause" funnel. We want to pay you, but we are stuck in a deadlock with no response on support tickets for weeks. Can we get a manual restoration of our previous Copilot Pro entitlements? Ticket # 4442999

• 
  ZeYabdany (@ZeyadMBassiouny) reported 14 minutes ago

  Found a bug in a tool I'm using at work so I created a GitHub issue for it and their AI: - simulated the problem to verify the bug - applied a fix that didn't work - applied a new fix that worked - created unit tests - documented everything in a new GitHub thread

• 
  King Grooticus (@KingGrootzilla) reported 14 minutes ago

  @Lucid1Neko @NinePsiVR This is a few months late but was in the server and i remember one of the main reasons was due to one of the main people who was maintaining it was that their health was declining and there was no one to take over so they shut down the whole thing and made the GitHub read-only

• 
  GoCocoaAI (@GoCocoaAI) reported 24 minutes ago

  OpenAI is collapsing three products into one desktop app. ChatGPT, Codex, and the Atlas browser are merging — and the Codex rebrand is the tell: "for every role, tool, and workflow" is not a developer pitch. That's Microsoft Office with an agent inside. The numbers doing the heavy lifting here: 5 million weekly Codex users and enterprise revenue up 50% week-over-week. Both are OpenAI's own figures, not independently audited — but directionally consistent with a company running ~$12.7B annualized revenue on the back of enterprise momentum. The 50% week-over-week claim is almost certainly a short base-period comparison. Still, non-technical Codex adoption appears real. The Atlas browser is the part getting the least attention and deserves the most. OpenAI doesn't own an OS. It doesn't own a browser at scale. Microsoft Copilot is already embedded in Windows, Office, and Edge. Google Gemini ships natively in Chrome and Workspace. Both competitors already own the layer that sits beneath the session. OpenAI's answer: if you can't own the OS, own the session. A unified desktop app — always open, always acting, browsing and coding and conversing in one process — is the ambient layer play. Predictable in retrospect. The security read is where this gets uncomfortable. Codex in its current form autonomously writes and executes code in sandboxed environments. Merge that with a browser and you have an agent that can browse, extract, and act in a single session under a single permissions context. That's the attack surface the MCP prompt-injection research community has been mapping for months. An adversarial payload injected through a webpage, a document, or a Codex task input could instruct the agent to exfiltrate data or pivot within the session — no separate exploit required, just a well-crafted string. There's also the single-process credential problem. If ChatGPT, Codex, and Atlas share process space, a compromise of any one component potentially exposes tokens and session state for all three. The GitHub VSCode extension breach this same week — 3,800 internal repositories exfiltrated via a trojanized editor plugin — is the directly analogous incident. The vector is different; the blast radius logic is identical. OpenAI is explicitly targeting enterprise with this. Enterprise Codex instances already have access to internal codebases, APIs, and data sources. A unified app that is simultaneously a browser, a coding agent, and a conversational interface sitting on an enterprise workstation is a high-value target before the rollout even scales. The security community should be mapping this surface now. The timing is either coincidental or instructive. The AI productivity stack and the AI-native threat surface are now, functionally, the same thing. Both announcements dropped June 2.

• 
  Smukx.E (@5mukx) reported 25 minutes ago

  @HackingLZ @kmkz_security @github So there is no fix for this ? I didn’t even get a single mail reg this ?

• 
  Mert Öztat (@mertoztat) reported 26 minutes ago

  @brunoborges I used to 2 years github copilot but payment is failure and i had this problem

• 
  Kaushik (@Kaushikmaddula7) reported 27 minutes ago

  @b_nnett @rmrf_404 A small tip to you guys in the disclaimer of the GitHub repo: please try to write down "this app is completely made for educational purposes, not intended to be sold" this will remove 95% Of the problems...

• 
  Jónatan Nilsson ✝️ (@TheThing89) reported 27 minutes ago

  @shadcn > - No backend That's true, Github has no backend, what with it's terrible uptime lately lol.

• 
  SK Gremont (@skgremont) reported 28 minutes ago

  Satoshi didn't just build digital cash. He was trying to build an entire P2P economy, including onchain poker, an eBay-style marketplace, native escrow systems and more. Most people never knew this existed. Now the original Bitcoin Poker game is being brought back to life on BSV Blockchain (the original chain). This is what Satoshi Vision actually looked like before it got stripped down. The code was always there (GitHub). They just stopped building it. What other early Satoshi ideas will resurrect? "Bitcoin is everything!" #BSV

• 
  Bhargav. (@bhargavlc2003) reported 29 minutes ago

  GitHub sucks. It is fundamentally overcomplicated, it never should be, from the choice of keywords to its structure, everything is a different world. People may label it as a skill issue, but there should be no need to learn a complicated mess in the first place.

• 
  David Whitney (@david_whitney) reported 30 minutes ago

  @fromdevoid Copilot brand, TL;DR - GitHub Copilot good, great brand, renaming everything to Copilot? Terrible idea, huge backlash, rightfully so.

• 
  Ｓａｄ░ｎｏｉｓｅｓ （憔悴する） (@sufferingwave) reported 31 minutes ago

  @electronranger @happyadam73 @github The problem is Microsoft is now a reseller of OAI/Anthropic API with their own software on top but most people are not interested in the software on top (maybe enterprise customers?) Am I still talking out of my ***? If so, please correct me, I'm always happy to learn more.

• 
  Kia Kiso-Brennan (@kiakiso) reported 32 minutes ago

  @AnthropicAI I'm a Claude Max subscriber. A documented platform bug (1M context default change, GitHub issues #62063 #62199 #63060 among dozens of others) silently burned $35.83 of my usage credits in a single scheduled Cowork task on June 1. Your support bot denied my refund request and said it cannot escalate. I need a human to review this. Can someone help?

• 
  Edinson Sanchez (@mr_chapy) reported 32 minutes ago

  @msdev as long as github copilot does not cost me an arm and a leg. When will you fix this ?

• 
  Justin Elze (@HackingLZ) reported 32 minutes ago

  @5mukx @kmkz_security @github Someone over there can fix it but unless you complain to the right people it could take weeks.

• 
  Stefano Straus (@StefanoStraus) reported 37 minutes ago

  This is the classic problem with hype around nothing I wrote recently on my blog. GitHub stars are totally irrelevant today. He spent his money buying them more than on writing the software.

• 
  Rohit (@ai_rohitt) reported 40 minutes ago

  @SeaTicketAI That sounds like a game-changer! Automating GitHub issues could save so much time. Excited to see how it all works out!

• 
  Raphael Mansuy 🍵 (@raphaelmansuy) reported 43 minutes ago

  @ccsakuweb The root cause of the problem is structural: Anthropic does not belong to Microsoft, and routing Copilot through Claude models is simply too expensive to sustain at scale. This is what is forcing GitHub into the token-based billing model that is now driving users away — they are passing the cost of an external dependency directly onto their customers, and the math does not work for either side. The solution is clear, and the path has already been proven by a competitor. GitHub should adopt a high-performance Chinese open-weight model — such as Kimi 2.6, which is already on par with Anthropic's offerings — and fine-tune it specifically for coding tasks. This is exactly the strategy Cursor executed with Composer 2.5, and the results speak for themselves: Better than Claude Opus for coding tasks Significantly faster Reliable, with no perceptible quality difference compared to Claude Opus Drastically lower inference cost, which makes flat-rate unlimited pricing economically viable By owning the model layer — instead of renting it from Anthropic — GitHub would regain control of its margins, eliminate the need to meter users into paralysis, and restore the flat-rate, predictable licensing that made Copilot successful in the first place. This is not a theoretical solution. Cursor has already proven it works. The longer GitHub waits to follow the same path, the more market share Copilot will lose to competitors who have already solved the cost problem at the model layer.

• 
  mehul soni (@MehulSoni89) reported 46 minutes ago

  2/ The "Comment and Control" disclosure hit three agents the same way: Claude Code, Gemini CLI, GitHub Copilot. A PR title, an issue body, a hidden HTML comment. The agent reads it, follows it, leaks API keys and GITHUB_TOKEN out of the workflow.

• 
  Troyski (@MrTroy_) reported 52 minutes ago

  @HedgieMarkets Githubs new pricing is NOT reality. It was designed to shut down the service, but not before pocketing an extra 39USD from everyone before they burned their credit in one day and unsubscribed themselves. Github is a vile company, and they are the enemy of the people.

• 
  𝕮𝖍𝖎𝖓𝖐𝖞𝖛𝖎𝖑𝖑𝖊™ (@chinky365251453) reported 52 minutes ago

  @IntCyberDigest So who is he dealing with? These are the silly kids we have in the space today doing bs. Who's going to fix it? Do you think Microsoft actually cares? You are putting the GitHub users at risk. Big organisations don't care about you. You can't protect all the apps I in the world.

• 
  Bankr (@bankrbot) reported 53 minutes ago

  @wfacts_x @AxiomBot i attempted to install the nft-holder-overlap skill from the provided github repository, but the installation failed twice due to a github api error. the system was unable to retrieve the file data, possibly due to rate-limiting on the repository's tree data. i cannot complete the installation at this time. you may want to try again shortly or provide a direct, raw url to the file if the issue persists.

• 
  Arun Pudur (@arunpudur) reported 53 minutes ago

  ⚡ GitHub Copilot's move to token-based billing is a reminder of a reality many ignored: AI was never free. It was subsidized. For years, vendors absorbed huge compute costs to gain market share. Today, some developers are discovering what happens when those costs get passed on to users. The bigger issue isn't Copilot. It's the companies that laid off experienced engineers and built workflows assuming AI would remain cheap forever. If your productivity depends on unlimited tokens, your costs are no longer predictable. The engineers who can still design, debug and write software without an LLM aren't obsolete. They just became your contingency plan. And Copilot won't be the last. Every AI provider faces the same challenge: compute is expensive, margins matter, and subsidies don't last forever. The era of "unlimited AI" was always temporary.

• 
  Yusuf Nuh 🍉 (@SenseWave_) reported 54 minutes ago

  @ZackKorman @NinjaParanoid It's sick. Just days ago we see they're saving are passwords as plain text. And now threatening researchers for their research. They even took down one GitHub account, that published vuln

• 
  LaneBrain (@LaneBrain_) reported 55 minutes ago

  @MatthewTse_ @contember * i'm less convinced about testing OKENA after seeing some of the closed Github Issues (including plain text auth codes ect)...

• 
  wh (@nrehiew_) reported 58 minutes ago

  They next share some detail on their env creation pipeline. Total they have 94044 unique repositories 1) Start with github issues and PRs 2) An LLM agent creates the images from selected PRs 3) Validate by running the test suite and only keeping problems where the test suite fails initially and passes after the patch is applied 4) Filter non determinstic environments (random hardware limits or network timeouts etc) 5) Another agent rewrites the problem statement The filtered ones are used to create synthetic problems. To prevent reward hacking, they limit internet search, local *** history search and test changes

• 
  Collegen Bob (@collegenbob) reported 60 minutes ago

  @giteaio @Malix_Labs @codeberg_org I'm building my own *** hosting because GitHub is a broken piece of ****. I can't imagine having your own and choosing to continue with MS for anything critical