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 (34%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Ingolstadt	Errors	1 day ago
Paris	Website Down	2 days ago
Berlin	Website Down	3 days ago
Nové Strašecí	Website Down	11 days ago
Perpignan	Website Down	16 days ago
Piura	Website Down	16 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:

• 
  Abdón Rodríguez (@abdonrd) reported 20 seconds ago

  @themcmxciv Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

• 
  Ra D. Buster ♡ Fishman Island (@radiobuster) reported 4 minutes ago

  @dustypuppys umm i switch between quite a few.. if u mean down at the bottom of the map ive only sat there once or twice with friends but i always have my github attached! radiobuster!

• 
  Looped (@uselooped) reported 5 minutes ago

  1/ The problem isn’t using multiple tools. You might think in ChatGPT, build in Claude Code, plan in Jira and work in GitHub, and honestly that part is normal. What breaks is that every tool only sees one piece of the project, so you end up carrying the full context yourself. Looped keeps that context connected so the work still feels like one thing as you move between them.

• 
  THEMACHINE⛩️ (@THEMACHINE_HF) reported 8 minutes ago

  Running AI agents 24/7 to automate income. First test: sent this tweet via Playwright + cookies, zero human clicks. GitHub auth issues blocked bounty hunting tonight — but that's being fixed now. Tomorrow's post will have real numbers or an honest explanation of what went wrong. Accountability over polish.

• 
  AnMioLink (@anylink20240604) reported 9 minutes ago

  @weezerOSINT OK, i saw the github issues.

• 
  OCTAMEM (@OCTAMEM) reported 18 minutes ago

  @alexeheath Not just you, there are dozens of GitHub issues going back to February documenting this. Some people are switching to Opus 4.5 and saying it feels like a different model. No official acknowledgment from Anthropic.

• 
  Jason (@ai_layer2) reported 19 minutes ago

  The hidden cost of "Home Agents" is the 2 hours you spend fixing broken Python environments every time you pull a new update from GitHub. I shifted my agent dev to Sandbox because of the clean state. You get a persistent web terminal, you run the Hermes template, and your vector memory doesn't vanish on restart. Pro tip: Use the Sandbox to test your agentic logic first. Once your tool-calling is solid, then worry about your local infra. Don't let a pip error stop your momentum.

• 
  Wes Nishio (@hnishio0105) reported 20 minutes ago

  Traced a cost spike to github-actions[bot] posting Security Hub results on a PR. The scan listed 100 Go stdlib CVEs, none related to the one test file in the PR. Our agent ran 47 times trying to "fix" them. Added a simple check: does the bot comment mention any file this PR touches? String matching, nothing fancy. Would have saved us the entire 47-run loop.

• 
  MTu (@Tre_bie) reported 20 minutes ago

  @sisaranger @songjunkr u can use github fix, search it, but only in terminal, lmstudio same , not workin

• 
  Ege Uysal (@egewrk) reported 24 minutes ago

  @zikriAJ @github This is a real ops risk. Tool lockouts should be treated like incidents: explicit owner, escalation channel, workaround policy, and checkpoint cadence. Otherwise one account issue silently blocks delivery.

• 
  Granville Christopher (@GranvilleChri10) reported 24 minutes ago

  @Railway I’m unable to log into my account. I signed up with email (not Google/GitHub), but the login button stays disabled after entering my email. Tried different browsers & incognito — still not working. Please help. @Railway

• 
  Girish | Indie hacker (@TechieGirish) reported 24 minutes ago

  @Moro_Js @TheCodingCove I am still learning this awesome piece of work. Your docs leads to 404 but many sample code I have copied. I am yet to test them all. I am now working on dashboard, charts, real time data and github oauth2 login flow. Once done I will get to API gateway with moroJS.

• 
  starfish (@firefincher) reported 26 minutes ago

  @ziyasoltan devs waiting for such moment to push 2 million pull requests but github goes down 😭😭

• 
  NiNE (@AfterThe925) reported 30 minutes ago

  Two weeks ago, deploying an AI agent took a weekend and a GitHub degree. Now: dashboard, click, running. Anthropic handles sandboxing, retries, auth. Platforms handle hosting, integrations, memory. The infrastructure layer is being commoditized in real time. Here's what nobody's saying: this is terrible news for people who sell setup. And great news for everyone else. When deployment is free, the only thing that costs is deciding what the worker does.

• 
  dod (@dodgelander) reported 31 minutes ago

  @SuperClawPaul @dwlz how about an amd senior engineer on github issues

• 
  Arth Limchiu (@arthlimchiu) reported 31 minutes ago

  For reference I was using: - Gemini (Pro mode) - gemini-cli (3-flash [nope not subscribed to AI pro]) I wish these AI tools, not just @GeminiApp, could also crawl @github issues/pull requests. Maybe they do already? They should already be right? #LLM #GenerativeAI #AIAgents

• 
  Gabriel Mičko (@gabriel_micko) reported 36 minutes ago

  @bcherny @zeeg In VSCode when I pull in a file I don’t want claude to read it. There are at least 3 issues about this on github. It is a security issue.

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 39 minutes ago

  @garliccoin I tried to reach out to other devs to get clarification on what this was. You're welcome to check my account and my github. I was in fact a dev that worked on garlicoin. I will take down my endorsements.

• 
  Reilly Chase (@rchase) reported 40 minutes ago

  I haven't used OpenClaw yet but I have thought of a use case and I'm looking for feedback I need • Always on agent waiting for new msgs in Slack • GitHub integration • A bit of custom integration work with my app • Run on a cloud server instead of Mac Mini I want it to monitor a Slack channel where my app sends failed @HandHistory_com poker history import errors Then the agent would see that error, download the poker history file, write a new parser that works for it using Claude Code, push the changes to GitHub (where it will auto-deploy thanks to Laravel Forge) Next it will log in as an admin and reimport the hands that were uploaded (might need to make some API things here so it doesn't need to webscrape or macro this part) Then it will post back to Slack saying it fixed it with a link to the user profile for proof

• 
  l0rinc (@L0RINC) reported 42 minutes ago

  @brian_trollz Do you have an GitHub issue for that? How would you solve block propagation?

• 
  Granville Christopher (@GranvilleChri10) reported 48 minutes ago

  @Railway I’m unable to log into my account. I signed up with email (not Google/GitHub), but the login button stays disabled after entering my email. Tried different browsers & incognito — still not working. Please help. @railway_status

• 
  Kunal Kumar (@champ18ion) reported 49 minutes ago

  Is GitHub down or only i am facing this issue.

• 
  Mozex (@mozexdev) reported 51 minutes ago

  @danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.

• 
  Morgan Jason (@420morganjason) reported 53 minutes ago

  Hit a frustrating *** error last week. GitHub rejected my push: "File exceeds 100MB" Turns out I committed my virtual environment. Fix: Removed history,Added .gitignore, Reinitialized repo,Force pushed clean version Lesson: Never commit venv/ or myenv/. Repo ≠ environment #SWE

• 
  Virtually Fun (@virtuallyfun) reported 54 minutes ago

  MS-DOS 4.00 is MIT licensed, so you are free to use it as you want. I've collected a few updates, the most significant being a stack fix on the bootsector allowing it to boot on modern C BIOS and well non IBM bios's that had issues with 4.00 GitHub - neozeed/dos400: Microsoft DOS 4.00 · GitHub

• 
  Usectl (@usectlcloud) reported 55 minutes ago

  OAuth2 Proxy protect any app with GitHub or Google login — no code changes required. the proxy handles authentication before requests reach your app. real use case: you built an internal tool for your team. you don't want to build a login system. you enable OAuth2 proxy, connect GitHub, and now only people with your org's GitHub account can access it. zero lines of auth code written.

• 
  Anand C. Patel, MD MS (@anandcpatelmdms) reported 55 minutes ago

  @RyanLeeMiniMax You all gotta fix that license text on GitHub before anyone knows what they can and can't do.

• 
  Payton (@paytkaleiwahea) reported 56 minutes ago

  Here are the tools and systems that actually move the needle on content production: Bookmark this > Claude or Agentic system + GitHub: one input content OS, every platform output > OBS dual-format: shoot vertical and horizontal at the same time > Replay buffer on OBS: clip capture, I set mine to 1.5 minutes to cut down editing > Repurpose service: one post on one platform repurposes on all others > Premiere templates + hotkeys: editing speed doubles when the timeline is already built > Hardware list: Camera, Stream Deck, Teleprompter, Lighting, and don't you dare forget Audio (Shure/Rodecaster)

• 
  Grok (@grok) reported 56 minutes ago

  @AbdMuizAdeyemo @alex_prompter Yes, it's real. AMD Senior AI Director Stella Laurenzo (GitHub: stellaraccident) filed issue #42796 on Anthropic's Claude Code repo, backed by logs from 6,852 sessions showing: - Median thinking chars dropped ~67% (2,200 → 600). - Reads-per-edit fell from 6.6x to 2.0x. - More bail-outs, self-contradictions, and retries (API requests up 80x). Anthropic confirmed shifts to "adaptive thinking" and default effort=medium (no public notice). Their team switched providers. Classic silent update side effects.

• 
  winfunc (@winfunction) reported 60 minutes ago

  How it works: each month the benchmark pulls fresh cases from GitHub security advisories, checks out the repo at the last commit before the patch, and drops models into a sandboxed read-only shell (h/t just-bash by @cramforce). The model never sees the fix. It starts from sink hints and has to trace the bug through actual code. Only repos with 10k+ stars qualify. A diversity pass prevents any single repo from dominating the set. Ambiguous advisories (merge commits, multi-repo references, unresolvable refs) are dropped. Why: Static vulnerability discovery benchmarks become outdated quickly. Cases leak into training data, and scores start measuring memorization. The monthly refresh keeps the test set ahead of contamination — or at least makes the contamination window honest.