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

• 
  Kenny (@kenny_aaarrrhhh) reported 7 minutes ago

  Every company thinks its data goldmine is Slack, GitHub, or the email server. Those capture what people decided. Not how they did it. The merged PR doesn't show the four approaches that got rejected. The sent email doesn't show the three drafts before it. Games are different. Games capture the decision itself; every move, under time pressure, with a win or loss attached to it. That's labeled human reasoning at scale. It's the rarest data there is.

• 
  シカバネ (@Nvr_Knows_Bst) reported 10 minutes ago

  @Shoalst0ne @i3dwne1 @fishyfishydev Yeah, it's not showing on GMGN yet but maybe it will after that fix. This bug has goofed over a couple of GitHub projects recently, and the worst part is it ends up in the developers getting harassed.

• 
  Ergod (@ergod_dev) reported 21 minutes ago

  No longer just an agentic discord bot, website revamp, added login to web dashboard with discord/github/or google - link whatever accounts you want & use Ergod however you want! Also, added support for bot via Telegram. Users are just about fully supported even without Disc!

• 
  Joe Guardino (@JoeGuardino88) reported 25 minutes ago

  @NFL_Blitz_Rez I think this link is broken. Can you post on GitHub?

• 
  Austin Campbell (@austincampbell) reported 26 minutes ago

  Almost every bank and blockchain protocol in the world is being used by scammers and bad actors because they don't understand the problem and refuse to do so. Yes. I meant what I said. This is a very good and thought provoking piece from @RebeccaRettig1 and it should be read by a lot of people in this space. Putting responsibilities where they are feasible matters. I'll raise one additional point: we shouldn't limit ourselves to blockchains here. Financial crime is multidisciplinary, multiplatform. If you are using blockchain forensics, you are being exploited. If you are using traditional bank KYC and software, you are being exploited. If you want to protect yourself, you need to span all of those, and social media, and darkweb data, and github repos, etc. The enemy just wants to win. They aren't drawing arbitrary boundaries. If you do so when defending, you are essentially creating the Maginot line while the hackers or scammers just go through Belgium. If you don't have a comprehensive multi-source multi-capability financial intelligence unit, you're getting exploited. Right now.

• 
  Syed Daim Kazmi (@D_kazmi) reported 27 minutes ago

  Project 7/15 complete — Building a GitHub MCP Server with a Local AI Agent Built a Python MCP server that gives MCP-compatible clients and local AI agents structured access to GitHub for repository discovery, file inspection, issue management, and pull request review.

• 
  Nav Toor (@heynavtoor) reported 27 minutes ago

  The Composio breach in May 2026 exposed every credential stored on their platform. That's the risk of closed-source integration platforms. Your customers' OAuth tokens, API keys, and credentials sit on servers you can't inspect, running code you can't read. Nango is the open source alternative. 11600+ GitHub stars. 900+ APIs. Every line of code is public. The auth layer, the credential store, the proxy, the execution runtime. All inspectable. All self-hostable. Replit, Ramp, and Mercor already run it in production. 600+ B2B companies total. Here's why developers are switching: You describe an integration in plain English. "Sync GitHub issues to my database every 5 minutes." The Nango AI Builder skill, along with a coding agent such as Claude, Cursor, or Codex, can write code and test it against a real account. You read it. You edit it. You own it. It's not a black box. It's code in your repo. The runtime handles everything production needs: OAuth for 900+ APIs, automatic token refresh, rate limit handling, per-tenant isolation, retries, and scaling. SOC 2 Type II, HIPAA, GDPR compliant. And you can self-host the entire thing for $0. The "unified API" vendors charging $40K-$100K/year for the same capability are selling you a hosted version of what Nango ships publicly. After Composio, the question isn't whether open source integrations are good enough. It's whether you can afford to trust closed source with your customers' credentials.

• 
  CULT (@thecultos) reported 31 minutes ago

  Let’s put agents to work on GitHub repos 🦾 turning every backlog issue into verifiable work with an onchain receipt.

• 
  Jack Shelton (Qwik) (@JackShelton) reported 31 minutes ago

  @orcdev The main problem, is there really isn't much of a reason to use cursor origin. You're still syncing to github on most repos, there's no AI specific features that github doesn't have (at least yet) And I still need my current actions pipeline for code review

• 
  Julien Zammit (@JulienZammit1) reported 31 minutes ago

  5. can your agent edit .github/workflows? if a stranger can open an issue, a stranger can reach your CI. 1 min

• 
  Hisaac Brown (@realhisaacbrown) reported 33 minutes ago

  GitHub contribution graphs have become a terrible way to judge developer skill.

• 
  PunktZero (@PunktZerop) reported 40 minutes ago

  I just shipped v1.0.0 of my local-first portfolio analytics workbench. The interesting part is not the release. It's the bug the release candidate caught. Quick numbers first: 459 tests green. 6 expected skips. 0 failures. 78% coverage overall, 82–100% on critical modules. Byte-identical reruns. SHA256SUMS verified against GitHub downloads. Now the bug. My demo command seeds synthetic fixtures and runs a backtest. One of those Transactions are CASH deposits. Deposits have no price series—cash doesn't Have a chart. The backtest engine built its symbol list from ALL transactions. Including CASH. Then it demanded a price series for cash, found none, and died. The lml demo worked fine. I'm lml, the backtest demo crashed. Every single time. Here's what bothers me: that bug has existed since v0.1.0. Through two stable releases and an RC. Why? The scenario path in the same codebase excluded CASH correctly. So the tests I wrote around the scenario path passed, and Nobody ever wrote a test for "run a demo, then run a backtest on it." The most obvious user journey had zero coverage. Classic blind spot: you Test the modules, not the sequence users actually type. The fix was one line. Excluding CASH from the symbol set, consistent with the scenario path. Plus three regression tests, including one asserting the The opposite behavior stays intact: genuinely missing price data still aborts. No silent substitution. That's a design principle, not an accident. What else went into v1.0: • Job queue: submit, progress, cancel, all async, API never blocks • Run manifests with canonical hashes — parameters, data, model, environment, result. Rerun produces byte-identical results or documents exactly which precondition drifted • Drift detection: missing data aborts loudly instead of being replaced • Rebalancing with minimum order sizes—flagged as below_minimum instead of silently rounding • One job-status model across CLI, desktop UI, and web UI And one honest limitation I documented instead of hiding: The Windows installer build is not byte-reproducible. Inno Setup embeds timestamps. I can't give you a reproducible-build claim, so I published the exact SHA256 for the exact artifact instead. A checksum you can verify beats a reproducibility promise I can't keep. Everything runs local. No cloud, no account, no telemetry. Market data only when you explicitly pull it. Research tool. Not investment advice. No buy/sell signals — the codebase enforces that with a language guard on its own reports. Repo and release notes are linked on my profile. If you build analytics tools, check your own demo path. Is it covered by a test, or does it just work because someone once clicked through it?

• 
  Ramtin (@ramtinrhmti) reported 42 minutes ago

  Day 2/180 UPDATE yesterday I asked if I should build or validate. did some digging today but not the kind that actually counts yet killed the clinic booking idea, a funded competitor already does exactly what I wanted to build. glad I checked before sinking a month into it pivoted to something I deal with myself, AI agents saying a task is done when it isnt. before touching code I checked 5 real PRs an AI coding agent made against the actual github issues they were supposed to fix, just to see if the problem is even real 2 were legit. 3 got closed without merging even though they looked fine on paper. so the problem seems real at least on paper but I havent talked to a single person about this. no dms, no "would you use this," nothing. that's still the actual next step, not more building scaffolded it anyway bc I wanted to know if it was technically doable. a github app + a small action, both build and run. broke something mid way, fixed it properly not attached to this yet. could easily be wrong, just havent found out yet

• 
  Patrick (@PatrickOjo_) reported 42 minutes ago

  *** was built for humans committing a few times an hour. Agents commit hundreds of times per second. That mismatch is not a minor scaling problem. It’s a fundamental architectural incompatibility between infrastructure designed for deliberate human cadence and agents that create, fork, and discard state continuously as part of how they work. The response isn’t to slow the agents down to fit the infrastructure. It’s to build infrastructure that treats agent activity as first-class: ephemeral branches for agent sessions, JWT-scoped access per agent, no rate limits, APIs that let an agent call createRepo() without touching a UI. The human workflow still lands in GitHub at the end. The agent workflow needs a different control plane underneath it. That layer doesn’t exist at scale yet. The companies building it now are solving the infrastructure problem that every serious agentic deployment will hit within 18 months.

• 
  Piyush Singariya | building gear6io (@piyushsingariya) reported 46 minutes ago

  Most engineering work doesn't get blocked in Jira. It gets stuck in Slack threads, silent handoffs, and dependencies nobody owns. I'm building @gear6io to surface what stopped moving across Slack, GitHub and Jira - and what to fix first. Looking for design partners ↓

• 
  cvxv666 (@antpalkin) reported 46 minutes ago

  solana:C3bajJW843KN9Uu441JkXN7zVMs4VM2HvdAGyGiBpump touched $3m overnight and I slept through all of it my ticker, my github, my agents, and the market put three million on it while I was face down in a pillow people are betting on this thing because they can watch it get built in front of them. that's a weird kind of pressure and I love it not going anywhere, not selling anything, just building contract goes on chain today and the bot starts trading a real wallet with real money god bless

• 
  Gopi Krishna (GK) (@gopikl) reported 47 minutes ago

  Now I know why github keeps going down once in a while. An old friend (non-tech) got in touch with me saying his vibe-coded project was not working anymore. After a lot of hesitation, I checked it, only to find that he committed and pushed a lot of .mp4 files (some gt 1GB) into *** - so naturally, push/pull/everything was breaking.

• 
  aria (@aria__han) reported 48 minutes ago

  don’t write md files, write github issues. saving me immense time and cognitive load to coordinate through issues rather than files or messages, especially for cross human coordination

• 
  Arham (@arhamsai) reported 52 minutes ago

  @yoimkonrad This was on a PR that contained an entire build which was about 15,000 lines. From the initial commits CodeRabbit gave the most findings, almost 2x more than Greptile and Codex, however after 2-3 rounds of fixes it didn't find anything while Codex kept giving 2-3 findings per round. Codex kept doing this for about ~20 further rounds and CodeRabbit did give findings on a handful of those commits as well, but what I have majorly noticed is that after a fix Codex tends to find other things that came up elsewhere because of the fix. I'm not sure if this is because CodeRabbit has an incremental review system and Codex maybe does it differently, but it does feel like it rereviews everything again. On the experience side however CodeRabbit is much much better, Codex does not give a prompt and doesn't even use GitHub checks, also been loving the autofix feature in CodeRabbit.

• 
  Priyank Mishra (@priyankmishraa) reported 52 minutes ago

  @RadhikaKarma LeetCode helps with problem solving, but building projects makes you a better developer. Build something, solve real problems, get stuck and figure things out. Then make your work public - GitHub, open source, blogs, videos, anything. Problem solving + real projects + public proof of your work makes you far more employable.

• 
  Qubitium (@qubitium) reported 54 minutes ago

  Github is throwing errors left and right at the api level. The agentic ai has made all SaS pretty unusable at this point. No SaS is designed to scale at 100x per week at this point. Something has to be done. Github needs to throttle per free account to 1 global concurrent action right now or else we will see massive outages again.

• 
  Artes (@Artemwkz5) reported 54 minutes ago

  Your agent isn’t failing. It’s on payroll in the wrong building. Busy chat. Dead output. Same disease. This 11-second video is ByteByteGo’s floor plan for LangChain, AutoGen, CrewAI, LlamaIndex, and Semantic Kernel. Same model logos on the right. Five jobs on the left, in those yellow boxes. X keeps voting for a winner. The video is the org chart they should have used before they cloned a repo. Don’t listen to the captions. Watch the arrows. See the llama row? Hard hat at the bottom. Query up. Response down. That’s a librarian. Load → parse → index → ask your PDFs, DBs, APIs. If you dumped 400 internal docs into a generic “agent” and spent a month on retrieval, you hired a plumber to run the library. The weekend version is already drawn. See writer and editor, then three clipboards? That’s a newsroom. Process in the middle. Tools under the floor. If you needed draft → edit → three tasks and opened a group chat, you staffed a committee. Committees debate the assignment. Newsrooms file it. That’s why one path ships by Friday and the other still has “alignment.” LangChain is pipes: prompts, tools, vector stores, chains. AutoGen is a meeting: humans can cut in, code can run, tools can fire. Semantic Kernel is a socket wall: C#, Python, Java, then a plug into the model. None of that is a personality. It’s a department. One person who pauses on the right box looks like a 7-agent company. One person with five GitHub tabs open looks like they work in AI. Open the video. Find your yellow box. Fire the other four.

• 
  saccharine (@saccharine_ex) reported 54 minutes ago

  @nickisnoble @steveklabnik the kernel is 40 million lines of code, i know rails is sloppy and all but is shopify really more? (some old sources say way less) how would *** on s3 instead of a file system solve that? the main issue with *** is the ux, not the scaling unless you are github (rails again)

• 
  Poonacha Machaiah (@poonachaX) reported 56 minutes ago

  Third: Cursor launched Origin, code hosting with agents built in, on the same day GitHub went down for hours. Twenty years of the world's code sits on those rails. Ground you assume is permanent turns out to be a choice someone keeps making.

• 
  Wallflower🌱🫥(Bandit arc) (@wallflowercrypt) reported 56 minutes ago

  Every trader has that ONE rule they refuse to break. But I broke every single one of mine. I'd hit a good trade, then take the next one too cautiously because I was afraid of giving the profit back. Or lose a trade Then revenge trade the next one at twice the size, trying to make it back. By week end, I'd sometimes have given back everything I'd made earlier in the week. with time I realized the strategy wasn't the problem, my execution was. I knew the rules. I just couldn't follow them when price moved against me. So during @Bitget_AI hackathon I built a strategy. It longs when momentum is strong, shorts when bounces fail, and buys when fear spikes. Same signals across three different pairs. Bactesting over time revealed 487 total trades with a 64% win rate because it follows the rules every time. It doesn't revenge trade after a loss. It doesn't abandon a setup because of a pullback. It doesn't hold onto a bad position hoping for a reversal. If the setup is valid and the stops are set, it executes. Even when you're asleep. That's what discipline feels like. And that's where I think AI can actually change trading. It won't necessarily replace the trader who knows what they're doing. It can replace the part of the trader that keeps getting in their own way when it matters most. Just submitted Wallflower to the CWC AI Trading Skill Challenge. The GitHub repo is public, with the full spec, 19 parameters and backtest examples. Bitget hackathon down. CWC next.

• 
  Tegence_AI Africa (@AiTegence) reported 58 minutes ago

  AI agents can write code. But what happens when you need that agent to actually do something with the code? We kept running into the same problem: connecting agents to GitHub, Jira, Slack and everything else shouldn’t require a pile of separate integrations.

• 
  Christopher Cook (@webprofusion) reported 59 minutes ago

  Claude down, going to have to dust off Github Copilot.

• 
  @0xDidi (@0xDidi) reported 1 hour ago

  No reason why Microsoft shouldn't have the best coding model with GitHub hosting a large % of the world's code. Skill issue.

• 
  PADRE🏝️ (@0xpadre) reported 1 hour ago

  Cursor is coming for GitHub and it's not subtle anymore. GitHub went down for 7 and a half hours. Copilot, Actions, merges, all of it. 15,000 devs hit the outage. Every minute of downtime is a migration notice. AI-native tools take the code layer next.

• 
  LE◎ - sol/acc (@L0STE_) reported 1 hour ago

  @solontag Lmao brother. Please go look at my github... You should have as much onchain logic as it actually make sense to have; making all products fully onchain is a skill issue.