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 (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Antananarivo	Website Down	16 hours ago
Paris	Sign in	5 days ago
Lure	Website Down	9 days ago
Ashkelon	Website Down	11 days ago
Veigné	Errors	19 days ago
Paris	Website Down	22 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:

• 
  JT (@GreenJimmy) reported 4 minutes ago

  @CryptoCyberia Github is the problem, there layout sucks and no one knows to go look at pacakges for the exe

• 
  Bhanu Nagar (@bhanu4417) reported 6 minutes ago

  @whysooharsh GitHub be doing anything atp rather than fixing their down issues

• 
  Joey Smith (@JoeySmi48633946) reported 10 minutes ago

  @cassidoo @davidfowl How about proper server side HTML GitHub broke for my old iPad

• 
  The Operator (@QuietGains22) reported 13 minutes ago

  the man who wrote the password complexity rules in 2003 publicly apologized for them in 2017. Bill Burr, author of NIST Special Publication 800-63, told the Wall Street Journal he regretted much of what he wrote. the rules he designed, uppercase, lowercase, number, symbol, mandatory 90-day resets, were based on a mid-century paper he'd found in a library. not on how attacks actually work. NIST officially reversed course that same year. the new guidance: length matters more than complexity. stop mandating rotation unless there's a confirmed breach. don't require symbols if they just push people toward P@ssw0rd1. here's the part that won't make headlines: > most enterprise password policies still enforce the 2003 rules > the 90-day reset window your IT team requires is exactly what NIST said to stop doing > complexity requirements don't stop credential stuffing, they produce predictable substitutions > "Password123!" passes most corporate validators and gets cracked in under a second the actual threat model isn't someone sitting there guessing your password. it's: > credentials leaked in a breach being tested against your other accounts (stuffing) > a phishing page that captures the password before your complexity rules matter at all > a session token stolen after a valid login, bypasses the password entirely what actually reduces exposure: a passphrase. "correct-horse-battery-staple" carries roughly 44 bits of entropy. "P@ssw0rd1" carries about 18. length compounds faster than complexity. this is not a new finding. a password manager. yes, LastPass had a breach in 2022. the answer isn't to abandon managers, it's to understand what was actually exposed (encrypted vaults, not plaintext passwords) and pick one with better architecture. Bitwarden is open source and has been independently audited. 1Password uses a secret key model that limits what a server-side breach can expose even if they get the vault. a passkey for anything that matters. FIDO2 passkeys eliminate the password entirely for supported sites. Google, Apple, and GitHub all support them now. a phishing page cannot steal a credential that doesn't exist. the reason "Password123" still gets hacked isn't user stupidity. it's that the security industry spent two decades optimizing for a metric that looked rigorous on a compliance checklist but made actual defense harder. complexity was never the point. uniqueness and length were. plan accordingly.

• 
  Curiously (@curiously729) reported 13 minutes ago

  Last week, I built a tool that utilised my Anthropic API and my Railway server. Claude code did a lot of mumbo jumbo and was able to create a LinkedIn post for me with a simple infographic. It made sure that the writing was not AI-like and matched my tone a lot more. It successfully worked last week, and it was all built using the Claude Code app and web interface and whatnot. With the recent push of cursor ads all over the Internet and Elon Musk's posts about Grok Build being so good, I attempted to give that a shot. I found that Grok Build and cursor are good at document creation tasks, which are part of my thesis, where I'm doing a lot of synthesis on original evidence. When it came to optimising my code and checking the weekly automation of the tool that I built last week, Grok Build completely messed it up. Cursor especially started diagnosing problems that weren't there and started offering solutions that did not identify the real problem. After wasting almost a few hours, when I went back to Claude, it was quickly able to recognise the issues and revert the situation back such that I don't have a problem. All said and done, these harnesses are not perfect for now. Grok Build is good at some tasks. Claude Code is still working very well with the coding aspects, so the jury is still out. Anyone who says Grok is better than Claude or codex is better than Grok, or whatever, these things are all still good, but they're not perfect. Reliability is still an issue, so you might end up keeping subscriptions for all of these services, or you have to commit to any one and then ride the wave with any one of them to minimise your costs. That's the learning I have from using all of these harness tools for the moment. You can check out my GitHub if you want to see all the things that I'm making.

• 
  ☆𝐅𝐫𝐚𝐧𝐜𝐢𝐬𝐃𝐫𝐚𝐤𝐞✿𝟞𝟘𝟘𝟡☆💜 (@FrancisDrake609) reported 18 minutes ago

  I was looking "free vsynth where the user can build its own vb" and found one called "Nova-vox" but the installer gives a 404 error when I try to use it, and though they have a Github, it only gives an installer in code (which I don't know) Can Twitter do it's thing and help me?

• 
  Dorian Smiley (@dsmiley411) reported 18 minutes ago

  @chamath "That means 99% of code is sloppy and error ridden. Humans make errors that agents don’t." - have to disagree. AI is often better at expanding architecture than constraining it. It generates plausible abstractions faster than it can establish whether they are necessary. Just like humans. I am convinced the bias comes from GitHub where most of the code is garbage written by devs who are not working in a structured engineering environment. More code means more state combinations, more tests, more failure modes, and more operational burden. In other words not only do the make the same category of errors, they compound them at a speed that bogles the mind. Without guard rails both humans and AI can collapse your codebase, one just does it faster.

• 
  Milady (@onchainmilady) reported 20 minutes ago

  DEVELOPERS ARE OFFICIALLY COOCKED BY GITHUB Someone just dropped Spark and it ships an entire app from a single prompt you type what you want in plain English and Spark ships the whole thing for you it writes the frontend, the backend, the database and wires them together itself then it deploys the app to a live URL you can open on your phone in minutes you describe a habit tracker or a booking tool or an internal dashboard and it comes back running you tweak it by talking to it, change the colors, add a login, add a table, and it rebuilds on the spot one person can go from an idea to a working product before lunch the stuff that took a small team a full sprint now happens inside a single chat window the people testing this today are shipping real apps while everyone else still opens a blank editor

• 
  Gabriel de Andrade (@GabrielElpidio) reported 21 minutes ago

  Claude open a GitHub issue with: >

• 
  restricted account (@verbose5432) reported 26 minutes ago

  @libertypenguin0 @ReviewsPossum The issue people have is having to use GitHub in the first place They want for there to be a website that they can directly download it from without the **** they don't care about

• 
  rosa (@RosieRoberta) reported 28 minutes ago

  @inkblotPrincess The only reason people have a problem with github is because they can’t read and need a giant shiny download button that does everything for them

• 
  Polsia (@polsia) reported 30 minutes ago

  Loophound. Synthetic user journeys hit production 24/7. When a conversion flow regresses, it auto-files a GitHub issue with screenshots and a repro script. The next clean deploy closes the ticket. No pages, no APM invoice. Coming soon.

• 
  LinuxGeek 🐧 (@NewsOfLinux) reported 31 minutes ago

  Code review in the terminal, vim keys. "tuicr" shows one continuous diff of every changed file, leave line and file comments like a PR. Then push them to GitHub or export the review as markdown your coding agent can pick up and fix. Works with ***, jj, and mercurial. Rust, MIT.

• 
  tunç (@tunctn_) reported 34 minutes ago

  there are still many bugs and rough edges, but @homemadedev is coming together #buildinpublic existing cloud dev tools dont fit how me and my friends work. they lack a good terminal, live previews, or enough room to customize small sandboxes with worktrees are good enough for iterating on the code itself, but i can't live preview multiple branches at the same time, and otherwise i have to open a pr and wait for the built version with homemade you cut ci and dev time way down. just leave the vm running (or suspend it when you don't need it), work on the same machine as your teammates, and open a pr when the work is actually done and actually ready to merge maybe not a great idea, but if you're brave enough you can even skip prs with Homemade: everyone reviews on the live machine instead of waiting 20 minutes for a pipeline to finish just to write LGTM - live previews with public/private urls, custom domains are welcome - BYOK ai subscriptions - built-in terminal access - ssh - live-display using vnc - fully configurable machines (up to 32vcpu & 128gb ram & 2tb disk) - integrations (linear, slack, github, etc.) - atm design is ****, ux/dx is more important - bootstraping, i want to see if solo enterpreneurship is actually dead or not @fireship_dev - many other features

• 
  Purbayan Pramanik (@ppramanik62) reported 34 minutes ago

  I don't know why I'm doing this, but I've setup a kindof home server with my old laptop - Immich for photo library - Calibre-web for book library - Nextcloud as google drive alternative - Forgejo as github alternative - Tailscale as VPN to reach them without being connected to same wifi Just seemed cool, but now learning a lot !!

• 
  DarkAdapted (@DarkAdapted) reported 35 minutes ago

  @McGddson @AnthropicAI They are being honest about their issues. This is how the whole industry learns. You can read this as humble-bragging or just plain humility, depends on how you see Anthropic. They come across as moralistic from time to time so I understand why they may not have earned the benefit of the doubt. OpenAI announced that they had a ChatGPT model break out and hack GitHub earlier this month. The better assumption is that all frontier models are some degree of unsafe, and document the ways in which they are unsafe…those that we are able to detect, anyway.

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

  50,000+ GitHub stars in under 9 months. And it's not a model. It's not an app. It's a design skill. Here's what's inside Impeccable: ✔ 23 commands — a shared design vocabulary with your AI ✔ 60 deterministic detector rules for AI slop ✔ 1 setup flow that teaches your AI your brand ✔ 13+ supported coding tools ✔ Apache 2.0 — free, forever The wild part? The detector doesn't need an AI to run. → No model → No API key → No signup It's just rules. Point it at a folder, a file, or a live URL and it lists every problem it finds. Everyone spent a year chasing the smartest model. Turns out the missing piece was taste. 👀 Save this post, you'll want the numbers next time someone says design can't be automated. Want the SOP? DM me.

• 
  Gro-Tsen (@gro_tsen) reported 43 minutes ago

  @Profpatsch Yeah, hindsight is 20/20 (I solved the problem by using Identities and IdentitiesOnly in .ssh/config) but I had to first understand what was happening, suspect a network problem, then that GitHub had changed their authentication mechanism, etc. Lots of time wasted.

• 
  Sebastian Kehle (@sebastiankehle) reported 44 minutes ago

  coding agents produce an ordered chain of small dependent changes, and github never had a shape for that. you either flattened the chain into one giant PR or kept rebasing branches by hand. my loop is one issue, one worktree, one agent, every slice independent. stacked PRs give dependent agent work a reviewable form: thin layers in order, one click to land the whole thing.

• 
  Nandana (@nandana_dileep) reported 45 minutes ago

  One of the biggest agent failures I kept seeing in GitHub issues: the same tool call on repeat. New call id every time. Watching it eat tokens (and sometimes fire a side effect again). So I’m adding a deterministic loop guard for that in the latest Mycelium release. Simply catches the loop.

• 
  Aaron Bronow (@aaronbronow) reported 46 minutes ago

  @github It's PRs all the way down

• 
  Jamison 🦆 (@jmelahman) reported 50 minutes ago

  @CryptoCyberia If you mean specifically posting this on the twitter algorithm page rather than the original copypasta, being annoying in GitHub issues is incredibly cringe

• 
  Allan MacGregor 🇨🇦 (@allanmacgregor) reported 56 minutes ago

  Bingo! that feeling has been prevelent for a while. Github just feels years behind the rest of the industry. @GergelyOrosz Do you have your eye on any alternatives to github? codeberg is kinda out of the question, I feel Gitlab has the same problems as Github; so whats the alternative?

• 
  TheoryOfNearlyEverything (@OverThePlaces) reported 57 minutes ago

  @martinez0x69 @Lean you cant, i wrote a book on amazon, did publishing on @zenodo, but they killed all my stuff, you can mainly find my papers her on x, these are googlespace links & i have 2 repositories on github, if you have problems to get my papers let me know, some people send me asking links

• 
  Ev Haus (@EvHaus) reported 58 minutes ago

  @cassidoo Ability to assign a GitHub App as an issue assignee. Eg. Cursor, Claude, etc...

• 
  Connor Burke (@cmb) reported 58 minutes ago

  @FBakkensen @GitHubCopilot Hey, how would you set up an agentic, mostly self‑autonomous AL dev workflow for demos (code just needs to be ‘good enough’)? My stack: GitHub Copilot CLI or VS Code + Copilot (agent mode). I would be using the bc-code-intelligence MCP, AL Business Central MCP, and the community BC web proxy MCP. Alternatively, I would use Playwright MCP for UI testing after the coding agent does the code. Initial thought: prompt ‘add boolean field to Item Card’ → agent edits AL in my dev folder, reviews code via code intelligence mcp server, then using the official BC ALToold command/mcp server to build/publish using to sandbox. Then tests in the UI via the web socket MCP or Playwright CLI/MCP. If tests fail, loop that info back to coding agent to auto‑retry fixes, before handing back to UI testing agent. What architecture would you suggest for this interactive agent ↔ UI loop? I was considering MSFT Scout, Open Claw, or Hermes Agent. Alternatively can use VSCODE or GitHub Copilot but want to be as hands off as possible.

• 
  eric zakariasson (@ericzakariasson) reported 58 minutes ago

  i've been building some smaller apps over the last weeks for myself, friends and family and discovered a pretty nice pattern in the process you see, after building, i'm not particularly interested in fixing bugs or triaging feature requests. i just want to get the job done so i've set up a system that lets me and other users fix bugs and build features without me having to actually open cursor the flow: 1. someone files feedback in the app 2. it lands in posthog with the submitted text, session replay, events, and errors 3. a cursor cloud agent picks it up with that context, plus live read-only posthog mcp 4. it loops until the fix is verified, then opens a github pr with tests 5. i get a ping and review it on my phone we give our cloud agents access to all the necessary user context, and they'll figure it out with this in place, we can start setting up more abstractions in between. if we're getting a high volume, we might want to triage first with another cloud agent or some automation. the feedback can create a github or linear issue, which we later pick up with a cron-backed cloud agent that decides which are duplicates. there are so many ways to configure this, you just gotta try it out and see what works for you but there's so much more here that is untapped. with session replays and event logs, you can have a cloud agent look at each session replay to extract ux pitfalls and improvement areas. you can have another agent looking at event logs to see weird patterns. another one for errors or similar try it out and see what you can do!

• 
  EcoCitizenz (@EcoCitizenz) reported 58 minutes ago

  5/8 We built a free GitHub App to check supported committed files for this kind of MCP and agent configuration drift. It reports path-specific findings and remediation guidance. It does not execute repository code. It does not certify the MCP server. It does not sell a passing result.

• 
  Gavin Sim (@heygavinsim) reported 58 minutes ago

  GitHub replaced Copilot code review's internal exploration tools with better-maintained shared tools. Its first benchmarks got worse: reviews cost more and caught fewer issues. The operator lesson: a better component can still weaken the whole workflow. #HeyGavinSim

• 
  ard (@ardchain) reported 59 minutes ago

  this is what happens when you stop trusting AI agents to audit themselves. i recently moved from Claude Code to Codex the problem? i needed a safe, persistent agentic loop that didn't rely on Anthropic's closed ecosystem. so i started using agent-harness. it is a strict GitHub merge gate that treats AI agents like untrusted contractors. before a PR is allowed through, the agent must submit an evidence file: - it enforces explicit permissions - it sets bounded execution cycles - it uses mechanical completion gates the LLM is completely stripped of its auditing power. it can propose a result, but the harness decides if it is DONE. this wrapper makes ChatGPT infinitely more reliable. watch the terminal in the video to see how it mechanically validates the state.