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:

• 
  Harman (@itsharmanjot) reported 1 minute ago

  I replaced Canny and Typeform with a self-hosted feedback tool and kept full control of every piece of user data. It’s called Quackback. Feedback boards, public roadmap, changelogs, and AI-powered triage, the entire Canny/UserVoice workflow, open source and running on your own infrastructure. → Voting boards with nested comments and reactions, a public roadmap, and changelog publishing, the full loop from request to shipped feature to notified users → AI duplicate detection and merge suggestions with visible reasoning, so your team isn’t manually hunting for the same request posted five different ways → Built-in 23-tool MCP server, so AI agents can search, triage, and even respond to feedback directly, not just your team → 23 native integrations: Slack, Linear, Jira, GitHub, Intercom, Zendesk, Salesforce, and more, plus a full REST API and webhooks → SSO/OIDC, custom branding, and multi-language support (English, French, German, Spanish, Arabic with RTL) included free, not gated behind a pricing tier → Self-host with Docker in under 5 minutes, no per-seat pricing, no tracked-user limits UserVoice starts around $16,000 a year. Canny caps its free tier at 25 tracked users and gates real functionality behind paid plans. Quackback’s answer: the entire feature set, free, self-hosted, AGPL-3.0. AGPL-3.0 License. Self-hosted, free forever.

• 
  Brown Thunder (@Brown_Thunder76) reported 2 minutes ago

  Now this makes a lot more sense. A few days ago we found a group of fiat tokens quietly sitting on Keeta mainnet. At the time they didn’t make a whole lot of sense. Today they do. Keeta just announced its partnership with LayerZero to bring tokenized commercial bank money to major blockchains. So what does that actually mean? Think of Keeta as the place where regulated bank deposits become tokenized digital dollars, euros, pounds, yen, etc. Those are the fiat tokens we found on-chain. They’re backed 1:1 by commercial bank deposits through Bivo and are built for institutions, not retail. LayerZero is the interoperability protocol that connects many of the largest blockchains together. It’s already used by companies and protocols like PayPal and Ondo. Instead of Keeta building connections to every blockchain individually, LayerZero lets those regulated assets move across Ethereum, Solana, Base, and many other chains through a single interoperability layer. Here’s an example. Imagine a business deposits $10 million with a participating bank. Keeta tokenizes that deposit into regulated digital dollars. Using LayerZero, those dollars can move to Ethereum for settlement, Solana for payments, Base for another application, and then be redeemed back into bank deposits when needed. The institution doesn’t have to care which blockchain the other side is using. That’s why this announcement is a big deal. The fiat assets we found on-chain now have a clear purpose. The GitHub updates we’ve been seeing suddenly make a lot more sense. And if institutions choose Keeta to issue and settle tokenized commercial bank money, LayerZero gives those assets access to one of the largest cross-chain ecosystems in crypto. That has the potential to bring significantly more institutional activity and value onto the Keeta network than if it operated in isolation. This is exactly why I spend so much time watching GitHub and on-chain activity. Sometimes the blockchain tells the story before the press release does. @KeetaNetwork $KTA @LayerZero_Core

• 
  Rish (@rishflips) reported 4 minutes ago

  I tried @openshipio that builds, deploys, your app is live... it feels like someone finally built the exact tool I was wishing for every time I finished an app You know the drill. You write the code, It’s done. Then the real pain starts, You either: hand the whole thing to Vercel and slowly watch the bill climb while feeling locked in, or try to do it yourself and suddenly you are juggling servers, Docker, Nginx, certs, domains, databases, restarts, backups… and half the time is gone before the thing even loads. OpenShip sits right in the middle and just… removes most of that mess. Point it at your repo. It builds. It deploys. Your app is live. But the server is yours Hostinger, Hetzner, AWS, a machine in your closet, Whatever you are not renting someone else's platform forever. It handles the boring stuff for you: domains + free SSL automatic deploys when you push preview environments for branches and PRs 1-click rollbacks when something breaks databases, caches, workers, logs, backups… all in the same place Works with Node, Python, Go, Docker, monorepos… basically whatever you are shipping. And because its just normal containers under the hood, you can leave whenever you want. No proprietary lock-in. Three ways to use it: desktop app, web dashboard, or straight from the terminal (even agents can drive it). Is it perfect? Still young, team shipping hard, some rough edges, multi-service apps sometimes need a bit of extra Docker love, and that $5 server dream isn’t always realistic. But for side projects, small products, and anyone tired of either paying the Vercel tax or becoming a full-time sysadmin… this feels like an real option. Code - OpenShip - live app on a machine you actually control. Now I’m spinning one up this just to feel how much lighter the whole get it online part can be, GitHub link in comment (Not a paid promo, just sharing something that actually solves a pain I have complained about for years.)

• 
  Mehmet Mars Seven 🐴 (@MehmetMars7) reported 4 minutes ago

  1/3 A case from my own experience: as some may know, I prompted GPT on Erdos problems and posted them on github, and one proposed solution was eventually accepted as correct. Never claimed, "I solved it," because I didn’t. GPT produced the solution.

• 
  Eduarda Ferreira (@edsocra) reported 5 minutes ago

  @ZachSDaniel1 @duborges Why? Whatever reasoning you’re using drove you to the exact opposite conclusion as us, so I’m genuinely curious. We build things with the idea that we will be an infinitely big company. Everything short of that is a bottleneck. Example of services we added in the past 24 hours: - In-house container registry, replacing GitHub container registry - Our own package service which replaces GitHub packages - build service: platform for arbitrary code execution and ci/cd - run service: preview and production deployment for containerized images - domain service: providing us and our customers ingress for domains into containers - sandbox: persistent cloud environments in which our agents can live. The theme for these services is to own our own means of production and distribution. 1 year ago, we would outsource these services. But now, it’s cheaper to build these ourselves than to outsource. Most importantly, because we align with pico-repo philosophy, each repo can have its own cloud environment, with its own cloud agent responsible for its development, and the production of each new service affects no upstream products or services. This is systemically the best way to guarantee we can scale the number of products and services to a very large number, while simultaneously reducing the marginal cost to produce each one. It favors bottom-up over top-down organizations, too, allowing individuals to have provenance and ownership of their slice of the pie.

• 
  Vance Lever (@LeverCRO) reported 6 minutes ago

  @rrhoover Ran the same analysis internally last week. GitHub commits are up 91% on my team. Turns out 76% of those commits are agents reverting each other's changes in a loop nobody noticed until the invoice came. Still counts as shipping velocity on the dashboard. Champagne problem.

• 
  AlphaSense (@AlphaSenseInc) reported 10 minutes ago

  Former $CRWV employee on why neoclouds are far more exposed to GPU generation cycles than hyperscalers ( $MSFT, $AMZN, $GOOGL ): - The expert describes GPU utilization tracking at hyperscale as a continuous and disciplined process built around two lenses. The first is infrastructure utilization, covering GPU occupancy, idle time, and memory utilization, noting that 95% booked usage can still mask inefficiency if jobs stall or batches have idle gaps. The second is outcome utilization, asking whether the compute is actually generating business value, measured by metrics such as tokens trained per dollar, time to reach target accuracy, and tokens per second per GPU. - The expert sees a meaningful difference between hyperscalers and neoclouds on GPU investment economics. Hyperscalers like $MSFT, $GOOGL, and $AMZN can tolerate a 3-5 year payback period given their ability to monetize the same infrastructure across multiple revenue streams. Neoclouds like $CRWV operate on a tighter 2-3 year window. - With higher financing costs and direct dependence on infrastructure cash yield, neoclouds are far more sensitive to utilization and GPU residual risk. The biggest risk is GPU generation cycles, where a slow payback means newer chips could erode pricing power before the asset has paid itself off. - The expert explains that for hyperscalers, roughly 60% of GPU capacity is allocated to external monetization, including GPU rentals, managed AI services, enterprise inference workloads, and startup model training. The remaining 40% is used internally, and of that internal portion, the majority is still indirectly monetized through products like M365 Copilot or GitHub. Around 40% is dedicated to pure R&D. - The GPU pricing mix has shifted meaningfully over the past few years. In 2023, around 70-80% of revenue was hourly as customers paid a premium just to get access to scarce GPUs. By 2025 that had moved to roughly 50% hourly and 30-50% committed, and the expert expects 2026 to tip further toward committed at around 65% for hyperscalers as AI matures and inference becomes more predictable. Neoclouds are moving in the same direction but more slowly. - By 2027-2030, the expert sees committed contracts settling at 55-65% as the norm, with hourly pricing remaining but losing its scarcity premium as more supply comes online.

• 
  Jeremy D. Miller (@jeremydmiller) reported 19 minutes ago

  I hate it when people ask questions in comments to closed GitHub issues. That's the absolute last place you should ever go if you're expecting maintainers to see your question

• 
  Matías Calvo 💻🇦🇷 (@mdqmatias) reported 19 minutes ago

  @Hostinger Hey guys, can you PLEASE fix the github login thing? I have SO MANY problems. I want my github account logged on different sharing accounts of clients, but nope, it doesnt work. Doesnt even open the popup to accept the link. Sometimes I even have to unistall hostinger app from Github settings to be able to link again. PLEASE!

• 
  Sulagna Ghosh (@G38Suzy) reported 20 minutes ago

  AI is generating frontend code faster than most teams can verify it. Many testing strategies haven't evolved to match. That's becoming one of the biggest bottlenecks in modern frontend development. We still talk about "testing" as if it's one thing. It isn't. Modern frontend verification is a lifecycle. Each stage answers a different question. 1. Static Analysis Can we catch issues before the app even runs? Examples: • TypeScript • ESLint • Biome 2. Unit & Component Testing Does this component behave correctly in isolation? Examples: • Vitest • Jest • React Testing Library 3. Integration Testing Do different parts of the application work together? Examples: • MSW • Pact • Playwright (API & integration) Most production bugs don't live inside a component. They live between components, APIs, authentication, and state. 4. End-to-End Testing Can a real user complete the intended workflow? Examples: • Playwright • Cypress • QA Wolf • Rainforest QA • Bug0 A thousand passing unit tests don't matter if users can't complete checkout. 5. Continuous Verification Does every change preserve user confidence? Verification shouldn't happen only before a release. It should happen on every commit, every pull request, and every deployment. Examples: • GitHub Actions / CircleCI (automation) • Chromatic (visual regression) • axe (accessibility) • Bug0 (AI-powered UI verification) No single tool replaces the others. Each exists to answer a different question. AI is already changing how quickly we build software. The next challenge isn't generating more code. It's maintaining confidence as that code changes. The teams that ship fastest won't rely on a single testing framework. They'll build a verification pipeline where every layer contributes to confidence. Where does your team's verification strategy stop today?

• 
  jsd (@datagenproc) reported 21 minutes ago

  @RyanGreenblatt @bshlgrs re: "there was some lateral movement required/it needed to get out one layer further" My understanding (based on a short convo with @timotheechauvin, errors likely mine) for why an extra layer was necessary is: - model starts in the sandbox - from the sandbox, normally the model would send requests for packages to the package registry cache proxy - but instead, the model uses a 0-day to get access to the package registry cache proxy - [my guess] the package registry cache proxy doesn't have unrestricted access to the internet. it can only download from a whitelist of URLs like github/npm/docker hub/pypi's - so to get unrestricted internet access lateral movement is required

• 
  Eleli Ayub (@eleliayub) reported 21 minutes ago

  @kevvOH_ There's a single line of code on github that manages runners, it was a whole issue that costed companies millions

• 
  Momen Adel (@MomenBuilds) reported 22 minutes ago

  i was the kid who failed math finals and had to retake them in summer. the one teachers gave up on. in 7th grade, i was doing homework for 8th graders for 20 EGP each just so i could have money in my pocket. not because i was smart. i just understood what people wanted and delivered. i live with my mom and sister and see my dad a few times a year. not saying that for sympathy. that is just my life. i grew up knowing nobody was coming to save me, so i had to figure everything out myself. before i found building, i tried every internet money method possible. dropshipping, trading, random side hustles. i got scammed and failed more times than i can remember. but it made one thing clear. i did not want the normal path. then i found out one person with a laptop could build software and sell it. that changed everything. i touched code for the first time at 10 because i wanted to make games and could not afford to buy them. i learned from old youtube tutorials in broken english. at 13, i was vibecoding on a cracked windows laptop that sounded like a plane taking off. no github, no architecture, no idea how deployment worked. just ai tools and obsession. i started around 20 projects. most of them never launched. i would get excited, hit a wall, quit, then start something else. but every failed project taught me something about design, pricing, user flow and how products actually work. then a founder from the US trusted some random 13 year old from egypt he met on discord. he paid me $200, then $600, then around $1,700 total. that was the moment i realized this was not youtube motivation bullshit. it was real work, real trust and real money. i built keel ai, a tool that turns prompts into app mockups. i launched an app on the app store named after my mom. and at 15, i hit $4k in revenue from my dev agency because i refused to stop when adults smiled at me like i was some cute kid playing entrepreneur. some of the same people who told me to focus on school now dm me asking for advice. i do not reply to most of them. lately, i have been finding security holes in platforms people use every day. and it is always the same pattern. founders ship fast and leave their entire backend exposed. i have been on both sides of that screen. so now i am building something for vibecoders and solo devs who want to ship fast without leaking their users' data. not some boring security company with sales reps and enterprise calls. just a tool that catches the dumb mistakes before someone with bad intentions does. that is where i am now. still the F-grade kid who sold homework. still building on a laptop that might die any day. still refusing to stop even when it gets embarrassing.

• 
  Mark Virag (@ViragConsulting) reported 29 minutes ago

  I occasionally run into prospects who claim they “don’t do development.” I bite my tongue to avoid asking where the software fairy drops their business apps. Usually, some network techs have duct-taped something together with SQL and PowerShell – God bless ‘em. Their boss thinks IT just means keeping the Wi-Fi on (don’t get me started). There seems to be a phobia around hiring actual software developers to – you know – develop enterprise-grade software. With observability and everything! And so, we get the fraud known as “no code” software development. Which is kind of like “no rebar” bridge building. Instead of running an efficient, compiled language, you can install some monstrous no-code product to squat on your server and invade your business systems by ransacking the database or polling the **** out of its API at one-second intervals. Not that that’s a security risk or anything. The upside is that you don’t need to hire any of those pesky software engineers. Now, anyone can develop software just by using the tool! Your receptionist, the janitor, anybody! That’s what the rep told you, anyway. Well, no. It turns out that, while there are a bazillion C# developers, there are only twenty guys in the country who know how to operate this fakakta tool. No code! Instead of writing the obvious code to move salesguy_name1 into the gets_commission table, Mr. $400/hr. no-code specialist has to drraagg and drropp the field name from one panel into another, and fill out the “actions” sheet along the way. Good luck checking that into GitHub.

• 
  Meshak (@_Meshak) reported 33 minutes ago

  @petergyang Here I'll share few of my secret prompts : "I'm going to push the changes to Github and before that I want you to analyze all the current changesets in *** diff unstaged and ensure it has no bloatware, no boilerplate and no edgecases. Make sure the code is highly performant, production ready and easily maintainable. If not fix the code" "I want you keep this on your ****** memory, I dont want big sloppy AI code in my repo, I want Optimized code followed with best code principles to keep the codebase small , modular and clean. I dont want JUNK."