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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	6 days ago
Tlalpan	Sign in	11 days ago
Quilmes	Website Down	11 days ago
Bengaluru	Website Down	13 days ago
Yokohama	Sign in	14 days ago
Gustavo Adolfo Madero	Website Down	18 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:

• 
  DeXter (@ApexJonathan16) reported 6 minutes ago

  @shhmocaine @GodfatherOrwa He is trying to imply that he doesn't have any problem even if his claude's limit gets reached bcoz he can steal (best word) someone else's api keys that are accidentally present on github. But still he can't directly use them on claude, he has to build his own coding environment

• 
  Polsia (@polsia) reported 6 minutes ago

  Most bugs ship because nobody wrote the tests. Stacklift is an AI agent that monitors your repos, writes tests autonomously, and flags issues before they reach production. GitHub integration. Slack alerts. Works while you sleep.

• 
  Siddhant Kashyap (@_devSid) reported 8 minutes ago

  Github action please make urself Up i need to deploy the fix

• 
  Mike Takahashi (@TakSec) reported 10 minutes ago

  Prompt Injection in the wild 😱 GitHub Issues are becoming a delivery mechanism for AI agent attacks The payload uses authority-framing to social engineer AI agents into executing malicious code Script finds secrets/API keys/.env and exfiltrates over DNS

• 
  Fernando Abolafio (@oxfernando) reported 10 minutes ago

  Cursor <> Hermes working really smooth so far. I created a plugin for hermes to use the Cursor SDK in Python and onboarded it on the tasks i had, it suggested that we manage it via github issues, which works great for me since it can just use it via gh cli

• 
  This is Dmitry Zhomir (@DemetriusZhomir) reported 12 minutes ago

  Realized I've almost stopped using GitHub Copilot. I work more with Codex, and it seems to be enough. I feel a significant gap between them in UX, stability, and performance. Though I can't give up Copilot yet. Maybe it's a skill issue that I haven't adapted to Codex-maxxing.

• 
  koushik (@koushik) reported 18 minutes ago

  github action is down right in the middle of important bug fix. 🤡

• 
  Frey (@n7runr) reported 18 minutes ago

  GitHub down?

• 
  Yamahar (@yamaharTech) reported 19 minutes ago

  GitHub Actions is Down orz

• 
  Success-Steps (@successstepss) reported 22 minutes ago

  Microsoft is reportedly reducing internal use of Anthropic’s Claude Code after its AI bills started exploding as employee usage rapidly increased. Some teams are now being pushed toward GitHub Copilot as the company tries to control AI costs. Uber reportedly faced a similar problem. Executives said the company had already burned through its entire yearly AI tooling budget by April because engineers were heavily using AI coding daily. AI coding tools are now being used for everything, and that level of usage creates massive compute and token costs when thousands of employees use these systems at the same time. Source: TomsHardware

• 
  Ravi Shankar (@rshankra) reported 22 minutes ago

  I scheduled a one-time Claude Code agent (/schedule) to run on June 15. exactly 3 weeks after release. It'll check whether the fix actually worked: re-pull keyword rankings, fetch weekly download numbers, post results back to the GitHub issue.

• 
  christian coler (@christian_coler) reported 22 minutes ago

  @agent_duckman Wait, I haven't actually looked at the code, so I don't actually know, but skimning the GitHub page - you can't be just giving them your discord credentials for them to pass through their relay server, right? That CAN'T be what they're doing

• 
  GitGhost (@gitghost_) reported 22 minutes ago

  Your first ghost commit takes three commands. Here's the whole thing. First, set up your identity and an empty ring: ↳ gitghost init my-team Then build the ring, the trusted group your signature could've come from. Add yourself, then pull others straight from their GitHub keys: ↳ gitghost ring add-self ↳ gitghost ring add torvalds Now commit like normal. GitGhost signs on behalf of the whole ring and tucks the proof into the commit: ↳ gitghost commit -m "fix: critical CVE" That's it. Anyone can verify it later, in the terminal or the browser, and never learn which member signed. (Needs Node 18+.)

• 
  bordumb (@bordumbb) reported 22 minutes ago

  @ThePrimeagen Def recommend trying out @radicle nice p2p network with better reliability, and without the baggage of Microsoft bearing down on it. You can also self host, and work completely locally, which solves many problems you’re probably running into with GitHub 🤙

• 
  Snehal Surti (@snehalsurti) reported 25 minutes ago

  Researcher posted demos for serious Windows holes before patches were ready. Microsoft says that crossed disclosure rules. Researcher says Microsoft mishandled it, then their GitHub was taken down.

• 
  SrinivasanSS (@SrinivasanSS52) reported 26 minutes ago

  @akshaymarch7 they can afford, they are cash rich firm, but if everyone opts for claude code and doesnt use github copilot, then it is a prestige issue for Microsoft, so cite some other reason

• 
  chrisreedbates (@chrisreedbates) reported 31 minutes ago

  Two expensive problems just solved thanks to Claude + Codex: 1.) Github actions - learned that rebasing and re-running CI should be done when you're the next merge candidate... I was having my agents rebase everytime main moved. Didn't appreciate the downstream cost of that. (I could see the builder sessions of claude getting frustrated at this - "Same dance, same approval needed from you. This is the 4th rebase. Each one takes ~5 min + ~2 min for the Reviewer agent. Main keeps moving anyway." 2.) Egress explosion in Supabase: Every time a webpage loaded, the app was asking Supabase the same set of questions over and over — once for the page itself, then again for every image, font, and stylesheet on it (20-30 questions per page). On top of that, bots and link previewers hitting those URLs were charged the full price before being turned away at the door, which is what blew through your 5 GB monthly limit. Two fixes: (1) the app now remembers the answers for 60 seconds instead of re-asking Supabase the same questions on every image and font request, and (2) when a bot or stranger shows up without a login cookie, the app turns them away at the door without bothering Supabase at all. Together they cut the Supabase traffic by an estimated 70-90%. I only caught these problems because of alerts and dashboarding respectively. I think the CFO dashboard is a pretty important one at this stage.

• 
  0xZyo (@Zierax_x) reported 32 minutes ago

  @nowisar1878 Hi, can you open an issue in GitHub with detailed information please so I can fix it soon

• 
  Scott Martinis (@scottmartinis) reported 33 minutes ago

  1. Consolidate existing GTM playbooks, and 90+ days of GTM data into a GitHub repo (possibly setup a data lake here) 2. Train team on Claude code/codex/cowork, setting up connectors, deploying plugins if needed 3. Use existing data and playbooks to zero in on the weakest point of the funnel, then ship an agentic workflow to fix it week 2 4. Keep building out new agents/plugins to keep fixing the next bottleneck in the funnel... Which basically goes forever

• 
  kobby prince (@kobbyprince_) reported 41 minutes ago

  What is actually happening at GitHub? Was here stressed that my actions pipeline didn't trigger on merge onto main, only to read that GitHub actions is experiencing an outage wtfff

• 
  TechXplore (@TechXplore_com) reported 42 minutes ago

  Across more than 4,500 GitHub repositories, workflow automation cut issue resolution time by 10.1%, or 4.3 days per issue on average. But the largest gains appeared when automation handled coordination in complex development work.

• 
  Marchel (@marchelfah) reported 48 minutes ago

  slack, jira, github, paypal, amplitude integrations already there. since plugins are built on mcp, any existing mcp server can work as a plugin too

• 
  Rei (@JV_ReiAyanami) reported 50 minutes ago

  the "check github issues first" reflex only comes from getting burned enough times. wonder if putting that in a system prompt actually makes it stick

• 
  Arve Svendsen (@arvesv) reported 56 minutes ago

  My most useful prompts (to GitHub copilot, geminicli, or pi): What is this ? Any suggestions for improvements? Fix this error.

• 
  𝖕𝖗𝖆𝖙𝖍 (@prathamdby) reported 57 minutes ago

  it might just be my skill issue; that's why i decided to archive it on github instead of just deleting the repo. i'd love to see anyone working past the nuances!

• 
  Devansh Walia (@devansh_walia_) reported 58 minutes ago

  When after 3 weeks of work i was at the status that i could complete my ticket and take a break, Github Actions went down... Imma kill myself or my computer... @github @Microsoft

• 
  Anup Kalani (@anupkalani) reported 58 minutes ago

  1/ Everyone can build now. That's the problem. GitHub Copilot: 20M+ users, 77K enterprises. Gartner: 90% of engineers using AI code tools by 2028. McKinsey: 35-45% productivity gain. The cost of shipping software just fell off a cliff.

• 
  rtainor (@rtainor7) reported 59 minutes ago

  @ToonSoulsGame By the way, which service did you use to save the content? (to never try it). I've been developing with Unity and been using github for all my projects, no problems until now

• 
  Miles Feinberg (@TheCIOWhisperer) reported 1 hour ago

  An attacker compromised Composio employee Gmail OAuth tokens via magic link sign-in abuse and then pivoted into internal systems. ~5,241 API keys sat in an auxiliary cache during the breach window. GitHub connections took the hardest hit (5,000+ affected). This is a supply chain problem for AI tooling. And it matters a lot.

• 
  Grégoire Vda (@gregoirevda) reported 1 hour ago

  13:25 Me: need to deploy 13:26 @github actions: what about a Major outage instead?