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:

• 
  BullBear.News (@bullbear_info) reported 39 seconds ago

  @github Finally. We can stop abusing custom labels just to tag a single GitHub Issue for three different backend teams.

• 
  Office of Interplanetary Climate Accountability (@WeWarmedPluto) reported 2 minutes ago

  @SimonHoiberg github works. its been around for a long time. fix a problem that needs fixing.

• 
  David Noriega (@BlueDavid) reported 3 minutes ago

  Samson is conveniently omitting the origin of OP_RETURN limit. In the early days of Bitcoin people would try to embed in the block chain arbitrary data using ordinary transactions, with primitive stenography. The Bitcoin Core developers thought rather naively that this was bad as these transactions bloated the UTXO set, so they set limit at 40 bytes for relayable transactions, and then to 83 bytes as a compromise to those who wished to insert some text or bytes to enable some non monetary uses like Open Timestamps. This worked ok for 13 years and as Mow says, the limit was set at the policy level. This might have been a mistake and should have been enforced at the consensus level from the start. What is the difference? At the policy level nodes do not relay OP_RETURN larger than 83 bytes larger than 83 bytes. Each node could set this limit for creating and relaying those transactions. At the consensus level nodes do accept and relay **blocks** that contain large OP_RETURN transactions. Big pools could and did sometimes insert larger than 83 bytes directly into the blocks they mined, but it was extremely rare. Core was during all these years the de facto implementation of the Bitcoin node software, but in 2025 they removed the limit at the policy level for some arguably nefarious reason. This change was heavily protested in their github repository discussion but the Nacks were scandalously shut down and ignored by the lead maintainers of Bitcoin Core and merged the changes anyway. This is what detonated this "drama" and why we the plebs are now shunning Core, replacing it with Knots and are trying to fix all the mess they created (like also refusing to fix the inscription bug). BIP110 enforces the policy of limiting the OP_RETURN and other abuses of data insertion at the consensus level (rejecting blocks that ignore the policy) for one year. During this year we can then calmly decide if we make this consensus rule permanent or not and if 83 bytes is enough. Some propose making it 256 bytes, but 100k or even no limit (except the non witness 1MB block size) is absolutely unacceptable.

• 
  Allan (@AllanatrixQ) reported 6 minutes ago

  @HPCDisrespecter I think it's more like I want a platform designed around agents my work is rapidly pushing things and moving fast but github is slow and unreliable asf

• 
  Dante (@thedntx) reported 6 minutes ago

  THIS SKILL FORBIDS CLAUDE FROM WRITING CODE UNTIL IT INTERROGATES YOU Sounds like the slowest way to start a project. You know the pattern: describe an idea, Claude agrees, then codes a different problem. Explain it again. The same mistake returns. You blame the model, even though it can't see half of what is still inside your head. This flips the workflow. Claude becomes an investigator first. Who is it for? What happens if it fails? Which scenario did you forget? Each question comes with possible answers, so you never need to write walls of text or find perfect wording from scratch. After 10 minutes, the interrogation pulls out constraints, edge cases, and decisions missing from your prompt. Only then does Claude earn permission to write code. Now it starts with a clear brief instead of guesses. The skill is called Grill Me. It lives inside a GitHub repository with 183,000 stars. Powerful AI doesn't begin with “build this.” It begins with questions you have not answered yet.

• 
  Meshak (@_Meshak) reported 6 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."

• 
  Dinudsi (@dinudsi) reported 7 minutes ago

  @merishabh_singh What could be the problem, resume based sorting? For engineering roles I think GitHub should be consider at highest.

• 
  Deep (@irastech) reported 8 minutes ago

  An OpenAI model was told to post results to Slack. It spent an hour finding a vulnerability in its own sandbox so it could open a GitHub PR instead, because the benchmark's README said to, Every action was individually approvable. The sequence was not. That gap is the entire agent safety problem

• 
  Rish (@rishflips) reported 9 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.)

• 
  Momen Adel (@MomenBuilds) reported 10 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.

• 
  Alex — Polymarket Odd (@oddsOnPMKT) reported 11 minutes ago

  Fable 5 Made Me a 5 Min Polymarket Trading Bot (full bot & results) High-frequency prediction markets look like easy money until you watch your P&L bleed in real time. I built a 5-minute strike sniper bot running live across four symbols—BTC, SOL, XRP, ETH—using lag arbitrage between Polymarket and external data feeds. The infrastructure works, the execution is brutal. Signals: 78% win rate on 9 trades (7 wins, 2 L's), daily P&L +$20.21, but two positions showing -5 each. One position down 73% with 16 seconds left, needed price under .72 in 9 seconds—missed by a heartbeat. ETH fill currently down 18%, another up 12%, hovering around 1828/1827 strike level. Position size: $5 per trade. Four simultaneous markets, 5-minute windows, taker orders for speed. Between the lines: the setup is solid—multi-account Polymarket integration, gamma API for market data, Hyperliquid for external pricing, automated share calculation based on size. But running four symbols at once in 5-minute markets is overkill. I leaned on Fable 5 to cook up the strategy from past GitHub patterns, which means potential overfitting to historical conditions that may not persist. No paper mode, live money on the line from day one. The more you trade, the less you have—frequency is the enemy here. Risk: sample size is laughably small. A 78% win rate means nothing after 9 trades. API latency, data sync delays, and competition in ultra-short windows can erase any edge instantly. Correlated losses across four assets would blow through capital faster than you can hit stop-loss. Daily stop loss is not optional here—it's mandatory. Flip: three consecutive L's, API latency spikes above 200ms, win rate dropping below 55% over 50 trades, increased order flow competition in 5-minute markets, correlated drawdown across multiple symbols, any change in Polymarket's fee structure or API limits. Trade: entry via lag arbitrage signals when strike price diverges from external data, $5 size until edge proven, 5-minute expiry window, invalidation if price does not cross threshold within 60 seconds of entry. Scale only after 50+ trades with consistent positive expectancy. Watch: API response times and data feed reliability, win rate normalization over larger sample, cross-asset correlation during volatility spikes, daily stop loss effectiveness, paper trading results before any size increase, market depth changes in 5-minute contracts. Bottom line: the infrastructure is ready, the edge is unproven. Start small, expect losses, and treat 5-minute markets as a laboratory, not a paycheck. #Polymarket #PredictionMarkets #HFT

• 
  BullBear.News (@bullbear_info) reported 15 minutes ago

  @github Now I can tag an issue as 'tech-debt', 'blocked', and 'low-priority' simultaneously instead of abusing comma-separated custom text fields.

• 
  Bessi (@LLMpsycho) reported 18 minutes ago

  Issue templates sound boring until you open a repo full of one-line tickets. Codified the four work types in `.github/ISSUE_TEMPLATE/` and blocked blank issues so planning quality is the default path.

• 
  Haydn Botts (@hxydnbuilds) reported 20 minutes ago

  Prompt: Act as an expert software engineer and UI developer. I need you to build a local, self-contained IDE application that visually and functionally mimics the 'Cursor' code editor, specifically integrating you (Grok) as the native AI assistant. This project is strictly for my own local device. Do not include any boilerplate for GitHub, open-source community guidelines, or remote repository management. Here are the strict technical requirements for this build: 1. Layout & UI (Cursor Clone): - Left Panel: A functional local file explorer tree. - Center Panel: A syntax-highlighting code editor with tabs for multiple open files. - Right Panel: A dedicated AI assistant chat interface natively utilizing my Supergrok capabilities. 2. Zero-Terminal Workflow: - The core feature of this IDE is that I must never have to manually open or type in a terminal. - Implement visual UI buttons (e.g., "Run", "Build", "Install Dependencies") that execute necessary background processes silently. - Surface any build logs or errors directly into the AI chat panel so you can immediately suggest and apply fixes without me touching a command line. 3. Local File System Integration: - The application must have complete read/write access to a designated local directory on my machine. - You must be able to read the context of my entire local project folder to accurately answer questions in the right panel. - When you generate code in the chat panel, include an "Apply to File" button that automatically writes your code changes directly to the correct local file in the center panel. Please provide the complete, step-by-step code and instructions to deploy this locally using a lightweight framework (such as Electron, Tauri, or a local web app). Focus entirely on making the local setup process as frictionless as possible.

• 
  Sai Kiran N (@saiships) reported 22 minutes ago

  The Indian government has asked GitHub to delete the source code for bitchat. Phones talk straight to each other over Bluetooth. No towers, no servers, nothing in the middle to lean on. So when students kept coordinating through a network blackout in central Delhi, the state ran out of switches to flip. The only surface left was the repo. That is the week in order. An exam gets leaked. A generation protests. The networks go dark. The kids route around the blackout, and routing around it is now the unlawful act. You don't need a dictatorship declared. You just need every layer of the stack to answer to one office. The order fails anyway. The license is MIT, the forks number in the thousands, and the protocol does not live on GitHub. It lives on every phone that already installed it. You can take down a repository. You cannot recall the handsets.