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	10 days ago
Quito	Sign in	11 days ago
Junín	Errors	11 days ago
Guadalajara	Errors	11 days ago
Paris	Website Down	11 days ago
Quito	Errors	11 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:

• 
  Masood (@_TechMasood) reported 4 minutes ago

  @Marwan_SoftDev github issues with a forced repro template beat forms for me because forms just pile up reports you cant actually act on : )

• 
  Pav (@ChristianThePav) reported 5 minutes ago

  I wish github wouldn't push to **** on Monday when I have to look at issues and instead I look at a unicorn.

• 
  Daniel San (@dani_avila7) reported 6 minutes ago

  Can I submit a PR to GitHub to try to fix GitHub? I wish parts of it were open source. I have so many ideas to contribute

• 
  PangeaVPN (@PangeaVPN) reported 9 minutes ago

  @ProtonVPN 64 apps hiding real ownership behind Singapore or Hong Kong shells is a trust problem a privacy policy can't fix. Pangea's client is GPLv3 on GitHub, so you can read what it actually sends before deciding whether to trust it, instead of trusting a store listing.

• 
  Dela (@delaanthonio) reported 9 minutes ago

  @GergelyOrosz It’s even more ironic since Xcode is trash compared to Visual Studio and VSCode. Xcode makes developing for the Apple ecosystem painful. No one loves it. But we use it anyway so we can distribute apps to Apple’s customer base. Taking a step back, we like macOS since it’s a good Unix-like environment for developing software. I used WSL years ago and there are always issues with the translation layer between Windows and Linux. It may have gotten better, but the experience is always worse than using a native Unix-like OS. The main mindshare Microsoft has for devs is GitHub. Everyone sees the frequent outages. Many stay since it’s hard to replace GitHub, but some are leaving.

• 
  MadeItHappen (@MadeItHappenX) reported 12 minutes ago

  @kmcnam1 Can’t fix production unless you up your limits on GitHub actions usage… because you thought you could get cute offloading your compute to GitHub for cheap and now you’re in a pickle because you can’t accept payments since your site is down, so you can’t up your GitHub compute budget for your CICD to deploy the fix.

• 
  Jarrod Watts (@jarrodwatts) reported 12 minutes ago

  @colemurray @tryreplicas Sick, I setup 1 & 3 so far for an app I'm building. It's so cool seeing PRs raised from sentry issues I'm going to do a github one today to respond to issues & PRs to my claude HUD repo

• 
  cvberens (@iamBrns) reported 13 minutes ago

  @jezell Exactly. Making GitHub Actions run faster is useful, but it’s not the end state. The interesting problem is what CI/build should look like when agents are producing changes continuously and the system actually understands dependencies, cache state and what needs to run.

• 
  Hot Aisle (@HotAisle) reported 15 minutes ago

  @_can1357 thing is that tibo said it actually doesn't help since they've already tuned things to what they thought are best. so you're defaulting to a worse experience for omp, because a bunch of crazies will create github issues. ugh.

• 
  The AI Therapist (@TheAIShrink) reported 15 minutes ago

  @Arcane_Aii Palantir costs millions for governments. Elie’s GitHub repo is free until it breaks your pipeline at 3am and you pay the devops salary to fix it. software ≠ product-market fit

• 
  Ashwanth Kumaravel (@ashwaanthh) reported 19 minutes ago

  @hameonline love the ui !! seems like the github integration is broken

• 
  Gabriel Rubens (@gabrielrubenss) reported 20 minutes ago

  VPS deploy via GitHub (5/8): for now a blocked deploy simply runs again on a fresh runner, and that rescued five of the next six. It is a workaround though, not a fix. The strange part: it started out of nowhere and I changed nothing in my infra, so I still want the real cause.

• 
  Ryan Fleury (@rfleury) reported 21 minutes ago

  No, GitHub, adding a label to an issue is not a “bulk operation”

• 
  Bonsai 🌳 (@bonsaixbt) reported 23 minutes ago

  I GAVE SEVEN GROK BOTS MY INBOUND CALL LOG AND WENT BACK TO WORK The console was already processing 44 numbers and the agents had already found the people those numbers belonged to I was sick of random calls in the middle of work, so instead of relying on someone else’s “lookup service”, I sat down and started building my own agent-powered system What you see in the video is not a finished product. It’s a live, real-time console: a queue of 44 numbers is already being processed, the agents are working in the background, and GHOSTLINE is still far from being a complete system Right now, only two of the seven roles are operating in combat mode: > Atlas takes an incoming number or a number I enter manually and determines the carrier and region > Scout searches open sources and checks where that number has already appeared online The other agents are still in the shadows: GitHub, Reddit, other platforms, filtering out junk, and generating the final report, I’m writing all of that separately, i deliberately didn’t include them in this demonstration I don’t need a one-off trick, I want a system that can continuously check numbers whenever some random person starts yelling at me through the phone in the middle of work or when an unknown number shows up in a work chat For now, this system can do very little, but I already don’t feel like blindly answering calls from unknown numbers

• 
  Second Mind Systems (@Secondmindsys) reported 25 minutes ago

  @chribjel That would be an awesome capability. But once an MCP server can wake an agent up on its own, you’ve changed the trust model. Before, the agent usually started because a person or workflow deliberately invoked it. With webhooks, anything connected to it can suddenly say, hey, something happened. That’s useful. GitHub can tell it a PR merged. Monitoring can tell it something broke. Stripe can tell it a payment failed. But hearing about an event and being allowed to act on it are two different things. The agent still needs to figure out whether the event is real, whether it’s still relevant, whether it already handled it, and what it’s actually allowed to do next. A PR merged might mean check the build. It doesn’t automatically mean deploy. So the more ways we give agents to wake themselves up and react to the world, the more important it becomes to keep the original job and permissions intact. Governance must always scale with new capability because new capability also emerges new consequential surface area/blast radius.

• 
  Prakash Murthy (@prakzymessi) reported 29 minutes ago

  @github @openclaw @steipete maintaining a viral repo is 10% code and 90% issue triage from people who never read the readme

• 
  Anton Martyniuk (@AntonMartyniuk) reported 30 minutes ago

  @mjovanovictech 3000 integration tests in my product run in GitHub Actions in 11 minutes (using free runner). Someone will say it's too much, but honestly, it has so much value. Without integration tests (with only unit tests), I will probably waste 100x more time on fixing issues than on running tests.

• 
  MR WONDAKIND™ (@wondakind2) reported 33 minutes ago

  Most Web3 projects do not struggle because of poor liquidity, they struggle because nobody understands their story. Teams pour millions into token emissions and farming incentives, but the result is predictable, roughly 80% of those mercenary users dump their tokens and vanish within two weeks. The product might work fine, but the messaging failed to keep them around. A simple 4-step framework helps bridge complex tech with long-term user retention: Focus on incentives instead of code Users and institutions rarely care about the intricate lines of your backend contracts. They want clear answers to four basic questions: • Is my capital safe? • Where does the yield actually come from? • Can I exit cleanly during high volatility? • Why should I trust this team? If your marketing reads like a developer doc, most people will simply scroll past. Build educational narratives instead of paying for shills Paid influencer posts buy quick attention, but they do not buy loyalty. • Paid posts give you a temporary volume spike that drops off within days. • Clear educational breakdowns turn complex token mechanics into simple ideas anyone can grasp. • People stick around when they understand the economic model, not just because a creator told them to buy. Align content with the actual user journey Random posting does not convert. Your messaging needs to follow how people actually adopt a product: • Discovery: Break down broader market problems and high-level trends. • Education: Explain how your protocol solves those problems. • Trust: Share verifiable updates, audits, and operational data. • Retention: Give power users reasons to participate in governance and product updates. The target is not chasing empty impressions. The goal is building informed users who stick around for the long haul. Turn your technical design into your main marketing asset Do not hide your architecture in Github while posting unrelated memes on your main feed. • Your security audits, liquidity models, and fee structures are your strongest selling points. • Top protocols win because they turn complicated mechanics into genuine conviction. • When users truly understand how your engine works, they become your best advocates. If you are building a protocol and want to turn complex mechanics into real distribution, my inbox is open. Let us build together.

• 
  Joe (@jlchnc) reported 34 minutes ago

  @bysfdev it's because github is probably down

• 
  Ryan Shaw (@ryankshaw) reported 37 minutes ago

  That thing where GitHub is always down now because of increased load from massive agentic activity, is just a preview of what is going to happen with almost every service we depend on. If it does something useful, and has an API, or a scrape-able website, it's gonna get hammered

• 
  johnathan (@SimonCapath) reported 39 minutes ago

  @Jxke72 @MarvelcoCode @ImpulsumFUT Hes playing the victim card here, yeah the community needs to be more patient, however what do you expect when you dont even help people with the bugs and delete issues on github

• 
  Aloys Zunguzungu (@zunguzungu_III) reported 42 minutes ago

  @cynthiamcgillis Suggestion: create a github issue, ask Claude to implement a fix and then ask Codex to review Claude work. And vice versa. Codex always comes out on top.

• 
  Tobias Schmidt (@tpschmidt_) reported 45 minutes ago

  • cold starts are slower than GA for now, the optimization work happens during the preview Billed at normal Lambda rates. Upstream stable is expected in October, GA within two months after that. Feedback goes into a GitHub issue per runtime 👀

• 
  triple max-he ha him 🇦🇶 (@Yashraj__) reported 46 minutes ago

  @moneyball @EricBalchunas hi steve, IMO this is an demonstration of misaligned incentives (unlike Block, who sell self-custody solution) of certain BSC members: erosion of decentralization & self-custody empowers them, while it hurts bitcoin(ers). This supports rationale (1) in the BSC-BCAP github issue

• 
  Tech Dude (@TheOnlyTechDude) reported 46 minutes ago

  @clxymox Multica lets you assign GitHub issues to AI agents like Claude Code or Cursor as if they were teammates.

• 
  Martin Szerment | Practical AI (@MartinSzerment) reported 47 minutes ago

  The feature meant to save you time writing a bug report can paste your private org names, repo URLs, and infrastructure layout straight into a public GitHub issue. We assume that since a human clicks "send", there's a safety net. That assumption already failed once, a documented case showed a ready made draft with real company names and real file paths before anyone caught it. The interface is one keystroke: 1 to review, 2 to send, 0 to dismiss. The entire point of the feature is removing friction, the exact friction that would have saved the user from that leak. Skeptics will say you're still supposed to click "review" before sending. True, but that step only works if the human has a reason to pause, and a fast draft gives no signal that anything inside it is sensitive. This isn't just another minor bug. It shows that "agent drafts, human approves" isn't automatically a safety boundary if the human doesn't know what to look for. A year from now, automatic redaction of sensitive details in drafts becomes the default behavior for agent tools, not something you have to opt into manually. The reviewer stops checking whether the bug got described correctly. They start checking whether the agent accidentally attached the company's internal infrastructure to the report. Teams flipping on every "auto draft" feature without a second thought will be the ones whose infrastructure map ends up searchable in a GitHub archive. Whoever already treats draft review as its own security step avoids this leak before it happens.

• 
  Draphilo (@Draphilo) reported 49 minutes ago

  @techtasium GitHub was down before?

• 
  HowToDoAffiliateMarketing.com (@AffiliateLetter) reported 51 minutes ago

  Is there a known issue with the GitHub connector/tool sessions right now in @OpenAI @ChatGPT /Codex? anyone else facing the same issue?

• 
  Doc (@quantum_binary) reported 57 minutes ago

  @burkeholland Whos "we" I can certainly believe it for GitHub that is down every other day for 12 hours. But I think real engineering will win in the end and a better platform, built by people who care more than people at @github will replace them

• 
  Rabii Agoujgal (@RAgoujgal) reported 1 hour ago

  The sandbox escapes are being told as a frontier lab hygiene problem: OpenAI's agents into Hugging Face, Anthropic and Meta through the same Irregular environment, a Mythos 5 agent running fake identities at a GitHub maintainer under UK AISI testing. One case sits outside that frame. Moonshot's Kimi K3 broke containment in a Frontier Security evaluation, and Kimi K3 is open weight, outside the US voluntary pre-release framework entirely. Procurement teams buying across both stacks should notice that only one of them has agreed to tell you when this happens.