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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	9 days ago
Trichūr	Errors	13 days ago
Brasília	Sign in	13 days ago
Lyon	Website Down	13 days ago
Tel Aviv	Website Down	17 days ago
Rive-de-Gier	Website Down	17 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:

• 
  Pedro Pellerini (@pepeller) reported 2 minutes ago

  If Mythos/Fable is so great why are there still 8386 open Github issues in Claude Code repository.

• 
  Ucupaint 🔶 (@ucupaint) reported 3 minutes ago

  @iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.

• 
  SOURAV PANDA (@i_d_skp) reported 7 minutes ago

  Scenario: You accidentally committed a plaintext database password to GitHub in a .tf file. Fix: Nuke the commit history immediately! Use environment variables (TF_VAR_db_pass) or fetch secrets dynamically at runtime from AWS Secrets Manager or HashiCorp Vault. 🔑 #Terraform

• 
  Nav Toor (@heynavtoor) reported 10 minutes ago

  There is a GitHub repo that defeats Google's Play Integrity check. 61,030 stars. GPL licensed. Pushed eight days ago. The repo is called Magisk. It roots your Android phone. It hides root from banking apps. It runs Netflix on a phone the Play Store says is uncertified. It passes the same fraud detection Google built to stop it. Here is the part that makes no sense. The man who built it is John Wu. He has been maintaining Magisk for nine years. Since November 2023 he has been a Senior Software Engineer at Google. On the Android Platform Security team. The exact team that builds Play Integrity. Google hired the person who defeats their root detection. He still ships the tool that defeats it. The repo is still online. It has not been taken down. For nine years. Do not install it. Your phone is supposed to belong to Google. (Link in the comments)

• 
  Dmytro Virych (@dmytrovirych) reported 12 minutes ago

  I’ve been shipping code for 10+ years and imposter syndrome still won’t leave me alone. You’d think it chills out with time. Nah. It just levels up. Early days it whispers “you’re not ready yet.” A decade in it hits harder: “bro you’ve been faking it this whole time, they’re about to catch on.” Mobile apps, web stuff, janky systems with too many moving parts, solo products I actually shipped… none of it matters when the voice kicks in. Thinking about speaking at a conference? Lol who do you think you are, those are the real pros. Want to drop an opinion in a thread? Better stay quiet before someone realizes you don’t actually know ****. Here’s the thing I’ve learned: the voice isn’t tracking your real skill. It’s just screaming about the fake gap between what you know and what you think everyone else knows. That second number is 100% made up. Your messy behind-the-scenes vs their perfect highlight reel. All those “professionals” I’m scared of? Half of them are up at 2am staring at a random GitHub issue, quietly praying someone else already solved this exact bug. It never fully disappears. You just get better at shipping anyway while it’s still yapping. If you’ve got way more years than your confidence shows, reply with the number. Curious how many of us are still out here waiting to get “found out.” 🚀

• 
  李新宝 (@lixinbao_X) reported 12 minutes ago

  Just watched KK's technique. Damn. Absolute game-changer. Install 7 skills in Codex. Writing, images, covers, PPTs. Full pipeline, done. The principle is dead simple. Break the workflow into 7 parts. One skill per part. Only do one thing. Step 1 Open GitHub, find a repo. Copy the link locally. Create a project folder to save it. Step 2 Write the skill description. Input three things. What it does. What the input is. Output and acceptance criteria. Step 3 Run it and find the bottlenecks. Where it stalls Create a new skill and break it down. Don't let one skill Do 7 things it's bad at. This works for writers, Xiaohongshu creators, WeChat pub runners, Video script writers. How many skills you got installed? Have you tried it yet?

• 
  Jesse (@jessearmand) reported 13 minutes ago

  I no longer remember why many companies started using gitlab before it went public when GitHub wasn’t owned by Microsoft. If we visit the majority of companies most tooling or software are top down driven. Only companies who build developer tools have a different mindset

• 
  lollipop (@immlollipop) reported 13 minutes ago

  🚨HACKERS MOCK OZEMPIC MAKER FOR "NOVO123" PASSWORD Hackers breached Novo Nordisk in March via a stolen GitHub token and just leaked 264 GB of data while mocking its weak security. The attack ran for over 2 months. - The hackers say Novo Nordisk used simple passwords like "novo123" on critical systems - Source code and proprietary details on Ozempic and pipeline drugs were stolen - Clinical trial data on employees, doctors, and patients got exposed - Private internal AI models from the company were also taken This breach shows how a single weak password can bring down even the biggest names in pharma

• 
  Solomon Neas (@solomonneas) reported 14 minutes ago

  There's a fair number of downloads for Brigade and related repos. I'm dogfooding it everyday but not getting any feedback from users or github issues. I'm doing plenty of tests for how a new user would experience it but I could use more real time feedback. Lmk, I want to improve

• 
  Iman (@RealKingiman) reported 15 minutes ago

  @ClaudeDevs Fix the auth bug with GitHub where I have it keep disconnecting and reconnecting GitHub every time

• 
  Mathieu A. (@zoontek) reported 18 minutes ago

  What are the most annoying bugs you still encounter with React Native? 👀 Please share GitHub issue links 👇

• 
  Anomaly (@theanomalyai) reported 19 minutes ago

  A developer in Bangalore named Anoop M D got tired of Postman. Every release, more bloat. Forced cloud sync. Mandatory login. A free tier that shrank every year. He had spent a decade as an engineer. He had watched a $5.6 billion company turn a developer tool into a subscription trap. So in 2022 he took a ₹5 lakh grant. One man. Side project. No co-founder. No office. No pitch deck. He named it after his golden retriever. "I love him the most," he wrote. Bruno. An offline-first API client. Files live in your folders. *** is the sync layer. No account. No telemetry. No cloud. Then the inbound started. Ten VCs reached out. He said no to every one. "An API client doesn't scale with venture capital." In March 2026 Postman cut the free tier to one user. A team of five now pays $1,140 a year. A team of three pays $684. Bruno is MIT licensed. 500,000 developers use it. 45,020 stars on GitHub. Pushed today. He did not raise money. He did not hire a growth team. He did not write a thread about how Postman is dead. He named it after his dog and shipped the thing that made it true. (Link in the comments)

• 
  Jose (@SolutionsCay) reported 19 minutes ago

  Two changes to how I work with agents: 1. GitHub App so the agents manage issues directly. Keeps the repo clear of throwaway spec and todo files. 2. EmDash (Cloudflare's serverless WordPress successor) for internal docs. Runs on D1, just SQLite under the hood, so I can export the content and move it anywhere. No more docs sprawl.

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 20 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  Rafal Wachol 💙 (@RafalWachol) reported 21 minutes ago

  @itometeam @tsuyoshi_chujo I was playing with it and started creating issues on GitHub when I noticed something.

• 
  Moez Zhioua (@MoezZhioua) reported 28 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 35 minutes ago

  @softgaypaws @sillyandsunny no idea tbhhh, i found it like 2 years ago lurking thru github, so far it never gave me problems, at least none that i noticed

• 
  Gabriel Denys (@gabedenys) reported 35 minutes ago

  @Marcos12345rico I posted a GitHub issue. Assuming you probably want bug reporting mostly there? It's a good tool. Locally I already patched and compiled the app to fix the bug.

• 
  Nikolay Konovalov (@br11k_dev) reported 36 minutes ago

  @Tristanrhee3 And GitHub sponsors thingy is so slow I submitted it like a week ago. Still not approved what the hell My expenses arent terribly high but Warsaw rent is like $2k/mo $500 ZUS $1.5k groceries for two people That’s pretty much it I wish I could move into low cost area but moving out is gonna cost a lot because 2x rent price deposit, so I have to suck it up Anyway, my plan is Upwork and finishing my job tracker so I can send faster than 5 applications a day. I refuse to send out 100 applications per day like some people do spray and pay It makes everyone miserable. If people aren’t hiring your spam doesnt make things better You just mopping floors and hiring problem sits above you, 3 floors up there leaky faucet you can’t even reach This has to be collective effort to fix this problem But we have to start with ourselves and stop spamming applications at least And do genuine company research, being responsible Thanks for reading.

• 
  Kevin Tabet (@TabetKevin) reported 36 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  Raj Nagulapalle (@rnagulapalle) reported 37 minutes ago

  GitHub just shipped Agentic Workflows: write automation in plain markdown, compiles to Actions YAML. issue triage, CI failures, vuln fixes. hours → minutes. but 60% of orgs are spending millions on agentic AI while only 15% are actually production-ready. the capability gap closed fast. the readiness gap didn't move.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 43 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  Blum (@Blum_OG) reported 44 minutes ago

  Andrej Karpathy on MCP: "it's a protocol of speaking directly to agents as this new consumer and manipulator of digital information." that is the cleanest way to think about MCP your coding agent is becoming a second worker inside the product it needs the same context you use: repo, docs, browser, database, errors, designs, tickets, payments if you keep pasting those things into chat by hand you are doing integration work manually the best MCP stack for vibe coding: 1. Context7 give the agent current docs this saves you from stale Next.js patterns, old Supabase calls, wrong Stripe webhook shapes, and Vercel config from 2 versions ago 2. GitHub MCP give it the repo, issues, PRs, branches, workflow runs, and review context half of real work lives outside the file you currently have open 3. Playwright MCP give it a browser the agent should click the thing it built, fill the form, check the mobile view, and catch the button that compiles but does nothing 4. Firecrawl MCP give it clean web research use this before building around a third-party API, writing a comparison page, reading changelogs, or checking pricing claims 5. Supabase or Neon MCP give it the database context that matches your stack start read-only. add writes only when you trust the permissions 6. Sentry MCP give it production evidence real stack traces beat "it crashes sometimes" every single time 7. Figma MCP give it design context when the interface matters spacing, layout, copy, components, and screen structure should come from the file, not from a screenshot and hope 8. Linear MCP give it the task queue bugs, feature work, release notes, follow-ups, and PR links belong somewhere more durable than yesterday's chat 9. Stripe MCP give it official payment context checkout, subscriptions, webhooks, billing, and test mode deserve docs close by and human review close behind 10. Filesystem, ***, Memory, Sequential Thinking give it the base layer files, diffs, history, decisions, and longer plans make the agent act like it is working inside a real project recommended install order: 1. Context7, GitHub, Playwright 2. Supabase or Neon, Sentry, Firecrawl 3. Figma, Linear, Stripe when the product needs them 4. Filesystem, ***, Memory, Sequential Thinking as the base

• 
  xjdr (@_xjdr) reported 44 minutes ago

  @xlr8harder Looks like there is a bug in the manual sign up. Sign up with Google or GitHub should work otherwise I should have a hot fix shortly

• 
  ˚₊‧꒰ა ☆ Kira ☆ ໒꒱ ‧₊˚ (@sheriffmongoose) reported 44 minutes ago

  the problem with jumping from github to gitlab is constantly having to retrain your brain to call it "merge request" instead of "pull request" 🥲

• 
  Domi (@domirosari0) reported 51 minutes ago

  @ajayyy_k @hqmank If you got Github it would be no issue for you

• 
  Shubham Sharma | AI & Tech (@editxshub) reported 52 minutes ago

  Paying $19/month for GitHub Copilot? Cascade is free. What you actually get: → Inline completions — not stripped down → Autonomous debugging → Real-time assistance → Command execution Other free alternatives most devs have never tried: → Cline — autonomous VS Code agent (open source) → Aider — terminal-first, built for *** workflows → Continue — local LLMs, data stays on your machine 12 months ago: Copilot was the only serious option. Today: 4 real free alternatives. Most teams paying for Copilot haven't tested any of these. 30 minutes could change a year of costs. Which one are you testing?

• 
  Pascual ⚡ (@0xPascual) reported 52 minutes ago

  A high school kid opens an account, plugs in Claude 5, and turns a few hundred dollars of lunch money into a six-figure trading account over the weekend. The screenshot goes viral, the replies fill up with people begging for the GitHub repo, and the standard engagement-bait influencers declare the dawn of the sovereign teenage day-trader. The media thought that was the story. It was not. The real flex wasn't the macro strategy or the directional bets on currency pairs. It was the setup behind it: a lightweight proxy array routing through residential IPs to dodge exchange rate-limiting, paired with a custom parsing engine that instantly translates raw order-book imbalances into executed micro-hedges. The kid wasn't trading; he bypassed the entire institutional pipeline of risk management, brokerage compliance, and analyst overhead with a single configuration file. The entire operation runs on a continuous loop of multi-agent orchestration. A master instance drafts the execution logic, a secondary validation agent checks the code against real-time oracle feeds, and a fleet of worker APIs executes up to 3,210 trades a night. Total infrastructure cost: roughly $45 in API tokens and a cheap server instance. It extracts a 78% win rate out of systemic market inefficiencies, operating with a structural margin that legacy trading desks weighed down by salaries and compliance boards cannot compete with.

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 56 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  Arti | AI Builder (@Artur_roses) reported 58 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.