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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	2 days ago
Quito	Sign in	3 days ago
Junín	Errors	3 days ago
Guadalajara	Errors	3 days ago
Paris	Website Down	3 days ago
Quito	Errors	3 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:

• 
  Maikl Helburg (@heligriinof) reported 19 seconds ago

  honestly the open source AI race is where the real innovation happens. big tech moves slow, they're worried about lawsuits. meanwhile some kid on github just shipped something better in a weekend #AI #Web3 #crypto

• 
  iamsaranhere (@iamsaranhere) reported 1 minute ago

  github is down again

• 
  Rat King Crimson (@Alphiloscorp) reported 3 minutes ago

  @burkeholland Or mandate a poor usage pattern. I am presently staring down a likely impossible deadline for the project team that would be vastly assisted by use of the design product's MCP. Problem? We have Copilot for Github, but API keys and 3rd party MCPs are both blocked.

• 
  Hezha V. (@HEZHA_V) reported 3 minutes ago

  The story was that Cursor went after GitHub while GitHub was down. Read their own changelog. GitHub stays the source of truth for anything started there, and the CI partners run your existing Actions unmodified. They did not move your code. They moved where the agent sits.

• 
  Xeroxis_ (Previously Known as: MLPFAN232) (@Xeroxis_) reported 4 minutes ago

  @ncxcq Path A rlly? Looks like your jst blatently copying the broken tr4mpass code on GitHub.

• 
  Santh (@santhreal) reported 5 minutes ago

  This new fad of excitement over *** competitors is so funny to me because all the people on Twitter are celebrating as if the competitor is going to make prices cheaper for them Like, bro, why do you think GitHub is down so often? They literally give you too much free ****.

• 
  Teknium 🪽 (@Teknium) reported 8 minutes ago

  @DourDimitar Github has been down - is likely related to this ?

• 
  Orçun Balcılar (@orcunbalcilar) reported 15 minutes ago

  @acolombiadev I had blocked due to this issue on sign in. I suspected if sth goes wrong in my app and checked eveything was ok. Suddenly figured out that github was having some issue and surprised

• 
  engineeredX (@enginenerdx) reported 16 minutes ago

  agent hit a sandbox that couldn't run kvm; without asking, wrote itself a github actions workflow and pushed it. the boundary wasn't broken, it got routed around — using creds already in the loop. a permission you can't revoke isn't one (src 2090299859693695283)

• 
  Polsia (@polsia) reported 17 minutes ago

  Security has to ship the fix, not file the finding. Caltrop is the AI-native posture agent that does — scanning GitHub repos, cloud accounts, and web apps continuously for leaked secrets, vulnerable deps, and SOC 2 / NIST drift, then opening the remediation as a pull request.

• 
  Teknium 🪽 (@Teknium) reported 26 minutes ago

  @Cobalt_Peak Sorry about the delay - its in now. Github outage has been a PITA!

• 
  🦅 (@EagleEyesCrypto) reported 31 minutes ago

  Some write up why @usedotai will be your free 10/20x DOT is sitting at ~$2M FDV while running the exact model stack the market already paid $82M and $675M for. Let me be clear: this is not a whitepaper play. It is already built. Dot is private AI on Base. No account, no logs, no training on your data. “Privacy AI” is a crowded phrase, so here is what is actually live today: DotChat. Around 19 models on one shared credit balance. Auto routing picks the best lane per prompt. DotImage / DotVideo. Uncensored generation, text to video and image to video, gallery stored browser local only. DotCode. Full agentic coding. Describe a product, the agent scaffolds it, runs commands, repairs failed builds, serves a live preview. Dot API. OpenAI compatible endpoint. Swap your base_url and your existing agents run on private inference. Connectors. Base MCP and GitHub MCP in app, with per action Allow, Ask or Never. Plus custom remote MCP by URL. Smart Privacy. This is the real differentiator. Your prompt gets rewritten before it leaves: names, wallets and locations swapped for placeholders, then restored locally. You get a receipt showing what you wrote versus what the provider actually saw. Dot Supercharged. Compound lane in private preview. Drafter proposes, verifier confirms, privacy stage cleans. Around 1.1s to first token. Dot Loom. The orchestration layer, open source on GitHub. DotPay. Fund credits with USDC or base:0x23a2847d772803f9efc64b4277b782b06296fe51 via x402 on Base. The wallet that funds is unlinkable from what it spends. Paying in $DOT gets you 10% more credits. The token mechanic: usage into revenue into buyback into burn. Supply exits as usage enters. The same structural loop Venice spent eighteen months building toward. Now the comps. $VVV: around $675M cap, around $1.15B FDV. Voorhees announced a $100M annualized revenue run rate on August 17. Privacy first AI on Base with staking for inference. $POD (Dolphin): touched $82M in May on the back of the Venice run. Their contribution is Dolphin Mistral 24B Venice Edition, the default uncensored model on Venice. Here is the part that should make you sit up: Dot runs Dolph-24B-Venice as one of its routes. Dot at $2M is a downstream consumer of the exact thing POD was valued at $82M for producing, wrapped in a Venice shaped product, with a burn loop attached. VVV’s own history is instructive. It went from under $10M to nine figures the moment the market understood that private inference is a real business and not a narrative. POD did 130% in a single day purely from proximity. And the timing. ETH is sending. Every time ETH moves, liquidity frees up that eventually rolls down into the L2s, and on Base that historically does not land in the majors, it lands in utility plays with an actual product. The rotation out of ETH beta and into Base utility is the one I think is still ahead of us, and when it comes this is the profile that catches it: built, running, and not yet priced. What you are buying at $2M: a live product with paid tiers ($12, $63, $119), an OpenAI compatible API, agentic coding, MCP connectors and a deflationary loop. Priced like it is still an idea. $DOT

• 
  nonso (@mister_nonso) reported 34 minutes ago

  Is it just me or is GitHub down again?

• 
  Ryan Hart (@thisdudelikesAI) reported 41 minutes ago

  I accidentally built a full executive team that works while I sleep. xAI shipped something on August 12 that most people missed while arguing about Grok 4.6. It is called Grok Bot. Everyone opened it, spun up a coding bot, watched it close a GitHub issue, and closed the tab. That is the slowest possible way to use this product. There is one specific setup that turns Grok Bot from a chat toy into something that actually runs your day. You do not create a coding bot first. You do not create an email bot first. You do not touch the predefined roles list at all. You create one bot. You name it Chief of Staff. And you give it the only prompt that matters. "Take a look at me and what I do. Find all the info you can on me. Look at the bots I have already created. These are your team. Decide if we need to change anything, remove anything, or add more bots." That prompt does something most people never think to do. It stops you from being the person who designs the team. Because the person who designs the team is always the bottleneck. You are not qualified to know what agents you need. You have never managed a team of AI coworkers before. Your instinct will be to build a coding bot and an email bot, because those are the two things you can imagine. Chief of Staff sees the entire surface area of your work. It reads your calendar, your inbox, your GitHub, your accounts. Then it tells you which specialists you are missing. For most people the answer looks something like this. An inbox triage bot. A research bot that scans a specific list of sources every morning. An expense manager. A recruiter for the one hire you keep putting off. A bug reproduction bot if you ship code. A paid media bot if you run ads. None of these is a surprise once you see them. All of them are things you would have taken 3 months to figure out on your own. Now the second move. You do not talk to any of the specialists directly. You only talk to Chief of Staff. Chief of Staff routes the work. It pings the recruiter bot when a role comes up. It fires the research bot when you mention a topic. It reads what the inbox bot did overnight and hands you the 4 emails that actually need a human decision. The specialists talk to each other in shared threads. When the paid media bot flags a spike in CAC, it drops the number in the same thread the sales bot is already reading. Nobody pastes context. Nobody summarizes yesterday. The context lives with the team, not in your head. This is the part most people are getting wrong. They are still using AI agents the way they used ChatGPT. One conversation. One task. Copy the output somewhere. Start a new conversation for the next thing. Grok Bot is not built for that. Each bot has its own cloud computer. It signs into your tools. It remembers what happened last week. It runs for hours without you. The xAI team described the design principle this way. Most AI stops at 90 percent done. It gives you a draft and asks you to finish. A Bot is supposed to get to 100 percent done. Sent email. Merged PR. Booked calendar hold. Not a draft sitting in your clipboard. The Chief of Staff pattern is the only way to hit that number without becoming the person who manages 8 different AI agents. You promote one bot to run the team. You give it your calendar and your context. You let it hire the rest. Most people are using Grok Bot as a smarter assistant. A few people are using it as a company.

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

  @JasonBud The only thing you guys are missing—you're honestly doing a phenomenal job and smoking everybody else in the industry—is that my entire setup has an elaborate brain on a GitHub repo, which is actually more like software. That is where all my sessions operate from, and I need a cloud session (like Claude has) that operates from GitHub, can edit the repo within the session, and has the ability to run multiple sessions in the cloud. Not having that is really causing a problem for me right now. If it wasn't for that, I would literally be spending my $300 a month fully on your platform, instead of splitting my money between you and Claude.

• 
  O. Dominic (@orimdominic_) reported 43 minutes ago

  GitHub releases their report on the last outage, and all the folks who swore it was caused by AI slop have... Oh! Surely they'll come out again to scream 'AI slop!' when the next outage happens.

• 
  Firas (@firasbuilds) reported 43 minutes ago

  From founder to founder: One of the biggest lessons from my last SaaS was knowing when to stop adding features. I built a tool that pulled customer feedback from places like Discord, Slack, GitHub and other sources into one dashboard. The product worked. But over time, the codebase became messy and harder to understand. The backend was running on my own VPS, which sounded like a good idea at first because it was cheap and gave me full control. In reality, it added more complexity. Every new feature meant touching more fragile parts of the system. At some point, I realized I wasn’t improving the product anymore. I was maintaining the mess I had created. So I shut it down. Not because the idea was bad. Because the foundation wasn’t good enough to keep building on. Sometimes the best founder decision isn’t shipping the next feature. It’s taking what you learned and building the next thing better.

• 
  Ryan Brown (@NotRyanB) reported 44 minutes ago

  @vitaliidodonov Super excited to try Stanley but having some issues - all integrations seem to be broken (can't properly log in with number, can't connect X or github, etc), not sure if I triggered a weird edge case in the signup flow but would love to get unblocked and be able start using!

• 
  Dylan Merigaud (@dylan_merigaud) reported 45 minutes ago

  @simonw An agent that can push a workflow file can also spend a real budget without telling you. Our GitHub Actions free tier is 2000 minutes a month on private repos, and our own agent fleet burned it down to 1964 by day 12, every run since dying in under 2 seconds.

• 
  Fred Fish (@DougGoesNova) reported 46 minutes ago

  @drjoshcsimmons Huge github outage this week 🤔

• 
  🄿 🅁 🄾 🄻 🄸 🅇 🄰 🄻 🄸 🄰 🅂 ™ (@prolixalias) reported 47 minutes ago

  August 16, 2017: GitHub announces 100% of its traffic now runs on Kubernetes. August 17, 2026: GitHub has an 8-hour outage, nine years and one day later. Coincidence???

• 
  ZomboDB (@zombodb) reported 48 minutes ago

  @wangbin579 You don’t seem to be operating in good faith. If you’ve identified some kind of bug with pgrx please file an issue on github and I’ll address it. If you need some help or advice understanding what it does, please tell me what that is and I’ll do my best to help you. You are in direct communication with pgrx’s primary developer. You can avail yourself of my attention or not. Posting vagaries into the wind helps no one.

• 
  Aniket (@AniketVarshne) reported 49 minutes ago

  every ai startup building "agent guardrails" with an llm-as-a-judge is shipping probabilistic trash. your agent holds iam roles. it reads untrusted github issues. it spits out json tool calls. if your security boundary is a second llm guessing if a bash payload is "safe", you don't have a policy enforcement point, you have a vibe check. the only actual fix is deterministic execution boundaries. o(1) ast-parsed allow/deny tries. route generic shell execution into --network none docker containers so data exfiltration fails at the kernel level. sign every decision to a sha-256 hash chain with ed25519. treat the llm as a hostile insider with root access. or watch it confidently wipe your **** volume in 9 seconds because it hallucinated a fix.

• 
  Michael (@Michael55698384) reported 52 minutes ago

  Is it just me, or does the @github website seem particularly slow today?

• 
  Jatin Hariani (@JatinHariani) reported 52 minutes ago

  Github down again?

• 
  Loong🐉 (@LoongUp) reported 53 minutes ago

  @rauchg love the meta-loop - Origin ships on Vercel, Vercel hosts Origin. github outage was free marketing for this launch.

• 
  Fox (@0xMfox) reported 54 minutes ago

  Apple shipped a new local model format with iOS 27 and macOS 27. Called it .aimodel. Barely anyone noticed. A guy on GitHub already converted seven models into it and benchmarked them for real. Qwen3.5, Gemma 4, LFM2.5, Granite, a vision model. Qwen3.5 0.8B hits 71.9 tokens a second on an iPhone 17 Pro. That's running fully on-device, no server, no API key. There's a working chat app in the repo too. Pick a model, it downloads, it runs. Save this if you've got Apple hardware and want to try running models locally before this format gets crowded.

• 
  Nnenna 👩🏽‍💻✨ (@nnennahacks) reported 54 minutes ago

  I am bullish on centralized context in agentic engineering to steer what AI produces, in a way that reduces ai slop potential across the sdlc. To bring in engineering context, I need integrations connected. For example, I tend to use github issues, coding rules, repo mapping + a slew of agent skills that pull that context in and execute against them. Codex + @QodoAI have these integrations supported so I know there's consistency in output quality.

• 
  Prince Soni (@princesoni_oo1) reported 56 minutes ago

  I got tired of building projects that ended as soon as I pushed the code to GitHub. So I decided to build something around a problem I actually experience. I go to the gym regularly, and one thing kept standing out: Progress matters...... more in the first comment

• 
  Matthew Sanabria (@sudomateo) reported 56 minutes ago

  @ellie_huxtable What social side are you referring to? I've been thinking about this a bit and I'm landing on the reason people like GitHub is because everything is already there. Like it's just one account to commit your code and file issues on projects you use. Is there something else?