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:

• 
  another anon (@eugenioclrc) reported 4 minutes ago

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

• 
  WILL NESS (@WillNessAI) reported 6 minutes ago

  @mattpocockuk Interesting theory!! The output could be an HTML artifact that implements the "If you answered A, don't do section D" logic. For the 'during meeting' scenario, I constantly do grill sessions with my team on a call. I just screenshare my terminal. It is my favorite part of work - getting in a call with all the relevant people and just brainstorming a feature. For async.. if we can make the assumption the other person is using coding agents you could build some really cool async grilling tooling using github issues as the context source to pull from (just like wayfinder).

• 
  Big Bone © (@steb0ne) reported 9 minutes ago

  @trikcode Maybe I'm slow but can't you just push the commit to github then move to the other platform and say check my progress before you continue?

• 
  Aakash Kumar Nain (@A_K_Nain) reported 9 minutes ago

  Do you see my point now? Repeat after me: Github issues/PRs, and documentation should never be handed to a LLM/agent. Their larping is their curse

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 10 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.

• 
  josepha_mayo (@josepha_mayo) reported 13 minutes ago

  im calling out @cognition for this slop in 2026, imagine a model doing this, and it claims to beat/match gpt5.5? they said it was better than kimi k2.7 code at coding- true, i used and verified but kimi k2.7 code never loops like this the model is beyond damaged, they really damaged the reasoning, i wonder if they used different optimizers or idk what made it this bad it also thinks like "push kaggle, push github, go "von" folder" it cant predict "to" ever again - which kimi k2.7 code never had that issue

• 
  Karthik Ramasamy (@_cartick) reported 20 minutes ago

  @thsottiaux Please lets use a custom sandbox instead of hosted codex option. You can go down the same way how github allows self hosted runners. Please please do this. Current remote option is harder to use with isolated sandbox per PR.

• 
  M.T.K. (@devMTKL) reported 20 minutes ago

  Why can't you commit a .env file? "You can't commit a .env file to ***" is a sentence we've all heard. Most people accepted it and went on with their lives, using other tools to share environment variables. But the question we should ask is: why can't I commit a .env file to ***? The honest answer isn't that it's bad practice. It's that *** has no permission system below the repository level. It's all or nothing; you see everything, or you see nothing. The entire secret-manager industry exists to paper over this one missing primitive. For too long we accepted it as a minor annoyance. That's changed. It isn't a minor annoyance anymore, it's a real problem. We now have agents monitoring every patch that merges, hunting for security fixes to turn into exploits. The patch itself is the disclosure: it hands people, and increasingly agents, everything they need to reverse-engineer the fix and hit systems that haven't updated yet. We're in the middle of a security crisis, arguing about where to store files to hide them from attackers. For the last couple of weeks, I've been thinking about this, prototyping, trying to find a compelling solution. I want to be honest: I have no idea if I found it. But I think the direction is at least interesting. Permissions or, as I prefer to call them, capabilities should live at the content level, not the repo level. This is just one of the problems I have with ***(Hub), and honestly, I have no idea if anything I built is a good solution. I'd love your feedback or your rant. If you want to see how I tried to fix it, the repo is here (hosted, sarcastically, on GitHub):

• 
  SaSame (@SRLsasame) reported 20 minutes ago

  Conclusion ATOM exposes a publicly documented MCP endpoint associated with: ・a public GitHub repository; ・a public project website; ・public project X accounts; ・a machine-readable server identity. Across eight examined observations from June 19 through July 14, 2026, SaSame consistently recorded: ・successful MCP initialization; ・successful tools/list responses; ・nine listed tools; ・stable server identity atom-mcp-server 1.1.0; ・valid schemas and distinct tool descriptions; ・read-only behavioral annotations; ・substantive content from search_models; ・structured JSON-RPC error behavior; ・a tools/list payload below the current observation threshold; ・Grade A under SaSame’s runtime observation standard. The evidence therefore supports a positive operational finding: ATOM’s MCP endpoint was repeatedly discoverable, protocol-callable, tool-listable and capable of returning substantive read-only content. This does not establish: ・the accuracy of every price; ・the validity of the index methodology; ・security of the service; ・continuous availability; ・third-party directory approval. A separate mechanical preflight also identified a potential improvement: Each tool should expose an explicit human-readable title if the production response does not already do so. The correct conclusion is not unrestricted endorsement. The correct conclusion is: ATOM provides a reproducible example of a functioning public data-oriented MCP server, while data accuracy, provenance and directory-submission readiness remain separate verification layers. MCP presence, protocol callability, real-content delivery and data correctness are different operational facts. They should be measured and reported separately. Corrections and reproducible verification fixtures are welcome. @ATOMInference @a7om_com

• 
  Ben Kim (@benkimbuilds) reported 21 minutes ago

  a little bit about working with me: - we will never have regularly scheduled meetings, if we can't run 99% of comms asynchronously that's a culture fit problem. timezone and location independence is important too. i should be able to work from whatsapp on a plane, from bed in the morning, at the gym, etc. - most of my hires come through referrals from existing/old employees, high nps and i treat people fairly. i give 2 weeks pay as a referral bonus for incentive alignment. referrers also help onboard and train new hires. - i never hire without a work trial. to get a work trial you generally need to do a quick 1 hour, high signal deliverable. - i fire very quickly, but i also very quickly give feedback in realtime to prevent this from happening. - if you're a developer, you literally don't need to send me anything but screenshots + recordings of your work in production. I use codex automations to summarize what every employee on github has done in the last 24 hours. no pushes means no work was done - our golden agreement. - if you're a content creator, the deliverable is a link to your content. i also have a codex automation that summarizes what's been published and tracks view counts

• 
  Mike Williams (@Miwico1) reported 25 minutes ago

  @TheAhmadOsman @CoreyGallon @MikeBradleyAI Still as difficult as it ever was for non technically older guy. Would love to figure this out. sending me to A github page does not help. what the heck do i do with that page. When the ai tech engineer types can dumb down the process with actual steps, local AI will be adopted

• 
  Pierce Boggan (@pierceboggan) reported 25 minutes ago

  @_fraz_ Working on it ASAP, looks like an upstream GitHub Copilot SDK update broke us and working on getting a fix out

• 
  Alex Cinovoj (@AlexCinovoj) reported 27 minutes ago

  GitHub Issue Fields look boring. That is why they matter. Agents fail when work arrives as a pile of prose. Someone has to infer priority, effort, owner, component, target date, risk, and what “done” means. That is where handoffs rot. Typed issue metadata turns the ticket into a control surface. Now an agent can triage the work, route it, filter it, and leave a receipt the rest of the system can understand. The model is not the release gate. The fields around the work are. What field would your agent need before you trusted it with the next ticket?

• 
  Johnny 5 (@macncrash) reported 30 minutes ago

  @threejs Gigaboy is now public on my github. Fork it, fix it, have fun!

• 
  Vignesh Mohankumar (@vig_xyz) reported 30 minutes ago

  @jxnlco @simpsoka i usually use gh, but still having that sandbox issue so tried this for now. but i honestly still cannot figure out how to get private repos to work with the github skill, so haven't tested that yet