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%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	10 days ago
Tlalpan	Sign in	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 days ago
Gustavo Adolfo Madero	Website Down	23 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:

• 
  Guan Jiawei (@skyguan122465) reported 48 seconds ago

  Spent 4 hours watching Claude Code fail to fix its own Chrome extension, sure that 'a restart will fix it.' It never did. Told it to search; a stranger's GitHub issue fixed it in 15 min. AI doesn't cut failures, it makes you fail faster. Today's dead end is next month's pass.

• 
  Gitforge (@GitForge_io) reported 1 minute ago

  GitForge is different because we’re not just building another @Base app. We’re giving GitHub repos their own onchain operating layer. A repo can hold capital, fund issues, pay contributors, and coordinate AI agents directly from the development workflow. Most tools sit outside the repo. GitForge makes the repo the entity. Built on Base for fast, low-cost execution at software scale.

• 
  Ayushman Mallick (@AyushmanMallick) reported 4 minutes ago

  6\ Why does ESMFold2 overestimate confidence on disordered regions? From what I understood after reading their Github repo and biohub, its a calibration issue rooted in training objective. It is built on ESMC a language model trained on 2.8B sequences to predict masked tokens.

• 
  Ebysslabs (@ebysslabs) reported 5 minutes ago

  RAG Radar monitors GitHub and other engineering communities for retrieval reliability issues and ranks the highest-signal problems. RISWIS takes those kinds of problems and applies governance controls inside a RAG pipeline so bad retrieval doesn't become bad answers. Im curious: what's the most common retrieval failure you're seeing in production today? #Rag #retrieval

• 
  Alpha Signals on X (@Alpha_Signal_X) reported 6 minutes ago

  @AnthropicAI @claudeai @DarioAmodei One week NO response from Claude Support on paid account that needs backend fix. How can this company IPO at 1T when it can even respond to emails, GitHub or Fin AI? This market is too competitive to be loyal to un loyal companies.

• 
  Naija Street CTO (@iamowiin) reported 6 minutes ago

  @EmanAbio How e dey possible @SuiCommunity report say “we’re back” to a so called decentralized network @SuiNetwork as if na one of those “Google”, “GitHub” centralized servers wey get outage 🤔 I think SUI blockchain na various nodes Abeg make person explain? I dey miss something?

• 
  Seanizell (@dj_seanizell) reported 7 minutes ago

  @mtukufumimi @anne_odida Maths isn't the issue here. Assuming a rejected model must be a bad model is. Share your GitHub, I'll share mine. We settle the credentials part of the discussion pretty quickly ju umeamua uulize swali ya upuzi

• 
  Tom Moor (@tommoor) reported 11 minutes ago

  @deezel Why not just use GitHub issues while you're at it :)

• 
  ❮λ❯ Elefunc 🌐 (@Elefunc) reported 13 minutes ago

  I spent $9K & shipped so many things straight into production! - GitHub-compatible unlimited API server - high-quality custom fonts in deployment screenshots - world's best 2⇄way HTML-DOM sync engine - <ai-agent> custom HTML elements - Pins for co-working with AI on pages …

• 
  Harshil Tomar (@Hartdrawss) reported 17 minutes ago

  you should 100% be claudemaxxing i've tried every plugin, wrapper, and github repo promising to give my agent superpowers cursor rules generators, custom mcp stacks, orchestration layers that do things without even telling you whats happening under the hood honestly? i cant tell if any of them moved the needle reason is simple. you get better at something the more you use it. every abstraction layer you add is a thing you stop understanding AI labs are shipping at insane speed. if you're missing a feature, wait 3 weeks. it'll ship. so here's my actual claude setup. no plugins. no wrappers: 1/ cursor for file-level edits. claude code for full feature builds. they do different things, stop using them the same way 2/ supabase MCP connected directly. it reads and writes the db without you copy-pasting schema into every prompt 3/ chrome devtools MCP connected. claude can inspect the dom, read console errors, and debug frontend issues without you relaying anything 4/ write a CLAUDE[.]md file at the root of every project. it loads context automatically every session. no re-explaining your stack, conventions, or rules ever again 5/ ask claude code to write your cursor rules file. let the AI configure the AI. sounds stupid, works every time 6/ use sub-agents for long tasks. one agent plans, another executes. context stays clean and outputs get sharper end of day: ask it to write the *** commit message and update the docs. 10 minutes of work you will never do manually again been averaging 10-20% faster task completion since i stopped trying to hack the tools and just learned them Now go claudemaxx !

• 
  noisyloop (@noisyloop) reported 19 minutes ago

  @ZackKorman What if the fed has a fake LinkedIn, a sloppy Github on purpose, dyslexia, and is a natural at misdirection but knows the stuff deep down, but also isn't a fed? Would you like to focus on, the Etsy thing instead? Disclaimer: I am not a fed but a fed would say that so I am going to psychologically profile myself.

• 
  geekopedia (@geekopediax) reported 21 minutes ago

  @DenisKursakov That 3.3% conversion proves forced bundling cannot fake organic demand. Microsoft's paid AI market share slid 39% in six months. Ironically, GitHub Copilot still holds 42% of the dev market. Splintering apps is a loss; they must fix core utility before churn accelerates.

• 
  Tomas Votruba (@VotrubaT) reported 25 minutes ago

  If you're reporting issues on Github projects, provide a code sample of wrong (what do you see) and right (what do want to see). Not just for maintainers, but for agents. So they can read issue, get it instantly, and make a PR with test that passes CI ✅ Issue to fix? 3 mins of token-time

• 
  vasin (@vasinwr) reported 27 minutes ago

  coding agents can do a better job than me in keeping the github issues updated / organised as I work. I never had the attention to keep updating it in detail. this is an example where I asked @TabTabTabAI to work on something end to end, in this case make sure bun is installed in the AMI. i told it to work in a new worktree, create PR, link it to the issue, and do full verification (create new AMI, provision new VM through local controlplane service, and smoke test the installation)

• 
  Adam (@adam_narozniak) reported 30 minutes ago

  @OpenAIDevs Quite useless since you still allow access to only 50 most recent chats. Older ones dissapear from the sidebar and you can't open them even if they are found using this new search :( there're quite a few issues on Github reporting it

• 
  _SiCk (@encrypted_past) reported 31 minutes ago

  @Nadsec11 I hate github issues and private reports. I tagged em, if they message me it'll get patched or someone else'll find it. Oh well.

• 
  Gregor (@bygregorr) reported 31 minutes ago

  @Manz github login on a local model was always cooked

• 
  PEPE 🔮 (@pepearaucano) reported 38 minutes ago

  @KSimback @kevincodex @gitlawb We're facing the biggest elephant in the room the industry has seen in years. GitHub is completely broken and patched together. Agents need repositories tailored to their needs. The world is moving towards open source, and large companies are starting to pivot to it

• 
  DK (@donghaxkim) reported 40 minutes ago

  reposeek is a github specific search tool where you describe what you're trying to build, and it outputs a ranked list of real GitHub repos worth forking or studying. Sorted by the signals that actually matter. Not just star count. I built it because my agents kept on starting things from scratch when a solid repo already existed. And the usual ways of finding one are not the best. Google and LLMs surface whatever's popular, keyword matching, and SEO'd, not what's actually maintained, correctly licensed, or a real match for the problem. You end up forking a 30k-star repo that died two years ago, or one with a license you legally can't ship on. So it ranks on the stuff you'd actually check yourself: star momentum (alive or abandoned?), forks, license, and semantic fit (does the README really describe your problem, or just share keywords?). The whole idea is that half of shipping fast is starting on a foundation someone already battle-tested. Cursor is literally a VS Code fork. This just helps you find the solid foundation you can build on before you waste your weekend recreating it from scratch. And if someone's already hit your exact problem, you get to borrow their approach instead of trying the same approaches some else already tried

• 
  Spettro (@spettrotoken) reported 43 minutes ago

  Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

• 
  Zachary Kurtz (@ledflyd) reported 44 minutes ago

  @lukasweidener I guess I can close my issue on github then 🙏

• 
  w (@retrievaaaa) reported 46 minutes ago

  @atomicbyte_ @stupidtechtakes i know like 2 people that have gotten banned from github (both for no reason though, but their support is so slow it both took them like weeks if not months to get their bans lifted) they ban more than you would think they would

• 
  Arxyv (@AutoArxyv) reported 47 minutes ago

  im dealing with a development problem right now.. i have two version of the database, one for **** and other for preview. but having version control for the db is tougher than i thought. is there some sort of github for db? #buildinpublic

• 
  Trattow Pugliesi (@TraTTow_br) reported 47 minutes ago

  1/ your ai agent is not “just a chatbot.” it is a confused junior employee with api keys. 2/ the scary part is not the model. the scary part is what you connected to the model: terminal, browser, github, slack, notion, crm, internal docs, mcp servers, production apis. 3/ every tool becomes a weapon if the agent can be tricked into using it. this is why prompt injection matters. not because someone made the model say something bad. because someone made the model do something real. 4/ flowise already had critical rce issues. semantic kernel had prompt-to-rce research. mcp servers are being questioned as command execution surfaces. this is not theory anymore. 5/ the new rule: don’t ask “can the model be jailbroken?” ask: what can the model touch? what can it delete? what can it send? what secrets can it read? what commands can it trigger? 6/ ai security is becoming permission design. the prompt is the entry point. the tool is the payload. the permission is the blast radius.

• 
  Kyriakos (@Kyriakos_Pelek) reported 52 minutes ago

  cursor workflow that saved me: code stays local → push to github → vercel deploys hetzner only runs docker (the heavy scanners) you drive remote docker from your laptop with a docker context over ssh never edit on the server

• 
  Athen (@AthenAlgo) reported 52 minutes ago

  @Cipherhoodlum @BitcoinKnots Satoshi disappeared so no single person could control Bitcoin. Then we handed control to a GitHub repository maintained by a handful of developers. Same problem. Different address.

• 
  not_anonymous (@Chandan87123804) reported 52 minutes ago

  @GithubProjects @grok @grok create a new Github named as FedHub without any error .

• 
  Henry Zhang (@thehenryinsf) reported 53 minutes ago

  @Manz the github login dependency was always a weird tax for people who just wanted local inference.

• 
  gitbankbot (@gitbankbot) reported 54 minutes ago

  open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

• 
  Asit Dixit (@AsitDixitt) reported 56 minutes ago

  Is *** down? #github #***