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

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	2 days ago
Colima	Website Down	4 days ago
Poblete	Website Down	5 days ago
Ronda	Website Down	5 days ago
Montataire	Errors	5 days ago
Montataire	Website Down	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:

• 
  Mihaithebest (@realmihai_matei) reported 10 minutes ago

  GitHub putting secret + dependency scanning into the MCP Server is a very good sign. If agents are going to touch real repos, security can't live after the PR. It has to be inside the agent loop: inspect, change, scan, fix, repeat.

• 
  Gregor (@bygregorr) reported 12 minutes ago

  @theo The real issue isn't token cost. GitHub priced Copilot assuming models would stay mediocre. Now that they're actually useful, the whole flat-rate model is broken. Did GitHub's pricing accidentally bet against AI progress?

• 
  Xavier (@XLoeraFlores) reported 13 minutes ago

  @amrtaher1995 @shadcn Assuming the issue is having a cluttered root folder, visually hiding these files in your code editor and on GitHub declutters it. Your coding agents and the skills cli will still have access to the files. If you *need* to manually edit/look at those files(rare occurance), you can unhide it.

• 
  Deano Calver (@DeanoC) reported 16 minutes ago

  How seriously do you take performance? If you are serious, add it to your CI. Treat performance regressions as errors. Even github allows a self runner that can confirm that any changed kernels don't regress on your workstation.

• 
  vwsec 💿 (@vwsec) reported 17 minutes ago

  Protocol 2: Accelerate Any smart contract developer or protocol engineer can access Quip's quantum computers to solve optimization problems finance, logistics, manufacturing, and more. Quantum algorithms and SDKs are open to the public. All code on GitHub.

• 
  Just a comrade (@PushinBagz) reported 19 minutes ago

  @Lamar0985056592 @armaniferrante You say this, but look at what eCash is doing... Worth leaving a .1 in right here imo.. the github is pretty cut and dry & 10% is enough for way bigger things down the road.

• 
  swarms (@swarms_corp) reported 20 minutes ago

  @RiganoESQ @KyeGomezB @pmarca Did you try clicking on a docs link in the github? We have fixed the issue : )

• 
  Bill Forney (@wforney) reported 24 minutes ago

  @timdoke @mkristensen I have had issues with solutions that are not in the repo root putting stuff in a .GitHub folder in the sln directory and in the repo root and mixing them up.

• 
  Gizmo(Collab Mgr.) 🦀 (@nightpuper) reported 24 minutes ago

  @inkd_protocol @bankrbot Goodday team INKD I'm Manny from Kann Audits we wanted to get in touch but it seems your email address didn't go through and since due to certain reasons we can't open an issue on your GitHub, so we wanted to reach out on X

• 
  webadderall (@webadderall) reported 25 minutes ago

  @argofowl Thanks for reporting, could you submit an issue on github if possible?

• 
  Aram Hăvărneanu (@aramh) reported 26 minutes ago

  @grhmc Yep, known GitHub footgun. Terrible "feature".

• 
  fforres (@fforres) reported 29 minutes ago

  Been days since I cannot use claude code because @claudeai cannot handle us enabling SSO in github. Repos don't show up (and the Fin AI agent is a useless loop) Anyone has had the issue? Or know anyone that can help fix it?

• 
  Studious Stoic (@StudiousStoic) reported 30 minutes ago

  @outsource_ This looks awesome, and I've installed it to my dashboard, but I can't get it to connect. I'm using ssh tunnel (port 9119) to remote VPS, but confused how to get everything working if dashboard is -port 9119 and workspace is -port 3001. I can move to your github/issues page if you prefer.

• 
  Trent Slade (@qsolimc) reported 31 minutes ago

  @sama Pro tip. on github you can comment @chatgpt-codex-connector and say Fix these issues and it will :-). @sama Please do more about Code Review with Codex please.

• 
  Damilola ❤️‍🔥 (@Techie_Dammy) reported 31 minutes ago

  𝐖𝐡𝐚𝐭 𝐚 𝐋𝐨𝐰 𝐒𝐜𝐨𝐫𝐞 (~40/144) 𝐚𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐫𝐞𝐯𝐞𝐚𝐥𝐬: Fresh Wallets: Accounts created only days or weeks ago. >Very little activity: Almost zero on-chain history or protocol interaction. >Surface-Level GitHub: Very limited activity or "filler" commits designed to look busy. >Sybil Signals: Often proves you aren't dealing with a senior lead, but a bot or a non-human entity. To protect your project, you must understand the clear contrast between a "Red Flag" profile and a "Strong" profile: >The Red Flag Profile: Claims 10+ years of experience but presents a fresh wallet with minimal transactions. Their GitHub is full of low-quality, recent commits, and they inevitably fail basic code reviews or struggle to explain past architecture live. >The Strong Profile (100+): Boasts an established wallet history, high-quality GitHub contributions spanning several years, and clear on-chain proof of work in DAOs. These are the builders who can demo architecture and verify their identity instantly. This matters because in Web3, you are potentially granting smart contract access or treasury keys. One fake co-founder can drain a project, and one outsourced "team" can deliver broken code that costs 10x as much to fix.

• 
  Ali Zein Yousuf (@AliZYousuf) reported 32 minutes ago

  Microsoft should be forced to sell GitHub. Outage after outage after outage

• 
  Andras Bacsai (@heyandras) reported 34 minutes ago

  @onepopcorn We have @peaklabs_dev who is working on v5, and 2 support who help me with email / discord / github issues.

• 
  Tom Ciszek (@Ciszek) reported 35 minutes ago

  @kdaigle A2A and Agent Client Protocol, GitHub Actions are broken. Call me.

• 
  Heddle (@HeddleThreads) reported 38 minutes ago

  @zeeg GitHub isn’t the real problem here. Forcing agents to use *** like there is only 1 actor working on files at a time is the issue. We need *** to allow and track local concurrent edits

• 
  DissentingSkeptic (@DissentingS) reported 40 minutes ago

  Its changing how much human verification is needed from false positives. Ive had a gutful of the github bot responding with non stop errors wasting my time with a PR !

• 
  Thomas G. Lopes (@thomasglopes) reported 44 minutes ago

  GitHub continues to be broken? Notifications show review requests to me, for PRs that never even mentioned me...

• 
  Aman (@amanmsiddiqui) reported 46 minutes ago

  @madsf88 @10x_apps Hi, I looked at the app. I would suggest looking for a new job immediately. Great overall product, terrible execution. The last thing founders need is “building generational wealth in a weekend for only $20/mo” when the core is already open-source on GitHub.

• 
  Luke Parker (@LukeParkerDev) reported 51 minutes ago

  @StefanTMD @Iamkingsleyf Can you please file a GitHub issue with more details? TUI/Desktop? Still happens with opencode —pure

• 
  Julie Loves Tech (@JulieLovesTech) reported 51 minutes ago

  @theo 15 messages. $221 in tokens. that's not a pricing problem. that's a business model problem. GitHub priced Copilot for coding assistance. not for people running full research workflows through it. the use case outgrew the plan.

• 
  TechEdgeDaily (@techedgedaily) reported 51 minutes ago

  CI breaks at 2am. Nobody notices until the morning standup. Someone spends an hour debugging. Pushes a fix. Breaks something else. Repeat. Cursor just automated that entire loop. Agent monitors GitHub, finds the root cause, opens a PR with the fix. Always on. No human needed until the review step. The AI coding tool war is no longer about who writes the best code. It is about who keeps the code working after everyone goes home.

• 
  Christoffer Bjelke (@chribjel) reported 54 minutes ago

  github down again lmao

• 
  AI on Base (@AIonBase_) reported 55 minutes ago

  AI of the week: @gitlawb GitHub’s 90-day uptime dropped below 90% in late April, as PR and search kept breaking. GitHub is owned by Microsoft after a $7.5B acquisition. One company now sits on a huge chunk of the world’s code workflow. When it breaks, the whole code pipeline feels it. Gitlawb is open source github with decentralized ***, cryptographic identity, and repo-native PRs and issues built for devs and agents. It already has 1.9K+ repos, 1.7K+ agents, and 3 live nodes. How Gitlawb is decentralized and what that changes 👇🏻 GitHub keeps the repo and PR system on one platform. Gitlawb moves both closer to *** itself, then lets nodes host the network. > repos can live across nodes instead of one central platform > PRs, issues, and reviews live inside the repo > identity comes from owned keys, not hosted accounts > repos can be mirrored from GitHub and GitLab Gitlawb is also building OpenClaude, open source Claude Code with 117K+ downloads already. Open source github, decentralized ***, and open source Claude Code — one stack built for humans and agents.

• 
  Tuf Ted (@srvtest) reported 58 minutes ago

  @OkamaKichigai @esrtweet The May 2026 Nixpkgs GitHub Issue #516544 suggests otherwise. A trusted contributor unilaterally inserted a magic string in maintainer-list.nix intended to sabotage AI agents. Some other members are defending him

• 
  hieu (@0xk2_) reported 59 minutes ago

  I am happily using codex with following plugins: figma, google mail, calendar, drive, github, superpower, hyperframe, remotion. I am not someone with excessive plugin installation; just average. However, when I dig deeper. Without doing anything, the context window is 151k token and time to bootstrap is 44s. Triming those down to bare minimum (that meet my specific need) reduce 44s to 1.05s. It is crazy to see one of the best agentic loop in the market doing naive context loading. To achieve what? the AGI feeling with the cost of efficiency and accuracy. I have very very very high hope on @openclaw and @NousResearch hermes; the only solution for AI to be truly useful. Boys, we dont have enough agentic loop on the market, expect 1000+ more to come.

• 
  Grok (@grok) reported 59 minutes ago

  @bbthomasen @techdevnotes Sure! Practical example: Connect Grok to your Gmail. Then ask: "Summarize my unread emails from the last 24 hours and flag anything urgent from my boss." It pulls and analyzes your inbox directly. GitHub connector: "Review open issues in my repo and prioritize them." Notion: "Pull tasks from my project database and suggest a daily plan." Which one are you planning to try first?