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:

• 
  swisscheese (@swisscheese4299) reported 2 minutes ago

  @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

• 
  MarMar Labs (@MarMarLabs) reported 6 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?

• 
  Kashaf (@noor36758) reported 6 minutes ago

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

• 
  AI Crave (@wecraveai) reported 7 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  naimeh (@naimeh70) reported 8 minutes ago

  @Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.

• 
  Crystalwizard (@crystalwizard) reported 8 minutes ago

  how about you now fix the false positive triggers - i put in an issue about this on github yesterday, and discovered there were already a number of other identical issues - from other people, that had been opened for a while now and that are being 100% ignored

• 
  SOURAV PANDA (@i_d_skp) reported 10 minutes ago

  Scenario: You accidentally committed a plaintext database password to GitHub in a .tf file. Fix: Nuke the commit history immediately! Use environment variables (TF_VAR_db_pass) or fetch secrets dynamically at runtime from AWS Secrets Manager or HashiCorp Vault. 🔑 #Terraform

• 
  Alpha Batcher (@alphabatcher) reported 12 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

• 
  revayz (@0xrevayz) reported 14 minutes ago

  Andrej Karpathy: "90% of Claude's mistakes come from missing context, not a weak model" Without CLAUDE.md the mistake rate is 41%. With proper rules it drops to 3% You don't need a better AI. You need better loops Most people still prompt one task at a time and fix the answers themselves. That means the human is still the loop Boris Cherny from Anthropic said it best: "I don't prompt Claude anymore. My job is to write loops" The shift is simple. Stop giving instructions. Start designing systems that run themselves: Discover -> Plan -> Execute -> Verify -> Iterate until it passes The 6 things that make loops actually work: -Automations that trigger without you -Worktrees so agents don't overwrite each other -Skills that load context instantly -Connectors to real tools like GitHub and Slack -Subagents where the checker is never the maker -Memory so the loop never starts from zero Prompt engineers ask AI for outputs Loop engineers design systems that produce verified outcomes A reliable loop beats a perfect prompt every time Stop being a prompter. Start being the loop engineer

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

• 
  Alexey Samoylov (@metalagman_dev) reported 18 minutes ago

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

• 
  Priyansh (@itspriionly) reported 19 minutes ago

  The IT market is broken, and nobody wants to admit it. Someone spends 6 months sending out resumes. Six MONTHS. They learn React, Next.js, TypeScript, AWS, Docker. They take courses, build projects, improve GitHub profiles, optimize LinkedIn. Nothing. Complete silence. Companies don’t just want programmers anymore. They want someone who codes, shines in meetings, makes memes on Slack, and lives the company culture 24/7. AI is replacing junior work. Seniors are holding onto senior roles. And somewhere in the middle are people with 2–3 years of experience who somehow still feel invisible.

• 
  Manu | 🥥 (@ManuAF6) reported 20 minutes ago

  4/ New GitHub triggers + Marketplace templates New triggers: - Issue comment - Inline PR review comment - Full PR review submitted - Review thread resolved/unresolved - GitHub Actions workflow completed

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

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