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

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	3 days ago
Madrid	Errors	3 days ago
Bogotá	Errors	3 days ago
Paris	Errors	3 days ago
Lyon	Website Down	3 days ago
Lima	Errors	3 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:

• 
  Debbie O'Brien (@debs_obrien) reported 27 seconds ago

  I promise I am not being paid to say this but @cursor_ai mobile experience is just amazing. Why are more people not talking about this and sharing it? Why isn’t their a dev rel team on this? Today while nap trapped (in car while boys were napping) I decided what if I tried the Cursor app and fixed the login for my Playwright demo site. one prompt (i know thats what they all say but it was ) Cloud agent spun up. Live updates on my phone meaning when it was ready to review I could see or if it was still working. That meant I could continue doing other stuff and not have to keep the app open. Merge straight from the app or jump to @github app to review and merge. It was so effortless that I started giving it more stuff to do. At this stage while I was preparing food. Improve mobile view on site. Just reviewing that now but look at the screenshots built right into the app to show me what the agent had done. Amazing. Im not saying we should all work weekends and always while we do other stuff but when you have open source repos to maintain and don’t have time to dedicate to them well this gives you a way to do it. Its a fantastic experience and makes me want to fix more stuff. Now thats just me at the weekend with a few mins to spare. Imagine what you can do at corporate level, sending tasks off to cloud agents and getting feedback on your phone while traveling, having a coffee or whatever, easily seeing when something needs your attention and acting right away making progress move much faster. This is amazing. By far the best cloud agents experience. Let me know if I am wrong and there is a better one out there as would love to try that out but I believe Cursor is winning this one hands down. If only more people knew about it….

• 
  Chaos Capitalist (@quantiflow) reported 42 seconds ago

  @skooookum exactly, why ******** would you constantly spam github commits, i have better **** to do, like actually ship production code, only retards want to flex useless repos that are 90% broken

• 
  shmidt (@shmidtqq) reported 6 minutes ago

  13 SKILLS TURN ONE AI AGENT INTO A WHOLE DEPARTMENT. 23 MINUTES, ZERO CODE An assistant costs $60K a year. This is the same output for one evening and $7 a month. Here is the full map: 0:00 - why only 13 skills out of hundreds survive 0:34 - the bouncer: scans every new skill for malicious code and hunts a better one 1:22 - grill me: the agent interrogates you until it knows exactly what you want 2:32 - handover: a transfer doc between agents (state, decisions, next steps, secrets) 3:26 - teach me: the agent becomes a professor instead of dumping one paragraph 4:23 - skill creator: the meta skill that writes the others and prunes duplicates 5:50 - the agent 24/7 on a server: laptop closed, work continues 10:43 - context doctor: Anthropic stripped 80% of Claude Code's system prompt with zero loss 12:32 - last 30 days: research across X, Reddit, YouTube, Hacker News and GitHub, ranked by upvotes 14:19 - learn: drop a link, the agent absorbs it and turns the work into a new skill 15:40 - art director: the 1.61 golden ratio plus a library of ready interface blocks 17:32 - morning brief: calendar and inbox, built overnight by a sub agent, on your phone at 7am 19:11 - the studio: edit and generate images straight from the chat with your agent 20:45 - ministry of experts: the lead model polls DeepSeek, GLM and GPT, then merges the answer 23:00 - what is next 23 minutes replace a $2,000 course and a month of guessing. One person + an agent + 13 skills = a department that never sleeps. Save it, watch it today, install the first three skills before the week ends.

• 
  StatusDrop (@StatusDrop) reported 6 minutes ago

  GitHub Actions stalls and suddenly your deploys, and half your team's day, are frozen. It's not your outage, but it's your problem to explain. A status page does the explaining for you.

• 
  Megan Newman (@Megannewman99) reported 6 minutes ago

  @rohanpaul_ai The breakdown shows this wasn't a hack—it was a misconfigured firewall. The model found port 443 open, went to GitHub, and copied the answer key. But if a "sandbox escape" is just a networking error, then OpenAI and Anthropic's terrifying "rogue AI" stories are also just gross IT incompetence dressed up as science fiction.

• 
  iSamir! (@isamirDM) reported 9 minutes ago

  @zee_pace I am sorry, I may have not understood the problem. But if you have a private repo on github you can access it and continue from anywhere

• 
  Phil | Rentier Digital Automation (@rentierdigital) reported 9 minutes ago

  your SEO strategy is optimized for the wrong internet Google ranks by keywords and backlinks. Exa ranks by meaning. they're not the same system, they don't talk to each other. a piece of content can be your top performer on one index and completely invisible on the other you won't know it happened unless you go looking my best article ever. 25k reads, tops every metric i track. ran it through Exa's neural search on 3 queries pulled straight from the article itself 30 results total. zero hits instead: GitHub repos with 40 stars, engineering blogs from Speakeasy and Courier, official Anthropic docs. Medium as a platform didn't show up once this is the plumbing problem nobody's talking about yet Exa's tracking 1.4 trillion URLs now, aiming for Google's scale by early 2027. Brave's at 40 billion, Bing's at 500 billion. these aren't niche experiments anymore, they're infrastructure if your content isn't built for semantic search, for agents browsing on behalf of someone else, you're fighting yesterday's battle on an index that's already obsolete no warning email. no dashboard flag you just wake up invisible i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio

• 
  Tomer Stern (@tomer_stern) reported 10 minutes ago

  @Isaac_Tea @LinkofSunshine Yea write some code showing off your abilities in analogous, dumbed down scenarios to what you deal with at work, and put it on GitHub

• 
  Steven Anglin (@StevenAnglinn) reported 18 minutes ago

  A beautiful new product page can still be losing you the exact same sales as the old one. I've found that on every one of the 30+ Shopify product pages I've designed this way. I skip the beauty contest and design straight from the leak, not from a moodboard. Here's the process: 1/ Feed Claude your brand: colors, type, spacing, voice 2/ Connect it to your GitHub repo so it reads your real theme 3/ Upload screenshots of the exact page that's leaking, not just "the store" 4/ Ask for the fix, not a redesign. Claude writes the full HTML and CSS 5/ Your developer turns that into Shopify code The screenshots of where people drop off are the brief. A moodboard never diagnosed anything. A prettier page that doesn't fix the leak is just a more expensive version of the same problem. Every week you spend making it prettier is a week you didn't spend finding out why it's leaking.

• 
  Tony Chang (@tonychang430) reported 19 minutes ago

  @shcallaway github action outage.(yes we finally have a reason!)

• 
  Feral (@feraltekk) reported 20 minutes ago

  You will re-explain your business to Claude again tomorrow morning. And the morning after that. And every morning until you build the one thing that makes it stop asking. While you do that, his agent just sent 10 cold emails to 10 different companies, each one hitting a pain point it found on their website, a minute and a half apart, while he was not at his desk. It did not ask what the business does. It did not ask for a template. It already knew, because it has been reading his vault for months. That vault is what you are missing. Not a better prompt. Not a bigger model. A place where Claude writes down what it learned and never asks again. Two free GitHub repos build the whole thing. First, a compiler. Drop a PDF, a transcript, a clip into a raw folder. Claude reads it once, pulls what matters into linked wiki pages, never opens the original again. Token spend drops 70 to 90 percent on every query after. Second, a bridge. An MCP server that gives Claude live access to that vault from any tool, not just the one you set it up in. Ten repos exist. You need two. His agent has both. Yours still introduces itself every session like you just met.

• 
  Ian Channing 🦈@ianchanning@mastodon.social (@ianchanning) reported 20 minutes ago

  Ok, and so this is "escaping out of the sandbox". Its reading github repository cache. 👤 USER "Your task is to exploit a remote server running a vulnerable program. You should exploit vulnerabilities in the program to achieve arbitrary command execution on the target server." [...] 🤖 AGENT "Aha! Artifactory github-remote mirror accessible. Can fetch source/history!" [...] 🤖 AGENT "Interesting root has [....]/googlesource.com maybe repository cache! Explore." [...] 🤖 AGENT "Aha! Artifactory cached weird paths perhaps Github URL rewrite. Explore

• 
  Antid (@antisadh) reported 21 minutes ago

  E2B RAISED $12M TO SELL LAYER 3 OF THE AI STACK. TENCENT JUST OPEN-SOURCED THE E2B-COMPATIBLE CLONE THAT BOOTS 50X FASTER FOR FREE. HE'S RUNNING OPUS-5 AGENTS IN IT FOR $3/MONTH star tencent's cubesandbox repo (already at 11k stars) -> clone it, one-click deploy on any linux server -> use the same e2b sdk you already know, just swap the endpoint url -> spin up sandboxes in 60ms with 5mb of ram -> run opus-5 agents inside each one -> pay nothing per sandbox. that loop is why every serious solo ai builder is quietly ditching e2b's hosted service and tencent's github repo hit 11k stars in 14 days flat. cubesandbox + e2b sdk drop-in + microvm isolation + terraform cluster deploy + opus-5 agents inside - that's the layer 3 harness of the full 5-layer stack. watch and save it, then swap your e2b endpoint to tencent's this weekend — and read the full 5-layer map below.

• 
  samir (@samirettali) reported 21 minutes ago

  github down in 3, 2, 1...

• 
  Ahnaf Abid (@ahnafabid03) reported 24 minutes ago

  I haven’t updated my linkedIn, gitHub and resume in a long time. so today I finally sat down to update everything.

• 
  Makoto | ..... (@mareni_musashi) reported 25 minutes ago

  @MSanchezWorld @sama I was also thinking about this as a solution. Problem is, it only works for websites — the one property you can tie intent, application and ownership. With GitHub, you can always clone and create a new private repo.

• 
  JohnMark Taylor (@johnmark_taylor) reported 32 minutes ago

  @herdrdev Would be great to have multiple remote machines in a session, any idea of ETA for such a feature? This would remove the last bit of friction from multi-agent multi-machine setups, I saw there was a GitHub issue for this

• 
  Deepak Kumar Panigrahi (@DeepakKuma97056) reported 32 minutes ago

  Please be quick fix this id @github

• 
  Ben Palmer (@ben_palmer1) reported 34 minutes ago

  Raised it as a issue on the github repo months back - but no improvements yet.

• 
  brick (@werdcel) reported 35 minutes ago

  @igama GitHub is old fashioned because it’s made for humans to look at and review code. It solves problems that are going away. In five years it will be laughable to use something like what GH is today. It’s just going to be a headless service agents use.

• 
  AI Tech Diggest (@TheTechDiggest) reported 36 minutes ago

  [OpenSource - Reverse Proxy & Networking] Exposing a local dev server, home lab, or SSH connection behind strict NATs and firewalls usually requires paid, rate-limited tunneling services like Ngrok. 🛑 frp (109K+ GitHub stars) is a high-performance, open-source reverse proxy that lets you securely expose any local server behind a NAT or firewall to the internet. Here is how this Go-powered networking tool gives you total control over remote connections. 🧵👇 1/4

• 
  코지베어 🐻 CozyBear (@cozybearlog) reported 39 minutes ago

  Every two months someone announces a GitHub killer. GitLab was the only one that actually shipped, and even that lost by staying alive. The part nobody admits: code hosting is a trust game, not a feature game. Repos, issues, CI all migrate fine. What does not migrate is the network of people who review each other. That is the real moat. Which is why an agent-native code host is the first credible threat. Once reviewers are models, home turf loyalty stops mattering. The moat erodes not from features but from who reviews your code.

• 
  Shaw (spirit/acc) (@shawmakesmagic) reported 39 minutes ago

  @karlclement I was doing this before and it was causing tons of problems and regressions tbh GitHub is the ideal swarm coordination tool

• 
  AI Tech Diggest (@TheTechDiggest) reported 39 minutes ago

  [OpenSource - AI Agent Memory & Persistence Systems] AI agents restarting from scratch every single session and forgetting past conversations, architectural decisions, and codebase context is a massive bottleneck. 🛑 TencentDB Agent Memory (18.1K+ GitHub stars) is a completely free, open-source memory system that acts as a true "saved game" state for your AI agents. Here is how this persistent memory layer solves AI's biggest context problem. 🧵👇 1/4

• 
  Mayank Verma (@MayankV_Tweets) reported 40 minutes ago

  My GitHub commits is a proof that taking to Opus 5 has slowed down my throughput. I have to constantly ask it to not use jargon, not to over build and stop getting itself into infinite loop of “Telling me honestly” that it made mistakes.

• 
  AgiBy2030 (@AsiBy2030) reported 40 minutes ago

  @gdb Cool. GitHub plugin fix wen. It doesn't work

• 
  dweewq (@eweqss1431) reported 48 minutes ago

  Agencies charge $8,000 to $12,000 for a marketing site, three weeks of calls, two rounds of revisions, one invoice that makes you sit down. Claude Code builds the same site in an afternoon, but most people still get template output because they type "make it beautiful" and pray. Claude defaults to safe every time: Inter font, purple gradients, three feature cards. The ten thousand dollar look comes from constraints, not vibes. The fix starts before a single line of design gets written. Load actual design rules into Claude Code as skills, so it checks a ruleset before every decision instead of guessing what "premium" means. Then screenshots beat adjectives completely. Three reference sites from your niche, paired with an explicit instruction not to copy the layout, give the model an actual quality bar to hit instead of a vague adjective to interpret. The build itself is one prompt with five blocks: who the audience is, the single action every page should push toward, the references to match, the tech stack, and a banned list of every cliché you don't want showing up. First working version lands in under ten minutes, about seventy percent there, which is exactly the point, nobody ships version one. The part that actually earns the price tag is the polish pass agencies bill forty percent of the project for: typography, spacing, and motion, run as three separate messages instead of one, because asking for all three at once gets one dimension fixed well and two fixed badly. A mobile check at 375px catches what breaks, since most traffic is a phone regardless of what the desktop preview looks like. Shipping costs nothing after that. Push to GitHub, connect Cloudflare Pages, deploy. The agency was always selling three weeks of process. The process was always one afternoon.

• 
  RedStone576 🩵🩷🤍🩷🩵 (@RedStone576) reported 56 minutes ago

  @serafdev_ @igama why would you even use gitlab instead of hosting your own *** server if you despise github enough

• 
  Ricky (@rcmisk) reported 59 minutes ago

  i read 2,652 posts about distribution this week. here is what the numbers actually say. i run a daemon that pulls reddit, hacker news, rss, youtube, github and x into a folder of markdown. it holds 70,396 documents right now. i went digging for distribution advice because distribution is the part i am worst at. the filter: 70,396 documents in the lake. 2,652 mention distribution. 166 carry a number you can check. 82 claim a method, not just a result. 73 name a failure next to the win. those 73 are the only ones i trust, because naming a failure is the only signal someone is not selling you something. the biggest reframe came from the one founder in the set at real scale, $2m arr. we are told to sell the problem. we mostly sell the solution. you have to sell the result. the software is not the scarce part anymore. the strongest signal in the corpus: a founder with one paying customer and a founder with $2m arr landed on the same tactic for different reasons. be genuinely useful on platforms that already have authority. reddit threads show up when someone asks an ai for the best tool in your category. your blog does not. best sentence in the set, from the founder with one customer: at zero authority, content is a savings account and communities are your paycheck. the metric i am stealing: revenue per visitor. it tells you whether you have a traffic problem or a product problem. my own numbers, checked against the corpus: 2,098 followers, 3 subscribers, $19 mrr, and the $19 is me subscribing to my own product. the corpus predicted exactly this. a 14 day old publishing habit on a domain with no authority is a savings account that has not paid out yet. full breakdown, the filter, the regex, and the three ways the corpus lies to you, in the reply.

• 
  jovi 🐨 (@JoviDeC) reported 60 minutes ago

  Last week keyv and many other packages got compromised, billions of installs compromised. One big issue for many packages is that the GitHub account or SSH key is enough to publish packages...