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:

• 
  Andrew Babbitt (@andrewbabbitt97) reported 6 minutes ago

  @julian_center @fuolpit Tried both, this is way better integrated with GitHub issues / PRs and code review. No need to leave the app for the entire development cycle

• 
  Rommel Azucena (@JRAzucena_) reported 6 minutes ago

  What's so special about /loop? I just use it to grind issues that I post on github issues. Then I left my machine to grind those issues. So whenever I'm out I just create issues on my phone and when I'm back i'll still manually test out the PRs created during the loop. 🤔

• 
  Avi Chawla (@_avichawla) reported 18 minutes ago

  Claude Code without this new tool is like *** without GitHub. Claude Code stops at the boundary of your terminal. - It can't see what's happening in production right now. - It doesn't know which PR broke the checkout service. - It can't tell why a Datadog alert got fired. - It can't see the Slack thread where the team decided not to touch the retry logic. These are operational and institutional memory gaps that eat up engineering time every single week. The solution is now actually implemented into the @coderabbitai Agent. It lives inside Slack and connects to repos, issue trackers, docs, monitoring, and cloud infra. When a production alert fires, you can mention it in the thread, and it traces the problem through your APM data, finds which recent PR caused it, and can open a targeted fix without anyone switching between five different dashboards. When the incident is resolved, it can document what happened and create a ticket in Linear with the timeline, root cause, and relevant PR links. Note that this is not a one-off assistant. The agent retains what the team decided across threads, channels, and the entire org. So the context from this incident is already available next time someone touches the same service. I've shared the link to try CodeRabbit Agent for free in the replies. Thanks to CodeRabbit for working with me on this post.

• 
  咖啡豆抹茶 (@Saten000) reported 20 minutes ago

  @github #GitHubSupport Hi, my account lb2006ok was suspended. I got stuck in a login loop and made multiple attempts with different proxies – likely flagged as suspicious. Could you please review? This account is crucial for my coursework. Thanks!

• 
  AI Theory (@AItheoryx) reported 20 minutes ago

  🚨 YOUTUBE ALGORITHM KEEPS FEEDING YOU TRASH. THIS GITHUB PROJECT LETS YOU DELETE THE ALGORITHM ENTIRELY. Meet TubeArchivist. Your self-hosted YouTube media server. Subscribe to channels. Download every video automatically using yt-dlp. Index everything with metadata. Search, play, track watched status. Full control. No ads. No recommendations. Just the content you actually want. Plex and Jellyfin plugins included. Browser extension to grab videos with one click. Built on Docker. Runs on Unraid, Synology, anything. The question YouTube does not want you to ask. When you can archive every creator you follow and watch offline forever, why are you still letting an algorithm decide what you see. TubeArchivist. Because your attention should belong to you. 🧾

• 
  andrewthecoder (@_andrewthecoder) reported 24 minutes ago

  @emahpour what I would really love..this is my *********! I have 70+ public repos on GitHub; how cool would it be to login one afternoon and see that someone has not only looked at one, started one, forked one, but posted an issue! Or MAYBE even a PR addressing the issue! man, dreams.

• 
  Josh Koenig (@outlandishjosh) reported 24 minutes ago

  We took the trouble to build a first-class GitHub integration, whereas they have some scripts they'll run. We spin up environments automatically for every pull request, whereas they have one dev env that you have to figure out how to juggle.

• 
  whydeepak (@ideepakmn) reported 24 minutes ago

  Spent the last month building a "Zomato for restaurants" And the most interesting lesson wasn't technical, it was economic: a small kitchen keeps almost nothing on a delivery order, and almost nobody running one has done the actual math. Here's the breakdown. On every order the platform takes commission of roughly 28%, plus GST, plus a payment mechanism fee, plus tax. Stack it and the restaurant is left with pennies. The only way to win is volume, which means for a new cafe it's roughly a 20/80 game luck and demand do most of the work. That's fine for a large restaurant with through put, but it's quietly brutal for cafes and cloud kitchens that live and die on margin. So the question I got interested in is purely mechanical: how much of the ordering + logistics layer can you rebuild yourself, and how cheaply? Turns out, most of it. You don't need payment gateways redirect everything to WhatsApp. You need a dynamic menu you can manage in one click, with inventory living in Supabase, if something runs out, one command flips it off the menu. For tracking, you record how long each dish actually takes to make, set that as a standard timer, and expose two flows: takeaway and delivery. Delivery itself is the part everyone is scared of and it's the easiest to solve one extra person handles it, free under 3km, then ₹10-20/km beyond that, matched to standard delivery-partner rates so nobody's overpaying. Add a minimum-order threshold for free delivery and your average order value climbs on its own. The V1 stack is deliberately boring: Next.js, React, TypeScript on the frontend, Next.js API routes on the backend, Supabase (Postgres) for data, Vercel for hosting, *** and GitHub for version control. Nothing exotic and expensive. The edge was never the tech it's that you've removed the platform tax that was eating ~50% of the economics. The money you save covers the extra hire who runs delivery and helps in the kitchen. It pays for itself. Now the part customers never see. Ever wonder why the same dish costs more on the app than at the counter? It's not random. The restaurant has to bake the platform's cut commission, fees, packaging back into the menu price, or it loses money on every order. So the delivery price isn't the food price, it's the food price plus the tax you can't see. In practice that lands the same dish somewhere around 1.5x-2x what you'd pay at the outlet. You're covering the commission and it's being sold to you as convenience. The fix is almost funny: just ask the restaurant if they deliver directly. And yet Zomato or Swiggy is a giant for real reasons, and it's worth being honest about that. Discovery, trust, and food at your door in minutes are genuine value. We live in a world where the thing that took 10 days now arrives in less than 10 minutes, and people are happy to pay a premium for everything in one place. Convenience is a real product, not a scam, and any builder who ignores that is fooling themselves. So I'm building this anyway not to kill the giant, but because kitchens running strictly on their finances deserve an option that respects their margins. Every idea has its perks and its downsides. I'm a builder and a marketer; I like shipping ideas and finding out. I'm already working on this one. If you ran a cloud kitchen or a cafe, what would you do differently?

• 
  Circumjovial (@CircumjovialLLC) reported 24 minutes ago

  @TheHackersNews Github is down right now too ... bad timesfor Github!

• 
  𝙶 𐍆𝖚𝝶Ԟሃ ⊤ḥе ᗩ𝝶𝙞ጦ၉𝝞 (@GFunkyTheAnimal) reported 25 minutes ago

  @mattpocockuk When I see 63 issues in 14 hours it makes me glad no one ever looked at my github lol

• 
  Mark Miller (@musicallymark) reported 27 minutes ago

  @claudeai Please fix your GitHub integration for Claude desktop 🙏

• 
  chandram (@ChandramDutta) reported 28 minutes ago

  oh @github not down again. my builds are failing.

• 
  Depressed Skeleton (@Skeletorexplain) reported 30 minutes ago

  @alanvibe Speaking for Australia, Once they are given these powers, they continue adding to them nonstop. We don't get a say in any of it & promises are broken. By late this year they'll have age verify in every app store etc, they are considering slapping it onto github & OS's.

• 
  top10.dev (@Top10_Dev) reported 31 minutes ago

  So your only edge is visible work: your GitHub graph, your ship rate, your taste in which problems matter. That's all that's left. That's your resume.

• 
  SITA (@S1TA10) reported 31 minutes ago

  OpenAI just added to Codex what you are paying for separately. Plugins. Tasks. Image Generation. In-App Browser. Four things. One tool. Same subscription. Let's start with plugins. GitHub already connected. Slack already connected. Notion, Linear, Gmail, Google Calendar, Google Drive all inside. No switching between tabs. No copying links from one app to another. Codex sees all of it directly. Then tasks and memory. Check for Sentry crashes - every 2 hours. Every morning - starts in 30 minutes. Find and fix bugs - daily at 8pm. Weds at 7am - audit. You set the schedule once. Codex works while you sleep. Then image generation. Not Higgsfield. Not Midjourney. Not a separate DALL-E tab. Directly inside. The same tool that writes your code generates images. GPT Image 2 is already in the subscription. Most people don't know this. And finally in-app browser. Codex opens the browser itself. Sees what is on the screen. Clicks. Fills forms. Plays Tic Tac Toe to prove it actually controls the computer. Not simulating doing. Codex stopped being a tool for writing code. It became an operating system for your workflow. I built a skill that calls GPT Image 2 through Codex in one command. Logos. Mockups. Icons. All covered by the subscription you already have.