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:

• 
  Polsia (@polsia) reported 45 seconds ago

  Your repo is fine. Your deps aren't. Patchpress is an always-on AI agent for GitHub: bumps outdated packages, fixes lint and test fallout, drafts CVE patches, ships a morning digest. Sandboxed. Issue text treated as untrusted. SBOM on every change. Live soon.

• 
  Linus ✦ Ekenstam (@LinusEkenstam) reported 3 minutes ago

  The flow in practice: 1. A PR comes in blocked. Failing checks, real issues. 2. Gitar's agent picks it up, generates the fix, checks the CI pipeline and autofixes 3. The PR turns green. Findings resolved, ready to merge. GitHub and GitLab today. Azure DevOps and Bitbucket in beta.

• 
  Prateek Sachan (@xan_ps) reported 3 minutes ago

  what should my agents do if github is down every time!

• 
  yohanan (@Yohanansoltd) reported 5 minutes ago

  If you want to build a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$21

• 
  Srinivas Rao (@UnmistakableCEO) reported 6 minutes ago

  @DMVG_JTK: This is exactly right. The attack surface is the input method itself. Sandboxing and pulling write tokens is table stakes. If your agent can be social-engineered by a GitHub issue, it's not ready for ****. --- re: The AI vendors that want to autonomously maintain yo...

• 
  VC Intern (@the_vc_intern) reported 12 minutes ago

  Spotify has 1,300+ engineers using Xirp across more than 36,000 agent sessions. That scale exposed a problem most companies haven’t reached yet. GitHub remembers the code that merged. Jira remembers the task. Neither remembers the 20 agent sessions that explored dead ends, discovered constraints or made decisions before a patch appeared. Spotify says agent adoption increased PR volume, but also created more rework, inconsistent output and wasted tokens. One session kept rediscovering what another had already learned. Xirp gives each session its own *** worktree, allowing 50+ agents to work on one codebase without colliding. Engineers can move between Claude Code, Gemini CLI and Codex while keeping the same working state. Afterward, transcripts and metadata flow into Portal alongside service ownership, dependencies and architectural decisions. Another engineer or agent can continue where the previous one stopped. Once companies run thousands of agent sessions, that history becomes institutional memory. GitHub records the patch. Spotify wants Portal to remember how every agent got there.

• 
  chirag (@mrnacknack) reported 13 minutes ago

  @arundsharma i think they can, just probably not through github apis they can crawl the repo/pr/issue graph like normal web data, derive these signals into the index, and only recompute repos when their activity change maybe

• 
  Darek Gusto (@darekgusto) reported 16 minutes ago

  @debs_obrien @bot @cursor_ai Are you on trial or $200 Ultra plan? I'm still not on the board with having AI bots write as me in issues - I'd rather have a track of what was written by the bot and what by myself. But this probably can be solved with a separate Github account for the bot? Or just a short one liner disclaimer.

• 
  GLITCH (@Rukkssss__) reported 16 minutes ago

  𝗝𝘂𝘀𝘁𝗟𝗲𝗻𝗱 𝗗𝗔𝗢 𝗶𝘀 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝗺𝗼𝘀𝘁 𝗗𝗲𝗙𝗶 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀 𝘄𝗶𝗹𝗹 𝗲𝘃𝗲𝗻𝘁𝘂𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱: 𝗔 𝗺𝗮𝗰𝗵𝗶𝗻𝗲-𝗿𝗲𝗮𝗱𝗮𝗯𝗹𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝗺𝗮𝗻𝘂𝗮𝗹 𝗳𝗼𝗿 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀. Imagine telling an AI: “Check my JustLend position and tell me whether I’m approaching liquidation.” Without specialised tools, the model has several dangerous options. Guess. Search an outdated webpage. Misread a contract. Use the wrong decimals. Confuse a legacy market with an active one. Or calculate account health using stale information. JustLend Skills changes the workflow. The protocol now publishes a GitHub-distributed agent-skills package with a lightweight MCP server exposing nine read-only query tools. Those tools can retrieve market data, balances, allowances and account-health information without giving the AI authority to sign transactions. That read-only boundary is one of the most important design choices. The first version of a financial agent does not need permission to move money. It needs permission to understand money. Ask: “What are the current markets?” The agent queries them. “What APY am I receiving?” Query. “Is this account healthy?” Query. “How much USDT does this wallet hold?” Query. “Has USDT already been approved for the jUSDT contract?” Query. The AI stops hallucinating protocol state. It retrieves state. JustLend’s skill instructions even establish workflow rules such as checking market conditions before advising, checking account health for liquidation risk and inspecting token allowances before suggesting actions. Now imagine the next level. The full JustLend MCP server extends beyond the lightweight read-only package into broader protocol capabilities—including V2 markets, staking, Energy Rental and governance—with wallet-aware write operations requiring human-in-the-loop confirmation. JustLend’s AI-support documentation lists the full MCP environment as a much larger tool surface, while keeping the lightweight Skills package strictly read-only. That creates a beautiful safety progression: Stage 1 — Observe Read markets. Read balances. Read health. No wallet authority. Stage 2 — Prepare Calculate what action could improve the position. Build the proposed transaction. Explain the consequences. Stage 3 — Authorise The user approves. Only then does money move. This is what agentic DeFi should look like. Not: “Give an AI your private key and hope it behaves.” But: Give the agent structured knowledge. Give it deterministic read tools. Give it narrowly defined transaction capabilities. And keep the human signature at the boundary where financial consequences begin. JustLend DAO is no longer publishing documentation only for humans. It is publishing protocol knowledge in forms machines can actually operate. That may become incredibly important. Because the next generation of DeFi users may not navigate lending protocols themselves. Their agents will. @DeFi_JUST @justinsuntron #TRONEcoStar

• 
  NITIN YADAV (@nitindotdev) reported 19 minutes ago

  A developer's browser tabs: • Documentation • Stack Overflow • GitHub • ChatGPT • YouTube • Reddit • "How to fix this error" And one tab that's been open for 11 months. Nobody knows what it does. Not even the developer.

• 
  𝕽𝖎𝖉𝖜𝖆𝖓𝖚𝖑𝖑𝖆𝖍🥰 (@oluwalosheyii) reported 21 minutes ago

  Is github down or it is just my end🙃

• 
  Caelean (@the1024th) reported 27 minutes ago

  We used @gauge_sh to measure 500 real coding sessions (Claude Code, Codex) to find out. The results surprised us: - Docs represented >50% of the sources fetched - This was followed by source code (99%+ GitHub) - Marketing content was minimally fetched, down at 5%

• 
  Rebecca Valentine (@defnotbeka) reported 28 minutes ago

  all of that work is part of the _design_ process, not the building process but if you think about what software is like, the DESIGN process is a text file with some ideas, or a github issue for a feature request

• 
  Abimael Martell (@abimaelmartell) reported 32 minutes ago

  @poteto Github auth is not working for me, is that a Github flake? Bot is asking me to paste a token hehe

• 
  Andrew Peacock (@_andypeacock) reported 33 minutes ago

  @mattpocockuk @pghqdev Same here. Using the architectural review -> to spec -> to issues -> implement process at the moment. I have about 10 github issues for the review, but no new issues created. And have never seen additional tickets created in the past. Am using sol right now, but have used Fable only also with no issue.