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	5 days ago
Ahmedabad	Errors	11 days ago
Delme	Sign in	12 days ago
Lyaud	Website Down	12 days ago
Catania	Errors	14 days ago
Inverness	Website Down	27 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:

• 
  Wlad (@dawnhell_) reported 7 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??

• 
  Gordo Polymath (@gordo_polymath) reported 8 minutes ago

  @github Please fix gh stack.

• 
  Chris Gilbert (@0xgilbert) reported 9 minutes ago

  Damn, GitHub has gone to ****. Features that have been cornerstones of solo devs and small businesses have been gutted or broken for months. How the mighty have fallen…

• 
  joithan (@jothantranston) reported 10 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.

• 
  Pranavvv👾 (@pranvv27) reported 13 minutes ago

  honestly, i’m not even mad at this. commit messages are a small thing, but they say a lot about how you work. “fix”, “update”, “changes” might get the job done, but meaningful commits show professionalism, attention to detail, and that you actually care about maintainability. your GitHub is part of your resume. might as well make it look like you know how software is built in a team.

• 
  Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reported 15 minutes ago

  I have many tokens to burn before tomorrow after the Claude reset. Send me your GitHub issues with context 👇

• 
  Bash (@bashirbuilds) reported 15 minutes 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.

• 
  Farley (@FarleySchaefer) reported 16 minutes ago

  @github Hope this doesn't bring down GH

• 
  ѕaℓoηι ηαяαηg (@thesaloninarang) reported 17 minutes ago

  I review resumes for DevOps beginners at meetups, and the same fixable problem shows up every time: bullets that describe the tool instead of what YOU did with it. Let me show you the difference with real rewrites. BEFORE: "Worked with Docker and Kubernetes" AFTER: "Containerized a 3-service Node app and deployed it to a local Kubernetes cluster with health checks and resource limits" BEFORE: "Knowledge of CI/CD" AFTER: "Built a GitHub Actions pipeline that tests, builds and pushes images on every merge to main" BEFORE: "Familiar with Linux" AFTER: "Debugged container startup failures using logs, exec and inspect on Ubuntu servers" See the pattern? Verb, artifact, specifics. A hiring manager can picture the AFTER versions. The BEFORE versions could be copied from any job description, and that is exactly how they read. You do not need production experience to write bullets like this. Personal projects count when you describe them concretely.

• 
  ONCHAIN COP (@OnchainCop) reported 22 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

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

• 
  Enfantshustle (@Ownerthoughts) reported 29 minutes ago

  Honestly, I always thought bots like this were some kind of magic for the elite, but here everything is broken down step by step. However, after reading it, one main question stuck in my head: how realistic is this for an average person who has no coding experience? I get that there's a GitHub and all that, but for me, just "running a script" is practically a heroic feat. Here's another thing that bothers me. The article does a great job explaining the architecture, but I still don't understand how much all of this will actually cost in the end. Besides Solana transaction fees (which, by the way, get absolutely insane during peak hours), you also have to pay for each Grok API call per token. The article says that for each approved token, it takes three model calls, and one of them is the expensive grok-4. If the bot scans thousands of launches per day, I'll just burn through my entire deposit just paying for the API without even buying anything. Maybe the author knows — is it actually possible to turn a profit after these expenses, or is this just a hobby for those with an unlimited subscription? Also, regarding Grok Bot as the "orchestrator" — it sounds cool in theory: describe the task and it does everything itself. But in practice, as I understand it, this still requires your account to be constantly online and have access to your wallet. And if it decides to buy some scam token at 3 AM that passed all the checks, I'll only have myself to blame. The article correctly mentions risk management, but this "trust" aspect is what scares me the most. In short, the idea is fire, but for me, this post feels more like a warning than a call to action. There are just too many things you have to keep in mind to avoid getting rekt. Although, maybe if you try it with really tiny amounts, it could be an interesting experiment. Author, if you're reading this — could you please make a separate post about the real, live results once everything is actually running, not just on paper? I'm really curious!

• 
  Phanindra Malladi (@malladiphani) reported 30 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.

• 
  Bash (@bashirbuilds) reported 30 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.

• 
  Franco Valdes (@francoxavier33) reported 33 minutes ago

  llms rather burn 1m tokens to hand roll something with gaps and broken edge cases instead of just npm installing a 100k github star library how can I stop this?!

• 
  Ravi Prasad (@ravikp7) reported 37 minutes ago

  Big NO to Github hosted CI runners for personal projects now. I have setup a self-hosted github CI runner on a spare laptop running ubuntu server. Been running it for 10 days and I did some calculations, for my usage if I run it on Github runners, it'd cost me around 200$ vs < INR 100 on electricity (local setup) monthly.

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

• 
  Curious Explorer (@PatelVatsalp732) reported 45 minutes ago

  I burned 14B Codex tokens. The official usage UI still cannot tell me what actually ate the weekly cap. So I shipped a Codex-only board: GitHub login, local-first sync, private by default, optional public rank + shipping proof. Roast the metric or join it.

• 
  Rusty Williams McMurray (@1RustyMac) reported 46 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.

• 
  LLL (@triplellltrbl) reported 47 minutes ago

  You know it's so funny to me That in today's age there are so many people that are just straight up copying workflows, AI automations or GitHub repos Without even thinking twice about what the workflow actually does or how it works They just watch some video, see the output, think, "Oh that's cool. I want that," and then try it Then when it doesn't work they get angry, upset, and say that AI is crap or prompting isn't real The issue wasn't the system or the prompt It was a fact that the system wasn't made for you and you don't actually understand it

• 
  Bratah (@BratahFGC) reported 48 minutes ago

  There may be many bugs so feel free to leave any issues in the issue section github! I hope that this release can push forward the preservation or our beloved game!

• 
  Shawn Yeager (@shawnyeager) reported 54 minutes ago

  My @bot keeps reaching for the browser and `gh` instead of using the GitHub plugin. Known problem?

• 
  RAVN (@ravnexchange) reported 55 minutes ago

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

• 
  Kun Chen (@kunchenguid) reported 56 minutes ago

  @petergyang yo @myfirstmate peter just told me his skills are all at user level. backpass currently only runs things at project level i want a proposal for making backpass support a user level run. put that into a github issue use fable for peter

• 
  Konstantin Elfimov (@elfh78) reported 56 minutes ago

  @topjohnwu Sorry for posting in the wrong place - I was trying to add magisk bug report on github and alway got errors with automatic issue closing. Is there any possible way to send it directly to you?

• 
  Åsa-Nietzsche (@AsaNietsche) reported 58 minutes ago

  @peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.

• 
  AINotes (@ainotesus) reported 59 minutes ago

  🔥 Trending on GitHub: Ponytail Ponytail helps Claude Code avoid writing code that does not need to exist. That means less clutter, fewer unnecessary dependencies, and simpler changes to maintain. Before custom code, it checks whether the feature is needed and whether the codebase, platform, standard library, or an existing dependency already solves it. It also reviews work, audits implementation complexity, and tracks unnecessary token use without dropping validation, error handling, security, or accessibility requirements. In reported Claude Code sessions on a FastAPI and React repository, Ponytail used about 54% less code, 20% less cost, and 27% less time than the no-skill baseline. Those measurements came from 12 feature tasks, so results vary with the work. Full analysis in the first reply ↓

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 1 hour 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.

• 
  Jason Waters (@jasonwaters87) reported 1 hour ago

  Anthropic just open sourced the code Shopify runs their shopping agent on. Free on GitHub. And I’m having lunch with a surgeon in San Jose last month and he tells me a patient no shows and nothing happens. Nothing. He has to walk up to the front desk himself and ask “did you guys call them?” 3 or 4 schedulers looking after 75 doctors. One automated call before the appointment and that’s it. His own dermatologist sends him three reminders. He called that “an easy fix.” That’s a merchant agent. Reminds the patient, rebooks the no show, tells him Thursday isn’t full so he can put a surgery on it. The code is sitting there free. Somebody still has to walk into his office and build it.

• 
  Max Rovensky (@MaxRovensky) reported 1 hour ago

  @thekitze you'd be even further down if you fixed the GitHub bug I just reported