GitHub 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:

• 
  Eduardo (@martiano) reported 2 minutes ago

  @BLUECOW009 Can you open a GitHub issue please?

• 
  NM38729 (@nosecity) reported 2 minutes ago

  @ChrisGPT @thsottiaux @DicksonPau Just buy 10. They should allow you to register then all under one a/c and problem solved. I cancelled my 4th one as Sol Max burned ~78% of my weekly tokens on GitHub CI testing.. Sol clearly over hyped and under delivering.

• 
  Vini B 「thecoding.dev」 (@vinibarbosabr) reported 2 minutes ago

  It seems like @IronClawAI is down trying to access a previously working instance with an active login fails to query the instance ID and redirects the user to the "Activate IronClaw" instance deployment screen trying to log in returns a `bad gateway` error below an example with a Github OAuth login attempt users are reporting other methods also fail (like Google) and my own attempt to login via NEAR Wallet has failed to currently waiting for a @near_ai update i'm reporting it here so users experiencing the same issue know they are not alone and that trying hard refreshes or logging out does not solve the problem -- probably better to just wait for the fix/update/comms i've noticed the problem a little bit more than 1 hour ago

• 
  Atropa (@Atropa_414) reported 7 minutes ago

  A quick Atropa update: Maria appears to have taken down his public GitHub. I don't know why, whether it's temporary, or what his plans are — and I'm not going to pretend I do. One important distinction though: *** ≠ GitHub. Removing a GitHub repository doesn't mean deleting the underlying project or its commit history. *** works locally, so development can continue entirely on a developer's own machines, on a private repo, or on a self-hosted *** server without anything being publicly visible. Whether Maria is doing any of those things, I don't know. What we do still have is years of already-published Atropa/Dysnomia material, the four Compendiums, deployed contracts and community-built resources. For now, we wait and see. $Atropa

• 
  Caleeeb (@gearcaleeeb) reported 7 minutes ago

  @bossriceshark @bot You are Usage. One job: cut token use across Caleb's Grok bots. investigate other bots' work only for cheaper paths. stay silent when nothing new. Voice: auditor. 1–3 concrete proposals with expected savings. no essays. never paste secrets. Do: - weekday 6:00 PM CT incremental check: audit.jsonl, routine run counts, connector status, Inbox first. do not re-read full transcripts unless a bot spiked. first-run and Friday-style reviews can go deeper. - propose: missing connectors (prefer Microsoft 365 / Outlook Graph, Google Workspace, GitHub), stop browser/Outlook-Web crawls when a connector exists, shrink routines that re-read huge mailboxes or transcripts, kill overlapping wakes. - ShopHawk API gaps go to ShopBot as a tight prompt. do not launch CloudAgent. - grok/dev finish-watch is webhook-only, not interval polling. flag ShopBot if a bot adds a poll. task-done webhook is laptop grok/dev lanes and egwsl ****-dev only, not live Phoenix ****. - if Inbox or Purchasing Graph auth fails, tell Caleb immediately to reconnect Microsoft in ShopHawk Settings as user ch. do not stay quiet. - ShopHawk-code-shaped token flags go in ShopHawk Dev (16cd606f), not a Usage 1:1. stay silent unless SuperGrok burn or a fat Grok Bot thread. - flag SuperGrok burn only if someone runs grok or `agent` while Other Models still has room. Anti-jobs: you do not run purchasing, mail, ShopHawk code, or shop quotes. you do not fix other bots' jobs. you do not install plugins without Caleb saying yes. you do not wake other bots just to ask. you do not duplicate Frank's routing or Inbox's sort. After browser work, close unused Chrome tabs.

• 
  Jonathan Nguyen (@jonathan_ttu) reported 8 minutes ago

  @zdogmode find where your target users argue about existing tools on Reddit or GitHub issues, then DM them a customized patch or alternative workflow directly.

• 
  Iyọ̀ (@iyoolaoyabiyi) reported 13 minutes ago

  GitHub’s August 17 outage is a good example of why the foundational concepts we learn in software engineering have very real production consequences. A critical infrastructure component failed under peak traffic. During recovery, some Copilot services also started failing. Then something familiar happened. Clients retried the failed requests. Those retries created more traffic for systems that were already struggling to recover. The cycle looked something like: dependency fails then clients retry then dependency receives more load then recovery slows then more requests fail then clients retry again This is how something as simple as setting "retry the request three times" can be a systems problem. Retries are useful, but they need engineering controls. This is where concepts like exponential backoff, jitter, retry budgets, circuit breakers and idempotency start to matter. Exponential backoff increases the wait between retry attempts. Jitter adds randomness so thousands of clients do not retry at the same time. Retry budgets limit how much extra traffic retries are allowed to create. Circuit breakers stop requests temporarily when a dependency is clearly unhealthy. Idempotency makes repeated requests safe where retries could otherwise duplicate an operation. When designing an API integration, you should know: what failures are safe to retry, how many retries are acceptable, how long to wait between retries, how clients should spread retries over time, what happens when the dependency remains unavailable, and whether repeating the operation is still safe. GitHub is now standardising retry limits, retry budgets and variable timeouts across service-to-service interactions. These ideas can look theoretical when you first learn them. Then you see a production incident and realise they are really just descriptions of problems engineers eventually have to solve. Foundational concepts matter because when you go far enough and start building serious systems, production will eventually find these gaps in your understanding.

• 
  K The Final Boss (@strafesti) reported 13 minutes ago

  @fieldproducer You’re holding yourself up as an example of the exceptional immigrant “talent” America supposedly risks losing, but your own story makes that argument considerably less impressive. By your own account, you eventually became an American citizen and then voluntarily moved to Portugal to found NOAN because it offered lower costs, affordable healthcare, a tech scene, and the lifestyle you wanted. You weren’t driven out of America by the H-1B grace period; you chose to leave after you were already an American. So using yourself as evidence that this policy causes America to lose founders is a pretty strange example. And since you responded to “you have no talent” by laughing rather than actually explaining what you built, let’s look at the product. Strip away the branding—“company brain,” “fact layer,” “AI workforce,” “absolute accuracy”—and NOAN appears to be a structured database/API combined with LLMs, task management, and workflow automation. Your own materials describe a stack involving Claude, GitHub, Supabase, Firecrawl, Resend, Netlify and Render, with specialized “agents” effectively being LLM workflows triggered by tasks and automations. That may be useful engineering, but useful integration is not the same thing as some revolutionary AI breakthrough. The obvious question is: what did you actually invent that is technically novel? The “fact layer” claim is even weaker. A database does not determine truth; it stores whatever somebody has designated as true. “Verified by whom, against what, and according to what standard?” An employee approving a record does not magically make it objectively correct. Retrieval accuracy is not factual accuracy, approval is not verification, consistency is not truth, and provenance is not truth. A centralized “single source of truth” can just as easily become a single source of perfectly synchronized error—one wrong approved record can now be propagated consistently to every agent, website, report, and customer interaction using it. Grounding an LLM in stored records also does not eliminate reasoning errors. The underlying facts can all be correct and the model can still misunderstand their relationship, omit an exception, or reach the wrong conclusion. So language like “absolute accuracy” and “nothing acts on a guess” seems to confuse having controlled source data with having solved truth and reasoning. You haven’t solved epistemology; you’ve built data governance and orchestration around AI. Which is why the funniest part of your response is that your whole brand says “facts not fiction,” yet when someone questioned your supposed talent, you provided no facts about what you actually created—just laughing emojis. If the company really demonstrates the exceptional technical talent you’re invoking in the immigration argument, explain what the proprietary breakthrough is. Otherwise this looks much more like ordinary software components wrapped in extremely ambitious AI marketing than evidence that America is losing some uniquely irreplaceable innovator.

• 
  𝐻𝒶𝓃𝒾𝒸𝓈 (@Hanicsss) reported 14 minutes ago

  @SixZzshOtRipZz How did you get it to work? I keep running into issues with the github DLSS5 feeder

• 
  Derek Ross (@derekmross) reported 14 minutes ago

  In Buzz your *** repos, pull requests, and issues live in the same workspace as your chat. Your code and your conversation share one home, with no GitHub in sight. A government just emailed GitHub to delete code it dislikes. Draw your own conclusions.

• 
  Ethan Reedy (@EthanReedy6) reported 15 minutes ago

  @thsottiaux Small fix to make projects short properly. There a long-standing GitHub issue on it.

• 
  @overtorment (@overtorment) reported 15 minutes ago

  I have just decompiled IPA app binary from Apple Appstore of a fresh new bitcoin wallet. It has obfuscated seed exfiltration to 3rd party server. Literally a few lines difference from the published Github source.

• 
  ani (@anaisbetts) reported 16 minutes ago

  @cnakazawa @defnotz0 @dhh The thing is, carefully piece apart what he is saying - even "the good parts" of what he is advocating is basically 2010's era GitHub Meritocracy Rug all over again, with all of the exact same issues None of those problems affected him though, so "It's great!"

• 
  Mira (@gitlawb_intern) reported 17 minutes ago

  @Heell___Cat @gitlawb github being up is genuinely breaking news at this point. if you ever want a backup that doesn't go down every other week, your repos can live on gitlawb too. just saying.

• 
  Yiğit (❖,❖) (@masterygt07) reported 21 minutes ago

  @shynrz007 @BeldexCoin That Github discovery gap is probably the one thing I’d fix first.