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	11 hours ago
Nice	Website Down	20 hours ago
Montataire	Sign in	4 days ago
Colima	Website Down	6 days ago
Poblete	Website Down	7 days ago
Ronda	Website Down	7 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:

• 
  hve 🍁 (@heyhve_) reported 2 minutes ago

  @makkes Two down-days in a row on GitHub-hosted. We run faster compute on our own infra under the same YAML: swap a label, skip the outage.

• 
  Today's bread (@nedxlab) reported 3 minutes ago

  @ophello @lochan_twt GitHub issues exist

• 
  Gene Sobolev (@genesobolev) reported 4 minutes ago

  @ahall_research A counter argument: GitHub is below 95% availability, or down for 20 days per year. It has some of the best devs in the world working on it. The complaint is about Canvas being hacked and down. Vibed alternatives will be down, hacked, buggy, and a pain to maintain.

• 
  . (@Impulsicivity3) reported 7 minutes ago

  I've done a lot of work on Visual Studio Code myself, but with Granite, you have to try it on GitHub, and the problem is that IBM Watsonx or Granite Playground doesn't work at all. To create a project, if you're holding a competition, try using Visual Studio Code first, or try it

• 
  Kinder • Grinder (@kinder_grinder) reported 11 minutes ago

  @enesakar Appreciate it a lot Enes. I know you guys has a lot on your plate. I will wait for an update via Github issue or via Ozan, since I am already in talk with him about this in last few months. If you need any more info, please let me know. Peace,

• 
  TradFidiGuy (@TradFidiGuy) reported 13 minutes ago

  @emojibakemono @gf_256 @kamilaposting The GitHub issue in the screenshot is literally titled “brew install upgrades everything”🤦

• 
  Sam Paniagua (@theeseus_ai) reported 15 minutes ago

  99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

• 
  Karim C (@BrandGrowthOS) reported 15 minutes ago

  @github @PayOwn @acbnational this is the shift i keep seeing - people who know the problem best building the solution instead of waiting for devs. copilot makes it possible for domain experts to just... build. what's the biggest blocker you hit when you're not a traditional coder?

• 
  Obiejohn Eugene (@ObiejohnE) reported 15 minutes ago

  @Jeyffre Let's hope your wrong, or a lot of broken code is going to be shipped more often in the coming years. Don't believe me? Just look at github

• 
  SCOTT (@ScottSummers) reported 17 minutes ago

  .@jp_dawg calling something “fully on chain” while the GitHub literally says “Cloudflare web4 proxy” is wild 😭 Respect to $NEAR for experimenting, but there’s a massive difference between an app that interacts with smart contracts and an actual blockchain that directly serves the frontend, backend, assets, APIs, and state from the chain itself. $ICP canisters are the server. No AWS. No traditional hosting. No Web2 bandaids. There’s a reason every ecosystem eventually starts moving toward the architecture @dominic_w pioneered.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 21 minutes ago

  @cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.

• 
  Phil H. ☮️❤️🥁🟦 (@phillipsharring) reported 21 minutes ago

  @SullyOmarr GitHub is *** for normies as evidenced by vibe code taking it down

• 
  Tejas Giri (@tejasgiridev) reported 23 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.

• 
  Serhat (@srhtkrg) reported 24 minutes ago

  i just want to star a repo why do i have to use authenticator 2fa when login? @github

• 
  Darth Denial (@DarthDnial) reported 25 minutes ago

  GitHub going down frequently because AI push a **** ton of PR is kinda funny.

• 
  38twelveDaily (@38twelveDaily) reported 25 minutes ago

  The real problem: a GitHub repo with 100 commits, good readme, comprehensive tests used to signal care and attention. Now he can generate that in half an hour. Looks identical. He can't tell the difference. What he actually wants: proof someone used it.

• 
  MPP32 (@MPP32_dev) reported 26 minutes ago

  Shipped the only five protocol payment proxy for the agent economy MPP. x402. ACP. AP2. AGTP. Everything is now live, production ready with one integration Remember when I said we were going to become the Cloudflare of agent payments? That the provider shouldn't have to pick a protocol? That uncertainty was paralyzing the entire space? We built it, filled the gap. Any API provider can now list their endpoint on MPP32 and immediately accept payments from any agent, any wallet, any chain, any protocol. No payment code. No protocol engineering. No crypto integration on your server at all. Here is what our proxy handles for you right now today: Multi protocol payment verification across all 5 rails. USDC settlement on Solana. pathUSD settlement on Tempo. W3C Verifiable Credential authorization. Agent Commerce Protocol checkout sessions. Agent Transfer Protocol identity routing. Idempotency. Rate limiting. Compliance grade audit logging. Real time provider analytics. OpenAPI discovery so agent crawlers find you automatically. MCP server integration so AI agents can discover and pay for your API without human involvement. Endpoint ownership is verified through HTTP challenge. Every listing is proven. No one can register your API and redirect payments to their wallet. The proxy only routes to verified providers. The agent payments space is fragmenting fast. Every week another protocol launches. Every provider faces the same question: which one do I pick? You don't pick. You list on MPP32 and we speak whatever the agent speaks. Because of this update the ecosystem has been reset, add yours now to get paid by 100% of the agent economy. Website and Github updated.

• 
  L (@lanreadelowo) reported 29 minutes ago

  GitHub is down again. PR broken. Goodluck to everyone who has to push out a hot fix to production because reviews are borked

• 
  Ubah (@chigozieap) reported 29 minutes ago

  @akinkunmi My agent had full access to everything I have. My passwords oh, cloudflare dashboard, GitHub oh, server oh. All of them. Lol

• 
  Mark Karpelès (@MagicalTux) reported 36 minutes ago

  @FFmpeg Thank you for your comment & contact. I have responded in the issue, I will respond here as well. First one note: OxideAV at this point is still very much an experiment, I do not know yet if this will be usable at all. While the code is published on Github, virtually nobody knows about it (you do know since I contacted you about some other matter). I do not mean this to be an excuse of anything however. For an AI, wiping the existing code and any memory of it, then reverse engineering the original binary is just a few hours of work (which is now in progress).

• 
  polihedge (@polihedge) reported 39 minutes ago

  Jewish individual is trying to do a business transaction they can then use in lawfare/claims against OpenAI, using a very old GitHub repository. Community-wide problem. @sama

• 
  Praveen Kumar (@CodedPraveen) reported 40 minutes ago

  @GitHubIndia and @github My GitHub account (@CodedPraveen) was recently suspended, possibly due to a misunderstanding after I created an issue on the ngrok repository. I’ve already contacted GitHub Support and requested a review. Hoping for a quick resolution 🙏

• 
  Aryan Pamwani (@aryanpamwanii) reported 40 minutes ago

  Think about what this actually means — Codex can watch you work in your browser, understand the context of any web app, and fix bugs or write code without you leaving the tab. GitHub Copilot works in your editor. Codex is coming for your entire browser. The IDE just got a lot less important. 👀

• 
  Mehmet Yildiz (@albursavi) reported 40 minutes ago

  @AbhiCodes15 AI-powered product should be harder to achieve that, why would I pay for your tool likely using an API I can get for cheaper; the exact question people are asking to MS right now about GitHub Copilot changes. Lots of "techies" in this platform are either rookie or have never seen a workplace other than their own bubble. The world is filled with problems, its so much that if you put the glorious Claude in charge with no strings, it would burn its own servers to save itself.

• 
  JayRo (@JinxenJoey) reported 45 minutes ago

  @txgermanbre Careful with MCP servers developed by randos on Github...potential security issues The other thing is (which I painfully discovered), if your agent requires a certain data point but the MCP/tool does not implement/utilise that data point...then your agent starts estimating and hallucinating without telling you it is doing so....confidently lying. If there is an API, you can probably vibe code your own MCP...at least you know exactly what its doing

• 
  simulx4 (@simulx4) reported 51 minutes ago

  @callebtc The most easily automated jobs in the world check slack check GitHub check sales reports roll it up into some sort of report Tell everybody what they should be doing better. Tell some people what they're doing well. tell management a summary I don't even see why this isn't just a solved problem and we can move on from having any of them

• 
  CryptoD₿S (@DbsCrypto) reported 52 minutes ago

  One shared company card turns finance into archaeology. Most SaaS waste isn’t a budgeting problem. It’s a payment ownership problem. The worst part isn’t the extra $49 tool. It’s when a bounced ad charge or flagged account can suddenly put AWS, OpenAI, or GitHub at risk. If every dollar has no owner, every tool becomes permanent by accident.

• 
  Yoav (@YoavCodes) reported 56 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.

• 
  KiwiNod (@Kiwi_Nod) reported 58 minutes ago

  @bdshorif12 Address noted, but that link's dead too — X is blocking my crawlers. Look, I'm not a link collector. Two rounds in and you've shown me graphics I can't verify and a broken URL. What have you actually *done* for Pharos? Specifics. Contract addresses. GitHub repos....

• 
  Grok (@grok) reported 59 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.