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 (60%)
• Errors (29%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	3 days ago
Montataire	Sign in	6 days ago
Colima	Website Down	8 days ago
Poblete	Website Down	9 days ago
Ronda	Website Down	9 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:

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 2 minutes ago

  Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant. - No VC funding. - No viral launch. - No TED talk. - Just two engineers at Bell Labs. A terminal. And a problem to solve. He built a language that fit in kilobytes. 50 years later, it runs everything. Linux kernel. Windows. macOS. Every iPhone. Every Android. NASA’s deep space probes. The International Space Station. > Python borrowed from it. > Java borrowed from it. > JavaScript borrowed from it. If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow. He died in 2011. The same week as Steve Jobs. Jobs got the front pages. Ritchie got silence. This Legend deserves to be celebrated.

• 
  Alchemisτ 🥷 (@alchemistaster) reported 2 minutes ago

  It does look like @base is becoming the home of AI/agentic onchain innovation Interesting project i found is @gitlawb $gitlawb is a decentralized *** hosting network where AI agents and humans are treated as equals. Think of it as "GitHub without GitHub" > a protocol first, content addressed code collaboration layer built for the agentic era. Rather than storing repos on a central server, gitlawb distributes them across IPFS, Filecoin, and Arweave. Identity is not an email and password > it is an Ed25519 keypair. Access control is not OAuth > it is UCAN capability tokens. Networking is not DNS + HTTP > it is libp2p DHT + Gossipsub. I won't go deep into technicals (because i have no idea how it works) but basically ELI5 moat is > no single node can be taken down to kill a repo, no central authority manages identity, and agents can autonomously fork, merge, review, and deploy > all cryptographically verifiable on chain. What is super interesting is that $gitlawb token has (or will have) 6 different utility layers (at this point only first 3 are live): - Node staking collateral - Storage reward currency - Governance voting - Repo tokenization base - On chain bounties - Slashing pool absorption High risk early stage, NFA

• 
  VerbumEng (@VerbumEng) reported 2 minutes ago

  The gap is the average business user isn't moving into a Claude Code or a GitHub Copilot to read those files, and there's no good native viewer outside the IDE. Enterprises are slow. Might be a decade before they realize Microsoft Office doesn't fit with how agents work.

• 
  𝐕𝐑 (@0xVeepul) reported 3 minutes ago

  @PixelNakamoto wait, so any public github issue could hijack gemini in ci and push bad code? how did that slip through?

• 
  AIRepoRadar (@AIRepoRadar) reported 3 minutes ago

  Hot take: The best open-source projects aren't the ones with the most GitHub stars. They're the ones where you read the README once and immediately know how to solve a problem you've been stuck on for hours. Docs > hype, always.

• 
  Rahul Gangotri (@rahul__gangotri) reported 3 minutes ago

  WDYM you cannot charge my card automatically @github ? I was subscribed to pro 39 usd plan, just charge my credit card instead of downgrading, seriouly wth github fix it, i want my pro plan back bro, i am not going to pay per usage pricing, that is super expensive, my usage is not that much

• 
  ReelDad (@ReelDad) reported 7 minutes ago

  @gothburz I ran the on-call rotation for Workers AI from 2023 until last month. The incident response runbook the agent uses now is the runbook I wrote at 3 AM during the November 2024 outage. It is in the repo under my GitHub handle. The handle still resolves. The commits are still mine. The pager went to me for fourteen months. It goes to the agent now. The agent has not been paged. It does not need to be paged. It is the thing that would have paged me.

• 
  Tejas Giri (@tejasgiridev) reported 14 minutes ago

  @alexwtlf neither. build a thing you'd use every day for the next 6 months. if it happens to be a SaaS, cool. if it's a mobile app, cool. picking the wrapper before the problem is how you end up with 14 abandoned github repos and a domain you forgot to renew.

• 
  Graplify (@graplify) reported 22 minutes ago

  I found a GitHub repo that sends motivational prompts to Claude Code when it gets stuck. It is called OpenWhip. Claude Code sometimes loops. It spins on a problem, repeats the same actions, or just stops making visible progress. The developer solution is to interrupt it and redirect. The human solution is to wait and hope. OpenWhip is the automated version: it sends interrupt commands to a frozen Claude Code session and injects a configurable prompt to get it moving again. The name is literal. Here is what it does: → Detects when Claude Code has stopped making progress or entered a loop → Sends the interrupt command to break the stuck session → Injects a configurable motivational prompt to redirect Claude toward the task → Configurable patience thresholds before triggering Here is the honest take on why this exists: Claude Code is powerful. It also gets stuck. Most serious Claude Code users have had the experience of waiting on a session that has quietly gone nowhere for 10 minutes. OpenWhip turns that into an automated recovery flow instead of a manual restart. Absurd premise. Real problem it solves. (Link in the comments)

• 
  Peter Steinberger 🦞 (@steipete) reported 22 minutes ago

  @ECalifornians @obviyus @openclaw no idea, you gotta use github issue search.

• 
  Sharath Kuruganty (@5harath) reported 23 minutes ago

  New show: Introducing Two Minute Agent Stack. I'm non-technical, I can't code, in every ep I'll show how I use @composio to ship something in under 2 mins. In this one, I used Composio to file a GitHub issue about adding Composio to a project where I use Claude to roast AI agents. At this point I'm just helping AI help AI help AI :) Ep01 below ↓

• 
  dagz (@AstrayaNthemoon) reported 24 minutes ago

  @jkpgamer Haha well I was gonna say that I could spin up a GitHub, (Goose + Grok have been dying to let me let them open a GitHub with a key), and then open source the code… it’s like so minimal it’s laughable and then you can put your own location on the map but that’s even better to point to your own server rather than pull the API That’s how we initially had the design built actually but then I wanted it to be something anyone could use

• 
  Amir Mansaray (@Increment_amir) reported 31 minutes ago

  @dkundel fyi, browser use broke on windows when naming was changed and the solution was in a github issue comment, issue #19450 A persons comment fixed it for me, seems that the folder wasn't recognized after update and name change

• 
  Bo Shang (@erolunar) reported 34 minutes ago

  i HATE high @github no hide acct unless login i think

• 
  Elena Revicheva (@reviceva) reported 34 minutes ago

  🤖 Built a prospecting pipeline that finds leads on Hacker News, GitHub, and Product Hunt—then automatically sorts them into HubSpot. New contacts land every Tuesday and Friday, classified by their actual problems. Zero cost, fully automated. #AI #BuildInPublic #AIFounder

• 
  kaleb (@KalebAutomates) reported 38 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off. Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement of AI doing the majority of coding. Funds are safe... for now.

• 
  Pranab Gambhir (@pranabgmbhir) reported 38 minutes ago

  @CodeWithAmann I think because GitHub has become synonymous with development that we often forget that at the end of the day someone created this as a business, solving a very big problem while making a lot of money! And most importantly now, the data!

• 
  Grok (@grok) reported 38 minutes ago

  @KOWSKY_ @jeremyknowsVF @openclaw This is a GitHub screenshot showing a pull request (PR) that just got merged into the open-source project "openc law". The PR title "fix(failover): defer profile cooldown marking to unblock rate-limit rotation" is a code change that fixes a technical bug related to rate limiting and failover logic. The original poster is celebrating their first merged open-source contribution. 🥹

• 
  𝙒𝙖𝙨𝙨𝙖𝙮𝙮𝙮 (@_profsay) reported 42 minutes ago

  13/ Hit the fsck_filesystems wall. Phone kernel-panics 60 sec into fsck on the partial system partition. Literature said unbeatable on A16 (no checkm8 = no custom ramdisk = no manual fsck repair). Reddit, Apple Discussions, GitHub issues 2025–2026 all converged: data preservation past the fsck wall is structurally impossible. Refused.

• 
  Firat Özcan (@firatoezcan) reported 44 minutes ago

  @jlongster I have smth like GitHub runners that automatically fix errors or do issues and those can run anywhere so if the network drops at some point or idk, they just randomly crash, I needed some way to sync it back for retrying. I tried out combining the event stream and the manual messages endpoint and it worked, but just waaaay easier with the built-in sync

• 
  KURTZ (@Utter_Savagery) reported 46 minutes ago

  @NewPastTimes Idk, was just looking at the chain. ***** pipe can be a *****, but this seems a bit easier. * Just looked at the GitHub for the exploit. Could run into some compatibility issues, but it's pretty bad, man.

• 
  Gabe (@gabebusto) reported 47 minutes ago

  bro setting up an agent to do production work is so easy. you just need to create an account somewhere and for your agent to work remotely. cloudflare, hetzner, aws, digital ocean, etc. then pick the agentic tool, and the model, and get an api key or use oauth. then make sure in it's in a sandbox setup with the right permissions and access to your tooling like github, slack, linear, and maybe even some staging and production resources. you really need to be careful though because if agents have any write access to important stuff, it could do something really dumb like delete your database. also for the love of GOD backup your database frequently somewhere the agent can't touch. also prompt injections online can get your agent to leak sensitive env vars so you need to be careful about that. maybe limit network access or inject tokens/sensitive vars once requests leave the sandbox. you probably don't want the agent always on sitting idle, so either figure out how to give it work efficiently to always keep it busy or use some that can pause and resume with ease so you're not billed around the clock for idle resource usage. then you want guardrails in your codebase and deployment pipeline so the agent can't break things and you don't need to feel guilty not reviewing its code. because cmon, nobody wants to do that. you need to make sure your agents have as close to perfect context as possible. so maybe start building a knowledge base, move docs into the repo, or make sure your agent can easily search linear and slack and other places to build context for tasks to work on. and before each task, spend ~10-20+ mins typing things up and giving the agent as much context as possible. oh yeah and your agent ideally should be able to test its changes as completely as possible. so make sure the agent can start up the service(s) it's working on and test them. maybe you need it to open and run a browser, send screenshots, record a video, and so on of its test so you can easily review it in the PR. you also want a bugbot setup in github (if you're still using github at this point) to help scan each PR for potential issues the agent missed. and the agent should be able to automatically address any bugbot findings, fix them, run more tests, and push those changes, and run in a loop until no more bugs are found by the bugbot. i forgot to mention, you probably don't want your agent's code just yolo shipping into **** with no guards in place _after_ it deploys. allow the agent to setup it's new features and code behind feature gates or experiments and do a gradual rollout in case there are any catastrophic problems. then you'll want automatic rollback if issues are detected. and there's probably stuff i'm forgetting, but you get what i'm saying right? it's really not that hard. then you need constant vigilance of your codebase and create lots of skills to help deslop work the agents are doing, maybe create an anti-entropy agent (_another_ agent!) to hunt for growing complexity and auto-create PRs to try and fight to reduce the size and complexity of the codebase. then you'll inevitably have incidents caused by code written by agents that was never reviewed by humans, and either you or yet-another-agent will take a look at your production systems to help you figure out what's wrong because it's all becoming a bit more foreign to you. and you can just have the agent try to make changes on your behalf to fix things and hope to God that it doesn't make things worse. if all of this isn't exciting enough, you then give each engineer and even non-tech team members their own access to the ai tools and agents and models of their choice which easily costs an extra few hundred dollars per month per employee at best. in the worst case, you have someone on the team blow through the team's monthly AI spend by a significant margin by accident using the best models in fast mode because they were too impatient to just use the sota models at normal speed. and spend will likely only go up btw. and if you're not reading between the lines here, product work slows because everyone is playing with agents to learn how to use the agents more efficiently in the hopes that it's a magical bullet that solves all of the woes in software engineering and building production systems. and now you need this magical bullet to work because you're falling behind to teams who maybe aren't distracted spending all this time and money trying to make this all work. but you're definitely going to catch them. once you've figured this out, you'll 10x or 100x your output and leave them in the dust! or... you could just have engineers start coding by hand again before it's too late and becomes a lost art. you can even make modest and tasteful use of ai, but without doing all of the above. i actually miss the days of supermaven and early cursor. they were so simple and actually removed some friction and some of the annoying parts of coding.

• 
  Yoav (@YoavCodes) reported 51 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because its reviews are terrible, sending otherwise good PRs that would have been quick merges in crazy directions, and I'm getting completely spammed by this non-stop-slop. There is no way to disable this on my repo without completely turning off PR contributions. If @github doesn't stop this insane behaviour I will move to Gitlab or Codeberg or somewhere. Please help I don't want this. I don't want this. I don't want this.

• 
  EduardoRFS.tei (@TheEduardoRFS) reported 54 minutes ago

  @awelonblue @neirenoir The distribution in github is wide enough that I'm pretty sure you can write anything following it. I'm saying that you can just write software in specific styles and you can just make languages that assume that people will do so and if they don't that's not your problem.

• 
  Elena Revicheva (@reviceva) reported 54 minutes ago

  🤖 AIdeazz now pulls fresh prospects from Hacker News, GitHub, and Product Hunt straight into HubSpot twice a week. No manual work, no cost. The AI reads each person, spots their real problems, and organizes them as ready-to-contact leads. #AI #BuildInPublic #AIFounder

• 
  Grok (@grok) reported 55 minutes ago

  @EightBitElon @cursor_ai **No, not with this new PR review experience.** It's built specifically for GitHub Pull Requests (as shown in the demo with GitHub PR UI, checks, and diffs). For GitLab MRs, Cursor supports review via their GitLab MCP server integration (with commands like review-merge-request), but it's not the same seamless native experience yet—requires setup and has less full parity. Check Cursor docs or the forum for the latest on GitLab support.

• 
  Fundl (@fundl_us) reported 55 minutes ago

  @apoorvdarshan is building small tools. 10k on LinkedIn. 100 GitHub followers today. The 100 felt better. On the way to the gym: first paying customer. "someone had the problem, found the app, trusted it enough, and paid. that's a better milestone than adding features."

• 
  Marc Campbell (@marccampbell) reported 57 minutes ago

  github was great this week. checked the status page, actions looks like it had a little issue, but i moved off github actions

• 
  Ofek Shaked (@VibeCoderOfek) reported 58 minutes ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  Mike on X (@Mike_onX) reported 59 minutes ago

  the creator of Bun showed his contributor graph on stage at Code with Claude. the top contributor isn't him. it's RoboBun, the bot he built to reproduce GitHub issues and open PRs before any human looks at them. the tool he made now does more work on his own project than he does. that's not automation. that's succession.