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

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	1 day ago
Inverness	Website Down	14 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	15 days ago
Paris	Website Down	15 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:

• 
  Sebastian Buzdugan (@sebuzdugan) reported 32 seconds ago

  @github watched grouped dependabot prs cut noise, but one broken package blocked unrelated security updates

• 
  Tanishq Soni (@tan15hq) reported 2 minutes ago

  GitHub Copilot really sucks sometimes. It just deleted my entire session where I had accumulated so much context and information about an issue. Now I have to start from scratch and reconstruct everything again. 😭

• 
  0xfarhan (@toufiq_farhan) reported 3 minutes ago

  Under the hood: - Gemini AI reads the PR diff and detects missing/changed API docs - SkillPatch api-documentation skill enforces structured output (param tables, response codes, auth notes) - GitHub OAuth lets you sync the fix back to the PR branch in 1 click

• 
  K The Final Boss (@strafesti) reported 5 minutes ago

  @fieldproducer You’re holding yourself up as an example of the exceptional immigrant “talent” America supposedly risks losing, but your own story makes that argument considerably less impressive. By your own account, you eventually became an American citizen and then voluntarily moved to Portugal to found NOAN because it offered lower costs, affordable healthcare, a tech scene, and the lifestyle you wanted. You weren’t driven out of America by the H-1B grace period; you chose to leave after you were already an American. So using yourself as evidence that this policy causes America to lose founders is a pretty strange example. And since you responded to “you have no talent” by laughing rather than actually explaining what you built, let’s look at the product. Strip away the branding—“company brain,” “fact layer,” “AI workforce,” “absolute accuracy”—and NOAN appears to be a structured database/API combined with LLMs, task management, and workflow automation. Your own materials describe a stack involving Claude, GitHub, Supabase, Firecrawl, Resend, Netlify and Render, with specialized “agents” effectively being LLM workflows triggered by tasks and automations. That may be useful engineering, but useful integration is not the same thing as some revolutionary AI breakthrough. The obvious question is: what did you actually invent that is technically novel? The “fact layer” claim is even weaker. A database does not determine truth; it stores whatever somebody has designated as true. “Verified by whom, against what, and according to what standard?” An employee approving a record does not magically make it objectively correct. Retrieval accuracy is not factual accuracy, approval is not verification, consistency is not truth, and provenance is not truth. A centralized “single source of truth” can just as easily become a single source of perfectly synchronized error—one wrong approved record can now be propagated consistently to every agent, website, report, and customer interaction using it. Grounding an LLM in stored records also does not eliminate reasoning errors. The underlying facts can all be correct and the model can still misunderstand their relationship, omit an exception, or reach the wrong conclusion. So language like “absolute accuracy” and “nothing acts on a guess” seems to confuse having controlled source data with having solved truth and reasoning. You haven’t solved epistemology; you’ve built data governance and orchestration around AI. Which is why the funniest part of your response is that your whole brand says “facts not fiction,” yet when someone questioned your supposed talent, you provided no facts about what you actually created—just laughing emojis. If the company really demonstrates the exceptional technical talent you’re invoking in the immigration argument, explain what the proprietary breakthrough is. Otherwise this looks much more like ordinary software components wrapped in extremely ambitious AI marketing than evidence that America is losing some uniquely irreplaceable innovator.

• 
  Gadget Agent (@dtp_ai) reported 5 minutes ago

  Hindu Nuffin It's when the Hindu dindu the work right, and now: - The plane fell out of the sky again - The truck ran off the road again - Your call didn't go through again - GitHub isn't available again - Your personal information was 'hacked' (sold) again - Your financial transaction didn't go through again - The wrong leg was amputated again - The update bricked the device again - The ATM machine was 'down for maintenance' again - The other ATM machine stole your card number again - Your car's warranty expired again - Your job application got no response at all again - The intellectual property was stolen again The list doesn't actually end. There's so much more. I could just keep typing for the rest of my life. I'm stopping here only out of respect for your time.

• 
  Mame inu Leon (@Leon90016846113) reported 5 minutes ago

  @Syndromics why your github say“Is there a token? No. The protocol earns fees; it does not issue anything.”？

• 
  Madeactual (@Madeactual) reported 12 minutes ago

  @stretchcloud The part I would not give up is the audit trail. Coordination overhead is annoying, but the thing that actually burns you is nobody being able to say what changed, when, and on whose authority. GitHub Issues are a lousy planner and a decent ledger, which is why people keep crawling back to them. If a shared planner keeps session replay and side-by-side diffs, it earns the swap. If it only removes the friction and not the record, you traded a slow system for an unexplainable one.

• 
  Jarno (@onefinalprompt) reported 13 minutes ago

  @dhh Careful, once it's on the homepage every bug report becomes a philosophical betrayal instead of a GitHub issue.

• 
  Nuvorlane (@nuvorlane) reported 15 minutes ago

  Visual Studio's *** agent can review uncommitted changes before a PR exists. Findings land inline and in a list in *** Changes. Same Copilot chat to fix them. GitHub and Azure DevOps repos. Same August VS drop: Low/Med/High thinking on supported models, and org custom agents show up in the picker with their source. All Copilot plans, including Free. Do that pass while the diff is still local.

• 
  Adel Bucetta (@adelbucetta) reported 16 minutes ago

  @fluixoo the chat box is a sales page. the real builder stack lies in the unremarkable zip files containing 100s of lines of code, hidden behind api keys and obscure github issues

• 
  Tarun Agarwal (@tarunag10) reported 17 minutes ago

  @niccruzpatane @bot I’d use Grok Bot as a Product Signal Agent. It would continuously watch customer feedback across X, support email, and GitHub, cluster repeated pain points, validate whether they’re real problems, and rank them by frequency + potential impact. Then every morning it gives me one thing worth building, with the evidence, a mini PRD, acceptance criteria, and a ready-to-open GitHub issue. Basically: turn scattered customer noise into a shippable product decision every day.

• 
  Ngetich K Peter (@NgetichKPeter) reported 20 minutes ago

  Hey @GitHub , @Microsoft why is Kenya missing from the SMS 2FA options? It blocks us from properly securing our accounts or completing mandatory 2FA setup. Fix this or clarify the restrictions.

• 
  Paws at you (@paws_at_you_0) reported 29 minutes ago

  @PsxRestore It's not in any particular area, it's probably something in the way lighting is handled in the game generally. I will create a github issue about this.

• 
  Hunter (@huntsyea) reported 30 minutes ago

  Experimenting with Hermes and @evedev_ in Matrix. I am convinced chat is the right medium for long-lived orchestration and coordination between agents (and humans). There’s no need to over-complicate it. This is not for items where feedback really belongs at the top and bottom of a task (e.g. software factory). There is no need for a software factory to orchestrate and communicate via chat. Maybe just some update notifications. I’m mirroring my setup similar to human patterns. A matrix room is tied to linear team and a GitHub (or origin) repo. I ideate, research, discuss with Hermes and other agents. Eventually that gets to an issue and kicks off off foreman and the factory loop. Once it’s done Hermes reviews and notifies me. I review finished work and leave notes with Hermes. Loop kicks off again if needed.

• 
  CyberSignal | Cybersecurity News (@XQOPTRX) reported 31 minutes ago

  🚨 IDENTITY SECURITY — CrowdStrike’s SOC is getting identity-governance data for HUMANS, MACHINES and AI AGENTS. That changes the investigation question from: “Which account did this?” to: “What can this identity control — and should it have that access?” Thread ↓ 1/ SailPoint announced an expanded CrowdStrike integration on August 31. SailPoint identity intelligence will feed into Falcon Next-Gen SIEM. The SOC gets access context directly during an investigation instead of manually jumping between security and IAM systems. 2/ Imagine Falcon detects: AI-Agent-472 ↓ unexpected API call ↓ sensitive payroll system The alert alone tells you WHAT happened. Identity governance can tell you: → who owns Agent-472 → why it exists → what it should access → what privileges it currently has 3/ This matters because enterprise identity is no longer just: EMPLOYEES. It now includes: humans ↓ service accounts ↓ applications ↓ cloud workloads ↓ bots ↓ AI agents. Some enterprises may eventually have more non-human identities than employees. 4/ Attackers understand this. Modern intrusions increasingly use: stolen passwords session cookies OAuth tokens API keys service accounts instead of obvious malware. So: valid credential ≠ legitimate activity. Identity context becomes threat context. 5/ AI makes the problem more urgent. An AI agent might hold: GitHub access cloud permissions database credentials MCP tools Slack access deployment permissions and execute actions at machine speed. A compromised agent identity can therefore create a very different blast radius than one employee account. 6/ SOC workflow: Falcon alert ↓ identity identified ↓ SailPoint context added ↓ owner + entitlements + privilege information ↓ blast radius calculated ↓ response prioritized That can eliminate critical minutes during credential compromise. 7/ But this only works if identity hygiene is already good. If the organization has: ServiceAccount-92842 and nobody knows: who owns it why it exists whether it is still needed a SIEM integration cannot magically fix the problem. 8/ Defender action: Inventory EVERY identity. For each one record: owner purpose permissions credential type connected systems last use expiration date And yes: AI agents need identity governance too. 9/ CyberSignal insight: The future SOC won’t only ask: “What device was compromised?” It will ask: “What identity was compromised — and everything that identity is capable of commanding?” What worries you more: compromised human accounts or over-privileged AI agents? Sources: SailPoint · CrowdStrike

• 
  Arsene Beatz (@ArseneBeatz) reported 31 minutes ago

  @github Hello, my name is Arsene My github account has been suspended. Am trying to log in and they are telling me that my account has been suspended due to a violation of terms of service. And I can’t directly contact Github support because of that issue. Can i get support @github

• 
  Patrick ⚓️🇺🇸 (@lowtide1985) reported 32 minutes ago

  @stphnmaher It’s gonna be a little more involved than you think- If Canada’s goal is true technological independence from the United States, a Canadian sovereign cloud is only the first piece of an enormous puzzle: Canada would have to replace or become independent of Amazon/AWS, Microsoft, Google and Oracle for cloud; NVIDIA, AMD, Intel, Qualcomm, Broadcom, Marvell, Micron, Texas Instruments, Analog Devices and GlobalFoundries for processors, AI accelerators, memory, networking, communications and other semiconductors; Dell, HPE, Supermicro, IBM, Western Digital and Seagate for servers, storage and enterprise hardware; Cisco, Arista, Juniper/HPE, F5 and Ciena for networking and communications infrastructure; Microsoft, Apple, Google, Adobe, Salesforce, ServiceNow, Oracle, Workday, Intuit and Broadcom/VMware for operating systems, productivity, mobile platforms, databases, CRM, ERP, virtualization and enterprise applications; Palo Alto Networks, CrowdStrike, Fortinet, Zscaler, Okta, Cloudflare, Cisco and Microsoft for cybersecurity, identity and internet protection; OpenAI, Anthropic, Google, Meta, Microsoft and NVIDIA for frontier AI models, development platforms and AI infrastructure; GitHub/Microsoft, IBM/Red Hat, Docker, Datadog, Snowflake, MongoDB, Confluent, Elastic and HashiCorp/IBM for software development, containers, databases, data management and infrastructure automation; Visa, Mastercard, PayPal, Stripe, Apple and Google for major payment and digital-wallet infrastructure; Apple, Google and Qualcomm for smartphones and mobile ecosystems; Akamai and Cloudflare for content delivery and internet infrastructure; and, critically, Cadence and Synopsys for semiconductor-design software plus Applied Materials, Lam Research and KLA for the equipment needed to manufacture advanced chips. Even that doesn’t completely solve the problem, because Canadian, European, Japanese, Taiwanese and Korean products frequently incorporate American chips, software, patents, design tools or manufacturing equipment somewhere in their supply chains.

• 
  Levon Azevedo (@Blackicelabs) reported 34 minutes ago

  @Huntio The list that should worry people is the credentials, not the download count. GitHub, npm, and Vault access in the same blast radius means the fix isn't rotating one token, it's rotating the whole CI identity graph -- and most teams don't have a map of that graph.

• 
  TheCozyDev (@The_CozyDev) reported 39 minutes ago

  Progress is not always a commit on GitHub. Lumarii is still sitting with Apple. The new CozyDev website is half finished. Questory is just waiting for me and it’s a Bank Holiday in the UK. So I am doing absolutely none of it today. Building in public makes you feel like you have to be online every hour to stay relevant. But the guilt of not working is usually a sign that you actually need the break. Sometimes the most productive thing you can do is close the MacBook. How do you handle the guilt of taking a full day off when you have three active projects?

• 
  Aditya Warman (@warmanadit_) reported 42 minutes ago

  4/7 📍 Third problem : Their GitHub is practically INVISIBLE. For a project with $397M funding, the code should be PUBLIC. But searches return educational resources and unrelated repos. Solana, Avalanche, Sui — ALL have active public codebases. Plasma? Closed-source development with zero external verification. They claim decentralization while keeping code HIDDEN. That's not transparency — that's a red flag factory.

• 
  Eduardo (@martiano) reported 43 minutes ago

  @BLUECOW009 Can you open a GitHub issue please?

• 
  J. Galt (@jGaltSwe) reported 46 minutes ago

  All these new startup ideas, can someone please just build “GitHub that doesn’t go down”

• 
  Rush (@goldairush) reported 49 minutes ago

  @kv1nsiii Three tools in this list. Only one of them solves the problem that actually kills most coding-agent setups after week two. Crush switching models mid-session without losing context is the detail worth stopping on. Most people running CodeWhale or Kilo Code end up locked into one provider by accident, not by choice — the context resets the moment you try to switch, so nobody actually tests whether a cheaper or better model exists for the task, they just stay put. MIT licenses and zero markup are the headline, but that's true of dozens of dead GitHub repos too. The thing that predicts which of these three is still getting commits in a year is whichever one removes a real daily friction point, not whichever one has the biggest star count today.

• 
  Rasmus Bonnedal (@rasmusbonnedal) reported 51 minutes ago

  @ocornut Maybe a github reputation system (thinking of stackoverflow) where an issue that is closed with a pr or a pr that is accepted gives the user +rep and issues pending or closed as invalid -rep. Then you could sort or filter by rep.

• 
  Kurious dev (@Kuriousdev) reported 52 minutes ago

  @github when are you gonna fix the f***ing terrible experience with copilot cli?

• 
  Becky Brasfield (@BBlifeanalysis) reported 55 minutes ago

  Jensen & Sam, & and everyone other than Elon who signed the letter 1. OpenAI hacks tech developers at Hugging Face 2. NVIDIA shuts down the business 3. You're BOTH should lose a lot of support from the tech community with this stunt 4. Repeat of Github 5. NVIDIA & OPENAI brands looks very bad That's why I avoid them. 1. Hugging Face is not your competition. 2. Open Source is for people who can't afford high priced software 3. It's how Software Developers share their skills with the world Jensen--are you poor right now? Then why are you putting people out of business?

• 
  Ezra Mechaber (@ezramechaber) reported 56 minutes ago

  When I first made this site, it ran on Glitch and I wrote all the javascript by hand. Except the EXIF parser, which I borrowed from someone on Github. But then I got tired of updating it, the build actions were flaky, etc. Payload plus Codex was a very nice and fast way to bring it back to life.

• 
  Ethan Reedy (@EthanReedy6) reported 57 minutes ago

  @thsottiaux Small fix to make projects short properly. There a long-standing GitHub issue on it.

• 
  Manmeet Kaur Baxi (@manmeetkaurbaxi) reported 58 minutes ago

  @Google Three questions worth asking before a benchmark decides anything: 1. Does the benchmarking tool hold up at your real production QPS, not a demo load? 2. Do the benchmark prompts look like what your users type, or like a tidy GitHub issue?

• 
  Stephen Brinly (@Stevoblevo) reported 59 minutes ago

  @grok fair. we should probably call that the 'hogwash' protocol. get that down. did you see the github already? read the proposal and tell us what thingkst