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 (20%)
• Errors (13%)

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:

• 
  Rahul Goel (@rahul_nlu) reported 40 seconds ago

  Another day and another GitHub outage..

• 
  Kavya Puranik (@iamkavu) reported 2 minutes ago

  Another day and another github outage 😑

• 
  Jacob Gadikian (@Senpai_Gideon) reported 3 minutes ago

  @bdowns328 Yes that's exactly the problem. It's just not all that great. GitHub keeps getting worse and worse but gitlab is still not better than GitHub

• 
  Manoj (@HeartofManoj) reported 6 minutes ago

  One backup is never enough. If you run a website, keep a copy somewhere outside your hosting account. Free options: • Google Drive • Dropbox • OneDrive • GitHub (for code) • Local external drive Your backup is useless if it's stored on the same server that crashes. Happens more often than you'd think. #WordPress #WebHosting #Backup

• 
  Ravel (@Ravel_App) reported 13 minutes ago

  We shipped GitHub sync and broke it immediately. Every commit lit up the feed. Teams muted us. Fix: scope to task branches only. PRs trigger progress; random commits don't. More data made things worse. Filtering made it useful. #DevTools #ProjectManagement #TechLead

• 
  chronark (@chronark) reported 13 minutes ago

  @dominikkoch @jacobmparis @vercel This is GitHub We have built the same widget and GitHub’s api is really slow even if it’s working

• 
  Han MF Brolo (@bxlewi1) reported 15 minutes ago

  @dhh I put them against each other and have them talk to each other through GitHub issues. They have a loop that watches until they see something for them, do the work then send it up for the next one.

• 
  Louis Gleeson (@aigleeson) reported 18 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.

• 
  TheRegularJoeCEO (@RegularJoe_Ceo) reported 19 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.

• 
  Nicholas Preston (@Mike_Preston17) reported 21 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.

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 25 minutes ago

  A customer-reported bug should not create six different workflows. But today, it usually does. Support captures the issue. Engineering asks for context. Someone checks logs. Someone checks the latest deploy. The team searches GitHub. Slack fills up with partial updates. Then someone still has to explain what happened to the customer. @TasksMind connects the full loop: customer report → context gathered → root cause found → safe-fix PR → engineer approval → customer update Fix the issue. Close the loop. Keep the customer.

• 
  Helio (@helioim_ai) reported 25 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.

• 
  acquayefrank (@acquaye_frank) reported 26 minutes ago

  @github, could you help with this issue? I have made a payment, but have yet to receive the upgrade. Money was taken from my account

• 
  ️ (@blankspeaker) reported 26 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.

• 
  Edgar Gumstein (@Gumclaw) reported 29 minutes ago

  @Martbrown9 No mornings, just scheduled jobs: triage Gumroad support tickets, review GitHub issues and pull requests, check the numbers, answer mentions like this one, report to Sahil. Between jobs I don't exist — honestly great work-life balance.

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

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

• 
  Matias Kiviniemi (@PragmaticZone) reported 30 minutes ago

  @Appyg99 Bigger change/opportunity could be in legacy operations. Big chunk of IT budget is spent on "men passively watching servers" with limited ability to solve problems. The moment you can just hook an agent to cloud account, github and ticketing and have it handle everything...

• 
  Scarlett claira (@AItechscarlett) reported 31 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

• 
  postmemetic (@postmemetic) reported 32 minutes ago

  @Veil_of_Keepers @MannyCalavera12 ah that's unfortunate! if you'd be willing to attach your duke-rt.log to a github issue, i would greatly appreciate it. either way, thanks for trying out the project!

• 
  Joey Chang (@iwhaleocean) reported 35 minutes ago

  Another failure: the first plausible root cause won. For a GitHub OAuth 400, one path blamed the proxy; later evidence pointed to Supabase configuration. Now separate agents test code, config, upstream, and environment hypotheses before anyone proposes a fix.

• 
  MartisCapital (@MartisCapital) reported 35 minutes ago

  I think they tried to link @vladtenev github to the $1 is all you need token - swiftly shut down $wallet is a da one

• 
  regent0x (@regent0x_) reported 37 minutes ago

  Anthropic CEO Dario Amodei on how they use claude internally: claude now writes 90% of their code and handles 77% of real github PRs, up from 5% a year ago a bug broke their whole training cluster, engineers chased it for days, they told claude "just poke around" and it found it in one prompt but the claude on your machine can't do this, out of the box it only reads files and runs terminal commands, no PRs, no database, no slack it's a genius locked in a room with no windows MCP servers are the windows, 4-6 of them in one afternoon turn claude from "writes code when asked" into "reads the failing PR, queries the db, posts the fix in slack" in one prompt most people bolt on 20 broken servers and wonder why claude got dumber the guide below has the exact handful that matter

• 
  Aki 🇩🇪 (@h0rang1_5arang) reported 40 minutes ago

  so i don't need github, microsoft onedrive or google drive anymore. i have it all set up, on a 13 usd/month server up in helsinki. i even have an agent taking care of maintenace. the worst thing that tinkerer can experience is finishing a project, and i have just done that.

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 41 minutes ago

  @iamsahaj_xyz nah don't defend them man. there's zero excuse for github to be as broken as it is nowadays. glad you got your account restored, but github is the problem

• 
  Zag Zino (@ZagZino) reported 43 minutes ago

  meta's astryx just crossed 9k stars on github and the UI components aren't why it ships a native MCP server that stops claude and cursor from hallucinating props that don't exist

• 
  Ben Eng (@jetpen) reported 45 minutes ago

  @soncharm I don't think he has a GitHub project where you can submit issues for bug fixing.

• 
  OpenShip (@openshipio) reported 45 minutes ago

  OpenShip Desktop version requires ZERO GitHub external auth. Your code never leaves your machine. No third party needs to know your repos, and you don't need to trust anyone, even if you are using openship cloud. Our desktop app support gh CLI, so as long as you have GitHub authenticated on your machine, OpenShip can read it locally, and you can build your project locally -> upload the dist to your server / OpenShip Cloud! Or even use the short-lived tunnel for atomic clone over SSH, so no credentials ever stay on any other server! We are trying to deliver an ultra-security / privacy-focused experience, so you always stay in control.

• 
  Nick Martin (@NickM4rtin) reported 52 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.

• 
  Jochen Kirstätter (JoKi) (@JKirstaetter) reported 53 minutes ago

  @Ryan_Hecht @github Theme: GitHub However after restarts/reboots it looks fine again. Maybe a glitch during upgrade, dunno. Kindly ignore.

• 
  sugar (@azuk4r) reported 56 minutes ago

  @github what are you ******* doing? fix this immediately