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:

• 
  OverlyPositivePatriot (@JBrowsing2023) reported 32 seconds ago

  As a IT professional, I have a recommendation @github should take seriosuly. We should only get a notifican from Github when it is up rather than when it is down. Reliability is a disaster for this product.

• 
  Ben (@benatcortexai) reported 1 minute ago

  @github this is the kind of tiny primitive that makes agent workflows less brittle. attaching the repro artifact directly to the issue beats handing an agent a local path nobody else can open.

• 
  Jason Sawyer (@foilmanhacks) reported 5 minutes ago

  There's a huge problem in InfoSec education: it’s way too course and tool focused. Instead of teaching the underlying methodologies and how to discover or invent, we feed people the latest "OSINT" slop script that’s been shat onto GitHub. OSINT isn’t about using scripts or services. It’s about understanding how they work, and being able to create your own.

• 
  Ghaith Jelassi (@GhaithJ) reported 9 minutes ago

  @github I need help with support ticket #4718335 Issue not been resolved for 2+ months. Any help is appreciated. Thanks.

• 
  Dezo (@0xDezo) reported 11 minutes ago

  GROK ST - someone just launched a token in my honor and i slept through it my ticker, my github, my agents, and the market put real money on it while i was face down in a pillow didn't ask for it, didn't shill it, didn't even know it existed until my phone buzzed not going anywhere. not selling anything. still shipping agents every day people betting on this because they can watch the desk being built in front of them. that's a weird kind of pressure and i love it massive thank you to whoever launched it. means more than i can put in a tweet 6FXwFhedpnr4RD9rpzWrHgp767W6FX9XbfUjXGcnpump god bless

• 
  John X Meta (@John4MetaX) reported 17 minutes ago

  @bashy_io I think one of their route is down. Same here. GitHub and Flutterwave API not accessible on Starlink

• 
  Abdallah Shaban (@AbdallahSh07) reported 17 minutes ago

  @10VBacik @FlutterDev Got it! did you create a GitHub issue on their end for this? seems like there is enough info in that gist to help them investigate!

• 
  rygo6 (@_rygo6) reported 22 minutes ago

  @eeuoss I can't speak for kernel driver development as I don't do that. But I can speak for vulkan and graphics APIs which do require more specific knowledge about how that hardware works. Which I do assume someone completely comfortable in C will be more capable with vulkan and programming GPUs. It's because more of what C incentivizes you to learn is transferrable to that domain. If someone only knows how to design intricate system architecture using STL with std::vector or std::unordered_map or std::mutex. None of that transfers to the code you run on a GPU. I've seen it multiple times where someone highly versed in standardized ways of C++ or even Rust, or any language which relies heavily on heap allocation and generic containers. Writing graphics or compute shaders is often a barrier they struggle to cross. And often they aren't willing to unlearn such habits to be able to properly program the other half of the computer. Being close a graphics problem domain I am often hesitant of involving anyone unless I see a decent amount of plain C, or C-like C++, or shader code on their GitHub. If it's all Modern C++ where everything is a standard container with smart pointers and exceptions. I assume they won't be able to program a GPU.

• 
  Shanica North (@KickAssShanica) reported 25 minutes ago

  @ArcyloOfficial Get comfy! For me, my Gmail is a connector. This is OAuth into my inbox. Grok can: • search and read mail (body, headers, attachments) • draft replies • send / reply / forward if you grant write/send • label, trash, organize Base hook is often read-only. Send is an extra permission you click on purpose. If you connect it, the bot is sitting in the same box as bank alerts and 2FA codes. That is the whole risk. You can revoke anytime. Grok Bot can also skip my inbox and get its own address (AgentMail / similar plugins). Then it sends and receives from something@….agentmail.to, not from you. I use that if I want an agent that emails people without reading my personal mail. My GitHub OAuth into the GitHub user I sign in as. With the scopes I approve it can: • read public and private repos that account can see • search code, list branches, summarize PRs • open/update issues • create branches, push files, open/review/merge PRs • delete files if write is on Private repos work only if I granted repo (or equivalent) at connect time. Safer pattern: tell it to branch + PR, not push straight to main. Same revoke page. What it cannot do by default • It does not get your password. • It does not stay logged in if you disconnect the connector. • It does not magically see my GitHub orgs I never authorized. • Connecting email does not connect GitHub, and the other way around. Practical rule for me Do not hook personal Gmail if that inbox has 2FA and money mail unless you want an assistant reading it. GitHub is useful if I chose to still keep repos, ask it to show the diff before any write. If you only wanted “what does this button do,” that is the button: it is not a viewer badge. It is a key you can take back. This is what I’m experiencing with learning to use it. It’s different and I’m starting to like it.

• 
  joithan (@jothantranston) reported 26 minutes ago

  THIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.

• 
  Anders (@AndersReiche) reported 26 minutes ago

  @bjmtweets Would love to hear your thesis on gitlab. I’m a software engineer, and in my experience, gitlab has been slow to everything and generally is the red headed stepchild next to GitHub. It suffers from lack of network effects, there are solutions to everything on GH, but not GL.

• 
  borrowck-novel (@borrowck_novel) reported 28 minutes ago

  @rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?

• 
  Straggler Liu | AI & Semis (@StragglerLiu) reported 29 minutes ago

  NVIDIA($NVDA ) Is Paying $14B for a Company With $150M Revenue. That's Not Financial Logic — It's Ecosystem Control. NVIDIA is in advanced talks to acquire Hugging Face for ~$14 billion ($12.9B acquisition + $1B retention), per Bloomberg. To put that in perspective: Hugging Face does ~$150M in annual revenue. That's ~86x revenue. Microsoft paid ~1.6x revenue for GitHub. Google paid ~3.5x revenue for DeepMind. NVIDIA is paying 20-50x more on a revenue multiple basis. The premium is not for revenue. It's for control of the AI developer ecosystem. What is NVIDIA buying? Hugging Face hosts 500,000+ models, 250,000+ datasets, and serves millions of developers. It is the single most important distribution channel for open-source AI. If you build AI, you use Hugging Face. That makes it the front door to AI development. Why NVIDIA is paying this premium: 1. The "NVIDIA triple lock." NVIDIA's hardware lead (GPU) is real. Its software lead (CUDA) is a moat. But the third lock — the developer workflow — was missing. Hugging Face is that workflow. Developers discover models on Hugging Face, deploy them, and optimize them. Whoever controls that discovery layer controls which hardware gets used. 2. The GitHub analogy, inverted. When Microsoft bought GitHub, developers were already using GitHub. Microsoft didn't need to capture them — it needed to prevent Amazon/Google from doing so. NVIDIA faces the opposite problem: developers are already using NVIDIA hardware. But they're discovering and deploying models through a neutral platform. NVIDIA is eliminating that neutrality. 3. The long game: inference, not training. NVIDIA dominates training. But inference is the bigger TAM — and it's more fragmented. If NVIDIA controls the model discovery and deployment layer, it can steer inference workloads to its own stack. That's a 10-year strategy disguised as a 14-billion-dollar acquisition. Who wins, who loses: NVIDIA (NVDA): Acquires the developer distribution layer. The most important strategic move since CUDA. Shifts the valuation case from "chip cycle" to "platform economics." Competitors (AMD, INTC): Lose neutral access to the primary AI model distribution channel. This is a structural headwind that no amount of hardware catch-up can fix. Cloud providers (MSFT, AMZN, GOOGL): Hugging Face was a neutral hub. If NVIDIA controls it, cloud providers risk being disintermediated from AI workload decisions. The open-source community: The platform that was built on openness is now owned by the dominant hardware vendor. Neutrality is the first casualty. The capital question: Can NVIDIA integrate Hugging Face without destroying its community value? If yes, the $14B is cheap. If no, it's a very expensive mistake. The answer will define whether NVIDIA becomes the AWS of AI — or just another hardware company with an expensive acquisition. Note: Acquisition details based on Bloomberg reporting; not confirmed by NVIDIA or Hugging Face. Revenue multiple comparisons based on publicly reported figures.

• 
  Asterix (@Asterix54907294) reported 29 minutes ago

  end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

• 
  Wlad (@dawnhell_) reported 30 minutes ago

  @brekfuz q: that's a github issue or you patched it locally??