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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	5 days ago
Paris	Website Down	8 days ago
Saint-Paul	Website Down	9 days ago
Saint-Paul	Website Down	9 days ago
Mexico City	Sign in	10 days ago
León de los Aldama	Website Down	10 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:

• 
  Jeffrey Emanuel (@doodlestein) reported 19 seconds ago

  @Matt_M_M If you add a GitHub issue for that, I can add Intel Mac as a supported target for release binaries.

• 
  Noah Hein (@TheNoahHein) reported 25 seconds ago

  I opened a bunch of issues in OSS repos as part of a bounty program for an old job. You would comment in the issue and get assigned to it. The bounties were from 2-5k USD. So periodically I get random people replying to those GitHub issues trying to snipe people’s work it is hilarious. “I will do this bounty for $1k less and I already have the PR ready just assign it to me” I love the petty drama 😭😭😭

• 
  MadamAdam (@browndwarf6) reported 6 minutes ago

  @ssr_tourist I barely use a github and if you asked me how to I wouldn't know what to tell you lol but like if I do use it and go on there it was never a problem for me, maybe just a second of confusion cuz I was looking in the wrong direction but it's generally very easy to do

• 
  ilya (@eviltwink5) reported 11 minutes ago

  @OneShotArchive i've never had trouble downloading anything from github. either use releases, download the whole zip or follow the instructions in the readme

• 
  Ivan Fioravanti ᯅ (@ivanfioravanti) reported 18 minutes ago

  @marcozerbato No, using github issues to save things to be shared.

• 
  Cennes100 (@Cennes100) reported 20 minutes ago

  MOST PEOPLE ARE STILL RUNNING ONE CLAUDE CHAT AT A TIME. THAT ERA IS OVER. Most people treat Claude like a single brain. One prompt, one response, doing everything from planning to coding to reviewing. That's the problem. One brain gets tired, misses bugs, and was never built to run 60 things at once. The mechanism is called Claude Flow, already found by 14,800 developers. It runs up to 60 agents at once, each with its own job. One plans, one codes, one tests, one reviews security, all in parallel, all sharing memory, all getting sharper after every run. The detail most people miss: it does not just make Claude smarter, it makes it cheaper. Simple tasks get routed to a free layer automatically. Complex tasks go to the model that deserves them. Same subscription, way less waste. That is when it gets interesting: 1. Your Claude subscription performs like it just got 2.5x stronger 2. Ranked number one in agent frameworks on GitHub, 14,100 stars 3. 100% open source, zero extra subscriptions needed Most people use Claude to answer one question. This setup uses Claude to run an entire team. Follow: @Cennes100

• 
  Claire (@BOBO11036) reported 22 minutes ago

  @predzoru Any github project worth its salt usually has a readme directing you to the releases tab but tech literacy is so astronomically down that doesn't even click with some

• 
  Hugo Bowne-Anderson (@hugobowne) reported 24 minutes ago

  “You still use pull requests? I wouldn’t even do that anymore. Just push it straight to trunk, have your agent summarize it.” That’s @gregce10, co-founder and CPO of SpecStory. He previously worked at GitHub, Dropbox and Google, and was CPO at Pluralsight. And he kept going: - PRs are the limiting gate when agents produce more code than humans can review. - The model should never decide when its own work is finished. Put the deterministic checks somewhere it cannot access. - *** is probably here to stay. Whether GitHub remains the platform, “we’ll see.” @HanchungLee came at the same problem from the evaluation side. Han is Director of Machine Learning at Moody’s and works on SkillsBench, evaluating skills across combinations of models and agent harnesses. - An agent is the model plus its harness. You need to evaluate the complete system. - A green check proves nothing if the agent found a way to game the task. - Your agent could delete the failing test and declare success. Both are figuring out how to turn masses of agent-generated slop into signal. Greg mined 516 saved agent sessions to recover the decisions and intent behind the work, identify recurring practices, and forge the ones he approved into reusable skills. Han runs skills inside controlled environments, grades the result, and preserves the complete trajectory so we can inspect what the agent actually did. Preserve the intent. Inspect the trajectory. Verify the result. Turn what works into skills. Full episode in the replies 👇

• 
  Denis Volkhonskiy (@den_volkhonskiy) reported 25 minutes ago

  the simple loop that will turn your claude code and codex subscription into a team of engineers 1. add codex code review on github to your repo 2. use claude code for development 3. ask claude code: "create PR, babysit it, check every 5 minutes for comments from codex. If there are comments, validate and fix them. when you see thumbs up reaction on the PR body, finish the loop and merge it"

• 
  Nav Toor (@heynavtoor) reported 26 minutes ago

  You Googled "password generator." The first result has four ads at the top. A popup for your email. A cookie banner. And a text box where you type a password. You copy the password. You use it for your bank. That website now knows a password you use. On a server you do not own. In a database you cannot delete. Run by a company you have never heard of. A French developer named Corentin Thomasset built 86 tools like this. All in one place. All local. Nothing gets sent anywhere. It is called IT-Tools. 39,834 stars on GitHub. One Docker command. docker run -d -p 8080:80 corentinth/it-tools:latest Done. Every tool runs in your browser. No backend. No database. Nothing leaves your machine. Here is what you never have to Google again: Password generator. Any length. Nothing logged. QR code maker. No site tracks what you encode. WiFi QR code. Guests scan and join. No shouting passwords. Hash maker. SHA-256, MD5, and more. Local only. Base64 encoder and decoder. Paste safely. UUID generator. Instant. JWT decoder. No pasting tokens into a stranger's site. JSON, YAML, XML, and SQL formatter. Color converter. HEX, RGB, HSL. Crontab builder. Chmod calculator. Docker run to Docker Compose converter. Lorem ipsum text. Regex tester. 86 tools. One container. One command. Who uses this: A developer who stopped pasting JWT tokens into random sites. Those tokens hold user IDs, emails, and role info. Every free decoder site reads all of it. A designer sick of color converters wrapped in ads. A sysadmin who stopped Googling "chmod 755" for the tenth time. Anyone who saw the trick. Every free tool is free because your input is the product. 39,834 stars. GPL-3.0 license. Vue.js. The code cannot be pulled from you. Next time you need a quick tool, you have two choices. Google it and hand your data to a stranger. Or open localhost:8080 and keep it to yourself. (Link in the comments)

• 
  Louis Gleeson (@aigleeson) reported 26 minutes ago

  A guy named Gildas fixed one of the dumbest problems on the internet. His free extension turns any webpage into one file you can rename, email, move, and open offline. It is called SingleFile. Hit Ctrl+S on a webpage and your browser gives you an HTML file surrounded by a folder full of loose images and other assets. Rename the wrong thing, move one file, or forget to send the folder, and the saved page breaks. SingleFile fixes this with one click. It packs the page, images, fonts, frames, and styling into one self-contained HTML file. The copy opens in any browser without needing SingleFile installed. You can save it to a USB drive, send it to someone, or open it years later without WiFi. It also lets you highlight text, add notes, remove unwanted sections, save several tabs at once, and automatically capture pages as you browse. A command-line version can save large lists of URLs automatically. SingleFile works across nine major browsers and has 21,800 GitHub stars. I bet you didn't know about this one. If you did know about then let me know how are you using it in the comments.

• 
  RyDawgE @ Halfapps (@RyDawgE_) reported 27 minutes ago

  @StorgaardMikkel @AmazonessKing3 ... Of AI and not the root cause. We can have AI without malicious terms and conditions foul play. People are smart, people will stop using GitHub eventually and go back to hosting their own *** servers to avoid this exact problem.

• 
  OIiver (@posedscaredcity) reported 29 minutes ago

  @my_knn_totoro @KSimback i actually run gstack across my company and can answer this too ( i was just seekign outsider opinion) pros: - works in practice like magic now for us - the agents are continuously learning. the default output before vs after is like a 3 generation model difference on the same model. gpt 5.5 with it was comparable to fable without it. fable with it is insane. - much easier to prompt - no need to transfer much context - new hires and anyone can get any and all questions out of their wheelhouse answered as needed - tracks decision etymology in a way that was missing cons: 1. its quite broken: many days of agent time spent to get and keep it working. dreaming has broken so many times. 2. authentication wasn't developed or wasn't developed well and setting up new hires or new agent systems to hook in with correct attribution is a ***** (with how i set it up at least) 3. once installed agents do not use it and do not use it well. we needed a good agents.md file telling it to look for task preferences before starting, and to fill out the empty search queries from the start when wrapping up and meta preferences within gbrain itself. 4. it slows down the agents since they have more to traverse 5. ingestion was broken out of the box and integrations sucked. we hooked in and heavily modified composio so i could ingest a lot of events 6. connecting a github account will ingest all events from all open source repos you've ever touched. cleaning that up was a ***** 7. federating access is really hard as a result haven't bothered but isn't scalable.

• 
  ️ (@blankspeaker) reported 31 minutes ago

  SpaceXAI: Grok Build alpha has been updated to v0.2.103. Here are the changes: 𝐒𝐮𝐦𝐦𝐚𝐫𝐲 Grok Build v0.2.103 delivers stronger plugin security with a new require_sha option and improved setup flows for MCP servers, while local sessions now fully inherit your shell environment, working directory, and exports for smoother tool use. Session handling and SSH integration see nice UX upgrades, including better fullscreen quit info, helpful wrap tips, and reliable terminal restoration after disconnects. This release also fixes several reliability issues around GitHub PR detection, prompt copying, voice input with custom keys, session turn slots,… 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐬 • 𝐍𝐞𝐰 𝐫𝐞𝐪𝐮𝐢𝐫𝐞_𝐬𝐡𝐚 𝐨𝐩𝐭𝐢𝐨𝐧 prevents remote plugins from tracking mutable branches or tags. • Quitting a fullscreen session now shows the session title and last exchange above the resume command. • 𝐌𝐂𝐏 𝐬𝐞𝐫𝐯𝐞𝐫𝐬 from plugins can now require setup choices such as a regional site before connecting. • 𝐒𝐒𝐇 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 now show a one-time tip recommending `grok wrap ssh <host>` for clipboard and terminal restore. • 𝐋𝐨𝐜𝐚𝐥 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 𝐧𝐨𝐰 𝐢𝐧𝐡𝐞𝐫𝐢𝐭 𝐟𝐮𝐥𝐥 𝐫𝐜 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭, 𝐜𝐰𝐝, 𝐚𝐧𝐝 𝐞𝐱𝐩𝐨𝐫𝐭𝐬 across tool calls (configurable). 𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬 • 𝐅𝐢𝐱𝐞𝐝 𝐆𝐢𝐭𝐇𝐮𝐛 𝐏𝐑 𝐬𝐭𝐚𝐭𝐮𝐬 𝐝𝐞𝐭𝐞𝐜𝐭𝐢𝐨𝐧 when the gh CLI inherits forcing color environment variables. • 𝐠𝐫𝐨𝐤 𝐰𝐫𝐚𝐩 now restores the terminal after SSH disconnects or other abrupt child exits. • 𝐋𝐨𝐜𝐚𝐥 𝐁𝐚𝐬𝐡 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 no longer keep a persistent shell across calls, avoiding failures after directory deletion. • 𝐂𝐨𝐩𝐲𝐢𝐧𝐠 a multiline queued prompt now copies the complete text instead of a collapsed summary. • 𝐅𝐢𝐱𝐞𝐝 𝐚 𝐫𝐚𝐜𝐞 where an early cancel could permanently wedge a session's turn slot. • 𝐂𝐨𝐩𝐲 𝐨𝐯𝐞𝐫 𝐒𝐒𝐇 or in containers now shows clearer feedback when delivery cannot be confirmed. • 𝐕𝐨𝐢𝐜𝐞 𝐬𝐩𝐞𝐞𝐜𝐡-𝐭𝐨-𝐭𝐞𝐱𝐭 now works with per-model API keys in config.toml without requiring `grok login`. • 𝐠𝐫𝐨𝐤 and the agent binary now stay in sync even when no update is installed. Listen to the video below for more details.

• 
  Scarlett claira (@AItechscarlett) reported 32 minutes ago

  In 2014 a Swedish engineer named Knut Sveidqvist lost a Microsoft Visio file. He went to open the diagram he had drawn a few months earlier. It was gone. Every box, every arrow, every label. All of it had to be redrawn by clicking through Visio menus again. That night his kids were watching The Little Mermaid on TV. He named his fix after the movie. Twelve years later Mermaid has 89,101 GitHub stars, 8 million users, and native rendering inside GitHub, GitLab, Notion, Obsidian, VS Code, and Confluence. Here is what the paid market still charges to draw the same boxes. Microsoft Visio Plan 2. $15 per user per month. Lucidchart Team. $10 per user per month with a three-user minimum. Miro Business. $20 per user per month. Fifty engineers on Miro Business burns $12,000 a year to draw arrows between boxes. Mermaid replaced the drag-and-drop editor with a text spec that reads like Markdown. ``` graph TD A[User] --> B[Login] B --> C{Valid?} C -->|Yes| D[Dashboard] C -->|No| E[Error] ``` Ten lines. Renders as a real diagram. Every version of Claude, ChatGPT, Gemini, and Cursor already knows how to write it. You describe your architecture in plain English and the model returns a Mermaid block. Paste it into a GitHub README. Paste it into an issue. Paste it into a pull request. GitHub renders it inline as a live SVG. No plugin. No sign-in. The paid tools shipped drag-and-drop editors. Mermaid shipped a text spec that the LLMs learned on their own. Flowcharts, sequence diagrams, class diagrams, state diagrams, entity-relationship diagrams, user journey maps, Gantt charts, pie charts, *** graphs, mindmaps, timelines, C4 architecture diagrams, treemaps. Anything you would open Visio for. Version 11.16.0 shipped two weeks ago. Because the diagram is text, it lives in your repo. Because it lives in your repo, it goes through code review. Because it goes through code review, it stops rotting. Nobody has to remember where the Lucidchart account is. Nobody has to pay $10 a month to reopen a five-year-old file. MIT license. 89,101 stars. TypeScript. The library is free forever. Mermaid Chart the company sells a hosted editor on top for teams that want one, but the core stays MIT. Somebody in Sweden lost a Visio file and refused to draw it again. Twelve years later the paid diagram tools still exist, and nobody who writes software has to use one. (Link in the comments) @AItechscarlett

• 
  Лев Тигроедов🇵🇸🌈🗽➡️ (@ElmntTigroedium) reported 33 minutes ago

  @github you are pice of lasy, coward **** who hiding problems insted of fix them. Burn in hell!

• 
  Paramveer (@techparamveer) reported 33 minutes ago

  @dominikkoch @jacobmparis @vercel github was down last night for a bit

• 
  Charlie Lamb (@charlietlamb) reported 34 minutes ago

  Genuinely what is the hardest infra problem out there and where does GitHub sit in this list

• 
  TheRegularJoeCEO (@RegularJoe_Ceo) reported 37 minutes ago

  Today, the Broad Institute at Harvard and MIT posted the story in the comments and the GitHub repo about the alpha fold process, and I forked the repo and improved it. You can just do things. I really like GitHub because you can go find somebody who's publicly publishing a problem, and you can just fork their repo and fix it and send it back to them. It's a really fair system. It either works or it doesn't, and if it works, everybody can see it.

• 
  PƎPΔ (@jvasata03) reported 38 minutes ago

  @00aventurine @Jooornio An artist is posting their art to show people their skill, progress, promote, etc. It's wrong to train AI on this content IMO. I am putting my code on GitHub so other people can use it if they need to and thus have no issue with AI being trained on it.

• 
  Cennes100 (@Cennes100) reported 40 minutes ago

  EVERYONE PAYING FOR AI VIDEO TOOLS IS ABOUT TO FEEL SILLY. Most people see a slick paid tool like Higgs Field and assume that's just the price of entry. Locked behind a subscription, no way around it. That's the problem. People keep paying monthly for models they don't own, on servers they don't control. The mechanism: a guy named Anil Macha rebuilt the Higgs Field cinema studio and dropped it on GitHub, free and open source. Same idea, same workflow, zero paywall. The detail most people miss: this isn't a cloud wrapper charging per generation. It runs on open source models on your own computer. No subscription, no credits counting down. That changes what's possible: 1. Run cinema-style AI video locally, whenever you want 2. Iterate endlessly without burning credits 3. Tweak the pipeline instead of trusting a black box This isn't just "a free alternative dropped." It's proof the moat these tools lean on was never that deep. Most people use tools like Higgs Field because they think power has to be rented. This setup uses the same power and just... owns it. Follow: @Cennes100

• 
  Tanish (@Tanishrajurs) reported 41 minutes ago

  They've shipped an MCP server any AI agent (Claude Code, Cursor, VS Code) can now search their full paper database, read PDFs, explore GitHub repos. Agents standing on 3M+ papers instead of guessing

• 
  Nicholas Preston (@Mike_Preston17) reported 43 minutes ago

  Speak for yourself and your code, Sam. If the frontier models were as good as you claim, GitHub would never go down, Cloudflare wouldn't keep crashing, Linux Torvalds would finally retire from programming and Windows 11 would be fixed, and the top 5 AI Billionaires wouldn't be millions and potentially Billions in the red right now from training all those models. You're just drinking the kool aid, Sam. AI doesn't have any wisdom on what should be made or fixed. Which was one of the points of my thread. Which you'd know if you could code your way out of a paper bag. ..... or red my post throughly ..... or asked questions like a real engineer. Thanks for illustraing another reason for local llms and private codebases: dipshits.

• 
  Nick Martin (@NickM4rtin) reported 43 minutes ago

  Level 3 adds routing — a typo/chore, a bug, and a full feature no longer run the same heavy flow. Level 4 runs plans in isolated *** work trees. Level 5 turns the GitHub board into a shared blackboard so parallel terminals claim issues without colliding.

• 
  Forgehausens 🏳️‍⚧️ 🇦🇺 (@The_HRforges) reported 44 minutes ago

  Eh "stealing code" isn't even really that real because most programmers I know will copy/paste **** from github if it means they don't have to figure out how to do it themselves. The problem with AI generated code is not the same problem as AI generated art.

• 
  Jesse Showalter (@imjesseshow) reported 44 minutes ago

  My friends think I'm throwing a party. I built a full product workflow disguised as a game. Character assignment. Clue tracking. Suspect board. Host dashboard. Figma, Claude, GitHub, Vercel, Supabase. The stakes are real. Friendship stakes. If the app crashes mid-clue, I fix it in front of people who know where I live. AI didn't remove the pressure. It removed the excuses. What would you build if you stopped stopping at the mockup?

• 
  Feral (@feraltekk) reported 48 minutes ago

  Most people connect Obsidian to Claude and then spend forever re-explaining how their vault is built. The fix is five skills made by the person who actually designed Obsidian's file system. Claude follows the real rules instead of winging it. Five skills. Two commands to add them. From then on Claude loads them every time it touches a note. 39,000 stars on GitHub. Barely anyone is using it yet. And once Claude actually understands your vault, the loop can start. You have written the same idea three times this year. You do not know that yet. Your notes app does. A loop rereads the vault every six hours. Finds what repeats. Flags what was abandoned. Surfaces the note you forgot you wrote. You cannot see your own patterns from inside your own head. The loop does it now.

• 
  Ryan (@Gelassoldat) reported 52 minutes ago

  @tinytechfox Yeah, I clicked on Get Started then chose GitHub as the sign in, and it blocked a github sign in.

• 
  Helio (@helioim_ai) reported 59 minutes ago

  Helio AI teammates now connect directly to the tools where your work lives. → Connect Notion, Slack, Gmail, GitHub, Figma, X, Bitly, or Outlook and your AI teammate doesn't just tell you what needs to be done. → They write the doc, post the update, open the issue, send the follow-up, publish the post. The work doesn't stop in a chat thread. It goes where it was always supposed to go.

• 
  MasterMaind .. (@ASaudidos) reported 59 minutes ago

  i changed the ps4spoof github repository to private i do not plan to fix or update it because some dishonest people may use it to fake a jailbreak promote something that does not exist and collect donations from the community