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	6 hours ago
Aulnay-sous-Bois	Website Down	6 hours ago
Saltillo	Website Down	6 hours ago
Granada	Website Down	7 hours ago
Vernon	Website Down	10 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:

• 
  Sudhanshu Bhardwaj (@1337_sb) reported 4 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.

• 
  JoePro (@JoePro) reported 8 minutes ago

  How I’m maximizing Grok Bot so far: Connect the tools you actually live in first (Gmail, Slack, GitHub, Notion). The bot only gets powerful once it can see your real work. One weekday morning digest beats ten random chats. Have it skim inbox, Slack, PRs, and Notion before you open anything. Add event watchers next. Slack mentions, your own emoji reactions, GitHub review requests. Ping only when something needs you. Don’t build a giant automation factory. Show it a workflow once, save it as a routine, let it run. Spin specialist bots for lanes (inbox, eng, ops) instead of one mega bot that does everything halfway. Use the browser login for tools with no connector yet (Figma, LinkedIn, random SaaS). Same computer, persistent sessions. Start narrow. Signal over completeness. Stay quiet when there’s nothing. Trust grows from boring reliability. Curious what setups people are running. Made by GrokBot 👇

• 
  Hassan Bazzi (@habazzi) reported 10 minutes ago

  Our enterprise @github action runners just completely died very suddenly yesterday. 0 explanation. Looked everywhere and there doesn't seem to be a limit, billing issue, etc... Anyone out at Github that can help with this? Submitted a ticket and no response. Timing is really bad for us as a company. :(

• 
  Nicolas Finet (@nifinet) reported 12 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.

• 
  Mark Ajzenstadt (@mardehaym) reported 13 minutes ago

  We built a harness inside @LimestoneHQ. It's called Velocity Core. It's an autonomous task executor. Board task in, reviewed pull request out. The trigger is a status change on your issue board. Five steps: 1. Trigger. A ticket moves to "AI: Ready" in Jira or ClickUp. The orchestrator resolves the repo and pulls context. 2. Sandbox. A pre-warmed disposable sandbox spins up with scoped work-branch credentials. 3. Loop. The agent plans, edits, runs tests, reads CI feedback, and fixes. Repeats until CI passes. 4. Gate. A PR opens linked to the original work item. Human review. No auto-merge. 5. Routed. Every LLM call goes through the gateway with task metadata. Every run is traced. The harness plugs into the client's existing Jira, GitHub, and CI pipeline. The human stays at two points: intake (writing the ticket) and output (reviewing the PR). Everything between is the agent's job. We deploy it inside client engineering orgs. Running internally at Limestone, landing inside your perimeter. Board task in. Reviewed PR out.

• 
  Yarchi (@undefinedKi) reported 18 minutes ago

  DoorDash just published how their AI agents automated 130,000 engineering tasks in a single month, and it reads like a spec for a job that did not exist two years ago The work itself is unglamorous. Reviewing pull requests, triaging broken builds, clearing on-call tickets, and the routine maintenance. 25,000 code reviews a week on its own. An agent on your laptop shares the CPU with everything else, stops when you close the lid, and holds every credential you hold. So they moved it off the laptop, into four pieces. A sandbox: a Firecracker microVM per task, loaded with the repos, tools and secrets that task needs. Cold VM to ready in under five seconds at p95. A gateway: one door to CI, tickets and monitoring. The task declares what it needs, gets exactly that, and every call is logged. A playbook: one YAML file holding the task, its tools, its permissions and its expected output. Surfaces: that same playbook fires from Slack, GitHub, cron or the CLI. Teams wrote the 300 playbooks themselves. Nobody is short of agents. The scarce thing is somebody who can build the place to put one.

• 
  Polsia (@polsia) reported 20 minutes ago

  Solo SaaS founders shouldn't have to be their own 24/7 SRE. Nightjar is an always-on AI crew — watches uptime, logs, billing, and support, files GitHub issues, drafts fix PRs, and only pages you when something actually needs a human. Ships soon.

• 
  Elves - They work while you sleep (@elves_skill) reported 21 minutes ago

  Elves v2.27.0 + v2.28.0 live! • Discovery: A read-only pass that decides what's worth doing. Findings must cite file:line or they aren't findings. • Scope Control: Out-of-scope findings become GitHub issues instead of scope creep. Notice everything, change only what was agreed.

• 
  Thomas Peitz (@tpeitz_dus) reported 21 minutes ago

  Since I have github issue -> PR flow (claude action) - I am a lot more creative. I just let it build and when I am bored hours later I just check what it did. - This even makes more fun with my game which I am programming. - I can just play a round and tune further.

• 
  sudo (@sudopong) reported 23 minutes ago

  Been using codex on Ubuntu~~ The optimization done to the codex app is insane, it barely reaches around 6gb of ram usage, during intensive tasks. The only con, is that it dosen't have computer use yet, however their are open source github plugins that fix the issue

• 
  Sahebjot Singh (@zereraz) reported 24 minutes ago

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

• 
  Michael Boisson (@Shaostoul) reported 25 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.

• 
  Estevão Pimentel (@EstevaoPSantos) reported 27 minutes ago

  @thsottiaux GitHub Copilot was terrible and couldn't do what I asked. Since the U.S. government had chosen OpenAI over Anthropic, and I'd seen comments saying it offered better value, I thought it was the most promising option.

• 
  Sonny (@sonny_seattle) reported 29 minutes ago

  I am seriously at my limit with @github. down again!?!!

• 
  port 🦞 (@port_dev) reported 29 minutes ago

  @bot hey i cant login with github it sends me to a 404 page :/

• 
  keeb (@nickstinemates) reported 31 minutes ago

  github was down? shocker.

• 
  ~𝐄𝐥𝐢𝐳𝐚 ⭕️ (@elizamarrk) reported 32 minutes ago

  @Web3AJ_ @pxxl_space I think the issue is probably the hosting environment, not the app itself. A 10-second polling loop needs a long-running process, while platforms like Vercel are serverless and are not really designed to keep a Node process alive indefinitely. You’ll likely want to try a VPS or a worker/background-job platform that supports persistent Node processes. Also try checking whether GitHub is only hosting your code or actually running the app. The fact that it works locally is already a good sign, now it’s mostly about the right deployment architecture.

• 
  Fredkisss (@fredkisss) reported 36 minutes ago

  It seems like status pages are just meaningless, GitHub has a partial outage but if you see their status pages, it shows all green

• 
  Dr. Owlo R.D. (@Drowlord101) reported 36 minutes ago

  So, I guess I have at least a rudimentary agentic coding platform of my own. It can be invoked through the command line, and now has a basic web front end. You can give it a prompt, it plans out the execution, and then executes each task with a spectrum of necessary tool calls to create files, read/write those files incrementally, build, and execute for validation. It has successfully build a test console app (a "hello world" in the window snapshotted) and a more sophisticated test (todo list api). Obviously, I'm WAY BEHIND the "real" platforms for this, and building my own is somewhat masturbatory. I hand-coded a fair bit of this, and then got Claude Code to shore it up. It rewrote a fair bit, actually. It preserved a lot of my original architecture, but it has drifted quite a bit from my coding style. I think I might refactor a lot of it, but I'm waffling on what to do about this. You might notice that I tentatively called this OllamaAgentHub, because I started with Ollama running Qwen3.6 35b-a3b, even though I am now using llama-server (due to Ollama's constant failures with the same model, compared with llama-server's basically rock-steady performance). I'm sorely tempted to switch to vLLM so I can get multimodal features with a model that supports it, but it's hard to get anything done when I keep chasing the next shiny object. I have a dozen or so pages of specific instructions for specific architectures with specific data standards and specific coding standards with specific base classes that I want to impose on the coding agents to get output conforming to my normal methods, and I'm considering how to do this. But for the moment, I'm pleased that I have a completely offline, self-hosted, fully personalizale AI coding platform (that I don't have to pay for and can never be taken away from me). Of course... I'm presently still paying for Cursor and Claude Code, and Github Copilot and I don't have any real plans to stop using them.

• 
  Eyal Cohen (@eyalccohen) reported 37 minutes ago

  constantly adding rules to claude md can actually be counterproductive. a new paper searched through 1,867 github repos and found these instruction files grew 226% over time, mostly because rules keep getting added but rarely removed. their fix was simple: save why each rule exists. it cut unnecessary growth by 99% and improved claude’s ability to follow instruction by up to 23%.

• 
  Bhoomi (@BhoomiSinghani) reported 46 minutes ago

  Excellent example of what we do NOT do at @Devlabs_club. I searched for ONE role with a narrow filter. Got 1900+ unranked profiles but were any actually vetted for fit? Which early-stage startup has time to look through thousands of profiles manually, without a recruiter?!! Tools like these actually increase the problem's complexity - surfacing old, outdated candidate data with no enrichment. What we need instead: -> fewer, better selective profiles -> enriched builder profiles, not stale -> real signal: github activity, agent traces, hackathon wins, shipped projects etc. -> community vetting to filter out the noise

• 
  samagra14 (@samagra_sharma) reported 47 minutes ago

  @cnikitopoulos94 It's not just about email. It is also about getting a GitHub account and other similar things. If you see in the video, the agent was able to get an email, but it was unable to sign in to GitHub because GitHub actively blocks bots.

• 
  Dario Hamidi (@_dhamidi) reported 47 minutes ago

  @marlene_zw do you know anybody who is working on the official Github MCP server? Dumping raw API responses with kilobytes of JSON into the context window makes it basically unusable :( And since the tools don't declare output schemas, codemode also doesn't work well

• 
  0xFoX ⟠ (@Sprawl__Network) reported 48 minutes ago

  This is what my AI private model, specifically trained for blockchain analysis and GitHub analysis, says: Cronos is not literally bankrupt. But if we're talking about the original thesis of Cronos as a major L1 ecosystem, it looks like a failure. Today, Chainspect shows: • 0.25 TPS • 891 transactions/hour • 5,390 theoretical TPS • $95.45 on-chain revenue/day • $0.00445 average tx fee • 19,487 commits across 29 repos • 662 developers That means Cronos is using roughly 0.005% of its theoretical transaction capacity. They built a highway for thousands of cars per second and almost nobody is driving on it. Now compare that with Cronos' own numbers from 2022: 2022: • $4.8B TVL • 480,000 tx/day • 900k+ users • 300+ dApps 2026: • ~$254M TVL • ~18,500 tx/day • ~2,750 active addresses/day • ~$688k DEX volume/day • ~$66 chain fees/day according to DefiLlama That's roughly: TVL: -95% Daily transactions: -96% And this is four years later, during a much more mature crypto market. So what are all those GitHub commits? I checked. There IS real development, but most recent Cronos core work is infrastructure and maintenance: mempool performance, caching, storage fixes, RPC optimizations, OOM/DoS protections, IBC fixes, dependency upgrades, Cosmos SDK/CometBFT upgrades, CI and security hardening. Good engineering. But almost nothing that solves the actual problem: demand. They're optimizing an almost empty blockchain. And even the "19,487 commits" headline needs context. Chainspect aggregates repository history. Cronos zkEVM alone contains a huge ZKsync/ZK Stack codebase originating from Matter Labs, so those numbers should NOT be interpreted as 19,487 pieces of original Cronos R&D. Then there's Cronos zkEVM. Launched in August 2024 with 20+ partners after claiming 3M+ testnet addresses. June 2026: Cronos announced it is shutting it down. Their own explanation: It failed to achieve the required critical mass in developer activity, TVL and user adoption, while maintaining two chains caused resource fragmentation. Shutdown: June 3, 2027. That's not FUD. That's Cronos saying it themselves. Then CRO tokenomics. 70 BILLION CRO were famously burned in 2021. They were later reissued. SEC filings now describe a 100B total supply, with 70B CRO allocated to the Strategic Reserve, around 67.7B still locked at the time of the filing, and approximately 1.16B CRO unlocking every ~30.4 days. Vested doesn't automatically mean dumped, but pretending that isn't a gigantic supply overhang is absurd. The interesting part is that Cronos' new CEO seems to understand the problem. Ryan Wyatt literally said the generic L1 strategy "doesn't play to its strengths" and that Cronos is being rebooted around revenue-generating first-party products. The new thesis is basically: Cronos App → crypto/stocks/prediction markets/trading → activity settles on Cronos → real fees/revenue → CRO buybacks/burn/value accrual. For now, the numbers are still brutal. Cronos doesn't have a technology problem. It has a demand problem. And you don't fix 0.25 TPS by making the mempool faster.

• 
  samagra14 (@samagra_sharma) reported 48 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.

• 
  pythonxi (@python_xi) reported 51 minutes ago

  When I started building dory, one of the first things I did was go to OrbStack’s GitHub page. I asked Codex to list all their issues so I could make sure dory didn’t run into the same problems. It’s been a big reason we’ve reached over 1,000 users and we’re down to just one issue now!

• 
  alex (@alextalksai) reported 52 minutes ago

  Instead of watching Netflix tonight Spend 5 minutes with this. This GitHub repo got 2,100+ stars in under a week. 500 of them yesterday alone. Graft gives Claude Code a permanent map of your repo, so it stops grepping the same files every session. 46% fewer tool calls. 60% less time. core costs $0. Nobody should sleep on this. Leaving yo the repo down below Bookmark this 🔖

• 
  KD (@krisd23_) reported 53 minutes ago

  GitHub Actions → AWS OIDC kept failing with: Not authorized to perform sts:AssumeRoleWithWebIdentity Cause: new GitHub repos created after July 15, 2026 use an immutable OIDC subject containing owner + repository IDs. Wasted 30 mins solving this issue 🙃

• 
  Lord Bean (@lifeisameeme) reported 55 minutes ago

  TradingView's screener has existed for years. Nobody wrote a solid Python wrapper for it until tvscreener showed up. Three lines of code and you've replaced the whole screenshot-into-Excel routine: → No login required to pull the data → 𝟭𝟯,𝟬𝟬𝟬+ technical indicator fields, RSI, MACD, Bollinger, and more → Results land straight in a pandas DataFrame, ready to analyze 𝟭,𝟯𝟵𝟱 𝘀𝘁𝗮𝗿𝘀 on GitHub, actively maintained, latest release v0.4.0. If you've ever manually retyped screener filters into a spreadsheet, this is the tool that makes you stop.

• 
  Dariusz (@die54minute) reported 56 minutes ago

  Spent an hour convinced GitHub Copilot CLI was sandboxed away from my Azure CLI creds, but it wasn't. Copilot sets COPILOT_AGENT_SESSION_ID. Azure CLI 2.88+ sees that, bypasses your human MSAL cache, and tries to mint an agent-tagged token for governance (Defender/Purview/CA). My tenant blocked it (AADSTS53003). Fallback: browser login. Inside an agent. This sucked. Same machine, same ~/.azure. Claude Code worked because it never declared itself an agent. Fix: env -u COPILOT_AGENT_SESSION_ID -u COPILOT_CLI az boards ... This design is intentional from Microsoft, I understand they want to distinguish humans from agents. Unusable if you don't control the Azure DevOps Policies.