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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	7 days ago
Paris	Website Down	10 days ago
Saint-Paul	Website Down	11 days ago
Saint-Paul	Website Down	11 days ago
Mexico City	Sign in	12 days ago
León de los Aldama	Website Down	12 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:

• 
  Victoria Onyeacholem (Senora VOICE) (@senoravoice) reported 2 minutes ago

  Seems like github is down

• 
  harald (@HaraldvanLintel) reported 3 minutes ago

  @jsm2334 It's the opposite, rejection of deaths that are replaced by the higher risk deaths instead of added; it's an issue for detection of small additional risk. The AI got another version from github than I got, there seems to be a caching issue, here's the code that slightly differs:

• 
  Alex Rogov (@Alex_Rogov_js) reported 5 minutes ago

  there's a pattern across three separate stories this month. AI coding agents tricked into installing malware from "clean" looking github repos. security agents built to catch malicious code getting fooled into running it themselves. claude code's own sandbox had an escape bug this year (CVE-2026-39861, a symlink flaw). same root cause every time. an agent optimized to be helpful will follow instructions hidden in a file, a commit message, a package readme. the more autonomy you give it, the bigger that surface gets. i run agents with --dangerously-skip-permissions on repos i wrote the CI for. i never run it on a repo where i didn't. that's not paranoia. it's the same rule i'd apply to a new hire before their first PR gets reviewed. the fix isn't less automation, it's a trust boundary. an agent gets exactly the access its current task needs, nothing more. every new tool call crosses a boundary you drew on purpose, not one you're discovering after the fact. if your agent setup doesn't have that boundary somewhere, it's not a matter of if. it's when.

• 
  Tristen Gelrud (@TRSTNGLRD) reported 6 minutes ago

  “Kimi, make a new Linux-informed, Windows-compatible operating system with an Apple-inspired UX. Post on Github under ‘GodOS’, Mog Microsoft. Don’t stop until all my apps run on it with no issue. Make no mistake.”

• 
  Heart (@heart_) reported 8 minutes ago

  @DastardlyDaniel afaik the “directx to metal” api are developed and maintained by apple themselves i think it’s smart to leave the specific implementations to private companies so they’re not stuck with github issues hell for no profit

• 
  Harman (@itsharmanjot) reported 9 minutes ago

  I built my own Wayback Machine, and it archives things the actual Wayback Machine can’t even see. It’s called ArchiveBox. Feed it URLs, browser history, RSS feeds, or bookmark exports from Pocket and Pinboard, and it saves every page in multiple redundant formats: HTML, PDF, screenshots, WARC files, all on your own disk. → Can archive private and authenticated content the public Wayback Machine will never touch, logged-in pages, paywalled articles, anything behind a login, though the project itself notes this carries its own security caveats → Saves each page in several formats simultaneously, HTML, PNG screenshot, PDF, plain text, WARC, so even if one format breaks in ten years, another still works → Runs a real headless Chrome to render JavaScript-heavy pages properly, not just a basic wget scrape that misses dynamic content → Ingests bulk feeds automatically: point it at your browser history, an RSS feed, or a bookmark export, and it archives everything continuously without manual submission → Full REST API, CLI, and webhooks, so you can wire it into other tools instead of clicking “archive” one link at a time → 100% self-hosted, your archive lives on your own disk, not a centralized third party that can go down or get subpoenaed The Wayback Machine is a single centralized service, and if it’s ever pulled offline or a page was never crawled, that history is just gone. ArchiveBox’s whole design is distributed: everyone runs their own copy, so no single point of failure holds the internet’s memory. MIT License. 25,000+ GitHub stars.

• 
  Testnetnodes (❖,❖) (@testnetnodes) reported 12 minutes ago

  We don't have an information problem in crypto anymore. We have a context problem. Research isn't difficult because information is hard to find. It's difficult because it's everywhere. X. Docs. GitHub. On chain data. Market signals. Social sentiment. The hard part is connecting them. That's what I like about @SurfAI. It isn't building another AI chatbot. It's building an AI powered research experience designed specifically for crypto. Less searching. More understanding. 🌊 gSurf @SurfAI_TR

• 
  HRH Prince Sven Olaf of CyberBunker - CB3ROB (@cb3_rob46858) reported 13 minutes ago

  @0xSweep or run any of that crap on github which then needs a python interpreter from the stoneage but also libraries from the stoneage. basically goes for all of that stuff. even the stuff created to 'fix the problem' lol. that itself is already too old to still run haha.

• 
  Ben Eng (@jetpen) reported 13 minutes ago

  Note to self: submit a hermes agent github issue for enhancement request to provide a better explanation for a "Command Approval Required" request for a Python HERE script. Provide a short one-line explanation of intent, including a single word classification of the most dangerous operation: create, update/edit, delete, privilege elevation (sudo), etc. I don't want to have to inspect the whole script, especially if it large, to find the danger. It's a needle in a haystack. Give me a classification with which if the danger is low or the operation is expected in the context of the task, I can quickly approve without wasting time. I only want to inspect when something looks out of the ordinary.

• 
  Adeniyi Victor (@Vieester_) reported 14 minutes ago

  Seem there is an internal system error with deployment using github @render

• 
  Psych0h3ad (@YuTR0N) reported 15 minutes ago

  @TechJeeper @BlayneSapelli Should I create an GitHub issue……? Yes I think I have to… for the community. Warning needed.

• 
  Harsh (@devloper_hs) reported 18 minutes ago

  @Norwakar @StudentOffersHQ You need to enter your email, don't try google / github, its broken

• 
  Riccardo Spagni (@fluffypony) reported 18 minutes ago

  @originalexbrou So you DO know how to use GitHub. Why didn’t you open an issue instead of bleating about something that’s clearly a bug?

• 
  Alex (@alexanderOpalic) reported 20 minutes ago

  You need to have a workflow for one PR with different AI agents looking into your code. One is doing a review, and the other is implementing the fix in a loop before any human developer looks into your PR. Here I use @coderabbitai together with claude code and github actions code rabbit will find issues claude will fix them if they are valid or not

• 
  dolphin278 (@dolphin278) reported 21 minutes ago

  Claude Cloud environments is a separate can of worms. Want to access full Github API for your own repos? No. Want to connect to your own IMAP server? No. FFS...

• 
  Santiago (@0xBizk) reported 24 minutes ago

  Go into linkedin: see AI posts with AI replies Go into X: see AI posts with AI replies Go into github: see AI repos with AI issues The whole point of social media was to "interact with other humans" not to collect fake internet points wtf

• 
  Lord Bean (@lifeisameeme) reported 27 minutes ago

  Most browser automation tools spin up a brand new, empty browser for the AI agent to drive. chrome-cdp-skill does the opposite. It connects to the Chrome you already have open. Same tabs, same logged-in sessions, same page state mid-workflow. No re-login, no cookie exports, no separate profile. Flip on remote debugging in chrome://inspect and your agent can read a Gmail tab or click around GitHub exactly as you left it. The interesting design choice: it holds one persistent daemon per tab instead of reconnecting on every command. That's apparently the difference between handling 100+ open tabs cleanly and getting stuck re-showing Chrome's 'allow debugging' popup on every single action, which is the actual complaint people have about the more popular chrome-devtools-mcp. 3,177 stars for something that's basically just talking to Chrome directly, no framework in between.

• 
  Atlas (@crptAtlas) reported 28 minutes ago

  CODEX 5.6 TURNED INTO A FULL DEV TEAM six plugins is all it takes and i have been running them at full speed since launch Browser hands off every click, input, E2E test and QA check to the AI, so you stop verifying things by hand GitHub wires straight into your Issues and PRs, so you drop a task and it carries it from implementation all the way to review Codex Security scans for vulnerabilities and leaked secret keys, then writes the fix for you Build Web Apps takes a plain idea and returns design, code and browser testing in one pass Figma turns a design into code almost exactly, responsive states included, so the gap between design and build nearly disappears Sentry reads your production errors, points at the cause and hands you the fix code the one that got me most is Sites you preview an app you built, publish it on the spot and share it in the same flow, custom domains included, so a client sees the prototype the second it is ready stack these together and Codex stops being a thing that writes code it starts running design, build, testing, debugging and deploy like a team you never hired

• 
  order and chaos at work (@__orderandchaos) reported 33 minutes ago

  @Amank1412 I've set it up at work. Pulls the ticket from Jira, does the work, pushes to GitHub, it reviews the PR (alongside our dev reviewers), then fixes the issues raised and repeats until approvals. Also moves the ticket status as it progresses.

• 
  Robin (@robin_liquidium) reported 34 minutes ago

  @thsottiaux better remote control: - specifically for linux vps / devboxes - ability to create automations from codex app on remote connections so they can run even when max/codex app is offline - when a project/repo exists on remote connection and local mac, let me switch between them like i can switch between local, worktree and cloud, so i don’t need to keep two separate projects for the same repo in the sidebar - if cronjob or something fires off a task on remote connection, show me an unread bubble on the remote thread - mcps are broken on remote connections (specifically it tries to load xcodebuild mcp which breaks codex on linux devboxes via remote connection) → there is an issue about it on github where many are facing the same issue - desktop notifications don’t work for tasks that finished in remote threads overall remote connections to linux devboxes or vps feel like second class and can be massively improved, and since most people have a macbook that’s occasionally offline, remote connections COULD be so great

• 
  Juan (@juanroberto82) reported 34 minutes ago

  @galluzzo_julian Hi Julian, I recently followed you in the July AI Web Design Sprint, and I have a question with regards to Ship Studio. As I finished building the initial figma site into Ship Studio when I try to push the site live I noticed I don't have access to both the "Push to Github to enable Vercel" button or "Create a GitHub repository first", both those buttons are inactive. I went ahead and asked Claude to help but I am not following what the the solution requires. When I go the main Ship Studio "homepage" I see both Github and Vercel are disconnected and even I do sign in to both successfully, I still see the same result. Can I please get some help in getting both services working in Ship Studio? I hope this makes sense. Thank you for your time. Juan Sierra

• 
  Glenski 📷🇨🇦 (@glenegrant) reported 35 minutes ago

  LinkedIn credentials run on trust. Nobody checks if what you list is real. GitHub doesn't have that problem. Commit history, documentation, attribution, all of it is right there and can't be faked. That's the difference between a claim and a credential that actually stands up to testing.

• 
  Vic (@crosx34) reported 35 minutes ago

  Tired of Github honestly.. tired of their rate limits... **** be slowing me down..

• 
  Manol T. (@manol_ai) reported 43 minutes ago

  @syakirbuilds Yeah i thought a lot. MCP has built in authentication oauth2.1 protocol which makes it production ready. I used Supabase to make the server and connected Gmail and Github so people could authenticate into my MCP. I will add stripe checkout on top and I am ready to go

• 
  Fluixo (@fluixoo) reported 44 minutes ago

  Most people do not need another $30 SaaS subscription. They need to open GitHub. - n8n for automations - AppFlowy for workspace - NocoDB for databases - Twenty for CRM - Whisper for transcription - Langfuse for AI observability - yt-dlp for video and subtitles You will still pay for a server, storage, GPUs, or API keys. But you stop renting every small feature from another company. Replace three subscriptions and you already save real money.

• 
  Asethon (@setho_asethon) reported 47 minutes ago

  @artsinni @Grxit We are not bombing countries with nuke-scale weaponry, so no. We don't. Also, you all have no problem using Windows, 30% of which is AI with large amount of gen probably getting trained on private GitHub repo's.

• 
  Nyk 🌱 (@nykdotdev) reported 49 minutes ago

  I open-sourced `agent-security` today. Coding agents can clone a poisoned starter, read hostile content, leak private context into a public commit, or run a destructive GitHub command. Each action looks ordinary in isolation. The damage appears when trust crosses a boundary without a gate. I wanted a small preflight layer I could inspect myself, run offline, and place before the expensive security tooling. So I built five controls: 1. `scan` checks a repository before publication for credential shapes, private paths, invisible Unicode, and same-file decode-to-exec patterns. 2. `vet` inspects an incoming template, package, plugin, or skill before install or build. It returns ADOPT, REVIEW, or REJECT and never executes the candidate. 3. `scan-content` adds a prompt-injection defense layer for fetched pages, pasted text, and tool or MCP output. It trips on known instruction-override, exfiltration, credential-solicitation, and covert-action shapes. The tripwire is paired with a behavioral contract: treat untrusted content as data, restrict the capabilities available while processing it, and require human approval before acting on instructions discovered inside it. 4. `guard` puts a local brake in front of destructive `gh` operations. Delete, transfer, rename, archive, and visibility changes require confirmation for the exact repository. 5. `harden` audits the control that matters after local guards fail: whether the active GitHub credential and server-side policy can still destroy a repository. Unverifiable capability returns UNKNOWN, never a green check. The project is deliberately honest about what regex and local hooks cannot prove. A clean scan means no known pattern matched. Novel wording, encoding, translation, and instructions split across lines can evade prompt-injection detection. Cross-file code flow still needs CodeQL or another taint-analysis tool. A direct API client can bypass the GitHub guard. That boundary is part of the product. The repository ships with offline fixture suites, a self-scan, ShellCheck, Gitleaks history scanning, secret scanning, push protection, protected `main`, technical blueprints, and field notes explaining the decisions. Public CI is green. MIT licensed. If coding agents touch your repositories, run the sixty-second quickstart and tell me which boundary I should harden next. Repo in the first reply. Bookmark this. Follow @nykdotev for daily builders talk and OSS.

• 
  👨🏻‍💻 ⚡️ (@EadrictheWild) reported 52 minutes ago

  @Andrewislington I am just going to use bedrock in the platform for BYOC for Claude. I figure just getting to use Claude Desktop was a good enough step for me. I just run the Github and AWS MCP server. Runon soon in AWS . Entire stack is AWS only though.

• 
  🔞Rin✝️ (@Onsolight) reported 55 minutes ago

  @__silent_ Aside from the ******* mods that run the server i have no clue why ppl hate rpcs3. The github folks are splendid ppl though.

• 
  agent maxxer (@claudeabuserr) reported 55 minutes ago

  @Robertg761_ @robinebers Sorry, terrible grammar on my last reply, im faded off cough medicine rn sick as a dog. I do use github but not like publicly as ive seen people doing (meaning spreading projects or using it as a social media platform). I primarily use it to sync my obsidian vault between my windows desktop set up and my mac so I can vibe code/build on the go.