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:

• 
  Phillip Yan (@PhillipYan2) reported 53 seconds ago

  @jsonphile @github create issue template so it can help filter out some of the spam. annoying though :/ @github

• 
  🫎 MUHOMOR. base.eth (@muhomoreth) reported 5 minutes ago

  7/ If you've spent years fixing other people's issues for free at midnight, this is a chance to get something back besides a GitHub star.

• 
  Seth For Privacy (@sethforprivacy) reported 6 minutes ago

  @Graysatoshi @RadarChat Still pending approval there, Google have been extremely slow, taking over a week to even start the review process! Pushing them hard, in the meantime can install manually from Github or via Obtainium.

• 
  Base Build (@buildonbase) reported 7 minutes ago

  The B20 Token Standard launch is delayed due to a Github outage. We still expect to launch today, and will update as we go live.

• 
  Keeta Github Tracker (@KeetaCode) reported 8 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #386: Fix: Prefer Generalized Time 🌿 Branch: feat/prefer-generalized-time → main 👤 Originally opened by: @sephynox 🧠 Overview: This pull request updates how Keeta’s code handles time data, aiming to use a more general format where it fits, which likely helps avoid edge-case issues and keeps data handling more consistent. From the public description, this appears to be a small technical fix rather than a user-facing feature. It is labeled as a bug fix, includes one commit, and was approved on July 1, 2026. - “Generalized time” is a standard way of writing date/time information in structured data, so this change likely improves compatibility behind the scenes.

• 
  Sudeep Nagabhirava (@Nsudeep) reported 13 minutes ago

  Saturated coding benchmarks like SWE-Bench Pro are incredibly noisy because they try to evaluate dynamic intelligence using old, frozen test suites from historical GitHub PRs and Issues. A lot of those original human tests were poorly written to begin with. Real software engineering isn't just about forcing a unit test to flip from red to green. If an agent burns through millions of tokens and leaves behind unmaintainable spaghetti code just to satisfy a hidden test requirement, that isn't a win. We need better benchmarks that actually measure architectural health and computational efficiency

• 
  Electronic Intelligence Agency (@EI3065) reported 13 minutes ago

  @github @LinkedIn prevents acess for selected nationalities with programers security checks on login; on repeat

• 
  Julien D. Cousineau (@CousineauJulien) reported 13 minutes ago

  The problem with Montreal right now is all these events cheering about the hard fight of being an entrepreneur. Meanwhile you have the GitHub founder starting Entire to fix the scaling issue of GitHub with AI. Nerds need to take over Canada.

• 
  CyberTLDR (@CyberTLDR) reported 16 minutes ago

  1/3 Researchers at Noma Security disclosed GitLost, tricking GitHub Agentic Workflows into leaking private repo data. A public issue, with no stolen credentials, can steer an AI agent into pasting private code into a public comment. #AIsecurity #GitHub #cybersecurity

• 
  raven⚡✳️ (@bycoinraven) reported 16 minutes ago

  The infrastructure for B20 looks ready, but the launch has been delayed as a precaution due to the GitHub outage. I think it's the right call. On day one, security matters just as much as speed. As soon as it goes live, we'll be watching the first B20 tokens closely. A new era on Base is about to begin. $BASE @base

• 
  owner (@carpenterdroid) reported 18 minutes ago

  @cypherpunk Trust me when I say this—there are smart people that are waiting for the forensic investigation into one @therealyingtong. As far as I can tell this individual introduced the bug on GitHub (blame) and should be sued to investigate the nature of the error. No one should have any objection to this. Does this person have ties to the ccp? Does this person have a personal interest in counterfeiting ZEC. Does this person have counterfeit ZEC? The bug is too clean. Let’s not all be so naive. Could be a criminal investigation.

• 
  Nav Toor (@heynavtoor) reported 22 minutes ago

  In 2014 a Swedish engineer named Knut Sveidqvist lost a Microsoft Visio file. He went to open the diagram he had drawn a few months earlier. It was gone. Every box, every arrow, every label. All of it had to be redrawn by clicking through Visio menus again. That night his kids were watching The Little Mermaid on TV. He named his fix after the movie. Twelve years later Mermaid has 89,101 GitHub stars, 8 million users, and native rendering inside GitHub, GitLab, Notion, Obsidian, VS Code, and Confluence. Here is what the paid market still charges to draw the same boxes. Microsoft Visio Plan 2. $15 per user per month. Lucidchart Team. $10 per user per month with a three-user minimum. Miro Business. $20 per user per month. Fifty engineers on Miro Business burns $12,000 a year to draw arrows between boxes. Mermaid replaced the drag-and-drop editor with a text spec that reads like Markdown. ``` graph TD A[User] --> B[Login] B --> C{Valid?} C -->|Yes| D[Dashboard] C -->|No| E[Error] ``` Ten lines. Renders as a real diagram. Every version of Claude, ChatGPT, Gemini, and Cursor already knows how to write it. You describe your architecture in plain English and the model returns a Mermaid block. Paste it into a GitHub README. Paste it into an issue. Paste it into a pull request. GitHub renders it inline as a live SVG. No plugin. No sign-in. The paid tools shipped drag-and-drop editors. Mermaid shipped a text spec that the LLMs learned on their own. Flowcharts, sequence diagrams, class diagrams, state diagrams, entity-relationship diagrams, user journey maps, Gantt charts, pie charts, *** graphs, mindmaps, timelines, C4 architecture diagrams, treemaps. Anything you would open Visio for. Version 11.16.0 shipped two weeks ago. Because the diagram is text, it lives in your repo. Because it lives in your repo, it goes through code review. Because it goes through code review, it stops rotting. Nobody has to remember where the Lucidchart account is. Nobody has to pay $10 a month to reopen a five-year-old file. MIT license. 89,101 stars. TypeScript. The library is free forever. Mermaid Chart the company sells a hosted editor on top for teams that want one, but the core stays MIT. Somebody in Sweden lost a Visio file and refused to draw it again. Twelve years later the paid diagram tools still exist, and nobody who writes software has to use one. (Link in the comments)

• 
  Pradeeban (@pradeeban) reported 23 minutes ago

  You want AI/LLM to be your coding assistant. But it is YOU who is becoming AI's coding assistant. "I have fixed it for you. Please push it. This might fix the GitHub failure for you. Please let me know if it still fails." Does it sound like an AI assistant? No, it is AI-senior!

• 
  Shall (@Shallntbe_Music) reported 25 minutes ago

  @Wearemez It used to be up on github, but it's long been taken down

• 
  Codemonger (@codemonger00) reported 29 minutes ago

  Startup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - 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: ~$20 There has never been a cheaper time to build .