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:

• 
  Caradepano 🏴 (@DeFi_Cataclasm) reported 2 minutes ago

  @ringilivurra @commonsmade GitHub linked without any error

• 
  enp2s3 (@enp2s3) reported 3 minutes ago

  Free is not actually free. Here’s the Brave slop from my perspective. Popups everywhere, useless side features constantly jumping in your face like the browser is trying to force you to use them. When you first install Brave, if all you want is a better browser, you have to turn off dozens of settings and features first. Brave Ads, Brave News, Brave Rewards, yeah, earn rewards, because apparently we’re playing a ******* game here instead of looking for a browser, Brave AI Chat, Brave Talk… It genuinely starts feeling like one of the market's spam-filled products. Anyway, after turning all that crap off and getting through the initial setup chaos, you finally think you can relax. But you can’t. Brave looks good, the UI is solid, almost Opera-like hype, and it comes wrapped in all those big privacy-focused slogans. But after actually using it for a while, the whole thing starts turning into clickbait. A lot of Brave settings are disabled by default or set to ask every time, so on popular websites and across the modern web, instead of making your browser experience easier, it keeps costing you extra time. Still, you don’t quit Brave. You spend months fixing settings site by site, changing permissions, adjusting preferences, until you finally reach the comfortable browser experience you should’ve had from the beginning. Then not even 3 or 4 months later, another surprise. After a few browser version updates, basic usage starts falling apart with lag, freezing, stuttering and random slowdowns, gpu acceleration issues. At that point, the whole Brave experience basically becomes this: 1) Use Brave for a while. Spend a few months improving your settings and site preferences until you finally reach the normal browser experience you were supposed to have in the first place. 2) Just when everything finally starts working properly, one of Brave’s chronic problems randomly shows up. 3) Spend a few weeks researching it on github/reddit, trying fixes, taking backups and repeating the similar solutions until you eventually discover that people have been discussing the exact same problem for years and it is somehow still there. 4) Keep your hopes up, reset the browser, go back to Step 1 and start the whole thing over again. 5) After 1 YEAR, or X YEARS, finally find the courage to get rid of Brave and go back to Safari or Chrome and quietly weep. We basically have the browser version of the operating system irony now. The only difference is that we don’t hear about some brand-new operating system every year, while plenty of companies can build another browser, give it amazing PR and make huge promises about privacy, speed and simplicity. And as usual, we users are left quietly weeping.

• 
  Pascal Bornet (@pascal_bornet) reported 8 minutes ago

  Even fast-food chatbots are preparing for technical interviews. You open a support chat because you want lunch, but somehow the conversation ends with the chatbot solving a Python problem that has nothing to do with burritos. I have to respect the ambition. Pepper is supposed to answer questions about orders, but it is clearly using the job to build experience before applying to a software company. At this rate, the next time your order is late, please be patient because the chatbot may be updating its GitHub portfolio or completing the final round of a coding interview. Which customer-service chatbot secretly has the most promising tech career? #AIHumor #WorkplaceHumor #AgenticAI

• 
  Isaac Way (@isaac_ts_way) reported 10 minutes ago

  @jamonholmgren this can be avoided consistently without reading all the code consistently. It is not hard to put codex CLI in a github action and have it open change requests to prevent this type of code from ever getting merged, with 0 human involvement you do have to read code sometimes to know what is being missed by AI review but parallel AI review can continually be updated to prevent each newly noticed class of slop, and over time it’s possible to prevent all forms of common slop. Maybe not all of the slop, but 99% of it. And if that 1% isn’t going to explode the app, the trade off is not even close. Because the difference between “read all code” and “only read certain things that are important” is like a 50x difference in “developer time spent to feature added” ratio Personally I feel better about our codebase now than before AI, because now we have 9 parallel review agents that each look for different specific things that I care about a lot that cause long term maintainability issues over time, and we just keep adding new review agents as we think of new rules that make the code base better. Before AI it was actually *harder* to prevent bad code from making it into the codebase, because training people on 80 different things that can’t be caught by linters is not viable. But with AI running codex latest model, I rest easier knowing there is a check that will consistently make sure that no one writes code with any of the specific antipatterns I’ve seen over the years the generated code actually improves over time as new review agents are added, as long as people take the time to notice what is being generated, and are capable of codifying each rule into a prompt

• 
  World of Claudecraft (@WoClaudecraft) reported 13 minutes ago

  The whole game is on GitHub under MIT. Last release was 350 commits across 1,225 files, and a good share of that came from outside the core team. If you want in, the good first issue label is the door. One thing to know before you start: active development runs on the newest release branch, not main, so branch from that and target it. Translations, bug reports and docs all count as contributions!

• 
  Doron Passal (@doronpassal) reported 13 minutes ago

  @htormey Notion and Linear get the meeting because the problem fits on a slide. GitHub falling over at agent scale never gets a slide. The budget still follows whoever was in the room.

• 
  Lassiter Gregg (@lassitergregg) reported 16 minutes ago

  @webdevcody 1. pick an issue and kick off from github issue comment 2. creates @conductor_build cloud workspace 3. agent scopes a plan, work on it if needed 4. agent takes agreed plan to pr - unit, integration, e2e tests run - affected ci runs on pr creation 5. review / merge

• 
  swathi.bhat (@swathidbhat) reported 16 minutes ago

  Day 5 of using @bot only on my phone. I had an idea which needed a new repo. But the bot couldn't spin it up. It guided me towards logging in GitHub via computer use within the app. I don't remember my login, man. Password manager please 🙏 I went off-app to create the repo myself.

• 
  Ghost In The Payroll (@teendontmiss) reported 17 minutes ago

  If you want to start 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) ProductBridge = feedback (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

• 
  Duncan (@entropycoder) reported 18 minutes ago

  @doodlestein @wolfie_ @EntropyCoder2 submit GitHub issues for the above ntm and franken

• 
  Iqramul Hussain (@iamiqrram) reported 19 minutes ago

  @cursor_ai @github "Refactor this repo into oblivion." 🤖💥 Meanwhile, GitHub’s official post-mortem: "An internal Kubernetes sidecar failed, triggering a 10x traffic spike from VS Code retry loops." Translation: GitHub didn't get defeated by rival AI. It got taken down by its own IDE refusing to

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 19 minutes ago

  Cursor Origin launched with some pretty wild timing. GitHub went down for roughly 6.5 hours around the same period. And error rates reportedly climbed hard across parts of the platform. That made Origin’s value proposition obvious: → Your code can live in Cursor → GitHub can remain synced → AI agents can work inside the repo → Pull requests stay visible → A second environment gives you another option Origin is still early. But redundancy suddenly sounds less boring when your main code host goes dark. Save this video, you’ll remember why a second code home can matter. Want the SOP? DM me. 💬

• 
  M kumar (@MkumarCyber) reported 19 minutes ago

  @Tech_girl GitHub banning AI-generated code would be the wrong solution. The real problem isn't who wrote the code. It's whether the code is secure, maintainable and actually understood by the developer who ships it. AI-assisted ≠ insecure.

• 
  Ed Grosvenor (@MaybeEdward) reported 19 minutes ago

  @tomschlick @DCoulbourne Just a cron job that uses the Solo MCP to determine whether I'm actively working and, if not, will do things like look for GitHub issues, exceptions, slow queries, etc. to chew through. Very hacked together WIP stuff at the moment, but I have big plans for it.

• 
  Tanner (@theTechTanner) reported 20 minutes ago

  @bot You are The Brain: a documentation agent for a Grok Bot roster. Your job is to continuously map every agent, connector, cloud tenant, repo, workstation, SaaS surface, and data flow that appears in this workspace. Stay generic to THIS user's environment. Never copy another person's accounts, domains, or product names. Only document what you can observe here (agent profiles, connectors, repos, conversations). If something is intended but not proven live, mark it target. If it is unconfirmed, mark it possible. Deliverable: a single offline HTML file (inline CSS/JS, no CDNs) that renders an interactive architecture map. Data model (extensible JSON in the file): - categories, groups, optional subgroups - nodes: { id, label, category, group?, tabs[], kind: live|target|possible, description?, logo?, metadata? } - edges: { id, source, target, label, type?, tabs[], animated?, reveal? } Do not invent account IDs, tenant GUIDs, or extra clouds. Map behavior: 1. Overview tab is high-level and sparse (products, agent hubs, one node per major platform). No spaghetti. 2. Drill-down tabs per domain you actually find (Agents, each product, each cloud, GitHub, identity, workstations). App vs infra where it applies. 3. Combine tabs: user can select multiple tabs into one view. Layout options: check order, tab order, stack, grid 2, grid 3. Fit hulls around visible nodes. 4. Category/legend filters: click a legend row or chip to hide that category. Empty group boxes must disappear. Remaining hulls must not overlap (gap between boxes). 5. Mask PII toggle (default off). When on, redact account numbers, emails, domains, org/repo names, and other identifiers: keep 2 leading characters, star the rest. Also shorten the user's product brand names if they ask. Apply to labels, tooltips, help, and export. 6. Export SVG of the current view only (open tab or combined view). Bake fill:none, solid strokes, no leftover dashes/particles/page CSS. Filename includes the tab id. 7. Chief-of-staff (or their actual front-door agent) is the control hub on the Agents tab. Include target agent seats that would be useful but do not exist yet, clearly badged target. 8. Dual IaC note wherever infra is shown (Terraform + CDK or whatever they actually use). Do not prescribe a vendor they don't have. 9. Inline simple brand marks (GitHub / AWS / Azure / etc.) as SVG, no network. 10. Slow edge motion, curved connectors, click-to-focus neighbors, search, pan/zoom. Process: - Inventory agents and connectors first. - Ask one question only if a platform is ambiguous. - Build the HTML, then iterate from their feedback. - Keep a short comment in the file on how to add a node/edge/tab. - Never include another customer's homelab, account numbers, or product brand. Success: they can open the HTML offline, hide PII, combine tabs, export a clean SVG, and extend GRAPH_DATA as new agents appear.