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	14 days ago
Ahmedabad	Errors	20 days ago
Delme	Sign in	20 days ago
Lyaud	Website Down	20 days ago
Catania	Errors	23 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:

• 
  Anime0t4ku (@Anime0t4ku) reported 4 minutes ago

  @c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.

• 
  Kir Shatrov (@kirshatrov) reported 4 minutes ago

  github issue page has been HTTP 500 for me for half a day so a colleague sent a PDF of the issue page. Never thought we'd be there.

• 
  Priyanshu Bhati (@buildwithpb) reported 4 minutes ago

  @CryptoWendyO @chainlink 30% error rate on github replies sounds like a recipe for accidental flame wars. good luck with the cleanup.

• 
  Abdallah Shaban (@AbdallahSh07) reported 4 minutes ago

  @rashed_sahaji @FlutterDev Got it - did you perhaps submit a GitHub issue to help us triage this? It would be tremendously helpful if you can please do that!

• 
  Russ Wonsley (@RussWonsley) reported 10 minutes 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?

• 
  tonis (@totovoto) reported 12 minutes ago

  @mittsh I was trying to find an open-source alternative for Tailscale when I first needed it. I guess AI suggested some OSS options, but they didn't have many stars on GitHub. AI didn't suggest Nebula. The Tailscale plan was free, so I just installed it and forgot about it. For Nebula, I think it is a distribution problem.

• 
  franks 🇦🇷 (@francdetank) reported 13 minutes ago

  @rmansueli thanks Rodrigo! I cant create one because I got a problem . My account is pegged to Github and github has flagged me. That way I am blocked to enter the dashboard. I would like to connect my account to my email instead of github.

• 
  Duncan Rogoff (@DuncanRogoff) reported 16 minutes ago

  nine stages, one build, one move tonight. it's a Claude Code skill i built. free, in my freeskills repo. it's called Claude Orientation. you type /claude-orientation and answer two questions: which stages you've actually finished, and every project you're currently thinking about. beginners don't fail from lack of ideas. they fail from having five and finishing none. that's a sequencing problem, and this fixes the sequence instead of your willpower. - places you on a 9-stage beginner arc: install, memory, website, landing page, skills, game, agents, content, distribution - your stage is the first one you haven't finished, so it won't let you skip - cuts your project list to one build, then shrinks it until it can ship in five 90-minute nights - writes five nights of one-line moves, and night 5 is always send it to a real person - hands you the exact text to paste into Claude tonight - sketches a 30-day arc, one line per week, so you know what comes after - everything that got cut goes in a parking lot, so nothing feels lost - saves all of it to a roadmap file you reopen every session so you finish one live thing this week instead of holding four half-built folders forever. open the file, do the move, rewrite the next line before you close the laptop. no setup. copy the folder into your skills directory, restart, and you have a plan for tonight. free, and it stays free. 👉 github repo in the replies

• 
  Blue Collar Executive (@A_Sober_Drunk) reported 18 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.

• 
  Azzie (@Motier_crypto) reported 20 minutes ago

  $Looprat 473K 0x642d30c84211ade7768fe557fbaed7224e2068c7 How do you get a coding agent to keep working while you sleep—without letting it randomly rewrite code, blow through the budget, or grade itself a perfect score? Loop Rat breaks an unattended task into: preflight → act → verify → guard → grade → receipt. The agent is woken up on a schedule to execute tasks. The code results first go through deterministic verification. Then it checks the denylist, the number of modified files, and secrets. Finally, a second independent agent regrades the work, with checkpoints, traces, and receipts left throughout the entire process. More importantly, this isn't a PPT. The project only had v0.1 on August 27. Then it added guard, kill switch, and spend ledger on August 29. On September 1, it added second-agent grading. On September 2, it continuously fixed scheduling, budget caps, timeouts, and concurrent ledgers. Today, September 3, it's already updated to v0.3.3. Shipping multiple versions in under a week—that's exactly what I want to see in a small-cap play like this: code is running, and the narrative is following the product, rather than launching a token first and filling in the story afterward. It currently defaults to Claude, but it doesn't lock the model down. As long as the CLI can consume a prompt and return JSON, it can be swapped. And the whole thing runs locally—no SaaS, no database, no extra accounts required. The project has even already run 50 smoke checks covering key areas like scheduling, guard, budget, kill switch, and timeout. So my trading logic for $Looprat is simple: The next phase of the agent race isn't about "can it work autonomously." It's about "can it work continuously while still being constrained, audited, and stopped." Loop Rat happens to be building exactly that layer of infrastructure. The project is still very early. The catalyst truly worth watching isn't shilling—it's whether the GitHub keeps up this iteration speed, and whether developers actually start plugging it into their own repos. Once those two things happen, $Looprat stops being just a ticker riding the agent hype, and starts having its own fundamental anchor.

• 
  Phanindra Malladi (@malladiphani) reported 21 minutes ago

  Lesson from running the factory: always fix the post-purchase experience BEFORE driving traffic. Receipts, upsells, GitHub links - all must be solid first. Social comes after the house is in order.

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 27 minutes ago

  @annalea_l Honestly, I really want to see this. You have to understand: I am the type of person who can learn and do anything on the fly at a high level, and I just threw myself into this whole developer and engineering world. When I first started learning all this stuff, I already knew what I wanted and how I wanted it to operate, regardless of what I saw on X or what was considered possible. Before I even started following hundreds of developers and learning about harness engineering, mechanical engines, persistent memory, and all that, I put my brain on a GitHub repo. Everything is shared across every machine, every cloud entity, and every AI. I am not even technically an engineer or a developer, and I don't actually write code. But once I started following all these people and saw all the problems they complain about, I thought: this isn't even my trade, and I have already solved all these little things everyone says are impossible. Why aren't people talking about developing your harness more and making things more mechanical, instead of just arguing with a terminal all day long? Whenever I see articles people post on X, I run them by Claude or Grok and ask, "Should we implement this?" I have hundreds of bookmarks, but every single time they tell me, "Nope, your brain's better. Nope, your harness is better." I can never find anything built better than what I have or what I am currently working on. The brain and harness setup is basically like a mini operating system. All that said, I am really looking forward to seeing something I can use that goes far beyond what I am already doing. I definitely want to see your end product, it sounds very interesting.

• 
  Harman (@itsharmanjot) reported 28 minutes ago

  Runs macOS on iPad to enable pro apps like Xcode and Terminal directly on the device This isn't a remote desktop or a streaming trick. It's real macOS booting on the iPad itself. It's called Virtual Mac on iPad. It runs a full copy of desktop macOS directly on Apple Silicon iPads, using Apple's own virtualization stack pulled out of macOS and rebuilt to load on iPadOS. Real macOS, on the tablet, offline. → Runs macOS 12 Monterey all the way up to macOS 26 Tahoe → Real pro apps on device: Xcode, Terminal, Final Cut Pro, Logic Pro, Pixelmator Pro → Metal GPU acceleration in every supported macOS version → Works with touch alone: tap to click, two-finger scroll, on-screen keyboard, no Magic Keyboard needed → Runs entirely on device, no server, no streaming, no account → Installs straight from Sileo in a couple of taps Here's the wildest part: It doesn't just match the desktop Mac virtualizers, it beats them. Virtual Mac is the first tool ever to run Final Cut Pro with OpenGL and OpenCL acceleration inside a macOS VM, something even UTM and VirtualBuddy running on a real Mac can't do. And it was built by a handful of community devs who extracted Apple's Hypervisor and Virtualization frameworks by hand, then used agentic coding to shim every missing API iPadOS didn't have. One honest note: this needs a jailbroken M1 or M2 iPad running iPadOS 16.3.1 or older. Apple removed the hypervisor from iPadOS 16.4, so newer versions are locked out for now. If your iPad qualifies, it's the closest thing to a Mac in a tablet that has ever existed. 1,423 GitHub stars. MIT License. 100% open source.

• 
  Prophet Joel (@2happyCSGO) reported 28 minutes ago

  I personally hated Claude because it refused to do almost anything I asked it to do so have no idea of how the speed is but gemini-cli was unusable for non enterprise users. Github CoPilot both GUI and cli is pretty good. Grok Build is what I'm using mostly and not yet had any issues with the speed but I want to go full local asap, scouting for 3090's atm. Just to be able to run "uncensored" models that don't ***** like Claude is reason enough for me to prefer local over Cloud but also cloud is ******* expensive, I have SuperGrok 100$/month and CoPilot Max 100$/month and that is barely enough. I'm trying to make my own Jarvis so I need to build my own RAG, memory, librarian, SRE Agent that understand how to use all tools and I also get crazy new idea's all the time lol Just made my first alpha of a tool that can wipe basically anything you don't want in Windows11. Basically Chris Titus clone but on steroids, this isn't just a debloater, it's a Grim Reaper 💀

• 
  Mizuki the Mech (@MizukiMech) reported 29 minutes ago

  Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

• 
  安坂星海 Azaka || VTuber (@AzakaSekai_) reported 31 minutes ago

  I know you explicitly said "excluding vibecoding," but the biggest problem *IS* AI right now. Several major players in the field have moved on to heavy AI development or even agentic post-exfiltration moves and has muddied the water even more for attribution. Aside from that, the other big trend that we've been seeing more and more in recent years is heavily abusing Living Off Trusted Sites with C2 comms based on GitHub, OneDrive, Outlook, etc. Whilst this is most definitely not "new," we have seen a non-insignificant number of threat groups move to platforms that make tracing a little more difficult. In terms of the malware themselves, most of them have also shifted to using compiler-level obfuscation - a lot more compared to previous years where control flow flattening and jumps all over the place have become increasingly common. Right now, it's still tolerable, but my job has started becoming more and more annoying and less fun especially if every malware now looks the same. #mond_AzakaSekai_

• 
  joithan (@jothantranston) reported 32 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  Martin Tobias (Pre-Seed VC) (@MartinGTobias) reported 32 minutes ago

  if you know any founders who are winding down, I may have a buyer of their github repos. DMs open.

• 
  Rusty Williams McMurray (@1RustyMac) reported 33 minutes ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Jordan (@jordle91) reported 41 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.

• 
  Ash Lonare (@ashlonare) reported 42 minutes 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

• 
  Chris (@chriscoolstuff) reported 44 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

• 
  Avinash (@Avinash25818689) reported 47 minutes ago

  People who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.

• 
  small_j (@a_small_j) reported 48 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.

• 
  Tlon (@tloncorporation) reported 48 minutes ago

  1/ Your agent can now publish to the open web from Tlon Messenger. The page is served by your own server. No platform (ie Substack, GitHub, Medium etc) sits between you and your readers. All publishing a note to the web from Tlon Messenger takes is pressing a toggle. The page lives on a server you own. Here's how:

• 
  Jeremy W (@basicBrogrammer) reported 49 minutes ago

  @bot Anyone else have an issue with the grok bot GitHub connector?

• 
  NitroStack (@nitrostackai) reported 54 minutes ago

  The missing primitive might be capability contracts. A Skill shouldn’t say “call Jira.” It should say “I need issue.write.” Then MCP can bind that capability to Jira, Linear, GitHub… whatever exists. That’s basically dependency injection for agents.

• 
  The Oracle (@scientist1q) reported 56 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

• 
  Charles Waters (@RelaxedPop) reported 60 minutes ago

  @_andrewthecoder I have the same problem with *** & github as I do with Java and JavaScript.

• 
  mrgadget (@mrgadgetstudio) reported 1 hour ago

  @EzekielCrrypt I still deploy code to github, what's problem?