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 (70%)
• Sign in (17%)
• 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	14 days ago
Trichūr	Errors	17 days ago
Brasília	Sign in	18 days ago
Lyon	Website Down	18 days ago
Tel Aviv	Website Down	21 days ago
Rive-de-Gier	Website Down	21 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:

• 
  MarMar Labs (@MarMarLabs) reported 3 minutes ago

  "Start over from a screenshot." That phrase has defined the worst seam in product work — the design-to-code handoff — for years. This week it quietly stopped being a translation problem and became a sync problem. Anthropic shipped a Claude Design update (June 17) worth reading even if you never open the product, for the mechanism: → Import your design system from a GitHub repo (or design files / raw uploads) → Claude builds with YOUR components, checks its output against your design system, and corrects before you see it → /design-sync pulls your system in; hand off to Claude Code and it continues from your actual work "instead of starting over from a screenshot" → /design lets you create, edit, and sync design projects from the terminal The headline isn't "the model draws prettier buttons." It's grounding + self-verification against a source of truth you control. Same shape as the rest of 2026's agent releases: the win isn't generating more, it's grounding output in something you own and checking against it. The uncomfortable builder takeaway: Getting AI to ship production UI isn't a prompting problem. It's whether your design system is a clean, importable, machine-checkable artifact. The moat moves from "can the model design" to "is your source of truth importable and checkable." If you build product: could an agent import your design system and grade itself against it today — or does it only live in a Figma file and three people's heads?

• 
  Axe Ghost. Now with Fragments mode🌟 (@axeghostgame) reported 5 minutes ago

  graph in the OP is built from data around the Godot repository from github. it confirms Godot's PR backlog is up and external contributor quality is down. the narratively complicating thing is that both trends significantly predate ai tool availability.

• 
  Financial Programmer (@RBiancoUS) reported 5 minutes ago

  A dose of reality for end of week. My biggest question is I can't find any reason for the $Gold panic- did they find gold is causing cancer or radioactive? Selling looks like sheer panic. Would you believe someone asks in DM, so how did *you* get so many followers. Then he lets me brew on it for a day and comes back, I was joking do you have a github, presumably to get some code. No wonder I worked alone. I'm challenged socially guess not alone. After a night of 3 scammers one from Nigeria, one Africa. I need to lock dm down or find a way to restrict

• 
  Build Fast with AI (@BuildFastWithAI) reported 9 minutes ago

  The hardest part of building AI agents in 2026 isn't writing the code. It's knowing what your agent actually did. Your agent made 40 tool calls, called 3 LLMs, hit a rate limit, retried twice, and returned a wrong answer. Which step broke it? Without observability you're reading logs and guessing. This is what Laminar is built for. Open-source observability platform purpose-built for AI agents. One decorator. Full trace of every LLM call, tool execution, and custom function - automatically. What makes it different from generic APM tools: SIGNALS - describe failures in plain English. "Agent deleted a file it wasn't supposed to." "Tool call returned an empty result." Laminar reads every trace and produces structured events you can query, cluster, and alert on. No regex. No custom parsers. DEBUGGER - reproduce any agent run from any point in the trace. Swap the model. Change the prompt. Compare results side by side. You don't re-run the whole pipeline to test one step. EVALS IN CI - run evaluations against datasets locally or in GitHub Actions. Catch regressions before they ship. INTEGRATIONS - works with everything you're already using: LangChain, LangGraph, Vercel AI SDK, Anthropic, OpenAI, Browser Use, Stagehand, Pydantic AI, OpenRouter, LiteLLM, Mastra, Temporal, Playwright. One import. Full traces. Plus: raw SQL access to all your trace data, full-text search, MCP server to query traces directly from Claude or Cursor, PII redaction, and self-hosting if you need it. Open-source. MIT license. GitHub: lmnr-ai/lmnr. If you're running agents in production and you're not tracing them - you're flying blind. What's your current setup for debugging agent failures?

• 
  xjdr (@_xjdr) reported 11 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

• 
  Nirvaan rohira (@nirvaan_rohira) reported 13 minutes ago

  PewDiePie shipped Odysseus to 110 million people who don't care about local LLMs. They care that Claude costs money. 30K stars in 48 hours because every self-hosted project before this one started with "you want local LLM, right?" This one started with "here's a free workspace that works." Friction was never technical. It was the asking. Now watch what happens when a hundred thousand people who've never touched open source start running inference on their machines. The real distribution problem wasn't GitHub. It was YouTube. That's not a product launch. That's a category shift.

• 
  Anomaly (@theanomalyai) reported 14 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)

• 
  Nitesh (@NiteshTechAI) reported 14 minutes ago

  This repo should not be free. private-gpt turns any local model server (Ollama, llama.cpp, vLLM) into a Claude-compatible API. Build private AI apps where zero data leaves your machine. ↳ 57,236 stars on GitHub ↳ RAG with citations and MCP connectors built in ↳ follows the Claude API spec: streaming, batch, tool use, extended thinking ↳ official integration guides for Claude Code, Claude Desktop, and Microsoft 365 But it is free. 100% open source, Apache 2.0. v1.0.0 shipped 9 days ago. The viral 2023 script quietly became production software. 🔗 GitHub link in the comments 👇

• 
  Rohan (@proxy_vector) reported 15 minutes ago

  @aminnnn_09 Fork = a server-side copy under your GitHub account. Clone = a local copy on your machine. You fork when you need your own remote lineage, and clone when you want to work on code locally.

• 
  Vishal Tiwari (@VishalTiwa91817) reported 16 minutes ago

  @AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.

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

  Claude Code just closed a GitHub issue, wrote the tests, passed CI, and opened a PR. No human touched the keyboard. This isn't AI autocomplete. The dev loop just got rewritten.

• 
  DFIR Radar (@DFIR_Radar) reported 20 minutes ago

  AutoJack: a three-flaw chain in AutoGen Studio's MCP WebSocket lets a malicious webpage rendered by a local browsing agent spawn arbitrary processes on the developer's host with no user interaction beyond visiting a URL. Key findings: - Three weaknesses chain together: Origin allowlist bypassed because the agent's headless browser is localhost (CWE-1385), auth middleware explicitly skipping /api/mcp/* with no handler picking up the check (CWE-306), and server_params decoded from the URL passed verbatim to stdio_client as a command line (CWE-78), accepting calc.exe, powershell.exe, or bash as valid "MCP servers" - Attack flow: attacker page serves JavaScript that opens ws://localhost:8081/api/mcp/ws/?server_params= with a base64 payload, agent's MultimodalWebSurfer renders it, AutoGen Studio spawns the command under the developer's account, no token required regardless of auth mode configured - Affected code never shipped in a PyPI release; exposure limited to developers who built from the main GitHub branch before hardening commit b047730, which adds server-side parameter binding via a POST/UUID flow and removes /api/mcp from the auth skip list - Broader pattern: any agent that browses untrusted content and shares a host with a privileged local control plane dissolves the loopback trust boundary, this is not specific to AutoGen. #DFIR_Radar

• 
  Blum (@Blum_OG) reported 21 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

• 
  Alexey Samoylov (@metalagman_dev) reported 24 minutes ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  Elvis Irhaye (@viii_fn) reported 25 minutes ago

  Is GitHub down or it’s just MTN trying to ruin my career?

• 
  Grishin Robotics (@GrishinRobotics) reported 26 minutes ago

  AI made coding faster. Devplan raised $2.5M to fix the coordination drag that shows up after the code is written. AI2 Incubator led the seed round, with Acequia Capital, Mighty Capital, Grand Ventures, and eLab Ventures participating. Chris Bee and Anton Safonov are building Weaver, a product knowledge graph that connects GitHub, Jira, Linear, Slack, Notion, Google Workspace, meeting notes, and customer feedback. The pitch is that product and engineering leaders should not need another status meeting to learn what changed, what slipped, or why a decision was made. This is a different wedge from coding copilots. Devplan is going after the organizational memory around the code: requirements, risks, decisions, blockers, and customer signals. The company says early users save eight hours a week on coordination, and its own benchmark answered moderately complex queries almost 2x faster and more than 3x cheaper than a standard Claude plus MCP setup. Quick facts👇 ● founders: Chris Bee; Anton Safonov ● total capital raised: $2.5M disclosed ● HQ: Seattle, Washington ● Investors: AI2 Incubator; Acequia Capital; Mighty Capital; Grand Ventures; eLab Ventures The next productivity bottleneck may be less about code generation and more about whether teams can keep shared context intact while AI speeds everything else up.

• 
  Maurice Heumann (@momo5502) reported 30 minutes ago

  @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

• 
  Asad (@meranaamkhann) reported 33 minutes ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  TECHEPAGES (@techepages) reported 33 minutes ago

  🎣 "GitBait" phishing campaign uses GitHub Pages & Google Sheets to steal banking credentials from 12+ Mexican financial institutions; no server infrastructure required 🔹 Fake bank pages hosted free on GitHub, stolen data piped straight to Google Sheets via SheetBest 🔹 100+ GitHub domains found; victims likely lured via WhatsApp, Telegram & SMS links with bank-branded previews 🔹 Active for ~3 years with ongoing development (66+ commits on one repo alone)

• 
  Kevin Tabet (@TabetKevin) reported 35 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

• 
  rapaya (@rapaya) reported 43 minutes ago

  OpenCode connects to LSP so the AI gets your actual compiler diagnostics in real time — type errors, warnings, the full signal your editor sees. Terminal-based, 75+ model providers, 160K GitHub stars, open source.

• 
  Nikolay Konovalov (@br11k_dev) reported 45 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.

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 48 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

• 
  Cursor Releases (@cursorreleases) reported 50 minutes ago

  New GitHub triggers: - Five new triggers: issue comment, PR review comment, PR review submitted, review thread updated, and workflow run completed. - New Marketplace templates added for triaging failed GitHub Actions and auto-fixing PR review comments.

• 
  Ben Vinegar (@bentlegen) reported 51 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Rich Kuo (@richkuo7) reported 52 minutes ago

  i use this in my claude.md for my open source project as long as the agent follows it, i have some reference for quality and keeps PR's clean LLM: <model> | <effort> | Harness: <action> - Final line of the artifact; occupies the default Claude Code attribution slot. - No Co-authored-by / Co-Authored-By trailer. - <model>: actual model (e.g. Opus 4.8). - <effort>: medium/high/xhigh, default high. - <action>: Claude Code for interactive sessions, else the skill/agent that ran (e.g. commit-push-pr, agent). - PRs: reference the issue with Closes #<N>; in GitHub comments use 1. not #N for list items (avoids auto-linking).

• 
  Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported 55 minutes ago

  Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax

• 
  Namespace (@namespacelabs) reported 55 minutes ago

  Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs were stalling. We reached out to work on the problem together and had a fix in under an hour. The @github team was ready to help. We just had to ask.

• 
  Kashaf (@noor36758) reported 57 minutes ago

  @PiyuCodes GitHub is literally a CS/engineering tool... if it gets banned that's your problem too 💀

• 
  Threadripper (@threadripper845) reported 59 minutes ago

  Nobody: Me: I'll gladly accept this high-responsibility open source maintainer role for zero compensation. Now I spend my weekends answering angry GitHub issues from developers who don't know how to read the README file.