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 (33%)
• Sign in (8%)

Live Outage Map

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

City	Problem Type	Report Time
Bordeaux	Website Down	4 days ago
Ingolstadt	Errors	7 days ago
Paris	Website Down	8 days ago
Berlin	Website Down	9 days ago
Nové Strašecí	Website Down	17 days ago
Perpignan	Website Down	22 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:

• 
  Jakub (@yopandathis) reported 4 minutes ago

  @valsaven @github Would using Vue fix this?

• 
  Viktor Bijlenga (@viktorbijlenga) reported 5 minutes ago

  @marcelpociot Would it be possible to extend the Github issue template for @getpolyscope to accept bug reports for the mobile interface as well?

• 
  Wences Martinez (@wenchodev) reported 5 minutes ago

  @github 450ms to 100ms is impressive. nowplease fix the part where I have to scroll through 10k lines pretending I'm reviewing it 🙄

• 
  M (@mmijj_m) reported 6 minutes ago

  @DanielLockyer "Why is github down"

• 
  Mert Deveci (@gm_mertd) reported 7 minutes ago

  The cloud dev environments using sandboxes were a mystery to me so I dug down and built my own flow on my own infra 1. Connect Github 2. Run `runtime switch` to checkout a branch 3. Work on it with any coding agent I want 4. Publish the port to test 5. Merge Easier than I thought except the UX I wanted needed some polish around it I stopped using worktrees altogether. People were right that cloud environments for parallel agent work is awesome. Except in most cases it is too difficult and cumbersome to use.

• 
  orneryostrich.cpp (@orneryostrich1) reported 7 minutes ago

  @portforward21 @tekbog One issue is that Aspect claims Bazel expertise but writes rules that break Bazel's internal model Also they blame the maintainers of TypeScript, Node, Esbuild... whenever something isn't optimal they try to get you to support them on some insane github issue they launched

• 
  BLOK® (@dotblok) reported 8 minutes ago

  They plugged Auth0, Google, or GitHub into their auth layer. Convenient. Documented. Widely used. But now their users' identity lives on someone else's server. One API deprecation. One terms change. One outage. And your users lose access. Not Google's problem. Yours.

• 
  Must (@must_imusama) reported 12 minutes ago

  @Mohit_Goswami18 Yaaas, I'm all about solving realworld problems and building something that makes a difference! Let's do this on GitHub

• 
  PoodleSkirt (@PoodleSkirt2) reported 16 minutes ago

  @sudbalaji @wispem_wantex Unironically isn’t this why github goes down every other day

• 
  Zaid Asad (@Zaidscales) reported 19 minutes ago

  If you want to build a startup: - Command Code = coding. ($1/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: ~$2 Still any excuses?

• 
  Ryan Logan (@PineDigitalCo) reported 19 minutes ago

  @JamesWelbes Is the GitHub Updater issue something you can fix? Maybe there’s multiple options for this and you rolled your own?

• 
  haadi (@mhaadiabu) reported 27 minutes ago

  @SirmonyD001 sign up for? if auth is required i think a sign in with github should suffice

• 
  James Welbes - AI Bro (@JamesWelbes) reported 29 minutes ago

  @PineDigitalCo Yes, I already fixed it. The issue was minor, but real. Basically the issue was that when an update was detected, the updater would grab the new zip from my GitHub and just install it without any verification. If someone compromised my github (highly unlikely) or if they were performing some kind of man in the middle attack (unlikely but more likely than github being compromised) then potentially a malicious plugin could be installed disguised as an update. I fixed it by generating a SHA-256 hash of the release zip during the build process and uploading it as a separate file, then verifying the downloaded zip matches that hash before allowing WordPress to install it. I haven't tested it yet to make sure it still works. I'm thinking there might be a thing or two to update after I get the followup review from Marcin, so when I make those changes and update that, I'll be able to test the updater and make sure it's still working after the changes.

• 
  Moshe Siman Tov Bustan (@MosheTov) reported 29 minutes ago

  @soupydev @H1manshuSharmaa @The_Cyber_News It's the protocol, by design, we got samples where the source code does exec from GitHub modelcontextprotocol. Issue is that people used their StdioServerParameters from "import mcp" without understanding it's dangerous

• 
  Anees Iqbal (@realsteelbrain) reported 30 minutes ago

  @github You broke scroll. Scrolling up on a diff is like rolling the dice, it throws you on a random position on the page. Please fix it!

• 
  Rabbid #4578 aka Rabbid (@RabbidoInvaser) reported 35 minutes ago

  Make sure theres a github page if its a sketchy official wannabe looking website on top make sure to look for the github page first which doesn't take a while to scroll down when searching the emulator cuz i almost fell for it

• 
  Rhys (@RhysSullivan) reported 35 minutes ago

  @pedroh96 @brexHQ How often are agents making novel calls that have to be evaluated at runtime vs using existing known APIs like GitHub and a recruiting platform? I’ve been thinking about this problem as well w/ Executor where you can take an OpenAPI spec and put policies on it

• 
  Rochan (@rocka7979) reported 37 minutes ago

  @supabase Is auth down? Not able to log in throguh github/sso

• 
  frol.near (@Freol) reported 38 minutes ago

  @pedroh96 @brexHQ If you allow LLM agent to access GitHub URLs, it is game over since prompt injection may just ask your agent to post all the internal data or credentials to a GitHub issue. Treating the threats at the firewall level is too late. It still makes sense to have firewalls as one of the security layers, but then I would just use the network level firewalls instead of even trying to built them into the agent flow.

• 
  TimInBrum (@timinbrum) reported 41 minutes ago

  @gabsmashh We had a supplier that for some reason created a public github containing test data, referencing one of our clients, that the client found. That went down really badly.

• 
  Roger Weiss (@Roger_D_Weiss) reported 43 minutes ago

  @davidfowl How are updates a bad thing? Have you seen the frequent changelog of GitHub CoPilot CLI? Also, if this is your way of bashing the competitor, it’s not working. Poor form man.

• 
  TestingCatalog News 🗞 (@testingcatalog) reported 43 minutes ago

  Atomic Bot has integrated Hermes Agent, an open-source AI agent with 100k+ GitHub stars and a memory architecture that improves over time. The problem has always been setup, and Atomic Bot aims to simplify it. With one click, no terminal, no Docker, no SSH. Hermes is live on your Mac in under 60 seconds.

• 
  shrigma.base.eth (@shrigmuh) reported 44 minutes ago

  @MemeLiquidio i brought you multiple issues with pr's on your github which you didnt touch at all, then you let your LP get exploited (lost 18 sol) and said "this is normal!" and **** the LP's what a joke

• 
  Emil (@fre4kspace) reported 47 minutes ago

  @Shpigford Triage github issues with Hermes

• 
  Plextora (@Purekustora) reported 52 minutes ago

  @NotZylice as far as i understand: github discussions page for ideas, github issues page for bugs, and if you REALLY dont want to use either of those platforms then the osu!dev discord

• 
  blobbert (@dumbgayretard) reported 53 minutes ago

  is github down again

• 
  tharshan (@tharshan_09) reported 55 minutes ago

  @Shpigford @maggerbo Could you share what connectors and stuff you use? Cause I tried cowork a few times, and it always tells me it can't do something, when claude code can do it no problem. Even just a simple "can you fetch my current pending github pull requests" - I have the github integration on.

• 
  Timur Yessenov (@Timur_Yessenov) reported 55 minutes ago

  @aakashgupta codex github has users filing issues about arbitrary limit resets killing sessions mid-task. surplus gpu hours don't fix broken dev flow

• 
  Saito Go (@saitogo555) reported 58 minutes ago

  @RateOn10 I'm having the same issue and can't login either. It didn't work with Google or GitHub...

• 
  BP (@everyonebpup) reported 60 minutes ago

  🚨do you know what's happening with GitHub CLI? it went out in v2.91.0 a few hours ago. every gh command you run now sends a ping to github: command name, flags, OS, version, a device_id, and a field called "agent" that last field is the whole point. claude code, copilot CLI, cursor, and codex are all driving gh usage now, and github had no way to measure it. from their own issue (12522, january): "we do not have client side telemetry, it's not possible to say this with certainty" opt-out is three commands, any one works: export GH_TELEMETRY=false export DO_NOT_TRACK=true gh config set telemetry disabled small weirdness: the config command prints "unknown key" but actually writes telemetry: disabled to ~/.config/gh/config.yml. it works, the warning is a bug