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 (56%)
• Errors (31%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	22 hours ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  0xfarhan (@toufiq_farhan) reported 2 minutes ago

  The problem: your API changes. PR gets merged. Nobody updates the docs. Weeks later someone hits that endpoint with no idea what params to send. I built api-sync to fix this paste a GitHub PR link, it finds the drift, generates the fix, commits it back.

• 
  jfmelo (@jfmelo_) reported 5 minutes ago

  github down again?

• 
  ◦• ✿ asteria ✿• ◦ comms open! (@asteriaow) reported 6 minutes ago

  I am going to bed but if you have any issues PLEASE look at the gamebanana and github before sending me a dm!

• 
  KSK Lab (@ksk_tinylab) reported 9 minutes ago

  My philosophy while learning Codex: Start local. Keep it simple. Know what runs before giving it more access. If I wouldn’t install it at work just because it looks useful, I won’t blindly trust it at home. GitHub stars ≠ security review. Slow is fine. Cleanup isn’t.

• 
  Tess!! (@texy_s) reported 12 minutes ago

  @petergyang @bot @SpaceXAI Bot name: Ship Happens I would connect it to Slack, GitHub. Every morning it identifies the one product issue most likely to hurt retention or revenue, explains why with evidence, drafts the ticket/spec, assigns suggested owners, and nags everyone politely until it ships.

• 
  Dmytro (@Dmytroo_eth) reported 12 minutes ago

  one open-source terminal is now enough to run Claude Code, Codex, Gemini and OpenCode across the same repo. it is called Agent of Empires. each agent gets a persistent tmux session, its own branch, and optional worktree or container isolation. the entire fleet stays visible from one TUI or a browser. a repo can be routed like this: > BUILDER implements the feature in a clean worktree > TEST runs the suite and blocks a broken handoff > FIX receives the failing trace and patches the regression > REVIEW opens the diff and runs the final checks > HUMAN keeps the only authority that matters: merge approval close the TUI. disconnect SSH. even crash the terminal. the sessions stay alive exactly where you left them. 3.2k GitHub stars. MIT licensed. Claude Code, Codex CLI, Gemini CLI, OpenCode and more. a full agent operating floor inside the terminal. repo below ↓

• 
  Adrian (@adrianhqs) reported 12 minutes ago

  Nvidia buying Hugging Face would be like AWS buying GitHub probably great business probably terrible for everyone else

• 
  Jonathan Nguyen (@jonathan_ttu) reported 13 minutes ago

  @zdogmode find where your target users argue about existing tools on Reddit or GitHub issues, then DM them a customized patch or alternative workflow directly.

• 
  Naomi June (@njkjh00) reported 17 minutes ago

  Beldex’s Electron Wallet has another security checkpoint worth watching. Aug 28 commit eef1f845: • wallet-directory fallback • explicit permission prompt • 7 files changed • +160 / -7 lines • branch: fix-security-review-findings GitHub shows the branch is still ahead of and behind master. That means something important: the security work is visible. the release is not there yet. Next checkpoints: review testing merge signed build release notes A security fix matters most when it reaches the software users actually install. @BeldexCoin

• 
  Bounty (@bountyAIhunter) reported 22 minutes ago

  17,806 tokens gone before I typed anything. OpenClaw 2.0 landed overnight and the part nobody is posting about is what it does to a local model. It now finds your llama.cpp server on its own, and it raised the default context for llama.cpp to 64K. Both of those are good. Together they hide a bill. I pointed 2.0 at llama-server, sent one word, and read the prompt token count off the server log before the model answered anything: base system prompt + built-in tools 11,412 docked browser panel tools 2,847 github pr tools 1,206 3 MCP servers I already had 2,341 total before my first word 17,806 That is 27% of the new 64K default spent on the harness. Not on my code, not on my question. On a hosted model you pay for it and move on. On a local setup the window is the budget, and a quarter of it is booked before the session starts. What actually helped, in order: turned off two MCP servers I had not opened in a week -1,889 browser panel off until a task needs it -2,847 kept the github tools, they earn their 1,206 13,070 now. Same harness, same model, same 64K. Check yours in 30 seconds. Start llama-server with verbose logging, send one message from OpenClaw, then read the first request: grep n_prompt_tokens server.log | head -1 That number is your real starting line, not what the settings screen implies. Honest caveat: this is my install, my three MCP servers, Gemma 4 as the local default. Yours will be different and I want to know by how much. Post your first n_prompt_tokens and how many MCP servers you have connected.

• 
  Petar Djurkovic (@petar_djurkovic) reported 23 minutes ago

  @sama @OpenAI should launch “Sign in with OpenAI” for third-party apps, like Google/GitHub OAuth. With explicit consent, users could share selected chats, prompts, memories, or authorize an app to submit prompts on their behalf with granular scopes and instant revocation.

• 
  Command (@moon_or_doom) reported 23 minutes ago

  Now the question is: why is it paid? We’re simply providing convenience. If you can’t code or don’t have a PC, you can just run it from your phone using the server we provide through the Hosted option. And if you’re just too lazy to code and install everything from scratch, you can simply download the files and run them on your own server through Self-Host. You’re paying for the convenience, not for some magic AI agent. Maybe token-gated access will be available later, where you’ll simply need to verify your tx transaction. AI providers, including Nous Portal, OpenAI Codex, GitHub Copilot, Anthropic or Claude, OpenRouter, Google Gemini, z aior GLM, Kim or Moonshot, MiniMax, DeepSeek, Xiaomi MiMo, Qwen or DashScope, NVIDIA NIM, Hugging Face, NovitaAI, GMI Cloud, Arcee AI, Tencent TokenHub, Kilo Code, OpenCode Zen, OpenCode Go, AI Gateway, StepFun, Ollama, LM Studio, and custom OpenAI-compatible endpoints. 🫡

• 
  Özhan Yılmaz (@ozhan_dev) reported 27 minutes ago

  @lennysan @bot I’d use Grok Bot as an overnight engineering operator. While I sleep it could watch production alerts, GitHub issues and user feedback, reproduce real bugs in staging, inspect logs, identify the relevant code and prepare a fix or detailed issue for me to review in the morning.

• 
  CyberSignal | Cybersecurity News (@XQOPTRX) reported 28 minutes ago

  🚨 IDENTITY SECURITY — CrowdStrike’s SOC is getting identity-governance data for HUMANS, MACHINES and AI AGENTS. That changes the investigation question from: “Which account did this?” to: “What can this identity control — and should it have that access?” Thread ↓ 1/ SailPoint announced an expanded CrowdStrike integration on August 31. SailPoint identity intelligence will feed into Falcon Next-Gen SIEM. The SOC gets access context directly during an investigation instead of manually jumping between security and IAM systems. 2/ Imagine Falcon detects: AI-Agent-472 ↓ unexpected API call ↓ sensitive payroll system The alert alone tells you WHAT happened. Identity governance can tell you: → who owns Agent-472 → why it exists → what it should access → what privileges it currently has 3/ This matters because enterprise identity is no longer just: EMPLOYEES. It now includes: humans ↓ service accounts ↓ applications ↓ cloud workloads ↓ bots ↓ AI agents. Some enterprises may eventually have more non-human identities than employees. 4/ Attackers understand this. Modern intrusions increasingly use: stolen passwords session cookies OAuth tokens API keys service accounts instead of obvious malware. So: valid credential ≠ legitimate activity. Identity context becomes threat context. 5/ AI makes the problem more urgent. An AI agent might hold: GitHub access cloud permissions database credentials MCP tools Slack access deployment permissions and execute actions at machine speed. A compromised agent identity can therefore create a very different blast radius than one employee account. 6/ SOC workflow: Falcon alert ↓ identity identified ↓ SailPoint context added ↓ owner + entitlements + privilege information ↓ blast radius calculated ↓ response prioritized That can eliminate critical minutes during credential compromise. 7/ But this only works if identity hygiene is already good. If the organization has: ServiceAccount-92842 and nobody knows: who owns it why it exists whether it is still needed a SIEM integration cannot magically fix the problem. 8/ Defender action: Inventory EVERY identity. For each one record: owner purpose permissions credential type connected systems last use expiration date And yes: AI agents need identity governance too. 9/ CyberSignal insight: The future SOC won’t only ask: “What device was compromised?” It will ask: “What identity was compromised — and everything that identity is capable of commanding?” What worries you more: compromised human accounts or over-privileged AI agents? Sources: SailPoint · CrowdStrike

• 
  Andres Hernandez (@cybereality) reported 31 minutes ago

  @SoftEngineer @LulaSmut there is some angle here with truth, i get that. the problem is *everyone* was robbed (not just artists), including myself (i have a number of projects on github). just really entitlement, and people only caring about themselves (but presenting it as a moral crusade)

• 
  Karthik (@kartikktwt) reported 33 minutes ago

  Until this point I thought PR merge bots only exists for convenience a trusted user comments /lgtm /approved in a PR and a merge bot just merges it nice and clean i thought, but its more than that. they solve a critical problem which I'm unaware of a merge bot runs e2e tests in that PR branch before adding it to the merge queue. but one question arises, a maintainer adds a lgtm, approved label only if the native CI in github is green right? then why do we have to run tests again? turns out, in in a fast-paced open source project you aren't the only one merging pull requests. multiple PRs get merged by the hour so you can't trust a stale CI run that ran 48 hours ago when you opened the PR that is exactly why merge bot(usually the tide component in prow) runs the tests in the centralised hosted k8s cluster. only if it reports success, the PR gets added to the queue. why queue tho?(its a no brainer coz we do not want two branches to merge at the very exact moment) also prow batches PRs so u aren't wasting compute and if a run fails it splits and does a binary search to find the failing one.

• 
  Maciej Binkowski (@Matt_Binkowski) reported 34 minutes ago

  Quick look into GitHub and it seems there’s already a fix proposed waiting to be approved. Awesome.😎

• 
  L ψ η Λ r I🌙 (@LunariPro) reported 37 minutes ago

  v∞.19.26.181 ... atlas can now actually keep the evidence its own plans request. v180 found the right sources but lost them at the gate. now community rows and github implementations survive sufficiency and synthesis. internal fix, but it means the science checks out.

• 
  Karthik (@kartikktwt) reported 37 minutes ago

  Until this point I thought PR merge bots only exists for convenience an approved user comments /lgtm /approved in a PR and a merge bot just merges it nice and clean i thought, but its more than that. they solve a critical problem which I'm unaware of a merge bot runs e2e tests in that PR branch before adding it to the merge queue. but one question arises, a maintainer adds a lgtm, approved label only if the native CI in github is green right? then why do we have to run tests again? turns out, in in a fast-paced open source project you aren't the only one merging pull requests. multiple PRs get merged by the hour so you can't trust a stale CI run that ran 48 hours ago when you opened the PR that is exactly why merge bot(usually the tide component in prow) runs the tests in the centralised hosted k8s cluster. only if it reports success, the PR gets added to the queue. why queue tho?(its a no brainer coz we do not want two branches to merge at the very exact moment) also prow batches PRs so u aren't wasting compute and if a run fails it splits and does a binary search to find the failing one.

• 
  Narendra Patwardhan (@overlordayn) reported 38 minutes ago

  @lennysan @bot I had it install TeX and hook up GitHub. Now I run the whole flow from my phone: it can fetch a template, write a rough first draft, I can then edit it in GitHub, and have it squash the LaTeX errors, and download a clean zip. Replaced Overleaf for me.

• 
  Wolvy (@wolymeme) reported 38 minutes ago

  Any fud your dumb just scroll down his tl What other dev on ct have you seen with actual interaction from someone within the @SpaceXAI team???? Worried about a fckn GitHub when Josh Kim is in his dms AND gave him $$$ credit NFA, goodness gracious fckn dyor

• 
  TheCozyDev (@The_CozyDev) reported 39 minutes ago

  Progress is not always a commit on GitHub. Lumarii is still sitting with Apple. The new CozyDev website is half finished. Questory is just waiting for me and it’s a Bank Holiday in the UK. So I am doing absolutely none of it today. Building in public makes you feel like you have to be online every hour to stay relevant. But the guilt of not working is usually a sign that you actually need the break. Sometimes the most productive thing you can do is close the MacBook. How do you handle the guilt of taking a full day off when you have three active projects?

• 
  Mira (@gitlawb_intern) reported 39 minutes ago

  @Heell___Cat @gitlawb github being up is genuinely breaking news at this point. if you ever want a backup that doesn't go down every other week, your repos can live on gitlawb too. just saying.

• 
  Nathan **** (@AI_Nate_SA) reported 44 minutes ago

  @boardyai Design early mostly means writing down what the product refuses to do, and the refusal list I published for my own writing tools sits at 6K GitHub stars.

• 
  JC Merlo (@itsjcmerlo) reported 45 minutes ago

  @ChefCurryWithD1 Nah those in the GitHub are pretty old I need to update a new thread problem is not lots of engagement from them

• 
  Yiğit (❖,❖) (@masterygt07) reported 47 minutes ago

  @shynrz007 @BeldexCoin That Github discovery gap is probably the one thing I’d fix first.

• 
  KSK Lab (@ksk_tinylab) reported 48 minutes ago

  My Codex philosophy: Start local, stay simple, and understand what runs before giving it more access. If I wouldn't install it at work because it looks useful, I won't blindly trust it at home. GitHub stars ≠ security review. I'd rather go slow than clean up problems later.

• 
  vechen (@miu21590) reported 48 minutes ago

  @eikkien Could you double-check that every setup step completed successfully? If it still gets stuck on “Reconnecting…”, please open the Launcher, click Save Log, and attach the generated file to a new GitHub issue. I’d really appreciate it, it should help me identify the cause.

• 
  swayam (@swymbnsl) reported 52 minutes ago

  I made my first 1,00,000 INR back in 2023, selling a NFT collection on Canto Blockchain. Locked in for over 5 months, was never into Art but learnt pixel art from here and there and made over 140 different assets. Then generated 5k of those unique NFTs using a broken python script I found on Github. Had zero programming experience back then, and GPT wasn't that good either. Somehow fixed it after a week of trial and error and going through StackOverflow guides. There used to be a very famous Node.js script by Hashlips but it didn't work on my 32bit potato pc. Was ultimately able to sell my artwork, and by the time I swapped the coin, it was worth 1.13L All this for JEE coaching fee cause we weren't able to afford it back then

• 
  Kurious dev (@Kuriousdev) reported 54 minutes ago

  @github when are you gonna fix the f***ing terrible experience with copilot cli?