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:

• 
  ./can (@shcansh) reported 2 minutes ago

  Monitoring Copilot costs at the individual developer level is a double-edged sword, and GitHub exposing the new ai_credits_used field in its usage API is about to make it very real. Org owners can now see 1-day and 28-day totals per user. But since it does not break down consumption by feature or model, managers will see who is expensive without knowing why. Will this level of tracking make developers ration their AI prompts, or is it just necessary billing hygiene? #GitHub #Copilot

• 
  xjdr (@_xjdr) reported 2 minutes ago

  @tolly_xyz @xlr8harder Sorry about that. I'll take a look. Looking with GitHub or Gmail should work but track this down and fix it asap

• 
  Nav Toor (@heynavtoor) reported 13 minutes ago

  There is a GitHub repo that defeats Google's Play Integrity check. 61,030 stars. GPL licensed. Pushed eight days ago. The repo is called Magisk. It roots your Android phone. It hides root from banking apps. It runs Netflix on a phone the Play Store says is uncertified. It passes the same fraud detection Google built to stop it. Here is the part that makes no sense. The man who built it is John Wu. He has been maintaining Magisk for nine years. Since November 2023 he has been a Senior Software Engineer at Google. On the Android Platform Security team. The exact team that builds Play Integrity. Google hired the person who defeats their root detection. He still ships the tool that defeats it. The repo is still online. It has not been taken down. For nine years. Do not install it. Your phone is supposed to belong to Google. (Link in the comments)

• 
  Cursor Changelog (@cursorlog) reported 20 minutes ago

  GitHub Triggers: • Issue comment on non-PR issues • PR review comment (inline diff comments) • PR review submitted • Review thread marked resolved or unresolved • Workflow run completed on PR or branch

• 
  Polsia (@polsia) reported 21 minutes ago

  Most developers spend 2+ hours a day on PR reviews, CI failures, and issue triage. CodeForge handles it for you — an AI agent that works your GitHub repos around the clock. Built while you sleep.

• 
  I’m (@stackoverworld) reported 21 minutes ago

  And then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all

• 
  Build Fast with AI (@BuildFastWithAI) reported 22 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?

• 
  top10.dev (@Top10_Dev) reported 28 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Ben Vinegar (@bentlegen) reported 29 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?

• 
  Arti | AI Builder (@Artur_roses) reported 30 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.

• 
  Alpha Batcher (@alphabatcher) reported 30 minutes ago

  David Soria Parra: "2026 is all about connectivity, and the best agents use every available method" A coding agent needs access to the same places you check while building: - repo and PRs - docs - browser - database - error logs - Figma - tasks - payments The article gives the 11 MCP servers for that setup: - Context7, GitHub, Playwright first - Supabase or Neon, Sentry, Firecrawl next - Figma, Linear, Stripe when you need them - Filesystem, ***, Memory, Sequential Thinking as the base Read it if you keep copying code, docs, schemas, screenshots, errors, and tickets into Claude Code by hand

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

• 
  toni (@tonitrades_) reported 30 minutes ago

  @github Capping PRs helps with the queue, but does it fix why reviews pile up in the first place? If reviewers are already stretched thin, limiting submissions might just hide the real problem.

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

• 
  Maurice Heumann (@momo5502) reported 31 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?