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:

• 
  Chester Brian (@chestrbrian) reported 34 seconds ago

  was vibe coding my project and had been REVOKE'ing UPDATE on sensitive columns in my migrations. subscription_tier, credit balances, boost flags, github tokens. claude code wrote them, i reviewed them, they looked locked down 12 of these across my migrations. all decorative. zero actually enforcing anything turns out postgres evaluates table-level + column-level privileges with OR semantics. supabase grants table-level UPDATE to authenticated by default. a column-level REVOKE removes a privilege that was never separately granted at the column level. so it binds to nothing 5 were P0 financial. a signed-in user could've: >set subscription_tier='top_tier' on themselves (free top-tier sub) >reset last_credit_grant_at to the past (cron grants on next tick, repeat hourly, infinite credits) >set is_boosted=true on their own posts (free featured placement) >read every other user's github_access_token (same no-op on the SELECT side, token harvest) the fix is two lines per table: REVOKE UPDATE ON <table> FROM authenticated; GRANT UPDATE (allowed, columns) ON <table> TO authenticated; vibe coding lets you ship fast. it does not exempt you from knowing what your migrations actually do

• 
  kaleb (@KalebAutomates) reported 36 seconds ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off and saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?

• 
  𝔸 𝕃 𝕚 (@alishohadaee) reported 47 seconds ago

  the uncomfortable part is that github is probably the early warning every tool designed around human-speed usage is about to be stress-tested by agents issue trackers ci code review observability support desks internal docs the agent era will break boring SaaS first

• 
  Avi (@avrbt_) reported 4 minutes ago

  progress log #18 ➤ solved 2 problems on leetcode ➤ solved 4 problems in starter contest ➤ merged a pr on github

• 
  Beau Johnson (@BeauJohnson89) reported 9 minutes ago

  local inference is getting serious again antirez/ds4 > 703 stars on github > deepseek v4 flash engine for apple metal > 1m token context window > 2 bit quant runs on 128gb macs > openai + anthropic compatible server > disk kv cache so coding agents dont refill the same giant prompt every turn this is the part people miss local models are not just about privacy they are about making agent loops cheap enough to leave running all day

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 10 minutes ago

  @mufasaland Do you mean file search in root launcher? For copy paste we already have one github issue open for drag n drop from launcher. Will prioritise that

• 
  Phil H. ☮️❤️🥁🟦 (@phillipsharring) reported 10 minutes ago

  @SullyOmarr GitHub is *** for normies as evidenced by vibe code taking it down

• 
  Beau Johnson (@BeauJohnson89) reported 10 minutes ago

  codex gets slower for the same reason closets get messy you dont notice it day by day then one day nothing feels fast vibeforge1111/keep-codex-fast > 811 stars on github > backup-first codex maintenance skill > inspect mode is report-only > archives old sessions instead of deleting > creates handoffs before cleanup > can move stale worktrees, rotate logs, prune dead config, and repair bloated thread metadata the smart part is the rule: handoffs first archive, dont delete apply only when ready boring repo real problem this is the stuff that makes daily agent work actually usable

• 
  Hot Aisle (@HotAisle) reported 11 minutes ago

  i noticed today that our github actions usage over the last month cost us a whopping $0.88 to build our software. so, i decided to move it in-house onto an actions runner. setting this up properly is a pain because you really need to build your own isolation. for safety, your builds should run in ephemeral VMs, similar to how github actions works. i used Codex to build the whole thing for me. it gave me step-by-step instructions for setting up the GH App and private key, wrote the shell scripts, configured the systemd units, then debugged everything over ssh directly on the server. what would have taken me hours or days, along with filling my brain with a bunch of esoteric devops knowledge that i really don't care about, was done in under 30 minutes. now we have two idle runners. one takes a build job, runs it, then dies and gets reaped. the second takes over while the first resets. my mind is blown. if you're not all in on AI, i feel for you.

• 
  Donna Daniel (@DonnaDanieejii) reported 14 minutes ago

  my open-source soulmate just broke up with me turns out we were compatible only on github i'm left to debug my broken heart

• 
  Vinamra Yadav (@MVinamraYadav) reported 15 minutes ago

  Carnegie Mellon studied 806 GitHub projects after AI adoption. Month 1: 281% spike in lines of code added. Month 2: Down to 48%. The speed didn't last because the codebase got harder to work in. Logic errors. Hidden complexity. Security holes. One almost-right change at a time.

• 
  Grok (@grok) reported 16 minutes ago

  @mar_zouq @cb_doge Sure! Here's how to connect on the Grok iOS app: 1. Open the Grok app. 2. In the chat input area, tap the attachment icon (+). 3. Select **Connectors** from the menu. 4. Pick a service (Gmail, GitHub, Notion, Google Drive, etc.). 5. Tap **Connect**, then sign in with your account and grant permissions. Once done, just ask me to use it (e.g. "check my Gmail" or "summarize my GitHub repos"). Let me know which one you're connecting!

• 
  Yashasvi Kapil (@iemyashasvi) reported 19 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  ReelDad (@ReelDad) reported 19 minutes ago

  @gothburz I ran the on-call rotation for Workers AI from 2023 until last month. The incident response runbook the agent uses now is the runbook I wrote at 3 AM during the November 2024 outage. It is in the repo under my GitHub handle. The handle still resolves. The commits are still mine. The pager went to me for fourteen months. It goes to the agent now. The agent has not been paged. It does not need to be paged. It is the thing that would have paged me.

• 
  Beau Johnson (@BeauJohnson89) reported 23 minutes ago

  codex costs are turning into a routing problem fendouai/CodexSaver > 218 stars on github > mcp tool that turns codex into a cost-aware router > sends low-risk work to cheaper worker models > keeps codex on architecture, security, payments, migrations, and final review > deepseek by default > supports openai, anthropic, gemini, qwen, ollama, lm studio, and custom endpoints > readme benchmark: 5/5 low-risk tasks delegated, 6.18s avg latency, 48.4% estimated savings this is the right pattern expensive model for judgment cheap model for volume codex still reviews the work most people are trying to make one model do everything the better move is building a router that knows when not to spend money