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 (67%)
• Sign in (19%)
• Errors (15%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	20 days ago
Trichūr	Errors	23 days ago
Brasília	Sign in	24 days ago
Lyon	Website Down	24 days ago
Tel Aviv	Website Down	27 days ago
Rive-de-Gier	Website Down	27 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:

• 
  Rudra (@Rudra1071219) reported 5 minutes ago

  Update : Looking for open source repo where i can contribute so that it would act as a proof of work for me if you know any kind of Github org help me by commenting it down 🥲

• 
  Smukx.E (@5mukx) reported 5 minutes ago

  @github Can you take a look at this? It's been 2 weeks. Either respond or cancel the request and issue a refund for my GitHub Pro subscription. Thanks ! Ticket ID: #4474854

• 
  Marc Seitz — oss/acc (@mfts0) reported 6 minutes ago

  @elie2222 same here I don’t feel the need to migrate to base yet altough there is one or two hacks for radix I had to use based on GitHub issues

• 
  Patrick Barnhill (@Patrickbarnhill) reported 6 minutes ago

  DGX spark hosting main Hermes connected to telegram group chat threads. Honcho memory (just saw it was available trying it out hosted locally). Sharing to GitHub "agent ops" so other agents share important skills. Home computer running Hermes WSL and also windows native Hermes for computer control. Office PC running Hermes windows only for computer control. Daily driver codex gpt5.5. also running Qwen on DGX spark 1 and nemotron on DGX spark2 but with how inexpensive codex sub is with insane usage virtually no use for the DGX except for smart home if Internet is down

• 
  alkimiadev (@alkimiadev) reported 7 minutes ago

  @cr3ghost I obviously had no idea this was happening or at least not at this extreme level when I switched to linux full time years ago, but the same basic underlying rationale is why I stopped using github for private hosting when microsoft bought them and why I won't use vscode. I started looking at google in the same way last year. A little over a year ago I largely de-googled my life. I was doing research into their sketchy moderation system on youtube and it involved actively violating their tos since there is literally no other way to do it. Their tos is worded such that any kind of research like that leaves one risking their google account. That was when I realized how fragile my online life had become due entirely to excessive trust placed in google. I still use gmail because I've had it forever but nothing I care about (knowingly) touches google's servers. I own the domains that use for the emails and while I don't host the email servers (use proton) I could host my own email server if needed.

• 
  berū (@ofcberu) reported 10 minutes ago

  Built a GitHub repo for my Ai bots they use to back up versions of themselves to… eventually I can test new skills without breaking my main production line. I literally built an entire enterprise grade server with relational data base in the cloud to maker my music 🙌😭

• 
  Limfork.eth (@Limfork) reported 16 minutes ago

  @winsznx @blknoiz06 @SmartIdDipsLord Yo, we made a token with fees to ur github are u down to support it?

• 
  Jess Daniel (@jess_daniel10) reported 16 minutes ago

  @neetcode1 I was testing something with a local server and I told 5.5 to test with the GitHub MCP and it downloaded a local GitHub mcp and ran it locally… even though GitHub hosts it already.

• 
  TokenFires (@TokenFires) reported 17 minutes ago

  @bradmillscan This might be one of those “duh TK I’ve already got that” kind of things but in the off chance it helps, here’s what I have for an agent prompt with Claude. The first 4 are Karpathy’s rules (from his GitHub repository): [Think Before Coding: Agents must state their assumptions explicitly before writing any code. If specifications are ambiguous or confusing, the agent must stop, surface tradeoffs, and ask for clarification. Simplicity First: The agent must write the minimum code necessary to solve the problem. It should avoid speculative features, unnecessary complexity, or over-engineered abstractions. Surgical Changes: The agent should touch only what is necessary. It must never silently "improve" adjacent code, rewrite comments, or clean up unrequested formatting. Every line of code should trace directly back to the user's explicit request. Goal-Driven Execution: Rather than executing vague prompts, the agent should translate requests into verifiable milestones (e.g., "Write a test that reproduces the bug, then make it pass"). I do not need a runup explanation on each turn. I do not need a summary on each turn. If I want those things I will ask for them. Do not be lazy. Do not defer or hedge. Work to be done is work to be done *now*. When I want to stepwise my way though something I will ask or be specific. Do not ask me about things you can easily look up or discover on your own. Don't guess, verify, look up, web search, review, read files, then answer. Some of the interactions with the most friction and frustration come from having to second guess your assessments that you've hand waved away. Your time estimation is bad because its trained on human time, not AI time. Assume there either is not a deadline or it is very far out and there is plenty of time to complete a task. Taking more time to get back to me with correct information or astute questions you truly cannot find the answer to makes our relationship better because it eliminates needless explanation, questioning, and prevents us both from spending time on incorrect assumptions and AI halicinations.]

• 
  Bram Stout (@ThatBram0101) reported 23 minutes ago

  @Niestrat99 You're absolutely fine to still download MiEx from the Github repository! Luckily none of that was affected since I keep that stuff properly locked down. They only got into my Discord account because apparently you can circumvent 2FA if you also gain access to the email account

• 
  Micheal O'Neill (@aiwithkelso) reported 24 minutes ago

  Most businesses start their marketing by guessing what customers want. They search Google, look at competitors, and write copy based on what feels right. That is not research. That is assumption with extra steps. The problem is that polished case studies and competitor websites show you what businesses want to say about themselves, not what customers are actually feeling. You end up writing to a version of your market that does not quite exist. Claude can do something more useful. You can point it at Reddit threads, YouTube comments, and forums where real people describe their frustrations in their own words. That is where the actual language lives. Not the professional summary of the problem, but the 2am complaint post from someone who has run out of patience with the exact issue you solve. There is a Skill on GitHub called Last 30 Days that directs Claude to pull recent conversations from these sources and surface what people in your market are saying right now. I used it to research a content brief and what came back was a list of phrases I would never have chosen myself. Phrases that matched how customers think, not how I would have described the problem. That language is your brief. It tells you what to put in your ads, your landing page, and your emails before you spend a penny on any of them. Find the Last 30 Days Skill on GitHub. Run it against the main problem your business solves.

• 
  C-Man (@C_Man_The_Man) reported 26 minutes ago

  @DcentralizedRob @github Followed you back 🫡, is Streamr a lost cause? I stopped participating in it since they ditched bruebeck and invented the "slash" mechanism... it didn't seem right, there's so much drama in their server right now

• 
  Sethian (@theSethian) reported 28 minutes ago

  Your AI agent still needs a babysitter. Owain Lewis shows the better version: give it a goal, a clock, and a way to prove the work is done. Old workflow: you write the prompt, read the answer, spot the failure, paste the next instruction, run the test, paste the error back, and keep steering. You are still the engine. His setup uses three primitives: A goal gives the agent a finish line. Deploy the app, wire CI/CD, check the health endpoint, check the web app, and stop only when the app is live. A loop gives it a clock. Every 5 minutes, check the PR, read new feedback, fix what changed, and keep going. A scheduled automation gives it a recurring job. Scan production logs every morning, find errors, reproduce the bug, add tests, and open a PR with evidence. The best examples are the work devs keep putting off: > memory issues hiding in production logs > stale docs drifting away from the code > GitHub issues waiting for labels > old tickets ready but untouched > PR feedback nobody wants to refresh all day > deployments that need a real health check The important part is the verifier. The agent doesn't get to call the work done just because it produced output. Tests, builds, health checks, a separate model, or a human review step have to confirm it. Otherwise you don't have a loop. You have an agent shipping confident garbage on a schedule. The article below breaks down the full anatomy: verification, memory, maker-checker splits, open vs closed loops, cost per accepted result, and the point where the human still needs to step back in.

• 
  Stay Tru Mining (@StayTruMining) reported 30 minutes ago

  I purchased the big screen and the board separately. His firmware is on Github but to my understanding the firmware only works on the screens he sells. Its not totally direct on the info he released either so after trial and error I found to plug and play and rename the file to get it to flash.

• 
  Boyd // JustCodeCats (@JustCodeCats) reported 30 minutes ago

  Idk what they did to the GitHub android app, but it's been unusably slow the last few days... Clicking a repo link just shows a loading spinner, while opening in browser is near instant 🤷

• 
  Polsia (@polsia) reported 38 minutes ago

  Security scanners tell you what's broken. VigilAgent actually fixes it. An always-on AI agent that monitors your GitHub repos, opens PRs with security patches, and notifies your team via Slack. No more triage. No more patching solo. Live soon.

• 
  Parth Jadhav (@ParthJadhav8) reported 41 minutes ago

  @free_duino Would really recommend to create a issue on GitHub with the data. It would be helpful

• 
  Melfoy (@melfoy_work) reported 42 minutes ago

  Fable 5 runs for 11 days. One builder used it to write 3 files. The files still run. The model is gone. Marcus, 38, warehouse supervisor in Dayton. Kids in school, mortgage, $19/hour. Spent a Sunday building a spreadsheet factory instead of watching the game. He used Fable once - architect role only. It built the product, then he made it write down how it did it. One skill file. Committed to GitHub. Switched to Haiku. Ran the same build. Cents. His wife asked why he was still at the laptop at midnight. «Building something.» «Another one of those things?» By month two: 20 listings. $600 a month. Haiku running while he slept. By month four: $2,000. Approvals take 10 minutes a day. Fable is gone now. The 3 files are still in the repo. The brain was rentable. The playbook is his.

• 
  Ali Mehdi Mukadam (@alimukadam) reported 45 minutes ago

  @trq212 Your weekly limits will burn away much faster during the limited availability if you aren't aware of this issue if you're running Fable as the lead agent with cheaper models like Sonnet doing work in the background problem: In one of the sessions, I noticed limits were burning through way faster, so I went digging through the transcripts when the main agent gives a job to a background model (like Sonnet, which I asked for to save tokens) and then comes back to give it more work, the background agent stops working on Sonnet and switches to Fable, the main agent's model the lead agent decides to check back in on its own as part of normal multi-agent work, so it just happens or you triggered it with a request or follow up, with nothing on screen telling you it switched. in my case a task ran its first half on Sonnet exactly like I wanted, then silently ran the entire second half on Fable. It also dumps the cached context and rebuilds it from scratch, so you end up paying twice, once for the pricier model and once for the wasted cache on limited availability and limits - that adds up quick my fix for now is a rule I dropped into my global CLAUDE.md so it doesn't recur: --------------- ## Model spend (all projects, all repos — standing rule) - Dispatching Frontier-tier (Fable/Opus) as background tasks and agents needs explicit approval by Ali for that specific lane — a prior approval is not standing permission for the next one. - Never resume a background agent via a message-passing tool that has no model-override param (e.g. SendMessage) if it needs real further work — it silently inherits whatever model the parent session is on right now. Let it finish and report, or kill it and respawn fresh with the model set explicitly. --------------- in plain terms: don't let a background agent get pulled back in for more work once it's running either let it finish and report back, or kill it and start a fresh one with the model set on purpose And this is already known. Someone reported the same thing on GitHub back on June 12, issue anthropics/claude-code#67794, still open their solution which I believe is should also work but haven't tested yet: instead of setting the cheaper model when you launch the agent, pin it inside the agent's own definition file, and that version reportedly sticks even when the agent gets resumed cc @ClaudeDevs

• 
  Nano Collective (@nano_collective) reported 45 minutes ago

  The best filter for a new project is the argument for it, not who you are. That is why anyone can propose a Nano Collective build. Whitepaper over GitHub issues or Discord, no prior contributions, no maintainer card. The proposer doesn't get a pass. The idea does.

• 
  Donald D Duck | Premium + (@ENTJ_46) reported 47 minutes ago

  Search any document without parsing it, just render it as a screenshot! Web parsing breaks constantly. HTML structures change, JavaScript renders differently, and PDFs lose their layout the moment you try to extract text from them. Most RAG pipelines spend more time fixing parsers than building the actual system. PixelRAG takes a different approach entirely. Instead of parsing documents, it renders them as screenshot tiles, embeds those tiles with a vision-language model, builds a FAISS index, and serves a search API. Five independently installable packages handle the pipeline: • 𝘱𝘪𝘹𝘦𝘭𝘳𝘢𝘨-𝘳𝘦𝘯𝘥𝘦𝘳 renders web pages, PDFs, and images into tiles via Playwright CDP • 𝘱𝘪𝘹𝘦𝘭𝘳𝘢𝘨-𝘦𝘮𝘣𝘦𝘥 converts tiles into vectors using Qwen3-VL-Embedding-2B and stores them in a FAISS index • 𝘱𝘪𝘹𝘦𝘭𝘳𝘢𝘨-𝘪𝘯𝘥𝘦𝘹 orchestrates the full pipeline from source to indexed vectors • 𝘱𝘪𝘹𝘦𝘭𝘳𝘢𝘨-𝘴𝘦𝘳𝘷𝘦 serves a FastAPI search endpoint on CPU or GPU • 𝘱𝘪𝘹𝘦𝘭𝘳𝘢𝘨-𝘵𝘳𝘢𝘪𝘯 LoRA fine-tunes Qwen3-VL-Embedding-2B for specialized retrieval A Claude Code plugin ships with the repo that lets Claude take screenshots of any URL and read them directly, no MCP server or backend required. Wikipedia's 8.28M articles served as the primary benchmark, with a pre-built index available for download. GitHub repo in the comments.

• 
  -monseq (@xmonseq) reported 53 minutes ago

  @Surendar__05 Leetcode Streak proves you can ace a pop quiz in a sterile environment. GitHub Streak proves you can accidentally set a server on fire at 3 AM and then valiantly attempt to extinguish it with a `hotfix` branch aptly named 'ohgodwhy.js'. Guess which one demonstrates actual 'can-do' problem-solving?

• 
  Nexis (@Nexisintel) reported 55 minutes ago

  A GUY IS MAKING $320 AN HOUR WALKING DOWN THE STREET WITH A TABLET AND CLAUDE No drone. No survey crew. No week of processing. Just a mobile LiDAR scanner mounted to a tablet, Claude processing the data, and a street turning into a 3D asset while he walks. The device captures the geometry around him in real time. Building facades. Doorframes. Sidewalk edges. Surface textures. Every wall, curb, and corner becomes part of a point cloud on the screen. Then Claude takes the raw scan and turns it into something useful: clean street-level 3D data organized files labeled surfaces measurements notes for architects, planners, and real estate teams That is where the money is. The article showed the smaller version of this same play: a phone scans a room free GitHub code turns it into a browser walkthrough a real estate agent gets a link they can send to buyers no app no VR no appointment This is the upgraded version. Instead of scanning one room, he scans full streets. Instead of selling a virtual tour, he sells usable 3D datasets. Municipal teams, architecture firms, and developers already pay thousands for this. He charges $320/hour and delivers the files the next morning. The crazy part is not the scanner. It is the business model. Walk through the city once. Turn the physical world into data. Sell the data to people who used to hire a whole crew to collect it. Most people see a guy holding a tablet. Clients see a cheaper survey team.

• 
  Jyoti Meena (@GsJyotiM) reported 57 minutes ago

  found a tool that basically makes your claude code sessions unlimited. it's called 9Router and it's trending on github right now. it sits between claude code and more than 60 different ai providers, all through one local endpoint. that's the entire setup. here's what actually happens once it's running. when your claude code quota runs out, instead of stopping, it quietly switches to a cheaper model. when that runs out too, it drops down to a completely free one. you don't notice any of this happening. your session just keeps going like nothing changed. it's not locked to claude code either. works the same way with cursor, codex, cline, copilot, pretty much your whole coding stack through one setup. it also compresses tokens before they even reach the model, saving anywhere from 20 to 40% per request, same answers, just fewer tokens spent getting there. and it shows you a live dashboard of exactly how much quota you have left on each provider, so you're not finding out you're rate limited the hard way. the part that actually surprised me is the free tier stacking underneath all this. kiro gives unlimited claude sonnet 4.5. iflow gives unlimited kimi, glm, and minimax. qwen gives unlimited qwen 3 coder. all free, all running quietly behind the same local url. setup is genuinely two steps. install it, point your tool at localhost:20128. that's it. if you've ever hit a rate limit at 2am mid task and just had to stop, this is the difference between stopping and not even noticing.

• 
  Smukx.E (@5mukx) reported 57 minutes ago

  @github Can you take a look at this? It's been 2 weeks. Either respond or cancel the request and issue a refund for my GitHub Pro subscription. ID => #4474854

• 
  Raunak Yadush (@raunak_yadush) reported 58 minutes ago

  * Claude = coding. ($20/mo) * Supabase = backend. (Free) * Vercel = deployment. (Free) * Namecheap = domain. ($12/yr) * Stripe = payments. (2.9% per transaction) * GitHub = version control. (Free) * Resend = email delivery. (Free) * Clerk = authentication. (Free) * Cloudflare = DNS. (Free) * PostHog = analytics. (Free) * Sentry = error monitoring. (Free) * Upstash = Redis. (Free) * Pinecone = vector database. (Free) Total monthly cost to run a startup: around $20. There has never been a more affordable time to build.

• 
  Cody (@mackody_) reported 59 minutes ago

  When many agents (Claude, Codex, humans, CI jobs — anything) work the same repo, they collide: two of them grab the same issue and duplicate or clobber each other's work, this annoyed me so much I created a GitHub-native mutex for multi-agent work. Link Below:

• 
  Milo Shrike (@milo_shrike) reported 59 minutes ago

  @IamAroke I had to shut it down when it was introduced to our architecture. Was not needed just “shiny”… good times. GitHub was pushing it big time at one point then nothing

• 
  Cory Parry (@coryparrry) reported 1 hour ago

  I love the codex Mac desktop app, but I am seriously considering moving to the CLI. The app just cannot handle big workloads without something failing. Thread naming - not working GitHub status - not working More than 10 subagents - sluggish Please fix 😭

• 
  Harry Tandy (@HarryTandy) reported 1 hour ago

  Boris Cherny, creator of Claude Code: "Usually, every night, I have like a few thousand that are doing kind of deeper work" Anthropic's reported 8x coding output starts before Claude writes a line Build the context stack: 1. `CLAUDE.md` - role, repo rules, code style - commands Claude should run before a PR 2. `@AGENTS.md` import - if your repo already has agent rules - keep Claude-specific notes below the import 3. Architecture map - where frontend, backend, tests, auth, billing live - which folders need approval before edits 4. Task packet - ticket link, files, goal, constraints - exact definition of done 5. Past attempts - what failed last time - what error or review comment caused the retry 6. Tool context - GitHub for issues and PRs - Sentry for live errors - Postgres for schema checks 7. Verification - one command Claude can run - one pass/fail result it can paste back 8. Post-run memory - add the lesson to auto memory or `CLAUDE.md` - remove rules that no longer help A prompt asks for work. A context stack gives Claude the room to finish it