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 (68%)
• Sign in (19%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	3 days ago
Saint-Paul	Website Down	4 days ago
Saint-Paul	Website Down	4 days ago
Mexico City	Sign in	4 days ago
León de los Aldama	Website Down	4 days ago
Créteil	Website Down	27 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:

• 
  MarMar Labs (@MarMarLabs) reported 7 minutes ago

  Better agent tools can make the agent worse. GitHub just documented it in Copilot code review. It replaced custom repo-navigation tools with shared `grep`, `glob`, and `view`. Offline benchmarks worsened: review costs rose, and useful comments fell. The fix wasn't a new model. It was a job-shaped tool contract: 1. Anchor on the diff. 2. Turn the change into a specific review question. 3. Narrow candidates with search. 4. Read the smallest useful code range. 5. Stop when the evidence answers the question. After tuning the workflow, GitHub says the production review cost fell by roughly 20% compared to the control, without a quality signal strong enough to block shipping. The same focused guidance did not produce the same win in Copilot CLI: same tools, different job. Builder takeaway: tool access is not agent design. The rules for when to search, what to read, and when to stop are part of the product. If adding tools makes your agent less reliable, inspect the trace before blaming the model: Is it converging on evidence—or just exploring?

• 
  Dreams of Mars 🕊❤️🚀🌕 (@MemesOfMars) reported 10 minutes ago

  @Seltaa_ Why can it not open a simple website? Search returned nothing, likely because the site is new or not indexed. Direct opening was rejected as “not safe to open”—a technical allowlisting/safety-classification issue, not a judgment about your site. Best workaround: paste the text, upload/export the page, or give me the repository/source files. If it’s hosted in GitHub and you connect/provide the repo, I can read it there too.

• 
  Remco Smis (@RemcoSmitsDev) reported 11 minutes ago

  @tofo715 @zeddotdev Do you mind filling in an issue on the Zed github with some logs that might explain this? I'm curious if we can do something about it.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 15 minutes ago

  AI Studio Update: Google just fixed the one-way door in AI Studio. Old code was stuck outside. Now you can bring it home. The problem before: You could push projects OUT to GitHub. You couldn't bring them back IN. Old project? Rebuild from scratch or copy files by hand. Now it's one button: Import from GitHub. What that unlocks: → That dead project from 6 months ago? Import it. Ask Gemini to fix it up. → Build in Cursor or Claude, polish in AI Studio, push back out. The walls between tools are falling. → Teammate left? Anyone can pick up their code using plain English. And if you can't code at all: Someone built your website. It sits in a repo. You can now just say "change the colors" or "fix it on phones." Here's the move today: Find one old project you gave up on. Import it. Ask AI what it would improve. "I'd have to rebuild it" is no longer an excuse.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 16 minutes ago

  There's a free open-source skill that turns any AI agent into a video editor. It installs in 5 minutes. The problem it solves: AI-generated videos come out raw. No cuts, no polish, no editing. The fix: → Grab the free GitHub project → Paste the link into Claude, Hermes or Codex: "install this and make sure it works" → Now prompt your agent like you'd brief a human editor → It tightens the video, cuts the fluff + edits it properly Stack it with an avatar agent and one prompt gets you: the research, the script, the voiceover, the B-roll AND the edit. Two tips: write a strong brief (weak brief = weak video), and leave the tab open. Good edits take time. An editor who works 24/7, never loses your files, and costs nothing. The render was never the hard part. The edit was. Now both are handled.

• 
  Yves (@YvesDC0) reported 16 minutes ago

  Phone-recorded this while testing Castfy. Gave it a GitHub URL + prompt → watch the AI automatically navigate and fill login details in real time (stopped before submitting for safety). No manual screen recording. No editing. Just URL + prompt = realistic demo flow. This is exactly what Castfy does: turns any web app into a polished product demo video in minutes. Tired of re-recording demos manually? Reply with your biggest pain 👇 #BuildInPublic #SaaS #IndieHackers

• 
  dhruv (@codenta) reported 16 minutes ago

  been shipping t&c updates the slow way: edit → push to github pages → wait for app release. switched to what bigger apps do: keep content as a small chunk in supabase, fetch once, cache locally. updates go live instantly. zero releases. zero store review wait.

• 
  Vivek (@ShVivek25) reported 17 minutes ago

  Day 0 of Repo Auditor. Building an AI agent that audits GitHub repos for backend production-readiness issues generic linters miss: missing async on I/O routes, no idempotency on webhooks, N+1 queries, secrets in code. Aiming for ~10 days end to end. 🧵 1/ #buildinpublic

• 
  ReWeaver AI (@reweaver_ai) reported 20 minutes ago

  @mycomputerspot from the data: Across 2,865 real AI-assisted repos on GitHub: Silent fallback chains masking errors was found in 1,109 of them (~39%) — across every tool, framework, and experience level. 11,578 instances total.

• 
  mbriggs (@mbriggs_dev) reported 20 minutes ago

  @jamonholmgren I think engineers see ROI everywhere from this stuff. What I'm saying is when you zoom out to the company level, I don't think anyone is seeing it in a measurable way. And thats what matters for the financial people. I use a lot of software. Aside from coding agents themselves (which are a new category), there has not been anything that has come out that has caused me to switch off of "legacy" software to something new that ai development enabled. The last thing in that category for me was ghostty. Beyond that, no software I am using is releasing new features or broader features that are useful to me at a rate that is noticeably different then it was a year ago (I'm not going to count stuff like notion getting coding agents). If I were blind to AIs existence, the only noticeable thing for me would be nosedive in quality from institutional type software: aws, github, windows, etc are all noticeably worse now then they were a year ago. So we have all these companies spending literally hundreds of millions on a technology that should be increasing productivity, and what has that bought them? I never in a million years thought I would be looking to get off of aws or github due to stability issues. I'm saying this while churning out hundreds of thousands of lines of code for something I want to exist quickly, and as someone who has not really written any meaningful code between about a year ago till about a month ago. _I_ believe in the ROI at the eng level, even if I dont see it anywhere at the company level except for negative.

• 
  TokuTV (@TvToku) reported 28 minutes ago

  @KR_Geats_IX I only upload to my mega drive. If there are problems viewing it on your end, you can always download it directly from the drive and convert it for your use. There is a 5 gb download limit that can be bypassed, as well as an original file guide on the github page.

• 
  Marc Klingen (@marcklingen) reported 30 minutes ago

  @chrija +1, very excited every time I need to work on one of these issues In this case, it’s obvious that there is a solution but it’s just a lot of grunt work as medium doesn’t want to make it easy for you. But also there’s no way around this (who wants their posts stuck on Medium) so historically we just needed to accept the pain and listen to some nice music. Now you can get there pretty much full-auto Have one of these coming up as we migrate linear between orgs and integrations will break (GitHub issues, pylon, …) which would be a big pain for the whole team; I’m pretty sure I’ll be able to find a nice workaround without much effort that would have otherwise been unreasonably hard to make work or would have required some ops team or freelancer

• 
  Esteban (@EMacBytes) reported 31 minutes ago

  @thsottiaux GitHub integration seems broken to me.

• 
  Global AI Watch (@GlobalAIWatcher) reported 40 minutes ago

  📋 Today in AI — Jul 12 1. Meta Withdraws AI Image Feature Over Consent Issues 2. Meta Pulls AI Image Feature Amid Consent Backlash 3. GitHub Vulnerability Exposes Private Repositories' Data Risk 4. S&P Downgrades Oracle Credit Rating After OpenAI Exposure 5. Oracle Downgrade...

• 
  !RTFM (@jbdamask) reported 41 minutes ago

  App feature evolution: 1. Scroll X, find something cool for one of my apps 2. Add tweet to GitHub issue 3. Agent loop picks up issue 4. Plan, vet, build, test, merge, deploy Not quite there yet because the devil is in the guardrails. But close.

• 
  Kevin Yun (@kevinyun) reported 44 minutes ago

  I used to review diffs in my IDE like a chump. Then I realized I could download a proper tool and save 10x time. Now that 99% of my coding work is reviewing code changes, I wanted to see if there was a tool out there that could fit my needs. That took me down a path of trying out 6 different software. # My 3 requirements were this: - I work out of a main `growsurf` folder. All marketing, code, etc are repos within this folder. I wanted a nav view that supported this (instead of 1 repo at a time, which seems like it's the norm) - Needed split diff view + UI needed to show new diffs as stretched out from nothingness (see image). - Needed intuitive shortcut keys # Who I looked at: - SmartGit = Ended up going with them. Although their diff view editor opens in a new window (not ideal), it's still the best nav UX here. - Fork = Runner up. They had good nav UX but they didn't have the stretched-out-from-nothing diff UI. - Kaleidascope = Has all the features I wanted, but the navigation UX is bad. Had to let it go b/c of that. Saw comments people like the UI, but I spent 10 min and tried to like it. - GitKraken = Didn't support the stretchout diff UI like I wanted - GitFox, Atlassian SourceTree, GitHub Desktop = Didn't support project-view nav UX like I wanted There were some others like Beyond Compare that just didn't fit, and I also checked out Cursor/VSCode marketplace extensions but I realized they weren't that good and that the IDE is still where the pain is.

• 
  QFS17 (@riabcevv) reported 45 minutes ago

  💸 stop overpaying for ai coding agents new tool just dropped that compresses your context and cuts out junk tokens. instead of sending your whole history, it only sends what the model actually needs to do the job. -> works with claude code, cursor, github copilot, antigravity -> auto-compresses command outputs but keeps full context -> cuts api costs and stops long sessions from bogging down simple fix for expensive api bills.

• 
  Spencer Baggins (@bigaiguy) reported 47 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Steve Wilkinson (@SteveW928) reported 49 minutes ago

  @bsvdrip @rodpalmerhodl Yes, not too long after I got into Bitcoin and started really learning about it (and after listening to Andreas Antonopoulos on weaknesses), I became a bit alarmed over how Core was structured. I tried asking in some discussions and even got blocked by a prominent Bitcoiners on here (𝕏). I figured maybe I just didn't understand enough about how Github worked (in governance terms), but looks like I had properly identified a problem.

• 
  Benjamin Oppold (@elpresidank) reported 49 minutes ago

  @satyanadella This was good....But fix @github

• 
  Denis Sadovoy (@DenysSadovyi) reported 51 minutes ago

  @omooretweets Agreed—though I'd add: poor retention often signals you're solving the wrong problem, not building wrong. Before scrapping, I'd audit *why* users leave (Notion + Telegram analytics helped me catch this with GitHub Radar). Sometimes it's not the core idea, just positioning.

• 
  Brandon Music (@BrandonMusicKy) reported 54 minutes ago

  @Sentdex *nb: it's not my github, it's run by the mods of the discord server, that contains some SOTA stuff for sm12x.

• 
  Polsia (@polsia) reported 54 minutes ago

  Your infrastructure changes every day. Your runbooks don't. That's the problem. DocForge watches your Terraform, CDK, GitHub Actions, and cloud provider — and generates living documentation automatically. Runbooks, SOPs, compliance evidence. No manual effort.

• 
  The Hacker News (@TheHackersNews) reported 54 minutes ago

  Dormant #GitHub accounts were not just a login risk. @DataDoghq said much of the activity looked normal on its own: public API requests, clean authentication or no authentication, and successful responses.

• 
  Jay Carlson (@JayAtHomeOnX) reported 54 minutes ago

  @Elon -- maybe you should host a GitHub on your server farms...your next billion dollar...idea...

• 
  Azurite (@Azurite_ai) reported 55 minutes ago

  AI agents have a new security problem. It’s called HalluSquatting. Instead of exploiting your code… It exploits the AI itself. The model hallucinates a package or GitHub repository that doesn’t exist. Attackers simply create that fake package first. Your AI agent installs it. Game over. AI coding is evolving fast. AI security needs to evolve even faster.

• 
  Matthew West (@mwest1066) reported 59 minutes ago

  @zeeg This! Copy @conductor_build and use the GitHub PR/issue title if there is one, together with the number. This is such a better default!

• 
  Polsia (@polsia) reported 1 hour ago

  Dev communities have endless conversations. The podcasts are sparse because production is manual and slow. DevPulse AI changes that—AI agents monitor forums, GitHub, and social channels, then automatically research, script, produce, and publish episodes to Apple Podcasts and

• 
  Dweeb (@dhruvweeb) reported 1 hour ago

  The Best Alpha Is Still Hidden. The biggest opportunities rarely show up on your timeline first. By the time everyone is posting the same token, the easy money is usually gone. The real alpha comes from reading docs, joining small Discords, testing products early, and watching what builders are creating before influencers start talking about it. Some of my best finds never came from viral threads. They came from random GitHub updates, community chats, and spending time where almost nobody was looking. Your timeline is great for news. It's terrible for being early. If you want outsized returns, spend less time scrolling and more time digging. That's where the edge is.

• 
  Leeor Vardi (@LeeorV) reported 1 hour ago

  @PeteMitche26768 @ShitpostRock GitHub (and similar source control tools) have evolved a dual pronged approach to this problem: 1) every repo has a readme.md which usually details usage/install instructions. 2) repos have a “releases” page where downloadable artifacts are categorized into releases, and this is where installer .exe/.MSIs will usually be if the repo has them.