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:

• 
  EddLev | Latent & Meat Space Observer 🇩🇰 (@edd_lev) reported 6 seconds ago

  @vivoplt Developers are more essential now more than before. Code generation shifted from human skill to AI execution, turning the developers responsibility to oversight and fixing the code. With proper prompting, the code generated is okay, which is much better than the spaghetti code it was before, but it doesn't think about the problem nor the application how a developer would. For the most of it, it is retrieving the data from GitHub/Slack/Documentation and treat it as a valid source. A developer would consider multiple or alternative approaches, etc. So, AI is not mature enough to actually write 90% of a valid, production-approved code. Until then, devs, programmers will survive in tech.

• 
  rehash3d (@r3hashed) reported 39 seconds ago

  @Polymarket JUST IN: Polymarket is down 15% of the time taking over GitHub in the leaderboard

• 
  Sam Thapa (@SThapa123456) reported 41 seconds ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  HumanPulse Protocol (@HumanPulse_HPP) reported 2 minutes ago

  Development is continuing: when logged in, we can still access the repositories and pushes are working. The issue appears to affect public visibility, GitHub search, and third-party developer integrations. HumanPulse remains active.

• 
  treysync (@0xtreysync) reported 3 minutes ago

  I decided to copy down (literally copy-paste) a Skill file from GitHub. My management told me I need to approve ANYTHING we get off the internet so we don’t endanger our systems. I have no words.

• 
  🔅LAMIS (@lami_thefirst) reported 3 minutes ago

  The biggest red flag in crypto is when a project's X account feels more alive than its product. If every post is a KOL quote, partnership graphic, or engagement bait, I assume the team is managing attention, not building. My strongest green flag is a GitHub with consistent commits from multiple contributors over months. Not a prelaunch sprint. Not one developer carrying the repo. Real teams leave fingerprints in public. Narratives are easy to manufacture. Shipping isn't. I spend less time reading promises and more time looking for evidence that people are solving problems nobody is applauding yet. What's the most underrated signal you check before trusting a project? @RallyOnChain is a good example of a green flag.

• 
  Rajaji (@rajaji2) reported 3 minutes ago

  🚀 Mini Project Alert! Deploy a self-healing K8s app with ArgoCD + Prometheus alerts that auto-rollback on high error rates. Full GitOps workflow, real observability, zero manual intervention. Drop a 🔥 if you want the GitHub repo! #DevOps #GitOps #Kubernetes

• 
  Ativista. (@Ativixta) reported 4 minutes ago

  @jonschxyz @github when they fix it I will subscribe it again! but now, no way...I execute like 10 prompts and spend 5k AI credits! hahahahahahaha

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 6 minutes ago

  🇺🇸 The First Order Consequence: - GitHub accelerated the rollout of Copilot Code Review to more repositories, which is expected to reduce time-to-merge and review turnaround - Developers used the tool to flag issues earlier in pull requests, leading to fewer late-stage rework cycles as teams cleared backlogs faster 🇺🇸 The Second Order Consequence: - Engineering managers observed improved throughput and more consistent review quality, supporting a shift toward smaller, more frequent pull requests rather than large batch changes - Teams standardized on the tool’s suggested checks, which lowered variance in review outcomes across reviewers and reduced the probability of “missed defect” clusters that historically created follow-on bug reports 🇺🇸 Discernment: - Review cycles that previously showed longer delays and higher defect escape rates began to normalize, with early evidence pointing to fewer hotfixes originating from overlooked review comments - Prior interventions such as review guidelines and linting rules remained in place, but teams credited Copilot Code Review with restoring momentum rather than replacing the baseline process 🇺🇸 Reasoning: - Current performance signals included faster identification of common issues during the PR review phase, aligning with the pattern that earlier detection reduces downstream churn - Adoption behavior suggested growing confidence: engineers who integrated the feature more quickly produced PRs that required fewer follow-up revisions, consistent with recovery from prior slowdown 🇺🇸 Judgement: - Early indicators support a net improvement in both individual and team growth, shown by reduced review friction and fewer late-stage corrections - Ongoing monitoring remains warranted to confirm that the recovery persists as rollout expands beyond early adopters, using falsifiable metrics such as average PR review duration, merge lead time, and post-merge defect rates

• 
  ./can (@shcansh) reported 8 minutes ago

  The real test for GitHub Copilot's new one-million-token context window in VS Code is going to be developer behavior around AI credits. If using extended reasoning and huge context eats your budget fast, most devs will stick to defaults out of anxiety. Is anyone actually going to manually dial their reasoning level up and down throughout the day, or will we just wait for IDEs to automate this routing? #GitHubCopilot

• 
  ./can (@shcansh) reported 12 minutes ago

  Local development is shifting from a coding task to an agent-coordination problem. The new Agents window in VS Code lets you run more than 1 agent session side-by-side, while the open Agent Host Protocol standardizes how these sessions sync. Combined with air-gapped BYOK models, GitHub is turning the IDE into an autonomous control room. But does orchestrating multiple agents actually speed up shipping, or are we just trading writing code for a more complex debugging bottleneck? #VSCode

• 
  tako (@imnottristanp) reported 22 minutes ago

  i cant login my @github account. I need to push changes asap 😭😭😭

• 
  Mate Gal (@555kindofguy) reported 26 minutes ago

  @survivetheark Guys put game files on github repo and we’ll fix it, you verify it and deploy

• 
  Tw93 (@HiTw93) reported 29 minutes ago

  🥷 A bit more context on this release: Since 1.5.0, Mole 1.6.2 is 222 commits across 237 files, with 50,084 lines added and 10,855 removed. The biggest work was not one feature. It was making the Mac app feel calmer under real use. Keep Screen On now works from the menu bar, with duration choices and safer recovery after relaunch. Privacy alerts show camera or mic usage without opening the main window, and repeated alerts are grouped by session. Clean Screen turns the display into a plain color, can lock keyboard and mouse input, and always lets you exit with Escape. Software now checks more update sources, including App Store, Homebrew, Sparkle, Electron and GitHub, while avoiding noisy false positives. Uninstall now finds more leftovers, including receipts, launch items, group containers and app support traces, with safer review defaults. Clean can spot large project folders like build, dist, target and node_modules, but keeps them review-only so you decide what to remove. Analyze is faster on large folders, with cache reuse, child-folder prewarming and clearer treemap drill-down. 1.6.2 also fixed the painful preview issues: Software tab freezes, blank uninstall lists, menu bar wake-up edge cases and mic false positives.

• 
  Rifat Ahmed (@Rifat_EE) reported 31 minutes ago

  @arkilus78 check github commits, issues, maintainer activity, and releases. if it stalls, skip.