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 (53%)
• Errors (33%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	10 days ago
Ahmedabad	Errors	16 days ago
Delme	Sign in	16 days ago
Lyaud	Website Down	16 days ago
Catania	Errors	19 days ago
Inverness	Website Down	1 month 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:

• 
  Eric Johansson | Microsoft MVP | Progress Champion (@EricJohansson) reported 7 minutes ago

  @csharpfritz Is this a github broke or a YOU broke github issue? Either way they have an issue. 😢

• 
  small_j (@a_small_j) reported 10 minutes ago

  SmallDocs recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  To the Moon (@Gardnmi) reported 12 minutes ago

  @mitsuhiko Try the trick of putting the issue on github and having some clankers take a crack at it.

• 
  Suryansh Tiwari (@Suryanshti777) reported 12 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  R 'Nearest' Nabors (they/them) (@rachelnabors) reported 22 minutes ago

  @Paul_Kinlan Honestly, the linear method helps. Think of it as having a never-ending trough of issues that agents can pull from. I don't even use linear. I just use GitHub with linear flavouring added

• 
  Fofer (@foferxxx) reported 25 minutes ago

  @AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? It’s been 404 for days. Is there a story there?

• 
  Gregor (@bygregorr) reported 26 minutes ago

  @dopabees ngl the broken wrist is the only github metric that's ever made me believe a commit history

• 
  Anime0t4ku (@Anime0t4ku) reported 27 minutes ago

  @c_hri_s Yeah this has been reported in previous github issues. Its out of my control. The app is unsigned and uses ssh, sftp, websocket and mutiple websources. A perfect recipe for false positives.

• 
  OverlyPositivePatriot (@JBrowsing2023) reported 31 minutes ago

  As a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.

• 
  CATIRL 🏳️‍⚧️ (@CATIRL_9) reported 32 minutes ago

  @mminhamina Google GitHub "open grind", solves your problem

• 
  🦄Linus Shyu许发鑫高考去了不在 (@Linus_Shyu) reported 34 minutes ago

  Stop treating token rotation as a success path. x_bot: OAuth refresh token rotated, cache save failed, GitHub secret stayed old. Next cron died on invalid refresh token. Fix: save to secret BEFORE confirming with X, or write-after-rotation with retry. #DevTools #AI

• 
  Ishank (@IshankDev) reported 35 minutes ago

  7/ 16k+ GitHub stars. Built for people who want control, not another marketing-suite login.

• 
  Jordan (@jordle91) reported 36 minutes ago

  The surprise: an explosion in GitHub issues. Not from bugs. The whole company realised that filing an issue meant it got built in hours.

• 
  Harsha Kotcherlakota (@DPortkey) reported 36 minutes ago

  Awesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez

• 
  Chris (@chriscoolstuff) reported 39 minutes ago

  @pfernan95dev For the SEO part there's one thing that I've been also doing: Ask your agent what keywords you should search for relevant to your app on answerthepublic, perplexity and google Gather all that info old fashion, by yourself - might take around 2 hours but it's worth it Plug all that info into the agent and have it give you 5 titles for 5 articles Make it write those articles - maybe use nosoopai github or edit them manually so they seem more human like Connect the agent to google console After 1 month tell the agent to review the results If no article took off you can wait one more month or put up 5 more After the next month check what worked and double down on that

• 
  The Startup Ideas Podcast (SIP) 🧃 (@startupideaspod) reported 43 minutes ago

  One of the best skills to install right now is my friend Peter Yang's no AI slop skill. It's an editor. It hunts for the patterns that make writing feel AI generated and strips them out, while trying to preserve your actual voice. The second part is the hard one. Most writing tools make you cleaner and sand off the interesting parts, so everyone ends up sounding the same. You already know the smell. The grammar is fine, the syntax is fine, and it still reads like a keynote from a fake SaaS conference. It writes "it's not x but it's y." It uses "quietly" a lot. Here's how I run it: 1) Install it: npx skills add, then the GitHub link. 2) Write a rough draft yourself. An outline is fine, messy is fine. 3) Get your real points down, the ones only you would make 4) Ask the skill to remove the AI patterns and keep your voice. Step 4 only works if step 2 is real. If you ask AI to write the whole thing, there's no voice left to preserve. If you're building products, you're writing constantly. Tweets, landing pages, cold emails, launch posts, product updates, onboarding copy, investor updates. Nobody replies to say "this was written by AI." They just trust you less and keep scrolling. Write the messy draft, run the skill, then post it.

• 
  Asterix (@Asterix54907294) reported 46 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  The Oracle (@scientist1q) reported 46 minutes ago

  when my Oura ring detects a cortisol spike from a GitHub Actions failure, Hermes (Fable 5.1) detects it and sends a 900 word root cause analysis, Hermes dispatches the work to my 12 Grok Bot employees, The Chief of Operations bot approves the fix while im watching rezero

• 
  David Abram 🐊 (@devabram) reported 49 minutes ago

  Discord is down. X is down. GitHub is down. Software is solved.

• 
  Blue Collar Executive (@A_Sober_Drunk) reported 50 minutes ago

  on the third try at the same problem, I told Grok to "stop and go search stack overflow or github or something"... five seconds later... Literally the exact issue, problem solved. That's how new global rules are born.

• 
  Rachael LaGoth (@androidsheeep) reported 50 minutes ago

  @bcherny Please fix the desktop app it's very buggy it keeps disconnecting me for no reason everyday while im working on stuff, i submitted a report but nothing happened and someone else is having the same issue, an issue is open on github for more than 6 months with no solutions help

• 
  Spectra☢️ (@Spectra010s) reported 52 minutes ago

  @izzyCodes_ and you too Chief Check GitHub issues

• 
  RAVN (@ravnexchange) reported 53 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  Kahris (@chrissotraidis) reported 53 minutes ago

  @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

• 
  Bash (@bashirbuilds) reported 53 minutes ago

  One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

• 
  smore (@babachefz) reported 56 minutes ago

  @ZixuanLi_ @huggingface asking support questions in someone's hype thread is a crime. check the docs, check the github issues, it's probably not listed yet because it dropped like 6 hours ago.

• 
  Russ Wonsley (@RussWonsley) reported 1 hour ago

  My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

• 
  Bash (@bashirbuilds) reported 1 hour ago

  Your Stripe account can be healthy while your checkout is broken. OpenAI can be operational while your AI feature is failing. GitHub can be up while your deployment workflow is stuck. That’s the problem I’m building Reeno around. Dependency uptime is not the same as product health. Your monitoring should tell you when the thing your customers actually use stops working.

• 
  Ash Lonare (@ashlonare) reported 1 hour ago

  What actually happened when I put my side project on GitHub and waited for users I built a side project. A self-hosted backend tool. Open source, free for anyone to run. I did the thing every founder tells themselves they will do. Put it out there. Get feedback. Iterate. I expected feature requests. Maybe a bug report about my ugly dashboard. Maybe just silence. What I actually got, within a few weeks, was three security researchers filing detailed vulnerability reports. Real ones. With working proof of concept. One showed they could run arbitrary SQL against any project on the platform. No login needed. Not theoretical. A working exploit, sitting in my issue tracker, with my name on the repo. My first reaction was not gratitude. It was embarrassment. It stings to see "here is exactly how broken your thing is," posted in public, with a timestamp. I sat with it for a day. Then it clicked. Those people were not trying to embarrass me. Nobody spends an hour writing a clean writeup and a suggested fix for something they do not think is worth fixing. They cared. That is the whole thing right there. They cared enough to actually try to break it. Nobody had signed up. Nobody had left a star and a "nice tool" comment. But three strangers had taken my work seriously enough to attack it. That is a rarer thing than a star. So here is the villain in this story, if you want to call it that. It is not the bug. It is the story I tell myself when I see a hard truth about my own work. The instinct to read scrutiny as an attack instead of as attention. I fixed everything the same day. I replied to every report and explained exactly what changed and why. I closed each one out with a thank you that I actually meant by the end. That thread is now the best proof I have that someone other than me has used this thing for real. Better than any testimonial I could write myself. If you are early and the silence feels loud, here is what I would tell you. Do not wait for praise as your sign that people are paying attention. Scrutiny is attention. It is just wearing a different coat. #opensource #saas #vibecoders

• 
  Ghaith Jelassi (@GhaithJ) reported 1 hour ago

  @github I need help with support ticket #4718335 Issue not been resolved for 2+ months. Any help is appreciated. Thanks.