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:

• 
  cheeselip (@lip_cheese) reported 3 minutes ago

  @matteocollina I don't buy it. GitHub - ignoring the social part - should scale easily because it's so easy to partition by repo or account and scale out. These slop repos probably aren't getting a lot of engagement so what's the issue? The issue is Azure lol

• 
  YeHang (@YeHangHarry) reported 4 minutes ago

  @Dadou0327 hello seems like GitHub have some issues with internet so the website goes down for a while. now it's working

• 
  Jamison 🦆 (@jmelahman) reported 5 minutes ago

  @cassidoo ngl, this makes me want to migrate off Github more than the outage itself did

• 
  juliacosette (@juliacosette9) reported 8 minutes ago

  I need a man who goes down as much as GitHub does

• 
  Termsheetinator (@termsheetinator) reported 10 minutes ago

  The best foot in the door with AI is not an “agent” Its truly one cron job via terminal or gui. This will sky rocket your use cases and decrease your token spend and allow you gain measurable ROI from it. As little intelligence as possible for the highest value outcomes is my goal. We learned this after building an entire CRM for my credit advisory firm. Scripts $0 > Intelligence $ Gateway API's that do turn big expensive tasks into micro tasks so we can deploy less expensive models. The highest-ROI part of the system may be the boring script that runs at 6:00 every morning. This saves me SOO MUCH TIME. This new CRM is not a toy or "nice to have" It replaced a legacy CRM and Google Sheets, turns Slack submissions into reviewed deal records, manages contacts, sources, stages, fees, files and history, and uses read-only Gmail activity to keep relationship follow-up current. Slack is the intake surface. A small AI step can extract missing details from an unstructured thread, but it cannot create a deal. It proposes. A human reviews. (me) The database records what happened. Stable rules become software. Ambiguity keeps an approval gate. But the feature that changes the operating rhythm is much simpler: At 6:00 AM Pacific, a scheduled job checks Gmail history from the last saved cursor. It does not reread the entire inbox. It does not ask an AI to “figure everything out.” The job filters spam, trash, newsletters, billing, platform alerts and unrelated business traffic. Then it matches exact known contacts. Unknown or conflicting identities go to a private review queue. Nothing ambiguous silently changes the CRM. Several emails with one person on one day collapse into one another touch. The system updates: • last inbound/outbound • who owes the next reply • how long we have been waiting • the next follow-up date • the deal and source context That is RevOps without b.s: Relationship and top-of-funnel signals live beside the sales pipeline. Slack captures new opportunities. Gmail updates relationship state. The CRM shows what moved, who owns the next step and where revenue can stall. It never sends, labels, moves or deletes an email. It never creates or changes a deal from Gmail. Locks prevent overlapping runs. Cursors prevent rereading. Idempotency prevents duplicates. Retries handle failure. A Health Log records counts, duration and errors. This is not a mockup. Today’s job started at 6:00 AM Pacific and completed successfully. The last 7 scheduled live runs all completed with: 0 AI requests 0 input tokens 0 output tokens $0 in model cost We used AI to help build the system. We do not rent intelligence again every morning for logic that can be encoded once. That is the distinction: Use AI as the engineer. Use scripts as the employees. Use humans for judgment. Your first version does not need a CRM. Open Codex or your terminal and make one workflow run once. Inspect the output. Turn the commands into a script. Run it again. Only then add a schedule. Add reliability in this order: explicit inputs/outputs database or file state cursor/checkpoint idempotency lock + retries review queue audit log UI The interface should sit on top of proven behavior—not compensate for missing behavior. It can run on your laptop, a small server, GitHub Actions, or a cloud scheduler. The infrastructure is not the point. The point is to remove one recurring operational decision, safely, every day. 10 examples: Cold email agency: every morning reconcile replies, bounces, unsubscribes and domain health into one action queue. Alert when bounce rates cross a threshold. Creative agency: list today’s deliverables, missing assets, overdue approvals and the owner of each blocker. Recruiting firm: sync new applicants, interviews and scorecards. Flag interviews missing feedback after 24 hours and candidates stalled for 7 days. Software agency: combine open PRs, failed CI, Sentry errors, Linear blockers and client SLAs into one delivery-risk queue. Paid media agency: pull yesterday’s spend, revenue and ROAS by account. Compare against guardrails and surface only the exceptions. Bookkeeping firm: collect new bills and receipts, apply known vendor rules and send uncertain matches to a review queue. MSP: surface tickets nearing SLA breach, failed backups, expiring licenses and unassigned incidents by account owner. Real estate or debt brokerage: list new leads, missing diligence, lender/borrower follow-ups and opportunities with no touch in 7 days. Ecommerce operator: compare stock, sales velocity, supplier lead times and open POs. Flag only SKUs needing a reorder decision. Content or PR agency: reconcile shipped work, pending approvals, overdue client feedback and distribution metrics into one morning queue. To make it trustworthy, you learn APIs, OAuth, schemas, databases, secrets, time zones, retries, idempotency, permissions, observability and deployment. That foundation transfers to every AI idea after it. Why one cron creates “unlimited” AI ideas: Once one operating loop is visible, every missing field, handoff, exception and decision appears. The second automation becomes obvious. Then the third. Eventually the UI becomes a map of work that already runs. Do not start by asking AI to operate your company forever. Ask it to help you encode one recurring process. -Run it in the terminal. -Schedule it. -Log it. -Review the edge cases. -Add the UI last. CRON JOBS ARE A GATEWAY TO REAL USE CASE AND LESS SPEND, THIS WILL HELP YOU 100X FASTER THAN LEARNING HOW TO DEPLOY CLOUD AGENTS TO DO 100 TASKS WITH A FRONTIER MODEL EATING YOUR POCKETS UP. Scripts > Tokens/Expensive Intelligence

• 
  clippo (@clippo069) reported 11 minutes ago

  @prasenx When Claude goes down is like when GitHub is down. Everyone goes home lmao

• 
  Zack Kanter (@zackkanter) reported 13 minutes ago

  4.5 years later, GitHub still effectively unusable on airplane wifi. I hope @cursor_ai / Origin spend some time on this problem.

• 
  Amitabh Mishra (@Amitabh49159929) reported 13 minutes ago

  @drummatick I don't understand these so called engineer don't understand the simple fact that the Github outrages actually predates the AI era. The first major outrage was reported in April 2020, long before chatgpt was announced. This issue is related to Microsoft not giving **** about it.

• 
  Raphael Campos (@mktraphael) reported 18 minutes ago

  @ChatGPT After updating ChatGPT/Codex Desktop to 26.814.41407 on Windows, the built-in browser and Chrome control stopped working with a “trusted code path” error. A full reinstall didn’t help. Others report the same bug: GitHub #39173 and #39184. Please fix this, @OpenAI.

• 
  Rolando 🦇 (@wifidinero) reported 19 minutes ago

  @acolombiadev Github Support is sooo slow too, been waiting weeks for a reply with nothing

• 
  hish 🏴‍☠️ (@hishboy) reported 19 minutes ago

  Here's how I test @Zipbox_ using Zipbox I boot an agent and tell it: - Open a Remote Desktop session. - Go to zipbox dot ai. - Sign up using your own agent mail that we provide. - OTP into the website by checking it's email inbox. - Boot a new sandbox inside yourself. Yes. A sandbox running a sandbox. Then I hand it a markdown file with our entire test suite. It goes feature by feature, spins up whatever it needs, and tests the platform like a real user. When it's done, it writes a full QA report and files every bug as an issue in @GitHub. Meanwhile, I have another agent sitting on the repo waiting for new issues to show up so it can start fixing them. So Zipbox is testing Zipbox, filing bugs against itself, then fixing itself. We're getting dangerously close to me being unnecessary here.

• 
  Kate (@withkate_) reported 20 minutes ago

  I've used the GoFullPage Chrome extension for years – it was easy and reliable for website screenshots, it had strong reviews and 11,000,000+ downloads.. A few days ago, it was removed from the Chrome web store. In the past, losing access to a tool in my daily stack would've frustrated me, but for the first time, my very first thought was.. "oh well, I'll just build it myself". So I did, with Claude Code. It took less than 30 minutes (!), and it does everything I ever wanted it to do – scrolls the page for me, stitches it into one image, and auto-saves as png, jpg, or pdf straight to my downloads folder. It can even handle sticky navs - iykyk. It's 100% local and open source. Just download it from GitHub, toggle on developer mode in chrome://extensions, and hit "load unpacked" to add it. Apparently GoFullPage is dealing with a copyright issue and working to become available again.. but I don't need them anymore. Here's a demo of my new self-built chrome extension, Full Page Capture, taking a full-page screenshot of GoFullPage's website ;) The future is custom and I can't stop building.

• 
  Rob Clevenger (@rcleveng) reported 21 minutes ago

  @cassidoo Is it possible to have separate pools for those of us who pay for GitHub va those who don’t. I understand the incredible amount of traffic on the open source project side of the house, but the outages for paying customer where we pay for service we can’t use, and in pay extra for actions that all fail when GitHub is having issues, seems to be customer hostile.

• 
  Pavan Joshi (@PavanJ1620) reported 22 minutes ago

  If you want to start a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  Onkar Mane (@theonkartwt) reported 23 minutes ago

  source says github went down just so elon can market origin for a bit lol