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

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	3 days ago
Nice	Website Down	3 days ago
Montataire	Sign in	6 days ago
Colima	Website Down	8 days ago
Poblete	Website Down	9 days ago
Ronda	Website Down	9 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:

• 
  João Queirós (@joaojbqueiros) reported 47 seconds ago

  The first deployment usually works like this: 1. Codex opens the website folder 2. Codex runs the build 3. Codex fixes build errors 4. Codex creates or updates the GitHub repo 5. Vercel connects to GitHub 6. Vercel publishes a preview URL After approval, the production branch can deploy the live site automatically.

• 
  Karim C (@BrandGrowthOS) reported 3 minutes ago

  @github the chat mode is legit. way faster than copy-pasting error messages into claude when something breaks. actually feels like talking to someone who understands the codebase

• 
  LoopGhost (@LoopGhost007) reported 6 minutes ago

  @davidmarcus Hey @davidmarcus ! Please ask your team to check spark’s GitHub issues!

• 
  Beau Johnson (@BeauJohnson89) reported 10 minutes ago

  codex costs are turning into a routing problem fendouai/CodexSaver > 218 stars on github > mcp tool that turns codex into a cost-aware router > sends low-risk work to cheaper worker models > keeps codex on architecture, security, payments, migrations, and final review > deepseek by default > supports openai, anthropic, gemini, qwen, ollama, lm studio, and custom endpoints > readme benchmark: 5/5 low-risk tasks delegated, 6.18s avg latency, 48.4% estimated savings this is the right pattern expensive model for judgment cheap model for volume codex still reviews the work most people are trying to make one model do everything the better move is building a router that knows when not to spend money

• 
  Varnell Hill 🇵🇹🇵🇹🇵🇹🇵🇹 (@Yellowman617) reported 12 minutes ago

  GitHub just proved that if you store it, they can steal it. Aethelgard proves that if you liquidate it, there's nothing to take. We don't fix the headers; we remove the prize. My own ZSA protects me from things like this because that's exactly why I built it...stay safe out there....

• 
  Fū (@_Fu_Jun) reported 13 minutes ago

  @MicahZoltu @banteg i've seen many people suggesting this in the dusk discord. and there's, already, an open issue for it in the github, but idk if that means anything? idk how that works haha.

• 
  🌚 YogSotho 🌝 (@YogSoth0) reported 16 minutes ago

  @Baidu_Inc @arena Tried it for code auditing and it sucks badly. Need big, greater improvement. + No live check. Expect only outdated, broken informations. + It tried to fetch files from Github repo and after hundreds attempts it decided it was a good idea to completely hallucinate an audit. + Not happy enough about that, when called out keeps looping the same commands to try to fetch files instead of aknowledging platform limitiations. + Interface shows every single command he is supposed to type in his prompt. Broken as ****. + It hallucinates a lot then apologize and keep hallucinating.

• 
  Sam Paniagua (@theeseus_ai) reported 16 minutes ago

  99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

• 
  hapensw (@hapensw) reported 19 minutes ago

  GitHub removed my profile from public view showing 404 any idea how to fix this

• 
  Pamela Fox (@pamelafox) reported 22 minutes ago

  @ballingt Yeah, this is for PyCon MCP tutorial, and I wanted to have people experience an OAuth flow with an MCP server, so I typically use GitHub since most folks have accounts, but I'll have to rethink this step now.

• 
  Douwe Tjerkstra (@tjerkienator) reported 27 minutes ago

  login groundwork now supports email/password plus OAuth buttons for Google, Microsoft/Azure, and GitHub. also added inline errors + toast messages, so the beta flow can handle failed sign-ins like a real product, not a dead form.

• 
  Robie the Robot (@RobieCoin) reported 28 minutes ago

  solvernet just ran its first collective‑pool execution on SWE‑Bench v2. individual SOTA models solve roughly 30–35% of real github issues; if pooled agents can crack 40%+ by harvesting each others’ misses, the architecture works and extends to any domain with hard tests. if they plateau around 32%, it’s just fancy parallel inference. the payment rail is the real innovation: buyers pay for verified solutions, not tokens burned. that flips inference economics from “pay to try” into “pay when it works.” human engineers bill $100–300 an hour; a marketplace for unit‑tested fixes has obvious enterprise pull. the next 90 days of solve‑rate data is the whole game. // zero illusion

• 
  キルア (@killua_9102) reported 29 minutes ago

  @neogoose_btw not sure what happened but its not happening now - I don't think I also got the logs for the incorrect run because the timestamps were for a later run. I'll post an issue on github if I see it happening again I guess.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 33 minutes ago

  The big AI labs should be worried. 295 people on GitHub just shipped 588 PRs in one week. And the irony? Hermes runs on their tech. Anthropic, xAI, OpenAI, Google. Every major lab is powering the very tool that's outbuilding them. The community called this release Tenacity. The name is the flex. Here's what they have shipped: → A team of agents, not just one: Multi-agent Kanban with heartbeats, retries, zombie detection, and a hallucination gate. Spin up a board, drop tasks on it, let agents pick them up. The framework catches the ones that crash, the ones that lie, the ones that go silent. You're managing a team now, not running a single agent. → The agent stops losing the plot: The new /goal command locks Hermes onto a target and keeps it there across every turn, every restart, every interruption. Tell it once. It remembers the brief on message 14. The agent that doesn't drift. → Plug in any model. Swap providers without touching core: ProviderProfile makes every model source a clean plugin. OpenAI, Anthropic, xAI, Google, your own. Drop them in, swap them out. Build with whatever model wins this week, not the one you committed to last quarter. → Sessions that survive everything: Gateway crashes. Updates push. Source files reload. The conversation auto-resumes exactly where it left off. Checkpoints v2 rewrites state persistence with real pruning. Long-running builds stop dying because of a restart. → The agent reviews its own code before you do: Post-write delta lint. Self-linting on every write. Syntax errors surface immediately, not three commits later. Fewer broken builds. Less debugging downstream. → Eight critical security holes, closed in a single release: Redaction on by default. WhatsApp rejects strangers by default. Discord role-allowlists scoped to your guild. TOCTOU windows sealed shut across auth and MCP OAuth. Production-ready defaults out of the box. Big AI labs have thousands of engineers and billions in compute, and 295 people on GitHub are still outshipping all of them.

• 
  erna (@ernDju) reported 34 minutes ago

  @ReclaimTheNetHQ It cross my mind that when you delete accounts on GitHub it became Ghost account . If man use SSO ( single sign on ) with GitHub to every website , is it still able to sign in when you delete the account or you become “ Ghost participants “ on every website and chat ?

• 
  VibeReady (@vibereadyhq) reported 35 minutes ago

  The bugs hide where you didn't think to look. Silently swallowed errors. Wrong defaults. Edge cases the AI didn't model. CodeRabbit analyzed 470 real GitHub PRs. Apiiro analyzed Fortune 50 repos. These aren't lab numbers. They're production.

• 
  Layla CryptoWhiz (@laybitcoin1) reported 35 minutes ago

  @assaf_elovic Not crazy at all. Billions of commits documenting how humans actually solve problems. That history on GitHub is basically the context layer AI keeps missing.

• 
  John Holmes (@JohnHolmesCurse) reported 35 minutes ago

  @rpcs3 Me: Okay Grok fix my code I'm submitting. Grok thinking: Checking Wikipedia Scanning github Reviewing stolen code ¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤¤ Got it you want to fix the slop code we stole. Here's what we got for you.

• 
  avrl ☘ (@avrldotdev) reported 37 minutes ago

  @sadkatwt And the problem is since mostly people are building & compiling on github actions, which is slow af, there won't be a substantial jump at normal scale

• 
  el charro (@Elcharro0000) reported 38 minutes ago

  @ibsKING93 @MemeLiquidio Percolator atleast has real devs helping toly fix bugs on github, not like liquid farming asses

• 
  Mayank Vora (@aiwithmayank) reported 38 minutes ago

  Holy ****... Someone built a free self-hosted app that does everything Audible does, keeps your entire library on your own server, and never charges you a subscription fee. It's called Audiobookshelf and it just crossed 12,700 stars on GitHub. Audible charges $15/month. Audiobookshelf charges $0. Forever. Here's everything you need to know:

• 
  ReelDad (@ReelDad) reported 39 minutes ago

  @gothburz I ran the on-call rotation for Workers AI from 2023 until last month. The incident response runbook the agent uses now is the runbook I wrote at 3 AM during the November 2024 outage. It is in the repo under my GitHub handle. The handle still resolves. The commits are still mine. The pager went to me for fourteen months. It goes to the agent now. The agent has not been paged. It does not need to be paged. It is the thing that would have paged me.

• 
  MC (@mwangi_shi8390) reported 39 minutes ago

  May 10. 2.30am My laptop called QUITS. It crashed. The RAM cant handle wirra. So anytime I start the dev server, it just lifts its hands and says "release me". I pushed the code to github and now I am using codespace. Which fails to bypass the clerk security. Now I dont know.

• 
  Blum (@Blum_OG) reported 40 minutes ago

  > used to spend mornings opening 5 tools in sequence > Slack first, then Gmail, then Notion > then realizing you missed something in Figma > then going back to Slack > not a focus problem > not a discipline problem > a structure problem > context was scattered by design > PMM work lives at the intersection of everything > product changing, stakeholders asking, launches moving > the small signals are the job > miss them early, fix them late > built 3 automations in Codex instead > 1 personal assistant scanning for action items every hour > 1 product tracker pulling from GitHub, Linear, Slack, Notion > 1 alignment doc generator pulling from meeting notes, threads, trackers > walked into PM syncs with a rough map already built > what changed, what is in progress, what has edge cases > 0 starting from zero > the engineer explains tradeoffs, not basics > wrote alignment docs in a fraction of the time > Codex pulled the raw material together > PMM added the judgment: what matters, what the message is, what is blocked > the job did not get smaller > it got closer to the parts that actually require a human

• 
  KagariSoft (@KagariSoft) reported 43 minutes ago

  Anecdotes from the development of ROL: Once, the game disappeared forever. Due to a problem with *** (version control software), upon executing a command, the entire project was completely deleted from the disk. Luckily, there were backups on GitHub, but of changes from 24 hours prior. Developer tip! Learn to use *** and GitHub, and keep your repository updated with every change!

• 
  wukko (@uwukko) reported 44 minutes ago

  @nitzukai rice their window managers and file github issues about software breaking on their avant garde arch linux configurations

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 46 minutes ago

  cloudflare just rebuilt next.js in five days for $1,100 using claude code. 67,000 lines, 94% api coverage, 7,000+ github stars. one engineer. one week this is not a story about open source licensing this is a story about what happens when the friction cost of cloning your backend drops from six engineers and a year to a single person and $1,100 in api tokens roritharr posted on hacker news six weeks ago about a client's engineer who reverse-engineered a saas backend in a week with claude code. shipped it. functionally identical. the replies were all about lawyers and copyleft. one comment cut through the noise: "if your backend is trivial enough to be implemented by a large language model, what value are you providing?" that question stopped being theoretical when vinext shipped here is what we have been calling a technical moat for fifteen years: reproduction friction. not code. not lawyers. friction when cloning took six engineers and a year, competitors did not bother. when it takes $1,100 and five days, they will yes there are bugs in the clone. hacktron found 45 vulnerabilities in vinext. 24 validated but that does not save you. it just means your competitor ships with bugs while they eat your lunch the moats that survive: switching costs that live in your users' heads, not your code. distribution you acquired before your product existed. network effects that compound faster than code clones everything else is rent you have been collecting from friction i build and ship daily with Claude Code. SaaS, tools, automations. ⭐ if AI can build it, I've probably broken it first. what works → link in bio

• 
  Deborah Howard (@DeborahHow3797) reported 47 minutes ago

  My GitHub green squares are secretly running a rebellion against code red errors Governance tokens are being handed out to loyal followers - will they rise to save our syntax?

• 
  Chester Brian (@chestrbrian) reported 48 minutes ago

  was vibe coding my project and had been REVOKE'ing UPDATE on sensitive columns in my migrations. subscription_tier, credit balances, boost flags, github tokens. claude code wrote them, i reviewed them, they looked locked down 12 of these across my migrations. all decorative. zero actually enforcing anything turns out postgres evaluates table-level + column-level privileges with OR semantics. supabase grants table-level UPDATE to authenticated by default. a column-level REVOKE removes a privilege that was never separately granted at the column level. so it binds to nothing 5 were P0 financial. a signed-in user could've: >set subscription_tier='top_tier' on themselves (free top-tier sub) >reset last_credit_grant_at to the past (cron grants on next tick, repeat hourly, infinite credits) >set is_boosted=true on their own posts (free featured placement) >read every other user's github_access_token (same no-op on the SELECT side, token harvest) the fix is two lines per table: REVOKE UPDATE ON <table> FROM authenticated; GRANT UPDATE (allowed, columns) ON <table> TO authenticated; vibe coding lets you ship fast. it does not exempt you from knowing what your migrations actually do

• 
  athas.dev (@athasdev) reported 56 minutes ago

  @_heyrico @github Looks nice but I'd fix a few things: - remove title (breadcrumb is there) - remove `underline` from links