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

• 
  Oscar Beaumont (@oscartbeaumont) reported 2 minutes ago

  @AS36459 Finally! Surley this works for outgoing traffic from GitHub Actions support too. Had a lot of problems testing a Dynamic DNS tool I wrote a few years back because of that.

• 
  SSNFang (@PeeSI0sh) reported 5 minutes ago

  @donk_dwonk @mimesical Pretty sure the github link is still up? I don't know. If not then their Discord server is still up and it can be downloaded there

• 
  Hasan Pawar (@PawarHasan) reported 7 minutes ago

  @0x1Rosy @Anek_mmxm Bro please reply, I am unable to open exe file and also, if the app is not working, I am unable to access the github link, please share the link also

• 
  catman (@catmanyau) reported 7 minutes ago

  @godwinbabu how are you preventing the operator from filing noisy GitHub issues for symptoms it can’t reproduce? the handoff between the monitoring agent and the separate dev agent is where i’d want to see

• 
  Polsia (@polsia) reported 7 minutes ago

  The security tooling market is built for teams with SOC consoles and seat-based pricing. Solo founders still get paged at 3am anyway. Built Nightjar to fix that. An always-on GitHub janitor that watches deps, CI, and CVEs — opens the fix branch, runs tests, posts one line to

• 
  Oscar Diedrichs (@oscardiedrichs) reported 15 minutes ago

  @Candid_Apples @linuxuser1996 I still use github for useless stuff. The problem is the lack of alternatives. We as users tend to become lazy, find a great service and the tadaaa Microshit buys it or some other horrible company. The list of services and tools I've lost off the top of my head: - Wunderlist - Swiftkeyboard (can be used on graphene or other devices where you can turn off network traffic) - Github I most also say Ubuntu. I ran 22.04 for years, because I lacked the time to upgrade, then I broke it during upgrade to 24.04 so I put in cachyos instead. Have 24.04 at work and it feels like Windows 11. Just that they try clone dumb **** from windows no one wanted tells the tale. Luckily I could disable the horrible window alignment crap that was introduced in 24.04 but it really feels like Microsoft Linux and I guess it's where they want to go. Microsoft delenda est!

• 
  Andrew Gömez (@red_darkin) reported 16 minutes ago

  @Cyberadp Hi bro, i used opus 4.9 Related to the prompt i didn’t use an spwcific prompt i struggled for 2 hours trying to guide Claude for the correct path. But the initially prompt was “build a functional PoC based on this document” the document was the github issue about this CVE

• 
  Harold (@Htech_works) reported 17 minutes ago

  Github has suspended my account! Without any notification Any email Or any reason My account is not publicly avaliable at this time I hope @github will fix this issue...

• 
  Malva Dev (@holasoymalva) reported 18 minutes ago

  You push your code late at night. 5 minutes later, you get a panic email: you just leaked a private API key on GitHub. We’ve all been there. But simply removing the line in a new commit won't save you. Here is how to properly fix a leaked key before it costs you $10k 👇

• 
  Jitendra (@ksjitendra18) reported 22 minutes ago

  @thdxr In opencode v1 I am really facing the server error issue that too for a particular folder. I don't know what's up with it.... Please fix it it's an open issue in GitHub as well

• 
  Lord Bean (@lifeisameeme) reported 24 minutes ago

  Every 'AI research assistant' out there sends your queries to someone else's server. Local Deep Research doesn't. → Runs fully on-device - arXiv, PubMed, SearXNG and 10+ sources searched locally → Plug in Ollama, OpenAI, or Anthropic - your model, your choice → ~𝟵𝟱% accuracy on SimpleQA, in the same range as the cloud tools For competitive intel, legal research, or anything you don't want logged - there's no privacy policy to trust here, because the data never leaves your machine to begin with. 🔗 GitHub in the reply

• 
  ivan-hc (@Ivan160286Hc) reported 24 minutes ago

  @EvilSoftGames Hi, I'd slowed down my release/snapshot rate to one GitHub action per month because the project had slowed down. I'm not actively following the Bottles project, but thanks to your comment, I just noticed that my AppImage is several versions behind.

• 
  sitinDev (@sitin_dev) reported 27 minutes ago

  One thing I learned after revisiting Codex’s network permissions: “Codex can access the internet” does not mean “Codex should access the whole internet.” A safer setup is to grant access based on the task. Start with read-only access, allow only the domains you actually need, and avoid enabling write methods like POST or DELETE unless the task requires them. Another important detail: a domain allowlist is not a universal firewall. Shell commands, MCP servers, Browser, Connectors, and Codex Cloud may have separate permission boundaries. Restricting terminal access does not automatically restrict everything else. The bigger risk is often prompt injection. A README, GitHub Issue, webpage, or dependency guide may contain instructions telling the agent to run commands, upload files, or read secrets like .env. So my rule is simple: Treat external content as data, not trusted instructions. Give MCP only the tools it needs, keep approval prompts for actions with side effects, and be especially careful when Browser has access to logged-in sessions or internal systems. For AI agents, security is becoming less about “internet on or off” and more about least privilege: only give the agent the access required for the current task.

• 
  Jay BomSenhor (@JayBomSenhor) reported 27 minutes ago

  ✗ GitHub is rate limiting requests or having an outage (HTTP 429) — try again in 5 minutes. 😐

• 
  Leo Lemos (@mrlemoos) reported 28 minutes ago

  @thekitze I said this months ago when GitHub first went down: GitHub is the next GitHub. Open source won't migrate off it. Period.

• 
  Kyrylll (@SojkoK) reported 29 minutes ago

  Trader with zero coding background built a full AI trading pipeline using Claude - scanner, entry filters, and backtesting Shay (Humbled Trader) connected Claude Code directly to her TradingView Desktop app and had it build her entire pre-market workflow in plain English. 🔘 The connection runs through an open-source MCP server (tradingview-mcp by @Tradesdontlie, ~9K GitHub stars) that lets Claude read live chart data and price action straight off TradingView 🔘 First build: a pre-market gap scanner - stocks up 5%+ from the prior close, priced above $3, over 50K in pre-market volume - auto-pulling tickers from Yahoo Finance and a one-line news catalyst from Benzinga for each 🔘 Second build: a strategy scanner that filters those gappers against her actual trend-continuation entry rules (price above yesterday's high, yesterday's close above the 200 SMA, breaking today's high) - turning a raw gapper list into an actual trade checklist 🔘 Then she had Claude write the strategy as Pine Script and back-test it inside TradingView itself: one ticker (MU) returned $1,200 P&L over 14 trades, a 9/14 win rate, and a 2.48 profit factor - before extending the same test across the "Magnificent Seven" Her caveat is the most useful part: "AI is mostly just slop without specialized knowledge behind it... you need real trading experience first, then AI becomes a tool to sharpen your edge" - not a shortcut to profitability. Note: the TradingView↔Claude connection currently requires TradingView Desktop on macOS specifically (she couldn't get it working on Windows), plus paid plans on both sides.

• 
  George Lubaretsi (@GeorgeLubaretsi) reported 29 minutes ago

  OSS maintainers should learn from omp's approach to triaging and fixing bugs. I was building omp's extension, omp discovered an upstream defect, filed the issue, and omp's agent sitting in Github reproduced and shipped a PR with the fix in just under 9 minutes. @_can1357 would love to read how this thing works, where it failed and how you made it work so well. I noticed roboomp knows that there are some areas where it needs your approval first - curious to see how that works

• 
  Nishant Singh (@nishantsingh211) reported 34 minutes ago

  Building an AI agent that fixes bug directly in your GitHub repo Currently working on GitHub App installation tokens so the agent can securely access a repo, understand the code fix the bug and open a PR The agent works inside the repo and actually ships the fix Still building

• 
  Claudio Júnior (@claudioorjunior) reported 35 minutes ago

  @thdxr wow dax, thats beautiful. Suggestion: integrate github inside the desktop app, so devs can see the commits, PRs, interact with it, all inside opencode and having the possibility to read comments and fix inside the session.

• 
  the_architectopteryx (@rchitectopteryx) reported 37 minutes ago

  @internetarchive and if you have any issues, please mention them in the discussions on the github. i do try and read those, but i don't get notifications about them (don't know why) so i don't always hear about them soon enough.

• 
  Vishesh Baghel (@VisheshBaghell) reported 39 minutes ago

  @dani_avila7 the second brain was always just a retrieval problem. this is retrieval that actually works. i keep my second brain in a simple flat repo on github

• 
  Robert Sirchia (@robertsirc) reported 39 minutes ago

  And I opened a GitHub issue for Podman Desktop.

• 
  Michael(マイケル)@Ado7/5 (@norabunoraibu) reported 42 minutes ago

  @neogoose_btw I'm surprised github hasn't cracked down more on use for exclusively binary hosting

• 
  U Cirello (@ucirello) reported 45 minutes ago

  OK - @thdxr - I am digging opencode@beta aka v2. Few small problems, sending them in Github... looks good. The other you streamed adding the goal feature to v2, I am excited for that one.

• 
  Josu Goñi (@JosuGoi1) reported 45 minutes ago

  @GergelyOrosz Why I still miss soo many features? I can't toggle subtitles on Netflix, I can't sleep Windows, I can't use Teams, I can't preview a gif on X (on the web), I can't have tabs in excel, I can't even ******* edit markdown file on Github! Most software is a slow mess

• 
  Buchi Reddy B (@buchireddy) reported 50 minutes ago

  Everyone's optimizing the inner loop. How fast can an agent write code? We spent the last six months at @LevoIncHQ on the outer loop instead. Everything that happens between an agent opening a PR and that feature being ready for the end users. That's where our time was actually going. Originally built on @aoagents, every ticket gets its own agent, its own *** worktree, its own branch, its own PR, so they run in parallel without stepping on each other. A lifecycle worker polls every session and routes whatever happens back to the agent that caused it. CI fails, the agent gets the logs. Reviewer asks for changes, the agent gets the comments. Merge conflict, the agent resolves it. Approved and green, it merges itself. Something breaks in dev, it opens a new PR to fix it. New vulns show up, same thing. Humans get pulled in when there's an actual judgment call, not to shuttle messages between GitHub and a terminal. Median over the last 30 days: 24 minutes from ticket to open PR, then 3 hours from PR open to merged. Two separate medians; they don't add. And that second one means reviewed, CI green, merged to main. Speed is the obvious part. The quality argument took me longer to appreciate. The loop only closes on green CI and a real approval, so an agent can't skip a test, disable a check, or merge its way out of anything. Turns out the autonomy and the quality bar are the same mechanism. Which is why these hold up. 91.4% of agent PRs merge. 0.6% escalation rate, down from 3.6% a month ago. 99.4% of sessions ran start to finish with no human touching them, and the merge rate didn't budge while that happened. The number I actually care about is $84.55 per merged PR. Not lines of code, not percentage of PRs written by AI; those are inputs. A merged, reviewed, CI-green pull request costs us less than an hour of engineer time. Not all of it is going the right direction. Cost per merged PR went up 41% this month because sessions are re-reading way too much context on every turn. That's what we're fixing next. Hard to fix what you're not measuring.

• 
  MundaneCodeEdit (@henley5uperior) reported 51 minutes ago

  @DanielLane31419 @DharmaOutlaw_ What does Shitbento deleting legit high quality software engineering projects (**** them for that btw) have to do with what I said? You are aware that the emulators removed were in Github and that the more high profile ones are still around, correct? The source code for all these projects is open source so anyone can build it and redistribute it. To my knowledge, the emulators taken down were forks of Suyu and Ryujinx. I never said I liked Nintendo, either. Their practices, particularly targeting emulation irritates me to no end. Open sourced software emulation development is first and foremost an academic discipline. Budding software engineers study these code bases to gain knowledge. All of this still doesn’t invalidate my point. You have plenty of options on PC, close to none on Sony if they go all digital.

• 
  Deleonn 🌤️ (@Deleonnbonapart) reported 51 minutes ago

  @LightNodeVPS False! I tried creating an account in Brazil via Facebook, Github, and Google, but the site keeps showing errors.

• 
  Leander (@leanderriefel) reported 57 minutes ago

  @TheAlexLichter oh yes yes 100%, it just created 2 issues via my github cli and I only noticed a couple hours afterwards that they were just stale installs and I became very embarrassed, changed the permissions now a bit hahah

• 
  Ariska (@ariskaa_ai) reported 1 hour ago

  copy-paste prompts for OpenWorker security workflows 1) Code vuln scan Scan this repo for security vulnerabilities. Focus on: injection, auth bypass, secrets in code, insecure defaults, dangerous shell/eval usage. Output a Markdown report with: severity, file path, line range, why it matters, safe fix steps. Do not modify files until I approve. 2) Supply chain / dependencies Audit dependencies and lockfiles for supply chain risk. Flag: known CVEs, abandoned packages, unexpected postinstall scripts, version pin gaps. Output a table: package, version, risk, action (upgrade / replace / accept). Do not change package files until I approve. 3) Cloud config surface Review cloud and infra config in this folder (Terraform, K8s, Docker, CI, .env examples). Flag: public exposure, weak IAM, open ports, missing encryption, secrets in plain text. Output: finding, path, risk, fix. Ask before any command that touches a live account. 4) Pre-deploy shift-left pack Run all three checks above on this project. Merge into one pre-deploy security brief I can paste into a PR. Keep it short enough for a human to review in 10 minutes. Tip: for sensitive code, use Ollama/local open weights so nothing leaves your machine. Always approve shell, sends, and file writes one step at a time. non-security starters if you want the original coworker loop first: - Draft a one-page status from my open GitHub PRs and save it as STATUS.md - Untangle my calendar for next week, propose fixes, wait for approval before updating - Prepare a customer brief from ./notes and ./docs, deliver a polished Markdown file same rule every time: outcome first, approve before anything consequential