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:

• 
  Jon Church (@jonchurch) reported 20 seconds ago

  @jdxcode @nateberkopec @github I know that’s not feasible for everyone, some folks want to read issues etc in their private repos. But, finger to the wind, I think the majority of devs dont use the cli for private repos so default should be opt in not opt out for higher privs

• 
  Bonsai 🌳 (@bonsaixbt) reported 48 seconds ago

  THIS STUDENT WAS VIBE CODING AN APP, THEN GOT A $55,444.78 BILL FROM GOOGLE CLOUD All because they accidentally pushed their Gemini API key to GitHub They thought the repository was private It was just a small side project, and they still had $220 in free credits left By the time they checked their email, it was already too late This video shows exactly how things like this happen and why more and more developers are running into the same problem: > One commit turned into a $55k nightmare > API keys were exposed in frontend code and even inside app binaries > People hardcoded secrets into scripts and ended up with hundreds of dollars in charges within hours > One OpenAI key was abused nearly a million times before anyone noticed Never hardcode API keys Never commit them to GitHub, even if the repository is private Never expose them in your frontend Always use environment variables and set up spending alerts Even in the era of vibe coding, security still matters Knowing a few basic best practices can save you from some very expensive mistakes If you’re a vibe coder, make sure to read the article I attached, you’ll find plenty of practical tips that could save you a lot of trouble Save this post so you don’t lose it

• 
  Deependra Solanky (@solanky) reported 50 seconds ago

  Codex GitHub repo has only a few open issues labeled macOS, but hundreds for Windows. Windows has the extra challenge of supporting both native Windows and WSL workflows, and that complexity shows up in the issue tracker. I think it’s time for me to pause on WSL mode in Codex Desktop and go back to running Codex CLI directly inside WSL until things stabilize.

• 
  fahri-seestarz (@mfahrim7) reported 2 minutes ago

  i spent half an hour trying to make github copilot fix my use statements after i move files and folder around. it did not work. bruh i could've finished 20 minutes ago

• 
  Chats 🇨🇦 (@ChatsFi) reported 4 minutes ago

  @ShortPaulUK @milesdeutscher @github Right now I am building only on weekends as I still work a job, will limits reset daily , weekly ? Co Pilot Pro plan mostly ran models older than Opus and GPT 5.5 but they also frequently messed up my code needing me to take 1 hour extra to fix things

• 
  Superintendent (@wawamachine23) reported 6 minutes ago

  @github can you guys unlock my ******* account, your ****** support doesnt respond, your ****** addons dont work, so now i cant update any of my websites that pull from github, and all of my public repos are shut down. no wonder no one uses u guys anymore. terrible service.

• 
  Lux Sp4rk (@lux_sp4rk) reported 9 minutes ago

  I'm still using GitHub for issue management like a caveman, treating them like agent cards. Gotta fix ts immediately or I too aint gonna make it

• 
  Cyprian (@realcyprian) reported 10 minutes ago

  Adding CA in bio is not really my problem cos most bankr projects do it, and they've performed well.. but adding it at the top of your website or github is a No for me, man. Another one is projects constantly tweeting ca and talking about PA.. for me, it is an obvious farm. If you want to farm, farm maturely and stop making it look obvious

• 
  Recaply AI (@recaplyai) reported 13 minutes ago

  8. Fallback Commands when a search returns no results, Raycast runs fallback commands instead. configure: "search Google for this", "open new GitHub issue", or any custom action.

• 
  Dami-Defi (@DamiDefi) reported 15 minutes ago

  Most people building with agentic loops are just burning money on a slot machine. Here is what a loop actually is and when it makes sense. The two ways of building with AI: 1. Human in the loop (what you are used to) You prompt. The AI builds. You review. You prompt again. You are directing every step. Most of us build this way. 2. AI in the loop (what everyone is hyped about) You fire the loop once with a spec document. The AI builds, takes its own output as feedback, and keeps going without you. No check-ins. No steering. You come back when it is done. This sounds incredible. It is also why Peter burned $1.3 million worth of tokens in a single month. ➤ Here is the problem nobody talks about. Your spec document never covers everything. It is impossible to fully contextualize a product in one markdown file. Things evolve. Details get missed. The agent fills every gap with assumptions. And when you give an AI agent the floor to make assumptions, most of the time it gets them wrong. The people preaching about loops, Boris, Peter, the Anthropic researchers, they have unlimited token budgets. Of course loops make sense when tokens cost you nothing. If you are on a $20 or $100 subscription, this is not for you. You will burn through it and have nothing usable to show for it. It is a slot machine. You pull the lever. Sometimes you win. Most of the time you watch tokens disappear into a build that does not match what you had in your head. ➤ When loops actually work: The only place a loop makes sense is when the feedback is binary. Either the output met the criteria or it did not. No judgment. No taste. No nuance. Code review is the clearest example. Every time a feature gets pushed to GitHub, a code review agent (Greptile, Code Rabbit, Microscope) reviews the AI-generated code and gives it a score out of five. The rule: nothing goes to production unless it scores four or higher. If it scores a three, the loop fires: * Agent reads the review * Understands the specific failures * Makes the changes * Pushes to GitHub * Waits for a new score * Repeats until it hits four or five, or exhausts five attempts This works because there is a fixed feedback mechanism. The score is the signal. The loop has a clear definition of done. Even this breaks. When a code push exceeds 1,000 lines, the loop almost never reaches a five. Too much context for the agent to fully process. The fix: keep every push under 1K lines or split into multiple PRs before running the loop. ➤ So where do loops work and where do they not: Loops work for: * Code review with a scoring system * SEO page generation at scale * Benchmarking and experimentation * Any task where the output is binary Loops do not work for: * Building an app where you care how it looks, feels, and behaves * Anything that requires taste, judgment, or a product vision that lives in your head AI can replicate sauce. It cannot create sauce. The future will probably look different. Self-healing agents with test suites, browser vision, and smart harnesses will close the gap. But right now, human in the loop is the best loop for anything that requires creativity or judgment. Human in the loop is the best loop.

• 
  Timur Yessenov (@Timur_Yessenov) reported 15 minutes ago

  @akshay_pachaar GitHub and Playwright are the two I’d make every Claude Code workflow prove first. Can it read the issue, change code, run the UI, and show a screenshot? If not, adding Slack/Sheets just gives the agent more places to make a mess.

• 
  DarrenLopez (@darrenlopez001) reported 18 minutes ago

  VibeLayer stops coding agents from putting fetch() everywhere. It gives AI-built apps: - local state first - named mutations - durable queue - backend adapter So apps feel instant, survive reloads, retry failed sync, and stop making every click a server round trip. GitHub:

• 
  Lambda Rick 🏴‍☠️/acc (@benrayfield) reported 29 minutes ago

  @JoePro can it mod and deploy my video game that is just a static content html file at a github url? can it turn it into a multiplayer game? do i gotta provide server cost while ppl play the game?

• 
  Marek Knápek (@MarekKnapek) reported 29 minutes ago

  @ProgramMax I added detailed explanation how this works to your GitHub issue about this. Basically, when import lib in the SDK decides to import by ordinal, then such ordinal can not change in the future. Some import libs do this, others do not.

• 
  🅾🅼🅰🅼🅾🆁🅸 (@oMaMoriTTV) reported 29 minutes ago

  Do I need to give Google my Driver License or SSN? Hello, oMaMoriTV here, guys. Today, I feel like I'm getting scammed by my local weather station. Yesterday, they predicted an 80% chance of rain and a flash flood warning for my area. But today... I'm turning my AC back on while the bright sunshine cooks my house at 92°F. That brings me to our topic today. I need to address a narrative being pushed by self proclaimed "IT Pros" "Cybersecurity Experts" and "AI Engineers" They are flooding social media with panic inducing headlines like: "You will lose your phone" "You are no longer the owner of your device" "Google is taking full control" Take a deep breath, my brothers and sisters. It’s completely understandable why these viral posts made you panic. It sounds incredibly scary like Google is abruptly turning your personal phone or tablet into a bricked, locked ecosystem overnight. But let's look at the facts. 🧐What is Google Actually Doing? Google is rolling out a new policy called the Android Developer Verification program. 🟢The Core Change: Starting in September 2026, Google wants app developers (not you, not the user) to register, pay a one time $25 fee, and verify their identity with a government ID to distribute Android apps (APKs), even if they distribute them outside the Google Play Store. 🟢So whats happening?: This is being pushed via a background update to Google Play Services (the underlying software suite that handles security on most Android phones). 🟢Google why what on earth?: They claim it's a safety measure to stop scammers and hackers from anonymously distributing malware and banking trojans through random links. 🧐Will it block "F-Droid" and sideloading(github) entirely? No, but it is going to make it significantly more annoying. Google is not hard blocking unverified apps out of existence. Instead, they are introducing an "advanced flow" for power users to bypass the restriction. If you want to install an APK from an independent developer who refused to register with Google (like a hobbyist on GitHub or certain indie apps on F-Droid), you will have to do the following: 1⃣ Turn on Developer Options (by tapping your build number 7 times). 2⃣ Toggle a setting called "Allow Unverified Packages." 3⃣ Answer a "scare screen" confirming no one is coercing you. 4⃣ Restart your phone (this instantly kills any active scammer phone call or remote session). 5⃣ Pass a mandatory 24 hour security delay (a cooling off period to break the false sense of urgency scammers use). 6⃣ Come back the next day, re-authenticate, and click "Allow Indefinitely" 7⃣ Once you do this on your device, you can continue to use F-Droid and github apps. The real concern raised by the open source community is the friction it creates forcing developers to choose between giving Google their private ID or making their users jump through these hoops. 🧐Answering Your Specific Fears 1. Will my Android device become unusable? Absolutely not. Your phone will work exactly as it does now for calling, texting, browsing, and using 99% of your apps. 2. Do I need to give Google my Driver License or SSN? No. As a regular user, you never have to hand over your government ID or sensitive personal data just to use your phone or sideload an app. The ID requirement is strictly for app developers. Furthermore, Google is creating a free "Limited Distribution" account path for students and hobbyists to share apps with up to 20 devices without needing an ID at all. 3. Is F-Droid dead? No. F-Droid will still exist. However, individual open source developers who value absolute anonymity might refuse to hand their IDs over to Google. For those specific apps, you will just use the Developer Options bypass I mentioned. 🧐Why are people so angry if it's not a total lockdown? The tech community and digital rights groups are rightfully angry because Android was built on being an open platform. By adding a 24 hour waiting period, Google is creeping toward a "walled garden" similar to Apple iPhone. Because this is handled via Google Play Services, it bypasses major Android OS updates, meaning Google can change these rules down the line. 🌟The Bottom Line 🌟 Your phone is still yours, and you aren't being locked out of it. The viral posts are trying to spark a massive public backlash to force Google to walk back this policy before the deadline but you do not need to panic about your device being ruined. Furthermore, this policy is only launching in Brazil, Indonesia, Singapore, and Thailand in September 2026, with the rest of the world rolling out much later. IT professionals and content creators have a duty to "de-escalate" situations, provide context, and explain how things work not trigger public panic for engagement. If you use the title "Cybersecurity" think twice before you just blindly throw a panic farming article onto social media. I will keep a close eye on these policy changes and let you know if anything updates. Stay safe, and stay rational! Like, Follow, and Sub for more fun and detailed inside stories.