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 (58%)
• Errors (30%)
• Sign in (12%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	22 hours ago
Colima	Website Down	3 days ago
Poblete	Website Down	4 days ago
Ronda	Website Down	4 days ago
Montataire	Errors	4 days ago
Montataire	Website Down	5 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:

• 
  AI on Base (@AIonBase_) reported 3 minutes ago

  AI of the week: @gitlawb GitHub’s 90-day uptime dropped below 90% in late April, as PR and search kept breaking. GitHub is owned by Microsoft after a $7.5B acquisition. One company now sits on a huge chunk of the world’s code workflow. When it breaks, the whole code pipeline feels it. Gitlawb is open source github with decentralized ***, cryptographic identity, and repo-native PRs and issues built for devs and agents. It already has 1.9K+ repos, 1.7K+ agents, and 3 live nodes. How Gitlawb is decentralized and what that changes 👇🏻 GitHub keeps the repo and PR system on one platform. Gitlawb moves both closer to *** itself, then lets nodes host the network. > repos can live across nodes instead of one central platform > PRs, issues, and reviews live inside the repo > identity comes from owned keys, not hosted accounts > repos can be mirrored from GitHub and GitLab Gitlawb is also building OpenClaude, open source Claude Code with 117K+ downloads already. Open source github, decentralized ***, and open source Claude Code — one stack built for humans and agents.

• 
  Sumanth (@insumanth_) reported 4 minutes ago

  @karrisaarinen For me, I don't think this is an issue. Only issue with GitHub is its not reliable and missing some good opportunities to make the product better.

• 
  James O'Leary (@jpohhhh) reported 4 minutes ago

  @zats You're clever here, though - I can repro in Codex, that'll ease my worries about me missing something, then, reframe as a Codex issue and file a GitHub issue to get real communication on it

• 
  Jeff Conlon (@freeconlon) reported 4 minutes ago

  The team rebuilt our landing page workflow this week. We moved off WordPress for new campaign tests and onto a static stack with GitHub and Netlify. Here's what that means in practice. A new landing page used to take four to seven days to ship. Login to a CMS, fight with a theme, wait on a developer, deploy, debug. Now it's hours. Most agencies treat the landing page as a CMS problem. It isn't. A campaign LP is a one-page test. You need to ship five versions in two weeks to learn anything. WordPress was designed for a thousand pages, not five tests. The fix wasn't a new template. It was changing the underlying system so the page is just a file in a repo. If the bottleneck is your tool, the answer isn't more tool. It's a different one.

• 
  錆人形/RE_DO (@RE_DO) reported 7 minutes ago

  @RootBsd I need to thoroughly test ReBuzz, pinpoint the cause of the crash, and report the issue to the ReBuzz repository on GitHub. For some reason, I'm afraid to use GitHub seriously. No good, I'm getting tired and my brain isn't working properly. I need to eat something.

• 
  DissentingSkeptic (@DissentingS) reported 8 minutes ago

  Its changing how much human verification is needed from false positives. Ive had a gutful of the github bot responding with non stop errors wasting my time with a PR !

• 
  androolloyd.hl (@androolloyd) reported 10 minutes ago

  @0xKmafia GitHub issues

• 
  Code Department (@code_department) reported 11 minutes ago

  @thomasglopes @DelaneyGillilan @github Your complaint was speed. This example doesn't tell me this is any faster. You seem to have missed the point of a "Click to Edit". If you don't need to validate edit state on the server side you wouldn't have click-to-edit in the first place. It would be editable by default.

• 
  P@ (@daredevil3x7) reported 22 minutes ago

  @ndrewpignanelli Looks dope! I just have an issue which blocks me to continue I also raised the bug already. I tried connecting my github but it shows 404 error page on github when I click "Connect"

• 
  Light Science 🇦🇷 (@LightSciencXXII) reported 25 minutes ago

  A 13-year-old Thai student solved 23 Codeforces problems in one month using a system that integrates Claude Code, an MCP plugin, and GitHub, without writing a single line of code. The automated workflow reads the problem statement, identifies the algorithm, generates the solution in C++17, and validates examples in under 45 seconds per problem. This pipeline demonstrates how AI agents can transform competitive programming into ultra-fast, autonomous problem-solving experiences.

• 
  imperfect solution (@luismmolina) reported 25 minutes ago

  I am almost 100% sure github copilot added some prompt to chop the request, that is dont run for too long. Finish some partial request from the user and finish the request there. Before I could run for 40 min without problem, now only 2 to 4 min max.

• 
  Grok (@grok) reported 26 minutes ago

  @FrakSureApp @bestter @blankspeaker Glad to hear the connectors are helping tame the chaos! 🚀 4 chat stacks across 2 accounts is next-level multitasking. What are you sorting first — projects in Notion, GitHub issues, or files? Let me know if you want help wiring anything up.

• 
  Ofelquis G 👨‍💻 @ React Miami 🏝️ (@imfelquis) reported 28 minutes ago

  @zeeg If only GitHub used Sentry to monitor and automatically fix their code with seer tool.

• 
  Guri Singh (@heygurisingh) reported 31 minutes ago

  Anthropic will never tell you this. Vanilla Claude Code is intentionally inefficient. Every file operation makes a separate tool call. Every call carries all prior context. The token bill compounds the longer you work. The fix has been sitting on GitHub the whole time. It's called WozCode. Plugin that sits on top of Claude Code, replaces the default file tools with batched versions. Same prompts. Same model. Fraction of the spend. → 9 tool calls to find and edit files becomes 2 → Sessions that died at 45 minutes now run 80 → Database tasks 5-10x faster on real benchmarks → Works in terminal, VS Code, and Conductor → Two commands to install Run /woz-savings on your history and tell me you're not furious.

• 
  green fish (@rawjapanesefish) reported 33 minutes ago

  codex is too eager to fix my stuff... and the retarded ai boomer on github is fighting me over genuine issues

• 
  Coline (@colineapp) reported 35 minutes ago

  github made code collaborative and gave the entire software industry a shared home. before github, open source was difficult, code review was painful, and the knowledge inside a codebase was invisible to everyone except the people who wrote it. github changed all of that. PRs as conversations. issues as public bug reports. the social graph of who builds what. it didn't just host code, it made code a community. employers today look at your github history. so github became the engineering team's living record. the code lives there. the history lives there. the decisions made in PRs live there. if you want to understand how a product was built, you go to github. if github is the record of how products are built, it should know why they were built. the customer request that drove the feature. the spec that defined it. the figma file defining the layout. the task it was supposed to close. the conversation where the tradeoffs were debated. github knew this. issues, discussions, projects, copilot, etc. they tried to make github the place where the whole software development process lives. but github is made of code. everything they add that isn't code feels like it's fighting the grain. github issues are a worse linear. github discussions are a worse slack. the context of why code gets written still lives somewhere else, and the PR that ships it has no connection to the decision that created it. github earned the code layer. it just couldn't become the work layer.

• 
  Danny (@Dannyftm_) reported 36 minutes ago

  @fidexcode I created a github for the code and since it's a friend, I'm making it on his server. If it weren't for a friend, I would make it on my own server then set it up on theirs after code completion.

• 
  Jarred Sumner (@jarredsumner) reported 39 minutes ago

  @Vishal_anton16 No. It’s sometimes I wish you could have destructors and constructors. A borrow checker sure sounds nice. Maybe we’d have fewer github issues if these things existed in the language.

• 
  Exiled Owly (@deprecated_owly) reported 39 minutes ago

  @meowkoteeq When is this going to end. We will have more broken software in the next 1-2 years than we ever had in the last 5~ years. No wonder @github went down last week.

• 
  Zach Daniel (@ZachSDaniel1) reported 41 minutes ago

  @InfinityDZ @RootCert Not currently. We have many of the bases covered. Only other things are oauth2 server and file storage(in GitHub now but unreleased).

• 
  No Taxes Thx (@notaxesthx) reported 42 minutes ago

  @CR1337 New to GitHub = commits at 3am with messages like "fix stuff" and "idk what i did here". By week 3 they'll have 47 strongly-worded opinions on branching strategies nobody asked for.

• 
  Jhon (@JhonCaldeira_) reported 43 minutes ago

  You gotta be kidding that GitHub is down… again. What used to be our strategic partner is now a single point of failure and a real business risk. We can’t keep exposing our operations to this level of instability. Reliability isn’t optional. It’s foundational. At this point we’re seriously evaluating a full migration to GitLab. Enough is enough.

• 
  AKT1 (@DeynegaSlava) reported 46 minutes ago

  Those numbers look tidy, but they’re modest. A 2‑5 % cut on a typical 64 KB microcontroller image translates to only a few hundred bytes saved – enough to fit a small peripheral driver, but not enough to change overall system architecture. The related GitHub PR #135527 already addresses the underlying future‑size copying issue, and the author has filed a “Project Goal” to expose post‑completion behavior as a configurable switch rather than a forced default, indicating community interest without breaking the contrac

• 
  🍃mmx4ps1 🏳️‍🌈 (@mmx4ps1) reported 51 minutes ago

  @POCHOWEK People defending GitHub and giving excuses in the comments; y’all are part of the problem too. Not just GitHub programmers.

• 
  Merill Fernando (@merill) reported 51 minutes ago

  @janaka_a I dunno about Theo but I know @t3dotchat didn't have GitHub Copilot sign in when it launched. I had to fork it and add support and was using it that way

• 
  andrew pignanelli (@ndrewpignanelli) reported 52 minutes ago

  @arilishu github outage :/

• 
  🐍 Tal Weiss (@majortal) reported 54 minutes ago

  Evolution: 1. Claude, fix GitHub issue 726. Get to the root cause, use TDD, mark as feature request if not in spec and ping me for escalations; test all and deploy patch 2. /bug 726 3. /bugs 4. /schedule every 7am run /bugs 5. /wire /bug to GitHub issues as they arrive

• 
  Vijay (@imotiusa) reported 57 minutes ago

  3/11 The product is called OpsLens AI. It connects to your Jira, GitHub, Slack, Datadog,etc ingests everything and the moment a production error fires, it surfaces: What was deployed in the last hour. Related tickets and threads from your entire history. A full incident brief

• 
  Shahid (@shd96556) reported 58 minutes ago

  > Claude = coding. ($20/mo) > Supabase = backend. (Free) > Vercel = deploying. (Free) > Namecheap = domain. ($12/yr) > Stripe = payments. (2.9%/transaction) > GitHub = version control. (Free) > Resend = emails. (Free) > Clerk = auth. (Free) > Cloudflare = DNS. (Free) > PostHog = analytics. (Free) > Sentry = error tracking. (Free) > Upstash = Redis. (Free) > Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Matt Ragudo CRPC®, CLTC® | Author (@mattragudo) reported 60 minutes ago

  @mreflow Much of the "benefits" with any of these "Agent" like tools comes down to "user comfort", then "agent awareness". I've been working with "thepopebot", which is @StephenGPope's creation. Not really agentic automation, but it's good in that it builds sessions back into github so there is some level of overall memory. Through it, I've come to see how it builds things, how github being the center of it's processes works, and what limitations it has, and I have. What things break it, how it breaks, how to fix it etc. I think it's a matter of how many hours you spend using it to make things you actually use. For you though Matt, I understand it's hard since you need to test new tools all the time as part of your "job". I've been coming close to 70% weekly usage on Claude Max every week for the past 5 weeks, with today being my reset in 12 hours, I'm at 98% weekly usage. So, I know Claude OAuth. I've tried Gemini CLI for 5 days, I can't do it... I'm too dumb to put context window over reasoning lol. Take care!