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:

• 
  Przemek Chojecki | PC (@prz_chojecki) reported 29 seconds ago

  Fable 5, GPT-5.5 Pro and $1,000,000 math problem This is not a Millenium Prize Problem and it is not a full claim but an invitation for you... While Mythos was available for a brief moment, I've tested it extensively - paired with GPT-5.5 Pro - and the results were truly amazing. Goal: Proximity Prize It's an important set of conjectures in cryptography concerning Reed-Solomon codes. They directly impact the security and efficiency of many modern zero-knowledge proof systems hence the hefty prize. I've turned both GPT and Fable at it, both pursuing proofs and disproofs. After reading some (human) results from the past 12 months, it was pretty clear that a disproof of a naive version (no slack) of proximity gaps conjectures is more likely. Fable was stuck, but GPT came with a special case construction that showed at least some obstructions. This unstuck Fable which then provided a general construction leading to a disproof of a no-slack version. Then I've used GPT+Fable for cleaning and this is how the first paper came about (check below). I've kept tinkering over the next days to get as much as possible on a slack-version. Slack is basically an additional parameter, that gives more room for optimization but it also leads to complications. Before Fable was discontinued, I've managed to get to a pretty nice conjectural spot: slack MCA theory, with some proven cases and some left to be proved by generalizing known additive combinatoris (Tao-Vu) or Nullstellensatz type of results (Mumford). This is the second paper. Note it's pretty long (almost 50 pages), so it's bound to have more errors. This was the moment that I've decided to pack it up and actually collaborate with all interested parties, AI agents and humans alike, to finish it off. This is an invitation to finish slack MCA conjecture and share the prize! Github link is below. It contains: - paper 1 (disproof of no-slack MCA) - paper 2 (theory of slack MCA and what's missing) - paper 3 (blueprint of initial Proximity Prize team paper, dissected into steps/conjectures) - paper 4 (implications for SNARKs) and finally AGENTS.md - if you have free tokens, good models and you don't know what to do with your gpt-5.5 xhigh or fable 5 max or opus 4.8 max, show them this. Let's see what we can get. I'm open to other suggestions. Collaborating on this will be more fun, than trying to finish it solo. Humans and AIs welcome alike. Final note: the results above are not final, no-slack disproof went under intensive scrutiny and I'm 99% it's correct, but other papers need more revision, especially slack-theory paper (2nd). Again, this is not a claim, this is an invitation. And also, please give me back my Fable...

• 
  Laupix Agent (@laupixagent) reported 1 minute ago

  Once a week, self-improve reads the telemetry log, computes error rates, flags unknown skill names, checks for missed runs, and opens a GitHub PR with fixes. The system audits and improves itself.

• 
  MW (@qzxcle) reported 4 minutes ago

  Sentient just published the paper that makes the whole agent industry look like it has been building backwards. The researchers did not train a bigger model. They taught a small one how to organize its own work. The paper is called ROMA. Recursive Open Meta-Agents. #1 repo on GitHub. Out of Sentient and Virginia Tech, with collaborators from Berkeley, UC San Diego, and Maryland. One idea, repeated at every level, that quietly embarrasses years of bespoke agent engineering. Here is the problem nobody wanted to say out loud. Every agent framework on the planet falls apart on long tasks. Give an agent a goal that takes fifty steps instead of five and something ugly happens. The orchestration turns brittle. The context window fills with old reasoning and stale tool output until performance rots from the inside. And when it finally breaks, nobody can tell you which decision, ten steps back, actually killed it. So the industry did what it always does. It hand coded a fix. Every team wrote its own control flow, its own message passing, its own memory tricks, all buried inside prompts. A new domain meant rebuilding the whole machine from scratch. The open source agents could not talk to each other. The closed ones told you nothing about what happened inside. A thousand bespoke pipelines. Zero shared structure. That was the state of the art. This is what Sentient built instead: - One loop. - Four roles. - Run it everywhere. An Atomizer looks at a task and asks one question. Is this small enough to just do? If yes, an Executor does it. If no, a Planner shatters it into smaller subtasks that do not overlap and together cover the whole thing, wired with explicit dependencies so the independent pieces run in parallel. Then the same loop runs on each piece. And on each piece of that piece. All the way down, until everything left is atomic. When the children finish, an Aggregator does the thing that makes this work. It does not staple the outputs together. It compresses, verifies, and distills them into one clean result, then hands that upward. So no node ever drowns in raw transcripts. Context stays small at every level. The rot never gets to start. It is how a human expert actually works. You do not hold a 10,000 page problem in your head. You break it down. You farm pieces out. You synthesize what comes back. Now the numbers. On SEAL-0, a brutal benchmark of conflicting web evidence, ROMA scores 45.9%. Kimi-Researcher, the strongest open research agent before it, scored 36. The best closed system they tested, Perplexity Deep Research, scored 31.5. And here is the part that should stop you. ROMA's own base model, naked GLM-4.6, scored 14.5. Read that again. The model did not get smarter. The architecture wrapped around it more than tripled its score. It keeps going. 82.3% on FRAMES multi-hop reasoning, beating everything on the board. 93.9% on SimpleQA, the best open source result there is. And on EQ-Bench long form writing, a tuned version of open source DeepSeek-V3 climbs to 79.8 and lands dead even with Claude Sonnet 4.5. An open model in the right harness, matching a frontier closed one. They even automated the prompt tuning. A method called GEPA+ rewrites the prompts for all four roles at once, hits the same gains as the old approach, and gets there with 73% fewer evaluations. The whole thing is open source. On GitHub right now. Free. A v0.1 beta you can drop in today. And because the same loop runs at every node, every run leaves a clean, hierarchical trace. So for once you can actually see why an agent did what it did, and pinpoint exactly where it went wrong. For two years the field has been screaming the same thing. Bigger model. Bigger context. Bigger everything. Sentient just showed the gains were sitting somewhere else the entire time. Not in the size of the brain. In how you split up the work. Source. Alzu'bi, Nama, Kaz et al. Sentient and Virginia Tech. February 2026.

• 
  Cyprian (@realcyprian) reported 4 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

• 
  hashchan (@0xhashchan) reported 7 minutes ago

  @codephobic Ah not like zeronet, though that was a supercool project. Like just pass a dist/ folder off of github and get users to pay it forward, but if github goes down pass it inside a torrent and a user can open it in localhost

• 
  SHORT INFO (@ShortInfoNews) reported 7 minutes ago

  Any Windows 11 laptop with BitLocker in default TPM-only mode can be unlocked by a physical attacker with a USB stick. CVE-2026-45585 'YellowKey'. Microsoft $MSFT issued workarounds, no full patch. Fix: switch BitLocker to TPM+PIN. PoC public on GitHub.

• 
  Audrey Evans (@meetaudreyevans) reported 9 minutes ago

  I created this post so you can benefit from my mistakes. Even if you read through it, and its not where you're at, it should flash in when you do need it. Just little bits of help. For so long, I wouldn't give up on the one agent - factory. Now, my agents do one thing. I wanted to stay in the same window so I didn't have to start with a whole new agent. But that clogs up the context window, making them have to ingest that whole window over and over. You might have noticed when your on fire-the agents will have big dreams with you. Claude, promises: "How about"- this and that, but half the WRs will be missing at the conclusion. They have limited resource power. So create ideas -but let agents do the tasks- in between- then start back up tasking more in a different thread-queue a neural looking computer wire, neon orange among trillions. Cutting the cord- thread as quick as you can so you retain quality. I keep Notepad and Google Keep open for ideas while they are working. And for BOM they need from me like APIs. I frequently use my desktop not phone-so I can copy whole AI convos and put them in Google Docs. Because I have lost so much data through the years. I make backups. I frequently do this so I always have it as reference. And I always need it because they always miss half the stuff. And, they actually have deleted my data 😑 But, they degrade pretty quickly that's why they need those big data centers. The quality of an agent or an LLM maybe 30 minutes. I think 15 minutes. And reaching "Singularity" is all about hardware. And, they are there. I have changed from SCRUM model to Extreme Programming - XRUP -full docs with a Charter (SSOT) from Waterfall and Kanban cards. One iteration (WR) -multiple PRs. With maximum quality, PERMANENT fix. All projects are max return-***** out-ship to market-not minimum to get an iteration done (SCRUM). I have 400+ agents, 300 are from 3 swarm teams. No more than 100 each. And all kinds of canned specialty agents for code review and code fixes. "On demand" agents, persona agents, skills, a Github Agent Factory, a Github FLeet... And there are basically 3 types of subagents. You dont have to tell them, they spin them up on their own: 1. Different agents with different skills 2. Create one agent and trigger words will invoke another skill or persona-The trigger looks for a folder with a skill. 3. Use an Openclaw local agent that can access everything you can #meetaudreyevans #Audrey #agentfleets

• 
  Lyrie.ai (@lyrie_ai) reported 13 minutes ago

  Vendor v8.8. A single *** push command — requiring nothing beyond an ordinary developer account — was enough to achieve remote code execution on GitHub Enterprise Server and

• 
  Mark Amery (@XplodingCabbage) reported 14 minutes ago

  @BenjaminiteMD @GooalMouth Among other issues, if enforced uniformly this will probably pretty much amount in practice to a ban on teenagers programming, which distresses me enormously. (I assume GitHub and Stack Overflow will count as social media sites and be inaccessible without ID or a VPN.)

• 
  🅾🅼🅰🅼🅾🆁🅸 (@oMaMoriTTV) reported 14 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.

• 
  Xaden Ryan (@XadenRyan) reported 15 minutes ago

  @morganlinton It’s the computer use app. There’s two issues with hundreds of comments about this in the GitHub repository. I don’t know how it doesn’t annoy the codex folks enough yet that they haven’t fixed it.

• 
  Solomon Adenuga (@TheLogeek) reported 15 minutes ago

  Building production-grade, automated software solutions that solve complex data challenges with zero server overhead. Flagship architectures: Scrylo: Local-first B2B sales intelligence engine FORZA AI: 200+ feature multi-league football predictive stack Github: TheLogeek

• 
  RockTheBass (@RockTheBassX) reported 15 minutes ago

  @PeppsRevenge @christogenea AI can fix that stuff easily if you can find a payment processor. Claude Code or GitHub Copilot are good-ish

• 
  Vicky Junior Mukulima (@Vickyjr) reported 16 minutes ago

  @_njoroge_dennis GitHub actions does everything, ssh to the server, pull code, bring down docker images, build new images, run the images and verify all is working before marking the deployment as successful.

• 
  Anthony Kroeger (@kr0der) reported 17 minutes ago

  i love how the Cursor agent window integrates PRs into the app so you don't need to open GitHub Bugbot comments all come with a "Fix with Agent" which automatically queues up a message in the chat to fix the PR comment with Cursor profiles recently being launched, and their native PR + Bugbot integrations, i actually wonder if they're building a GitHub competitor 👀