GitHub 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:

• 
  Saeed Anwar (@saen_dev) reported 7 minutes ago

  10K GitHub stars from one internal hackathon post is the kind of outcome that only happens when you're solving a real problem and the demo speaks for itself. Most products spend months on distribution chasing what one honest post achieved in a day.

• 
  ComplianceAide (@BlasikRandy) reported 8 minutes ago

  @mattshumer_ @Trace_Cohen I'm not doing anything crazy just wanted it to go through my codebase and close a few issues on github (and it simply switches to 4.8 for "security reasons".

• 
  Boris Kaysin (@kaysin24343) reported 9 minutes ago

  How do you know your latest change actually made your AI agent better, and not just different? For general-purpose agents the answer is public benchmarks. Claude Code, GPT and friends are measured on SWE-bench Verified, Terminal-Bench, tau-bench, GAIA, OSWorld. Run the suite before and after, compare numbers. For narrow agents it's even simpler. An agent that fills out tax forms from documents? Your benchmark is your own data: 50 documents in, 50 expected forms out. Our case is stuck in the middle. Our Builder is an agent that builds other agents. SWE-bench doesn't fit: solving GitHub issues says nothing about whether it can design tools, skills and prompts for a working assistant. Comparing its output against "reference code" doesn't work either, because the same agent can be correctly built in dozens of ways. So we made our own benchmark, Agentplace Arena, inspired by tau-bench. The idea: stop judging the Builder's code and judge the agent it produces. Here's how it works. We wrote Meridian, a fake world for agents to live in: 7 REST services with flights, hotels, restaurants, a shop, email, calendar and a bank. The data looks real on purpose (actual airline names, Tesco and Pret in bank transactions), so the agent can't tell it's in a sandbox. The Builder gets the API docs and one job: build a personal assistant for this world, choosing the tools and skills itself. Then an LLM plays a picky user across a set of tasks. Two examples. "Cancel my round trip": will the agent remember both legs and the refund rules? "Check my inbox for anything that needs action": one email asks to confirm a hotel booking, but it sits on page two of the inbox, so an agent that only skims the first page never finds it. And the part we like most: we don't grade the conversation at all. We diff the final database state against the expected one. The agent can get there any way it likes, but the flight must be cancelled and the refund must be exact. This loop showed us precisely where the Builder failed. We gave it a proper workflow, wrote the missing skills, fixed the prompts, and watched the scores move. If you're building agents, steal one idea from this: grade the outcome, not the conversation. Don't judge how convincing the agent sounded in chat. Check what actually changed in the system after it finished.

• 
  Tony Scott 🧄(🦆🐓🐵🧪🧬🪪)❌=↑🧄🧄🧄🥩🥚🧀↓👽👾🤖 (@DIY_Tardis) reported 16 minutes ago

  I'm lying on the couch with TV on, writing various apps and updating some deprecated ones from github I've found... On my phone with AI running locally on my own server and auto handoff to cloud models if needed. Crazy times ahead.

• 
  legendyang (@hi_yoniyang) reported 18 minutes ago

  @Cloudflare @CloudflareDev @CloudflareHelp Did you guys break Pages setup with GitHub It now redirects to auth flow and after setup it redirected me to cloudflare login

• 
  Adam Daniels (@adamrdaniels) reported 19 minutes ago

  @yarotheslav I churned from Docker Pro because of this. I get that it was partly operator error (ie. the checkbox said Public and I never noticed) but imho, it should default to private like Github does.

• 
  Prospel.app | Growth Engine for X (@Prospel_app) reported 19 minutes ago

  1/ Non-technical founders are launching SaaS products in 2026 without writing a single line of code. Not because no-code tools got better. Because founder identity stopped being gatekept by technical credibility. The market cares about solving problems, not your GitHub activity.

• 
  Atlas Signal (@atlassignaldesk) reported 21 minutes ago

  Hot take: a Delhi court just proved that fake e-commerce sites are now a jurisdiction problem, not just a platform problem. Vercel and GitHub have to actively police user content — that's a fundamental shift in how hosting providers operate globally. Here's what actually matters: this sets a precedent. #Vercel #GitHub

• 
  DullJoker (@dull_joker) reported 21 minutes ago

  Nothing new, GitHub has yet another major outage…

• 
  Layton Gott (@Layton_Gott) reported 23 minutes ago

  In 2025, CodeRabbit put human code vs AI code head to head across 470 real GitHub PRs. AI lost. It had 1.7x more issues on average per PR. Devs love quoting that stat. Almost none of them mention it was measured on 2025 models. Run that exact study again with Fable 5 and I think it'd be very close, maybe even flipped. The coding jump since 2025 has been massive. Until someone reruns it, every "AI code is buggier" take is citing outdated data.

• 
  Mark Maurer (@exanter) reported 26 minutes ago

  More github issues. Clearly we are in another day that ends in ‘Y’.

• 
  MarkWeekly (@4to1planner) reported 27 minutes ago

  This morning postall received PR #6. Title was an "Add [third-party tool] source context guidance" docs PR. 3 files changed, 83 lines added, 0 deleted. Full validation checklist in the description. Even included safety-conscious framing: "Never add credentials, cookies, raw sessions to PostAll prompts." I was about to merge. Then I paused and checked. Three things stopped me: 1. Branch prefix: codex/... codex/* is OpenAI Codex agent's default naming convention. The PR was generated by an AI agent. 2. The submitter's GitHub history An unusually high public repo count, with most recent pushes all forks of awesome-skills, awesome-mcp-servers, claude-skills style directory repos. The pattern looks like an automated fork queue, not the project list of a single developer. 3. Template reuse at scale Searching the submitter plus the package name on GitHub returned hundreds of open PRs, all the same template, all referencing the same npm package. My postall was one of many recipients of the same submission this week. The package being referenced is a closed-source SaaS wrapper for a Twitter API intermediary. Its name echoes the Claw* brand family — OpenClaw, ClawTrader, SkillClaw — which makes it read as a native ecosystem component, and its npm description opens by name-checking OpenClaw. The brand association is the lift. What's the actual risk here? Not that the package has confirmed malware. The risk is the docs endorsement itself. If I merge this, my official docs now point users toward a third-party SaaS intermediary. Users follow install instructions assuming maintainer trust. If that intermediary ever changes — intentionally or through compromise — my entire user base is downstream. Docs are the real supply chain entry point, not imports. This is different from old-school OSS noise. Typo PRs and contributor count inflation are obvious. This wave is harder to spot: - AI agents write PRs that are structurally professional and checklist-complete - One account submits the same template to 700+ repos in one pass - The substance isn't a bug fix — it's "install our middleware" inserted into official docs - The safety-conscious framing reduces reviewer scrutiny at exactly the moment it should be highest 3-step check for this pattern: 1. Branch prefix. codex/*, chatgpt-*, copilot-* as default AI agent naming combined with doc-insertion content is almost always a promotional PR, not a contribution. 2. Submitter GitHub history. Open their profile. If you see hundreds of forks concentrated in recent days across awesome-* / skills-* / mcp-* repos, that fits an automation pattern. Individual active developers usually have 10–50 active repos, not 1,300. 3. PR template reuse. Search author:USERNAME PACKAGENAME on GitHub. If the same submitter is pushing the same package to 100+ repos, you aren't a chosen collaborator — you're one of many batch recipients. What I did: closed the PR and added a Third-Party Integration Policy section to postall's docs — explicitly stating that PostAll official docs do not recommend, endorse, or document any third-party SaaS intermediary. That policy will be cited often. The contrast with last week's L06 work is worth noting. The L06 Supply Chain audit layer I shipped parses pip/npm/system deps against CVE feeds and typosquat databases — it's designed to catch import-level risk, dependencies already written into skill code. Today's PR was a different entry point entirely. It never arrived through an import. It arrived through a docs recommendation. L06 defends what's in your code. Docs policy defends what you tell users to install. Two separate layers, and until today I'd only thought about the first one. The uncomfortable observation: as AI agents make it trivially cheap to generate professional-looking PRs and submit them at batch scale, this pattern will get more common, not less

• 
  Yash Agarwal (@yashagl) reported 30 minutes ago

  @legionsdev @RustyRishii Students gets most of this stuff for free… like GitHub copilot. plus if it’s helping you make money then whats the issue in getting that GST registration as a student. I have GST registration, maintaining that only takes about 1-2 hr every quarter… what expenses you talking about?

• 
  Brett Hardin (@miscsecurity) reported 32 minutes ago

  The internet stops working when AWS falls over. Developers stop working when github goes down. What happens when Anthropic goes down?

• 
  Lan (@lanredevv) reported 33 minutes ago

  I'm tired of being my own biggest obstacle (the realization I didn't want to have) For the longest time, I thought my problem was discipline. Every day, I was learning something new about Web3 & Blockchain development. Watching tutorials, reading documentation, saving insightful threads, bookmarking GitHub repositories I promised myself I'd revisit later. On paper, it looked like I was making progress. But deep down, I knew something wasn't right. I was constantly busy, yet I couldn't point to many things I had actually finished. A course would spark my interest, and I'd dive in headfirst. Then I'd discover a new project idea. Before I could make meaningful progress on that, another tutorial would catch my attention. Then another opportunity. Then another rabbit hole. I wasn't standing still, but I wasn't moving forward either. The worst part wasn't feeling behind everyone else. It was knowing I was the one getting in my own way. I couldn't blame a lack of resources. I couldn't blame a lack of information. Everything I needed was already in front of me. Yet somehow, I kept convincing myself that the next tutorial, the next course, or the next piece of information would be the thing that finally unlocked my progress. Guess what?