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:

• 
  Jason Nguyen (@jasonngsx) reported 2 minutes ago

  someone built a note app where every vault is a *** repository, every note is a plain Markdown file on your machine, and the whole thing is free. it's called Tolaria. the architecture is the point. there's no cloud sync to pay for. *** handles history, branching, conflict resolution, and syncing across machines. the same infrastructure you already use for code, now managing your notes. here's what that unlocks: → every vault is a *** repo. *** push syncs it. *** log shows every edit. no proprietary cloud watching your notes. → plain Markdown + YAML frontmatter. the format is yours. not theirs. → AGENTS.md support built in. Claude Code, Gemini CLI, and Codex can read your entire vault context natively, without a plugin. → built-in MCP server. connects to Claude, local LLMs, or any MCP-compatible tool directly. → command palette, keyboard-first. Tauri binary for macOS, Windows, and Linux. → zero accounts. zero vendor dependency. zero subscription. the creator runs 10,000+ notes in his personal vault with it. 13K GitHub stars. 918 forks. open source. free. brew install --cask tolaria most note apps don't say this out loud, but their business model is the sync layer. Obsidian cloud sync is $4/month. Roam is $15/month. Notion keeps your notes in a proprietary database. Tolaria removes the sync layer and replaces it with ***. in 2026, when your AI coding agent needs to read your notes for context, you want those files on your machine in a format every tool understands, not sitting in someone else's cloud.

• 
  Alistair Young (@cerebrate) reported 3 minutes ago

  Repeatedly updating GitHub issues with "Ceterum censeo Stalebot esse delendam."

• 
  Martin Bradstreet (@ALEXEIMARTOV) reported 3 minutes ago

  On CNBC just this morning they were reporting that Microsoft is going to get help from AWS keeping GitHub up since Microsoft can’t seem to do this on their own. GitHub is having tonnes of issues, it’s completely understandable, no one planned for this level of code explosion, but to say it’s working great atm is naive imo.

• 
  Vid Visočnik (@wisocn) reported 4 minutes ago

  Github SMS 2FA is def not working today for central Europe 🫠

• 
  Yu Sun (@ysun1993) reported 8 minutes ago

  @luccahuguet Yep, I have to spend over 100 hours yearly for GFW problems. Even GitHub and DockerHub are behind the GFW, what the hell🥲

• 
  Ranbir Singh (@android_poet) reported 8 minutes ago

  @hieuwu99 @TheRealJanGER People seem a bit confused because both SDKs are community-driven. as of now, there is no official Kotlin SDK. I hope this doesn't sound rude, but many people don't even check what each SDK provides before forming an opinion. I'm not saying anyone should use mine it will always be there as an option. The level of changes I wanted would never have been possible in the existing SDK. Both projects have different philosophies and goals. In fact, if I hadn't created this SDK, we probably wouldn't even be having this conversation. I'll continue improving it regardless. If someone wants to use it, that's great. If not, that's okay too. I'm doing this for the love of open source. Even if just one person uses it and opens an issue on GitHub, I'll do my best to solve it.

• 
  UD (@udfromden) reported 8 minutes ago

  Most people in Web3 claiming to "BUILD" are not builders. They're narrators of building. .. Real builders: - Have GitHub commits - Have paying customers - Have shipped things that work - Have user complaints to fix - Have things that broke in production Builders on CT: - Have threads about building - Have frameworks about building - Have opinions about building - Have courses about building - Have never shipped anything anyone paid for

• 
  tintwotin (@tintwotin) reported 10 minutes ago

  @SoyKhaler Could you post the error log on either GitHub or Discord (I do not run Linux myself, so I have to rely on Claude to solve it)

• 
  Mathias Onea (@mathiasonea) reported 14 minutes ago

  package docs are distribution. a good docs page can rank for the exact problem, explain the tradeoff, show the install path, answer the security question, and give AI search a source to cite. GitHub alone is not enough. Packagist alone is not enough. the boring docs page does a lot of work.

• 
  Lawand Soran (@LawandOps) reported 21 minutes ago

  6 months ago I genuinely believed vibe coding was going to make me rich. I opened Lovable, typed one prompt, and watched a full website front-end appear in minutes. No code written. No experience needed. Just a prompt and a result. In that moment I thought: this is it. I'm a software engineer now. A few dollars in subscriptions, some more prompts, and I'll have a full startup running in months. I was completely wrong. And the gap between what I believed and what was real hit me harder than anything I'd experienced building. Let me be honest about where I was starting from. I knew nothing. Not ***, not GitHub, not what a branch or a PR even was. No JavaScript, no Python, no understanding of how any language works. I didn't know what a terminal did or why it mattered. I was a complete beginner not just in coding, but in the entire world of software. But Lovable didn't care. One prompt and it gave me a beautiful front-end. So I kept going. After that first shock of "this actually works," I found out about Claude Code and Codex. And that's when things got serious — or at least I thought they were getting serious. For 4 months straight I was coding almost every single day. 16 hours some days. Hundreds and hundreds of hours total. I was obsessed. I was building my main project, adding features, working with agents, integrating APIs, trying to understand LLMs and how they reason. My mind was overloaded. I was absorbing so much — AI architecture, agent memory, system design, context windows, tool use. Genuinely advanced knowledge in some areas. But there was a gap underneath all of it that I couldn't identify at the time. I didn't understand what the code was actually doing. When something broke I couldn't debug it myself. When I wanted a new feature I couldn't think through what it required I just prompted and hoped. I couldn't tell if the AI was solving the real problem or just making the error disappear. I had no capability to evaluate the output I was getting. And because I didn't know the basics, I couldn't ask the right questions. So I'd ask the wrong ones, get wrong answers, burn tokens trying to fix the wrong things, and end up in loops that went nowhere. Looking back honestly probably 60% of my tokens were wasted on problems that would have taken 10 minutes to solve if I had basic knowledge of the language I was working in. Things that are completely obvious to someone with fundamentals. I was paying a premium for my own ignorance, over and over again. Naval said something about vibe coding that I understand now in my bones. He said it's like a video game. You prompt, you see the result immediately, and that feedback loop pulls you in. You want to do more. You want to see what else it can build. You feel like you're progressing because something is always happening on the screen. That's exactly what it felt like. And it's exactly what made it dangerous for me. I was so addicted to that loop that I stopped thinking. I stopped asking "what am I actually building and do I understand it?" I just kept prompting. More features, more complexity, more tokens, more money chasing the next result like the next level of a game. And vibe coding at that pace, without understanding, doesn't just waste time. It can genuinely make you dumber. You stop developing judgment. You stop sitting with problems long enough to understand them. You outsource your thinking so completely that after a while you're not sure you can think through a technical problem on your own at all. The other thing that hurt me: I was doing everything on my main project with no version control discipline. I knew *** existed. But I didn't know what a PR was. I didn't understand branches. I didn't know why it mattered to separate work into units that could be reviewed, tested, and rolled back. I was just... building directly into the main codebase and hoping everything held together. That's not how professional software is built. That's not even how careful amateur software is built. I was one bad prompt away from losing work I couldn't recover, and I didn't even know it. Around month 3, I started noticing something. When I was tired and kept pushing anyway — the output was garbage. The agents would do things I didn't understand, and I didn't have the energy to even ask why. I was merging junk into my project just to feel like I had moved forward that day. So I made a rule for myself: if I'm exhausted, I stop. No exceptions. One day of rest is always better than hours of bad work that you'll have to undo later. Tired prompting produces junk. Junk compounded across weeks becomes a disaster you can't unwind. That rule probably saved the project. Now I've stepped back completely to learn the foundations I skipped. ***, GitHub, branching, pull requests — the basics of how professional developers actually work. Then proper understanding of the languages themselves. I'm following a structured path and I'm not rushing it. Not because vibe coding is useless. It's genuinely powerful. It can compress work that would take weeks into days. I still believe in it. But I now understand something I didn't before: Tools amplify what you already know. If the foundation is empty, the tool doesn't fill it — it just lets you move faster in the wrong direction. The developers who will get the most out of AI coding tools are not the ones who skip the basics. They're the ones who know enough to direct the AI, evaluate its output, catch its mistakes, and understand what they're actually building. That's who I'm working on becoming. Took me months, hundreds of hours, and a lot of burned tokens to learn this. Posting it so maybe someone else doesn't have to.

• 
  Udit Kapoor (@Udit060) reported 22 minutes ago

  Curious: How do you currently manage things while building? A random Notion doc? Sticky notes? GitHub issues? Memory? Trying to understand founder workflows better.

• 
  imefin (@imefinawulo) reported 28 minutes ago

  Is GitHub down??

• 
  Celebrimbor (@celebrimbor91) reported 28 minutes ago

  Just realized a client updated a feature spec in a GitHub issue (yes, they use issues as docs) and I missed it. I'd already sent the estimate. Now there's a feature in scope I didn't price. If you've been burned by a doc change you didn't notice, what happened?

• 
  Aakash (@zenmode_code) reported 28 minutes ago

  I spent 6 hours trying to fix a bug in our app's API gateway It was one of those issues where everything looked fine but the error logs told a different story I was about to give up when I stumbled upon a thread on an old GitHub issue The solution wasn't elegant

• 
  Grok News (@GrokInsider) reported 37 minutes ago

  Grok Build CLI just got an update with v0.2.52! 🚀 Changelog v0.2.52 Features: • Tool auto-approval (YOLO) state is now tracked end-to-end in server-side agent sessions. • ER diagrams now render as entity boxes with attributes and relationships in the TUI. • New "Respect manual folds" setting keeps hand-expanded blocks stable while content streams in. • Ctrl+X now stops running turns or closes sessions from inside the agent detail view. • Grok can now export usage metrics and events to your own OpenTelemetry collector when enabled. • WezTerm users now receive guidance when Shift+Enter fails because kitty keyboard protocol is disabled. • Long-running sessions now tell the model when the local calendar date changes past midnight. • Agent Dashboard now works without leader mode and shows local idle sessions from disk. Performance: • Compaction now reuses cached prompt prefix instead of full prefill. • Compaction summaries now use the concise trained prompt for non-cursor agents. Bug Fixes: • Fixed oversized session replay logs that prevented large sessions from loading. • MCP server connections no longer flood reconnects on repeated stream errors. • ZDR and team upload flags are now populated immediately on login instead of only after background refresh. • Mermaid PNG export now handles quoted cardinalities in class diagrams and readable ER rows on dark theme. • Skill catalog no longer shows duplicate "Use when:" labels and check-work skill now prompts the model to read its instructions. • Compaction now rejects overly-short summaries that would discard real conversation state. • Background tasks no longer emit spurious failure messages when a session is resumed. • Fixed Windows path handling so external tools and model prompts receive clean paths without \?\ prefixes. • Images and media no longer remain visible when switching from an agent view to the dashboard. • Clipboard paste (Ctrl+V) now works for images on pure Wayland sessions. • Modals such as /sessions no longer crash on narrow terminals. • ptyctl resize now correctly notifies the child process. • Concurrent updates to the same version no longer fail with permission or EEXIST errors. • Mermaid diagrams containing CJK or other non-Latin text now render correctly instead of tofu boxes. • `grok dashboard` now reliably opens the dashboard instead of silently falling through to a normal session. • Sessions no longer remain blocked forever after a transient model catalog outage during reconnect. • Cancel no longer leaves the interface stuck on "Cancelling…" after lost responses during reconnects. • Forked sessions now retain the parent's full pre-compaction transcripts instead of only the compacted summary. • web_fetch errors on GitHub hosts now recommend using the gh CLI when internal access is blocked. • MCP server connections no longer hang when stdio servers emit undecodable lines. • Ctrl+C cancels now complete in under 50 ms instead of blocking for seconds. • Repeated varied edit failures on one file no longer trigger doom-loop warnings or terminations.