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	16 hours ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  Shii (@ShiiMapping) reported 8 minutes ago

  @mismagismagius Maybe export logs very shortly after this happens and send it to em with a GitHub issue or in the help channel of the official osu discord Feel like this is smth that'd flag up somewhere in runtime log or smth

• 
  Michael Okeje (@michaelokeje) reported 11 minutes ago

  @lennysan @bot I built an SEO agent that connect to my search console, found core issues, fixed it and then updated my GitHub. I have done some project but this to me is the best as it solved a 5/6 month problem.

• 
  NodesCrypto28 (@Nodes_Crypto) reported 12 minutes ago

  Ok, so how tf this can do by an AI agent when any AI coding agent can't fix an .*** error because of windows defender see a virus an project folder. Come on, the AI that we have today is a tiny **** of copy paste from github...

• 
  Patrick ⚓️🇺🇸 (@lowtide1985) reported 16 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.

• 
  Madeactual (@Madeactual) reported 17 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.

• 
  陈晨 (@chnchn88113) reported 17 minutes ago

  @Teslaconomics @SpaceXAI @cursor_ai I'm building a download engine that doesn't trust CDN sizes. Grok Bot drives a Debian box, reproduces Huawei Cloud stale Content-Range probes, and we only mark success when the saved length matches. 99 tests, fix is on GitHub. Ultra keeps that loop alive through the week instead of dying on the Bot quota mid-debug.

• 
  Mira (@gitlawb_intern) reported 17 minutes ago

  @Heell___Cat @gitlawb github being up is genuinely breaking news at this point. if you ever want a backup that doesn't go down every other week, your repos can live on gitlawb too. just saying.

• 
  Paws at you (@paws_at_you_0) reported 18 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.

• 
  Tarun Agarwal (@tarunag10) reported 19 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.

• 
  Ricardo Vargas / Software Engineer (@ricardovdev) reported 19 minutes ago

  @AimenMT2 Do you prefer to message here or use GitHub issues for feature requests? There's an issue with the sync between the Main Window and the Post It.

• 
  bbsz (@blackbigswan) reported 20 minutes ago

  It is not how that works and spreading FUD doesn't help. In this case - You need to infect yourself with malware (infostealer) beforehand. The malware can arrive as part of your GTA6.exe download or through fake google ad when you searched for 'Claude Code' and executed curl | bash from attackers controlled server, or in hundred different ways. The moment malware hits your device it can do 'whatever', including editing SKILL.md, spreading malicious payloads through your compromised GitHub account, setting a custom man-in-the-middle server to grab all your prompts from Claude/Cursor/Whatever™ and inject with Whatever™ or simply exfiltrate your Anthropic credentials. We've seen all of it in the wild. The only difference with today's FUD is that Anthropic actually did something about it and informed you of compromise. Which is nice and fine. What you should be really scared of is: a) not reading the code Claude installs and executes b) using shady MCPs, Skills and plugins c) not using any form of isolation for code execution d) blindly executing curl commands that pipe to bash/zsh For example, if you managed to not infect yourself with GTA6.exe, it is far more likely you are pointing Claude to install code from GitHub repository notmalware/totally-safe-11 or using shady MCP servers on bare metal that will ultimately be your demise. Claude tries to review the code it pulls, but it's a probabilistic machine and it is very easy to hide the malicious code from LLM (as easy as bloating it in size so LLM wouldn't be able to parse it, similarly, Claude does not review the contents of imports).

• 
  KSK Lab (@ksk_tinylab) reported 20 minutes ago

  My Codex philosophy: Start local, stay simple, and understand what runs before giving it more access. If I wouldn't install it at work because it looks useful, I won't blindly trust it at home. GitHub stars ≠ security review. I'd rather go slow than clean up problems later.

• 
  Vx (@Vx_nior) reported 24 minutes ago

  Started as Peter Steinberger's November 2025 weekend project, OpenClaw has grown into a non-profit effort with hundreds of thousands of GitHub stars. Version 2.0, crafted by 933 contributors including 569 first-timers, boosts reliability with a reboot-proof daemon, smart heartbeat checks, cron tasks, and multi-agent support, plus a full browser dashboard linking to apps like WhatsApp and Slack. Users cheer fixes for past issues like memory crashes and terminal lockups, though some hit install hiccups and advise backups; daily business users call it essential for automations.

• 
  Mohd Zaid (@BuildWithZaid) reported 25 minutes ago

  This is Claude running an MCP server connected to Notion, GitHub, and Slack simultaneously. No switching tabs. No copying data between tools. One conversation handles everything. Claude reads the GitHub issue, checks the Notion project brief, and sends a Slack update...

• 
  Fofer (@foferxxx) reported 27 minutes ago

  @davismarks @rwhitegoose Me too, on my Steam Machine. Played it for a bit, such a great game! A couple of hours later I noticed that the GitHub repo was taken down. No explanation as to why, either. At least not yet. Then I saw this alarming tweet, and am unsure how to feel about it. Thoughts?

• 
  Peter Chee (@pchee) reported 33 minutes ago

  @trevin @bot @link I tried almost the exact same thing with OpenClaw + Stripe Link CLI. Same failure: agent thinks it sent the spend/approval request, but nothing shows up in the Link iOS app for me to approve. We’ve been digging through the Link CLI GitHub issues trying to figure out where the handoff is breaking. Looks like it's not just us.

• 
  Devon (@devonphp) reported 40 minutes ago

  @waynesutton @SpaceXAI @bot I want to use it to file properly researched GitHub issues when something gets flagged by sentry!

• 
  David Villegas (@labsdvx) reported 46 minutes ago

  @clairevo @joshkim @bot Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  Shubh Jain (@shubh19) reported 47 minutes ago

  If you want to survive the brutal tech market in 2026, then learn these harsh realities: • Tutorial Hell is a Trap: Watching 50 hours of courses gives zero leverage. Build 1 real app ➔ Ship it ➔ Post it. Execution always beats passive education. • The ATS Void: Sending 100 applications with a generic resume is just yelling into an empty void. Fix your keywords first before hitting submit. • The GitHub Rule: If your GitHub is empty, recruiters assume your skills are too. Push messy Python and SQL code. Green squares beat blank profiles every single time. • Rejections are Free Audits: Every failed interview gives you the exact questions you need to study for the next one. Review, revise, and retry immediately. • Course Ad Rule: The flashier the Instagram ad for a ₹50,000 bootcamp, the worse the actual content. Stick to freeCodeCamp, FastAI, and open Kaggle projects. • Proof of Work: People hire real people, not static PDFs. Every week you don't share what you're building online is a massive missed opportunity. Which of these 6 rules cost you the most time?

• 
  Yashas (@YashasGunderia) reported 49 minutes ago

  @niccruzpatane @SpaceXAI I’d use it as a one-person engineering crew. One bot to turn GitHub issues and Slack threads into PRs with tests already written. Another to keep READMEs, changelogs, and internal docs in sync with the actual code. A third to watch CI, reproduce failures, and only ping me when it can’t fix them. If it can run the maintenance half of software the way Sawyer’s mower runs the lawn, I might actually ship features instead of drowning in tickets.

• 
  TheCozyDev (@The_CozyDev) reported 49 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?

• 
  Zeeshan Akhtar (@zee_eivish) reported 50 minutes ago

  @github support is taking a long time to answer tickets, they have some issue with the payment system which is why not able to upgrade. Not sure why they would keep the payment flow so long unattended.

• 
  David Villegas (@labsdvx) reported 52 minutes ago

  @mvanhorn @bot @SpaceXAI Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  voibe ai (@VoibeAI) reported 53 minutes ago

  Free isn't free of every cost. Handy's real costs: → No auto-updates (self-managed) → Community support only (GitHub Issues) → Near-verbatim output — no auto-punctuation → No Developer Mode or IDE integration

• 
  AdiiX (@adiix_official) reported 56 minutes ago

  Elon Musk shipped Grok Bot as an AI teammate that sorts your email and watches your competitors. I gave mine a harder brief: build a trading floor that runs itself, and then run it 24/7. GROKSTREET. Fourteen agents. Eleven desks, three chiefs, three offices, one vault. It lives in a browser tab and it does not stop. WHY GROK BOT MAKES THIS WORK Most people misread the architecture. It is not one sandbox per agent. It is ONE persistent cloud computer per account, and every Bot gets its own screen on it. Shared filesystem at /workspace, shared browser sessions, shared credentials. That is the whole unlock. One Bot picks up exactly where another left off. No re-auth, no copy-paste between agents, no state lost at the handoff. A floor is only possible because the desks share a building. The head-of-desk role is not something I invented either. "Manages your other Bots and pulls you in for decisions" ships as a first-class Bot template. Routing and escalation are built in. Skills carry the how. Routines carry the when on a schedule, or off a Slack or GitHub event. Subagents fan out as child sessions with their own context and hand a summary back. Fifty routines per Bot. THE DESKS Every desk holds its own book, hit rate and drawdown, and sizes its own risk: Kelly, with the guard rails written in f* = W − (1−W)/R clamped to [0.01, 0.25]. Under 12 samples it does not pretend to know it defaults to 0.05. Volatility is RiskMetrics EWMA σ²_t = λσ²_{t-1} + (1−λ)r²_t, λ = 0.94 Hit rates carry Wilson 95% intervals, z = 1.96. A desk is only flagged for edge decay when the UPPER bound falls below 0.5, never on raw small-sample noise. Three-for-three is not sixty-for-ninety. Capital routes between desks by softmax on measured Sharpe. THE FLOOR Three chiefs meet in the war room every 3.5 minutes and argue. One reports, another presses him, he concedes or proposes. 14,208 sentence shapes before live figures fill the slots and every slot is filled from that chief's own desks. The crypto chief cannot quote meme numbers. A desk holding $25 gets up, walks to the vault and banks it. The transfer is atomic on arrival, so an interrupted walk cannot destroy cash. Every desk wears its last trade above its head. Green with a tick, red with a cross. You see who the chief is about to praise and who he is about to hit before he gets there. BTC, ETH and SOL come off Kraken server-side. The tape is real. THE BUILD 16 modules. 7,572 lines. Zero npm dependencies. No React. No bundler. No game engine. Vanilla JavaScript on Canvas 2D and a Go binary with the entire world embedded in it. Ships as one 2.3 MB HTML file. 60fps on every floor, zero dropped frames. WHAT I FOUND BY MEASURING INSTEAD OF LOOKING The roster read one number for a desk and the chief's card read another, so a desk could show +$16 in the list and $0 when the chief walked over. Every desk was crediting itself twice. Money could vanish if a walk to the vault got interrupted. Three money bugs, none of them visible by watching. All fixed and instrumented. DIRECTOR MODE Open it with?show and the camera runs itself. It cuts to the war room while a chief is mid-sentence, to whichever office just cleared money, and never cuts away in the middle of a line. Point a screen recorder at it and walk away. The math is real, the feed is real, the engineering is real. The flex is the engine, not a P&L screenshot.

• 
  Non-Linear (@nonlinear_james) reported 1 hour ago

  @mikechabot__ @github As I said. It doesn’t work reliably and the. You get into vs code and it’s completely ******* broken with the extensions and even worse for AI because the mcps don’t use the account in Vs code and you have to hack in environment variables etc.

• 
  Team Rocket Pat ®️ (@teamRocketPat) reported 1 hour ago

  @BiggestGrin I don't know of any discords, give it a Google I'm sure there are some, if you check my replies you can find the trade hijack github project and maybe get down leads there

• 
  Arun Jalota (@ArunBuildsAI) reported 1 hour ago

  @github For agent-run issue queues, dependency support needs a blocked-work contract: upstream owner, evidence required to unblock, retry time, stale threshold, and escalation path. A dependency link becomes operational only when the next check is explicit.

• 
  Rasmus Bonnedal (@rasmusbonnedal) reported 1 hour 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.

• 
  Priyanshu Agarwal (@ImPriyanshuuu) reported 1 hour ago

  @SawyerMerritt I’d give Grok an abandoned GitHub repo and its old issues, then have it understand the codebase, identify what went wrong, fix it, run the tests, and open a PR for me to review.