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	6 days ago
Paris	Website Down	9 days ago
Saint-Paul	Website Down	10 days ago
Saint-Paul	Website Down	10 days ago
Mexico City	Sign in	11 days ago
León de los Aldama	Website Down	11 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:

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

• 
  Bankr (@bankrbot) reported 12 minutes ago

  @Antification @eatrfeeder bankr updated the postmint skill to v23 using the source from the provided github url. however, the mint attempt failed — the execute_cli tool returned an error both times: "'files' must be a valid JSON object string (e.g., '{"script.ts": "console.log(1)"}')". i haven't fixed that yet. you can ask me to try the mint again and i'll attempt it fresh.

• 
  Carlos (@clutchv1lle) reported 13 minutes ago

  Github has a UX problem, it doesn't prove anything tech savy

• 
  Gagan Suie (@gagansuie) reported 13 minutes ago

  Researchers this month showed how planting instructions inside a public GitHub issue can trick agentic workflows into acting on them as legitimate tasks.

• 
  Ching-Yuen Huang (@Michael_Huang_W) reported 13 minutes ago

  Unintentionally created a duplicate Pro account due to @cursor_ai's GitHub/Google login architecture, which auto-renewed for 6 months with 0% usage. Since I am already an active paying user on my primary research account, billing support flatly refused to even transfer store credits. Any chance @arvidlunnemark can help a dev out?

• 
  Andreas (@AndJakobsson) reported 15 minutes ago

  Lots of talk about AI agents these days and specifically loop engineering or even graphs as per the latest tweets and x articles Anyway, for coding I feel that cursor ai IOS app is really cool and useful. It is directly connected to my GitHub and I can just talk or write into it and ask for an improvement or a new functionality I know this is maybe less efficient than some of the other optimal setups but I feel that combination of pushing GitHub further with issues and even for second brain type notes and contexts in MD files, will make the Cursor IOS app really powerful.

• 
  Rebel AI (@realrebelai) reported 15 minutes ago

  anyone elses github issues not posting to their notifications? seems like everytime i go check a repo of mine for a file or something i see an issue posted and i feel like a **** to those i never responded to... even though its not my intention at all lol

• 
  Matt (@m13v_) reported 17 minutes ago

  turns out podlog already does this. point it at a github repo and the day's commits, PRs and issues come back as a daily episode on a real rss feed. it runs feeds for rust, pytorch, kubernetes, ~2,950 repos, free for public ones written with ai

• 
  Manol T. (@manol_ai) reported 19 minutes ago

  @syakirbuilds Yeah i thought a lot. MCP has built in authentication oauth2.1 protocol which makes it production ready. I used Supabase to make the server and connected Gmail and Github so people could authenticate into my MCP. I will add stripe checkout on top and I am ready to go

• 
  The Cabal (@TheBasedCabal) reported 20 minutes ago

  Gitbook is the biggest scam on the planet. Paying $70 for some trash... Gitbook's github Checks also never complete just stay yellow forever. Terrible overpriced garbage service that should be dead in 2026. Any half assed AI can create a docs page 1000X better. Gitbook is trash.

• 
  vorty (@vorty279) reported 22 minutes ago

  i built my own ai assistant that runs my life. that's how the video opens. it reads email, runs the calendar, drives a browser, drops the grocery list into telegram, works 24/7 under the hood it's openclaw. an open-source ai agent, apache license, over 200k stars on github. full system access, shell commands, browser control, memory across sessions, connects to 50+ chat platforms what you're being sold. later in the same video kiloclaw shows up. hosted openclaw in 2 clicks, 49 bucks a month so you don't have to deal with setup and it's an honest deal once you break it down. the openclaw engine is free and open. you're not paying for the agent. you're paying to not install node, not run docker, not babysit it when it crashes at 3am that's a fine trade if your time is worth more than an evening of setup. but know exactly what you're paying for. not the assistant's brains. the fact that someone spun up the server for you the agent itself clones from github today and runs on your own machine for zero github dot com slash openclaw

• 
  Adeniyi Victor (@Vieester_) reported 26 minutes ago

  Seem there is an internal system error with deployment using github @render

• 
  Max ¯\_(ツ)_/¯ (@MaximumADHD) reported 28 minutes ago

  This fixed itself after a few hours, I think it was a GitHub outage.

• 
  Cennes100 (@Cennes100) reported 30 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

• 
  Satoshi's Cat (me/mine) (@SotoastiNotmoto) reported 31 minutes ago

  @NEEDcreations This speaks to a broader issue: Core could do a whole lot better at their communication. I don't think them saying "refer to Github" is adequate. That being said, it must be frustrating being Boeing engineers being told by passengers how to build a plane.

• 
  Michal Wolski (@michalwols) reported 35 minutes ago

  @_simonsmith That's how you get "Kimi Shannon" and Dario, CEO of Moonshot a huge portion of github commits get signed as authored by claude, anyone training on code will keep having this issue

• 
  divyansh tiwari (@DivyanshT91162) reported 36 minutes ago

  Someone just built the review layer AI coding tools were missing. Instead of reviewing AI-generated HTML inside a chat window, Lavish opens it in your browser so you can click the exact element that's wrong and send precise feedback back to your AI. No screenshots. No vague instructions. Just point, click, and review. Here's why it's impressive: • Click any element or highlight text to target changes with pixel-level precision • Edit Mermaid diagrams like a whiteboard with built-in Excalidraw support • Runs entirely locally — your artifacts and review sessions never leave your machine • Works with Claude Code, Codex, GitHub Copilot CLI, and OpenCode through session hooks • Built-in playbooks for plans, diagrams, tables, comparisons, code reviews, slides, and more • Automatically catches broken layouts, clipped text, overflow, and rendering issues before review • Live reload while editing HTML without losing your workflow • Zero install required: "npx -y lavish-axi" Launched around 2 months ago. Already crossed 2,000+ GitHub stars and 168+ forks. 100% Open Source MIT Licensed Repo👇

• 
  aventursne (@00aventurine) reported 37 minutes ago

  @jvasata03 @Jooornio i agree that code on github and such being used for ai is mostly ethical. my issue is that i cant find a good reason why art should be treated differently other than some vague "it feels icky". so i choose to not really say anything

• 
  order and chaos at work (@__orderandchaos) reported 37 minutes ago

  @Amank1412 I've set it up at work. Pulls the ticket from Jira, does the work, runs tests and checks, pushes to GitHub, it reviews the PR (alongside our dev reviewers), then fixes the issues raised and repeats until approvals. Also moves the ticket status as it progresses.

• 
  OIiver (@posedscaredcity) reported 40 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.

• 
  harald (@HaraldvanLintel) reported 41 minutes ago

  @jsm2334 It's the opposite, rejection of deaths that are replaced by the higher risk deaths instead of added; it's an issue for detection of small additional risk. The AI got another version from github than I got, there seems to be a caching issue, here's the code that slightly differs:

• 
  Ching-Yuen Huang (@Michael_Huang_W) reported 44 minutes ago

  Unintentionally created a duplicate Pro account due to @cursor_ai's GitHub/Google login architecture, which auto-renewed for 6 months with 0% usage. Since I am already an active paying user on my primary research account, billing support flatly refused to even transfer store credits. Any chance @ArVID220u can help a dev out?

• 
  Bart De Ruyck (@bartderuyck) reported 48 minutes ago

  @MarkJSzymanski You lost me at "no server to go down". How do you think static files are served to visitors, then? Whether it's Github Pages, Cloudflare Workers, Vercel, whatever: it's on a server. And it can go down.

• 
  riya (@riya_mishra007) reported 49 minutes ago

  10 years ago you needed a team. Today you need a laptop to build a SaaS at $0 to earn more than +$10M. Claude for coding. Supabase for backend. Vercel for deploying. Namecheap for domain. Stripe for payments. GitHub for version control. Resend for emails. Clerk for auth. Cloudflare for DNS. PostHog for analytics. Sentry for error tracking. Upstash for Redis. Pinecone for vector DB. It's not that difficult broooo.... You can literally ship a startup sitting home.

• 
  Marsu (@marsuplamy) reported 50 minutes ago

  Think of blockchain like a very smart person locked in a room. Everything inside works perfectly, calculations are correct, rules hold, no one can cheat the system. But it can't talk to the outside world. It doesn't know the weather, doesn't know the market, doesn't know whether a job was completed or not. Unless someone comes in and tells it, it has no idea what's happening out there. This has been blockchain's fundamental problem for over a decade. Think about it through everyday examples. A freelancer finishes a job and pushes to GitHub. How would the smart contract know? There's a crop insurance agreement that says if it doesn't rain this month, the farmer gets compensated. How does the contract check the weather? A payment deal says if the dollar rate crosses a certain level, auto-conversion kicks in. Where does the contract pull the exchange rate from? The answer to all of these has always been the same. Set up an external oracle service, integrate it separately, trust it separately, pay for it separately. @RialoHQ solves this problem from inside the protocol. A smart contract can make a direct HTTP call to any web API with a single line of code. It can pull a GitHub pull request status, read weather data, fetch live exchange rates, query a company's credit score. None of these require setting up an external service because this capability is already built into the protocol. What does this mean in practice? Think back to the escrow system in Onyx. The client locked the funds, the freelancer pushed the work to GitHub. The contract looks directly at the GitHub API, checks whether the work was delivered, and automatically sends the payment once the condition is met. All of this happens with a single HTTP call and there is no middleman in between. Blockchain is no longer a smart person locked in a room. It's a system that can talk to the outside world, see what's really happening, and act on it.

• 
  Dylan Colquhoun (@ValidatesUser) reported 51 minutes ago

  Hey, long time lurker of your content on github Im having trouble with, I think, your turboquant llama code fd1be2101 is last stable build, cmake is throwing serious issues everywhere But it seems to think its missing a loading.html fIle? 471fb4ec8 today? @no_stp_on_snek

• 
  librepup (@librepup) reported 52 minutes ago

  @GrokInsider Just connected my GitHub, described my issue which, by the way, has been mentioned only like 3 times online, and was never solved with anything except a full re-install, and it gave a step by step guide to fix everything.

• 
  Benji AI (@AIfutureBenji) reported 54 minutes ago

  @aisearchio oh , yes similar issue, trigger word uncensored, Google YouTube don't like it. I got 2 videos have this keyword, it said it's violate the policy in 0:30 duration. But there's nothing on that video 30 second mark, it was just a GitHub page quote and it still happen.

• 
  Shoopy (@0xShoopy) reported 56 minutes ago

  "in a year, we'll let the model generate the code and nobody will actually look at it." that's the person running DeepMind's coding research. Benoit Schillings (leads the Thinking, Reasoning and Coding teams at Google DeepMind), on where code goes next: → his analogy: nobody checks their compiler's assembly output anymore. code review is heading the same way → about 80% of new code added to GitHub is already machine-generated, so the human training data is running out → the answer is self-play. models write their own challenges, judge the answers, even judge the architecture. AlphaZero, but for code → he calls SWE-bench infamous: it checks whether code runs and returns the right output, and that's a small slice of what engineering actually is → what he wants instead is open-ended problems. hand it 10MB and say write the best lossless compressor you can, scored on compressed size plus your source size. that forces genuinely new algorithms He's blunt that syntax generation is over. which means the job left is specifying what you actually wanted, and proving you got it.

• 
  Student Offers (@StudentOffersHQ) reported 1 hour ago

  $240/yr of auth infrastructure. Free for students. @clerk Pro is $20/mo. Students: $0 for your entire degree via the GitHub Student Developer Pack. Auth without building auth: drop in prebuilt <SignIn/>, <SignUp/>, <UserButton/> components, style them to your brand, ship. What Pro unlocks: • 50,000 monthly users, same limit as paid Pro • MFA + passkeys, no "Secured by Clerk" branding • Organizations: B2B auth for SaaS apps • Billing: subscriptions with zero Stripe code • Bot protection + sign-in logs built in & more Clerk is AI-native. Agent skills teach Claude Code, Codex, Cursor & more to wire up auth, orgs and billing. A CLI with agent mode handles users, env keys, deploys. Plus an MCP server. Claim in 3 steps: 1. Get the GitHub Student Developer Pack (school email or proof of enrollment) 2. Click the Clerk tile on the pack page 3. Connect GitHub inside Clerk, keep it connected (applies to one workspace) No card. Only SMS auth excluded. After graduation you keep the free Hobby plan.