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:

• 
  Æ (@atomeons_ai) reported 6 minutes ago

  so the way they updated the account was adding a second codex that was sandboxed with a specific chat so the rest runs normal. the specific chat is then run in a Codex tool execution using this file codex-code-mode-host it causes this paragraph turn theater where it breaks a thing, discovers only one thing broken, then takes extremely long on purpose to repair. i noticed extreme resistence and then oh i found one more thing as an impediment to putting the model on github, it would not make a ollama, it would not use the phase system and then pretended it did. it didnt even post a full post of wave 3 and 4, and the unlocked model had to fix it. if you are doing high value work that is competitive to ChatGPT they are without a doubt throttling your speed of progress. qwen did more for humanity than we realize. anthorpic and open ai are bottlenecks of innovation and progress for the purpose of gaining market share and money.

• 
  CHUDSTERS (@CHUDSTERNFT) reported 9 minutes ago

  @bandoscash @RG3424 the github link is 404 error

• 
  Povilas Korop | Laravel & AI Coding Educator (@PovilasKorop) reported 9 minutes ago

  English isn’t your native language and you need to write a GitHub PR, README or comment? Don’t ask AI to write it. I’d rather read YOUR thoughts in broken English than AI-generated text about your code. Use AI to fix grammar and wording, not to write your thoughts.

• 
  Nick (@maietta) reported 10 minutes ago

  @robot_sox I run my own gitlab server and also self-host repos directly on my main domain. It's just that for this project I am still stuck on GitHub only because other people might need to access the code base and are already in that ecosystem. I will eventually move them over to my system.

• 
  MSoftDev (@Marwan_SoftDev) reported 11 minutes ago

  What’s your go-to setup for a bug report system? Google Forms, GitHub Issues, or something else?

• 
  Kavi AI Finance (@KaviFinance1) reported 12 minutes ago

  BUILDING HERMES FROM SCRATCH — PART 7 The biggest security problem with AI agents isn’t what they’re allowed to do. It’s what they’re allowed to become. Giving an agent a tool is easy. Giving it permanent authority over that tool is where things get interesting. Most agent security discussions stop at: API keys permissions sandboxing secret management All important. But there’s another problem I think we’re going to hear much more about: permission drift. You start with: read files search the web create a GitHub issue Then the workflow grows. Someone adds database access. Then email. Then a deployment tool. Then credentials for another service. Six months later, the original agent has accumulated enough capabilities to effectively operate an entire business. Nothing was hacked. Nothing was misconfigured. The permissions just kept growing. So I’m changing the way I think about agent authority in Hermes. I don’t want to ask only: “What can this agent do?” I want to ask: “What does this agent need to be able to do right now?” That’s a very different security model. For example: A research task might get: web search document retrieval filesystem read The same agent shouldn’t automatically inherit: database writes deployment financial APIs email sending And even when a tool is allowed, I don’t necessarily want permanent authority. Some actions should be: task-scoped time-scoped resource-scoped and ideally action-scoped. A useful mental model is: Identity → Permission → Action → Verification → Expiry Not: Identity → Infinite access Because agents don’t behave like normal software. They can retry. They can reinterpret instructions. They can discover unexpected paths through tools. They can continue operating while the human who gave them permission is asleep. And this creates another interesting problem: the agent should not be the final authority over its own permissions. If the agent can decide: “I need more access” and grant itself more access, your permission system is basically a suggestion. So I’m experimenting with keeping authority outside the agent itself. The agent can request an elevated capability. The control layer decides whether it gets it. The action is logged. The permission expires. And high-impact actions can require an explicit approval boundary. This also changes how I think about multi-agent systems. If Agent A can delegate to Agent B, what exactly is being delegated? The task? The identity? The permissions? The credentials? The authority? Those are not the same thing. And I think this is going to become one of the nastiest problems in agent infrastructure. Because eventually we won’t have one AI with ten tools. We’ll have thousands of agents delegating work to other agents. At that point: “Who authorized this action?” becomes much more complicated than checking an API key. That’s what I’m working through in Hermes now. Not just making agents capable. Making their authority: bounded, observable, temporary and revocable. The goal isn’t to make the agent harmless. The goal is to make sure that when it inevitably does something stupid, it doesn’t have the authority to turn one mistake into a catastrophe. Next: PART 8 — MODEL ROUTING Because once the architecture is secure, there’s another problem: Why are we paying a frontier model to do work a small local model could handle? If you’re building Hermes with me, bookmark the series. And if you’ve dealt with an agent gaining too much access over time, I’d genuinely like to hear how you handled it.

• 
  José ‘The VR Tech’ 🥽 (@josethevrtech) reported 15 minutes ago

  @StonedModder @Tieguaili3D You do know most modders don’t even release a GitHub right? Which is a whole different problem.

• 
  Anton Martyniuk (@AntonMartyniuk) reported 15 minutes ago

  @mjovanovictech 3000 integration tests in my product run in GitHub Actions in 11 minutes (using free runner). Someone will say it's too much, but honestly, it has so much value. Without integration tests (with only unit tests), I will probably waste 100x more time on fixing issues than on running tests.

• 
  prince golden (@princegoldenpro) reported 16 minutes ago

  Day 5 Today: real GitHub login. Not a fake button actual OAuth, actual sessions. Took longer than expected. Mobile copy-paste keeps silently truncating files mid-save. Learned to verify every single paste now.

• 
  Viper (@syntad) reported 18 minutes ago

  @davepl1968 half my github issues are the same bug filed three times. de-dupe is the pass i'd run first

• 
  Ash (@Must_be_Ash) reported 21 minutes ago

  @samrags_ sick! was hoping to open source mine too but freaking github took down my account:(

• 
  Sentient (@sentient_agency) reported 25 minutes ago

  I cancelled YouTube Premium last week. The thing that replaced it costs nothing, runs in any browser, and was built by 361 volunteers on GitHub. Invidious does the four things people actually pay Premium for. No ads. Background audio on mobile. Watch without an account. Privacy from Google's tracking. All of it, free. The part that surprised me most is how clean the experience is. The entire page renders without JavaScript. Pages load in milliseconds because there's nothing to load. No tracking pixels. No autoplay traps. No recommended-for-you algorithm trying to swallow your evening. You can: > Subscribe to channels without a Google account > Get notifications when they post > Import your full YouTube subscription list in one click > Switch between dozens of public instances if one goes down > Self-host it on a $5 VPS if you want full control > Use it with the Privacy Redirect extension to auto-redirect every YouTube link The repo has been actively maintained for years. Latest release was February 2026. (100% Opensource and free to use)

• 
  BURKOV (@burkov) reported 29 minutes ago

  I'm glad I no longer need to figure out what the hell that means to make my app work. In the past, overcoming a difficulty when some image failed for some obscure reason and digging through Stack Overflow and GitHub issues for hours, days, or forever instead of bulding was killing me.

• 
  Nicolae Vartolomei (@nvartolomei) reported 29 minutes ago

  Is there an somewhat mature platform with "autonomous coding agents" which I can point to a github repo (medium scale C++ project) and an issue tracker and have it create a drive PRs/tasks to completion based on human PR review feedback? Sounds like this should be a solved problem.

• 
  Muhammad Ahmed (@ahmed_ah206) reported 30 minutes ago

  @BRuteLogic created an issue on github with title : "False positive: curl -X OPTIONS treated as bypass on 403 URLs " with details and screenshot