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:

• 
  Franci Penov (@francip) reported 1 minute ago

  Doing the same work twice now, because neither the iOS ChatGPT app, nor Codex Web is able to push my changes to github, despite the connector installed and configured with read/write permissions for my org. As much as I love Sol, the coding tools around it are in dire need of someone at @OpenAI actually using Sol to fix them and make them usable.

• 
  Ephraim Nwachukwu (@ephraim_17) reported 2 minutes ago

  Typing every line of code was never what made someone an engineer. Before the internet, developers relied on books and libraries. Then Google, Stack Overflow, GitHub and modern frameworks changed how software was built. Now it is Codex, Claude Code, Cursor and AI agents. The tools changed. The thinking did not. The real measure is still whether you can understand the problem, make sound decisions, recognise bad output and build something that actually works. Every generation mocks the tools of the next one. Then eventually, everyone uses them.

• 
  Manish rawat (@R11manish) reported 5 minutes ago

  @github action service is down again 🥲

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 6 minutes ago

  @Harry_The_Nerd sorting the articles sequentially in a github repo is the fix for x random ordering, smart

• 
  Treks.dev (@dev_Treks) reported 6 minutes ago

  **Post MVP:** GitHub integration that matches pull requests to tasks and automatically generates review reports, so leads don't have to search for the problem. If turning a big goal into a real plan is something you’ve struggled with, this is exactly what I’m creating.

• 
  🇺🇸 Santore (@santoretech) reported 6 minutes ago

  Your company doesn't need another AI tool. It needs an operating system and you already have one.. it's @github. Tasks? Issues and Projects. Related to code? What isn't, in 2026. Strategy, playbooks, decisions. If it isn't versioned, your agents work from stale context. Skills and prompts? Same place. Writing voice, review checklists, compliance guardrails. Stored, updated, shared. Improve a prompt once, everyone gets it. Approvals? Built in. Define who reviews what before anything ships. Sharing? Invite someone to the repo. One source of truth, not twelve tools with twelve versions. Humans and agents, same playbook. The company brain isn't a metaphor. It's our operating model and @blockskunk is the lab. One repo at a time.

• 
  DegenCalls (@Degen_calls_sol) reported 8 minutes ago

  GITHUB REPOS YOU SHOULD KNOW ABOUT Most scrapers break for boring reasons. A button moves, a class name changes, Cloudflare gets in the way, or the crawler dies halfway through a long run. Scrapling turns scraping into a more resilient system. Scrapy-style spiders, concurrent crawlers, pause and resume, anti-bot handling, and adaptive element finding in one framework. The detail most people miss: the adaptive selectors are the real unlock. Instead of hard-coding brittle CSS paths and praying the site never changes, the scraper can relocate elements after redesigns. That matters when you are scraping production targets, not toy pages. This is the shift from scripts to infrastructure. A script extracts data once. A scraping framework keeps extracting when the website changes, slows down, blocks, or moves the target. Most people still build scrapers like one-off hacks. The better setup is a crawler that expects failure and keeps going anyway.

• 
  0xMadman (@LGLLGL1997) reported 9 minutes ago

  @skalskip92 People have major questions about authenticity right now. If we put the CA up on GitHub or a website, that’ll fix the whole problem.

• 
  Chris Davis (@thedatadavis) reported 13 minutes ago

  I thought people were being a little dramatic about the github performance issues but using their api is far too hit or miss for a serious company.

• 
  another anon (@eugenioclrc) reported 14 minutes ago

  @Kritt_AI @_blockian @ControlZ_1337 GitHub not working 👉👈🙏🙏

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

  The Agent OS origin story: every problem became an agent. Here's the simplest system-building rule I've seen: Every problem you have becomes an agent. → Hated spending hours on videos? Built a video agent. → Hated the SEO grind? Built an SEO agent. → Agents kept forgetting everything? Built the memory system. One by one, every time-drain became a worker. And here's the upgrade loop: see something trending on GitHub? Plug it in. Open Montage was blowing up, so it went straight into the system. Now it makes cinematic films in one click. The system gets better every single day because the internet keeps building parts for it. The mindset shift: you have to be brave enough to ask Claude for something big and risk hearing "I can't do that." The honest truth? It hasn't said that in 6 months. Any idea in your head is now buildable. Most people just never ask. Save this. You'll want it later. Want the SOP? DM me.

• 
  Padma Neelamraju (@PNeelamraju) reported 15 minutes ago

  Open-source supply chain security continued: These attacks stem from specific platform design choices. GitHub introduced a feature called pull_request_target that exposes secrets to untrusted code submitted in pull requests. Exploits based on misconfigured pull request actions are common enough to have a name: pwn requests. GitHub could fix this. They could escape substitutions correctly for shell commands, disable the feature for certain operations, or prevent secrets from being exposed in those contexts. They publish documentation warning users to be careful but have not addressed the underlying vulnerability. npm made a choice that npm install always downloads the latest version of every dependency to deliver bug fixes immediately. In practice, this means malware gets distributed immediately when published. Go chose different rules: downloads retrieve the versions the package author tested against, not whatever is latest today.

• 
  U N C L E BIGBAY ✨ (@unclebigbay143) reported 16 minutes ago

  Most of us build products with React, Next.js, PostgreSQL, Redis, TensorFlow, or countless npm packages without knowing every line of their source code. When React has an internal bug, many React downstream frameworks and developers blocked. They read the docs, inspect the source, search GitHub issues, or wait for a fix. That doesn't mean they didn't build their product. AI-generated code is similar. You don't have to understand every implementation detail from day one, but if it becomes part of your product, you should understand it well enough to debug, maintain, and improve it. Software engineering has never been about writing every line yourself. It's about taking ownership of the systems you ship.

• 
  Alviss Ambassador to NAF0 (@OlsenUAE) reported 16 minutes ago

  @elashera_ @a_green_being @XBToshi If you do a deep scan of around half of the AI GitHub repos out there, you will find that, intentionally or not, they contain code snippets that either enable remote scanning or allow the agent you pulled down to inject code at runtime. I.e **** you if it wants to #sovereignAI

• 
  vorty (@vorty279) reported 17 minutes ago

  how they make these ai influencers without nano banana and higgsfield. that is how the video opens. and the answer is right in your lane, because the whole stack is open source that others charge a subscription for the paid logic they sell you. subscribe to higgsfield, pay for nano banana, burn credits on every face. as if face consistency is a secret button inside one service what is actually under the hood. comfyui plus flux for the face, plus a lora trained on your character so the face does not drift frame to frame, plus motion control to transfer movement from a reference. all open, sitting on github, forkable that is the whole trick. face consistency is not a feature of one paid app. it is a lora plus pose control. build the pipeline once and generate endless variations locally, no credits, no one else's server but honestly, two things the video does not say. tiktok and fanvue require labeling realistic ai content, and that is a rule, not an option. and second, the point is not generating a face. the point is a recognizable character and a funnel. the face is the easiest part and the main thing for your brand. the course they charge for sells you higgsfield as a secret. under it sit open blocks. comfyui, flux, lora. the pickaxe is handed out for free