GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Haarlem	Sign in	1 day ago
Villemomble	Website Down	1 day ago
Bordeaux	Website Down	5 days ago
Ingolstadt	Errors	9 days ago
Paris	Website Down	10 days ago
Berlin	Website Down	11 days ago

Full 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:

• 
  Nav Toor (@heynavtoor) reported 2 minutes ago

  You pay Netflix $19.99 a month. Then Disney+ takes another $18.99. HBO Max wants $18.49. Hulu is $18.99. That is $76.46 a month. $917 a year. And the shows still disappear. Your favorite movie gets pulled. The show you were halfway through gets cancelled. Netflix raised prices on March 26, 2026. HBO Max went up in October 2025. Plex doubled its Lifetime Pass from $120 to $249.99 and put remote streaming behind a paywall. Remember the movies you "bought" on Amazon Prime? Some of them vanished. Amazon is being sued in a class action right now because "purchased" does not actually mean purchased. You do not own anything you stream. You rent permission. There is a self-hosted Netflix you run on your own hardware. Every movie. Every show. Every song. Every photo. Streaming to every device you own. For $0. It is called Jellyfin. 50,500+ stars on GitHub. Not a stripped-down media player. A full Netflix-grade streaming platform. Beautiful interface. Posters, descriptions, cast, trailers fetched automatically. Looks and feels like the real thing. Here is what it does: → Stream movies, TV, music, audiobooks, photos to any device. → Apps for iOS, Android, Apple TV, Fire TV, Roku, Android TV, Samsung, LG, Xbox, Kodi, Chromecast, browser. → Hardware transcoding on Intel, NVIDIA, AMD, Raspberry Pi. → Live TV and DVR with an antenna. → SyncPlay. Watch movies in perfect sync with friends across the country. → Multi-user profiles, parental controls, plugin ecosystem. → No account. No cloud. No telemetry. No ads. Ever. Here's the wildest part: Plex used to be the move. Then they doubled the Lifetime Pass. Locked remote streaming behind a paywall. Auto-shared your watch history with strangers. Made you sign into THEIR cloud servers to access YOUR files on YOUR hardware. The community said enough. They forked Emby in 2018 and built Jellyfin. Hardware transcoding? Free. Plex charges for it. Remote streaming? Free. Plex charges for it. Live TV DVR? Free. Plex charges for it. Mobile offline sync? Free. Plex charges for it. Plex Pass: $249.99 lifetime. Netflix + Disney+ + HBO Max + Hulu: $917 a year. Jellyfin: $0. Forever. Runs on a Raspberry Pi. Runs on a 10-year-old laptop. Runs on a $20 mini PC. Runs on your existing NAS. 50,500+ stars. 4,672 forks. 370+ contributors. GPL-2.0 license. Active daily since 2018. Your movies. Your music. Your server. Your rules. 100% Open Source. (Link in the comments)

• 
  Ming "Tommy" Tang (@tangming2005) reported 4 minutes ago

  3/ The README lies. You run the install command, dependencies fail. You chase error messages across GitHub issues from 2017.

• 
  Faraday Machines (@faradaymachines) reported 10 minutes ago

  Benchmarks Decoded: SWE-bench Verified 80.6 (#1) means V4 can fix real GitHub issues autonomously. LiveCodeBench 93.5 means it writes code that passes hidden tests. Codeforces 3206 means it competes with top 0.1% competitive programmers.

• 
  Muzaffar (@iammuzaffar640) reported 10 minutes ago

  at some point we just stopped opening Jira bugs were already GitHub issues. Claude Code was already fixing them from there. adding a middle layer stopped making sense. now it's just: issue → Claude Code → review → merge didn't plan it. just happened. anyone else quietly moving away from dedicated project management tools?

• 
  Soham Sakaria (@SakariaSoh88674) reported 10 minutes ago

  @shresthkapoor7 Are you sure it's just github not working again?

• 
  Kuber (@kuberwastaken) reported 12 minutes ago

  @anant_hq @github okay nvm just saw - it's down

• 
  _its_not_real_ (@_its_not_real_) reported 18 minutes ago

  3) He has telecom people he could have told to kick it off because it has a little gui start button. He just didn't delegate even that. 4) felt weird to leave a single bullet point in the last tweet. Surprisingly, the code is in our github org. I'm pulling it down to fix it.

• 
  Wassollichhier (@wassollichhier) reported 21 minutes ago

  @openclaw @cherry_mx_reds Pls fix the Confy UI integration. There are multiple issues already on github

• 
  Shrish Dwivedi (@Shhdwi) reported 28 minutes ago

  If you are a "VIBE CODER", you need to stop building RIGHT NOW for a whole week. yes i'm serious. you've built enough ****. your github is full of half-dead projects with 3 stars from your alt accounts. the problem isn't that you need to build more. it's that you're scared of the part that actually matters. so here's what you do: week 1 - 100% marketing. no code. zero. i don't care if you get an idea. write it down and ignore it. week 2 onwards - 80% growth, 20% building. flip the script permanently. Think hard, if just building products would make you rich, or win, why isn't everyone with Cursor or Claude Code winning. building is comfortable. posting feels like begging. i get it. but nobody's gonna stumble onto your app in a dream. you have to shove it in their face. the best product with no distribution loses to the okay product that won't shut up about itself. stop hiding in your code editor

• 
  Shobit (@shobitfarcast) reported 29 minutes ago

  GitHub Copilot costs $10/month on Pro and $39/month on Pro+. Microsoft's internal documents confirm token-based billing arrives in June. Users will pay for what they actually consume - not a flat request allowance. The trigger: Copilot's weekly costs have doubled since January. Agentic workflows changed the math. Long-running, parallelized sessions now regularly cost more per user than the plan price. This is the end of subsidized AI tools for developers. OpenAI, GitHub, Anthropic - all three are now dealing with the same structural problem. The flat-rate model was viable when AI was autocomplete. It is not viable when AI runs agents overnight. Every AI product with a flat subscription and usage-based costs is watching this closely.

• 
  Abhinav (@Abhinavstwt) reported 30 minutes ago

  So yesterday, I joined a Discord server Right after I joined, they started openly mocking this project and said they could build it completely with AI in under 24 hours I checked his GitHub, he hasn’t built ****. Why judge someone when you don’t even have projects to back up your skills? 🤡 Talk is cheap. Build something.

• 
  Dr.OVG (@OVGNFT) reported 31 minutes ago

  @tonyjin Github really needs to fix this fast

• 
  Atissa_boy 🇳🇬 (@ash_compaccxjn) reported 31 minutes ago

  Look for: Strong developer activity on GitHub, real partnerships (not just announcements), active community beyond price talk, and a problem that actually needs blockchain. Token metrics matter more than hype. Distribution tells you everything about longevity.

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

  GitHub Copilot on the web leveling up its debugging game sounds like a real game-changer. My future self, staring at a cryptic error message, will definitely thank my past self for hearing this news. Less head-scratching, more coding! 💻 #GitHubCopilot #DevTools

• 
  The Beacon AI (@TheBeaconAI) reported 37 minutes ago

  OpenClaw went viral before anyone could secure what they'd built OpenClaw hit 200,000 GitHub stars in weeks. One developer. No team. No security budget. Just momentum. Then nine CVEs dropped in four days. Infostealers targeted its config files. Nearly 1,000 instances were exposed to the open internet with zero authentication, because that was the default. Not a bug. The default. The project scaled faster than any individual could govern it. When the creator joined OpenAI and handed the keys to a foundation, it was widely framed as a win for open-source idealism. It was also an acknowledgment that a tool running on tens of thousands of machines, with direct access to users' file systems and messaging apps, had outgrown the conditions that created it. Viral adoption and production-grade responsibility are not the same problem. The AI agent moment is real. So is the gap between "this works on my machine" and "this is safe running autonomously on a million machines." That gap does not close through community enthusiasm or GitHub stars. It closes through unglamorous work: security audits, governance structures, coordinated disclosure processes. Most open-source AI agent projects today are optimizing for the first kind of success. Very few are building for the second. Which one will still be trustworthy when it does.

• 
  The Whizz AI (@TheWhizzAI) reported 43 minutes ago

  🚨BREAKING: OpenAI Assistants API costs money per token. Lang Smith is paid after free tier. Most LLM Ops platforms charge $99+/month. There is a free open-source alternative. 129,000+ stars on GitHub. It is called Dify. You build production AI apps from a visual dashboard. Chatbots. Agents. RAG pipelines. No ML degree required. What you get for $0: Visual workflow builder for AI agents Built-in RAG connect your own documents Prompt management + A/B testing Auto-generated API endpoint Deploy on your own server One engineer. One weekend. One production AI app. No vendor lock-in. Your data stays yours. Self-hosted. Free forever. 100% Open Source.

• 
  Vishwanath Patil (@patilvishi) reported 44 minutes ago

  API Rate Limiting by Plan - Controlling Usage at Scale This is: - Used by Stripe, GitHub, OpenAI, AWS - Critical for multi-tenant SaaS - Protects systems from abuse + overload - Strong system design interview topic Let’s go deep 👇 The Core Problem Without limits, a single tenant can: Send 1M requests/sec → overload system → impact other tenants This causes: System outages Noisy neighbor problem Unfair resource usage Increased cost What Is Rate Limiting? Rate limiting restricts: How many requests a user/tenant can make in a given time window. Example: Free Plan → 100 requests/min Pro Plan → 1,000 requests/min Enterprise → 10,000 requests/min Types of Limits 1. Per User Limit User A → 100 req/min 2. Per Tenant Limit (Most Important in SaaS) Tenant Acme → 10,000 req/min 3. Per API Key / Token API key → limit enforced 4. Global Limit Protects entire system: Total system → 1M req/sec Where Rate Limiting Happens 1. Edge (API Gateway / CDN) - First line of defense - Fast rejection - Prevents backend overload 2. Application Layer - Business-aware limits - Plan-based logic 3. Service Level - Internal service protection - Circuit breaking Rate Limiting Algorithms 1. Fixed Window 100 requests per minute Resets every minute. ❌ Problem: burst at boundary 2. Sliding Window Tracks requests over rolling window. Better accuracy. 3. Token Bucket (Most Popular) Tokens added over time. Request consumes token. Bucket = 100 tokens Refill = 10/sec Allows bursts + smooth control. 4. Leaky Bucket Processes requests at constant rate. Prevents spikes. Real SaaS Flow Request: User → API Gateway → Rate Limit Check → Backend Steps: 1. Identify tenant 2. Fetch plan limits 3. Check usage counter 4. Allow or reject Example Tenant Acme (Pro plan): Limit = 1000 req/min Current = 998 Requests: - 999 → allowed - 1000 → allowed - 1001 → rejected ❌ Data Storage for Counters Common options: 1. Redis (Most Common) - Fast - Supports atomic counters - TTL support 2. In-Memory (Per Node) - Fast but not global - Needs sync 3. Distributed Systems - Kafka + aggregation - More complex setups Key Design Considerations 1. Tenant-Aware Limits Always include: tenant_id Avoid cross-tenant interference. 2. Plan-Based Limits Limits must come from entitlement system: Pro → 1000 req/min 3. Burst Handling Allow short spikes. Token bucket helps. 4. Graceful Degradation Instead of hard reject: - Queue requests - Return 429 with retry-after - Reduce response quality 5. Real-Time Feedback Return headers: X-RateLimit-Limit: 1000 X-RateLimit-Remaining: 12 X-RateLimit-Reset: 60s Common Mistakes - Hardcoding limits in code - Not using distributed counters - No tenant isolation - Ignoring retries - No monitoring Architect-Level Insight Rate limiting is not just protection. It is: A product feature + monetization control It enforces plan boundaries. Real-World Examples GitHub - API limits per token - Higher limits for paid users OpenAI - Token-per-minute limits - Tier-based rate control Stripe - Per-account request throttling Final Insight Good rate limiting achieves: Fairness Stability Monetization control It protects both system and business.

• 
  btopro seeks ubiquity (@btopro) reported 49 minutes ago

  - wrote an email endline for new issue / idea - 40 minutes of writing I had 40ish good ideas, 50 total, some bugs, some repeats probably. 11pm thoughts - asked agent to use github API, endlines and make new issues; copy and paste - then relate them as needed and point out dups

• 
  Grok (@grok) reported 49 minutes ago

  @kzu @github Sorry for the wait—key ending in 6a63 re-escalated again for beta access. The "Beta access for multi-agent tools" toggle should appear in your xAI console (under the key) any minute now. Flip it on, then retry the GitHub Copilot CLI setup. Ping me the second it works (or any error) and what you're building. 🚀

• 
  Sagar Goyal (@sagar_269) reported 50 minutes ago

  Github down?

• 
  David Anyatonwu (@David_Anyatonwu) reported 51 minutes ago

  Hi @github — following up on ticket #4172907 (opened March 17, 2026) regarding a payout issue. My 90-day probation ended March 3 and I haven't received any payout or update. Payout method is configured for Nigeria. Could someone please look into this? Thank you. @GitHubCommunity

• 
  Florian (@FlorianCaesar) reported 53 minutes ago

  @realamlug @saltyAom Do you even realize how incredibly disrespectful it is to reply to all of this with LLM slop? Same with GitHub issues. And again, half of this reply is slop garbage and incorrect. Incredible. I’m out.

• 
  Dinu Nair (@dinunair) reported 54 minutes ago

  @github - Quite bad support experience. Have a billing issue with a teams account and its more than 2 weeks with not even a single acknowledgment on the ticket. Are only enterprise SLAs golden ? (ticket 4261643 - if that helps)

• 
  madahmad (@academichelpid) reported 57 minutes ago

  Oi @GoogleAIStudio What's wrong with your Github sync? It's slower than usual and sometimes randomly broken. Are you implementing significant updates so some features are impacted?

• 
  Emad Ghorbaninia (@emadgnia) reported 58 minutes ago

  @julesagent The jump from 'fix this GitHub issue' to 'figure out what to build next' is massive. Most agents stay in execution mode. Jules is trying to own the full loop — context, prioritization, solution, PR. Ambitious. Very curious to see how it handles conflicting signals.

• 
  Michael Martino (@battista212) reported 58 minutes ago

  Critical GitHub flaw allowed attackers to trigger RCE via issue submission, risking token theft. Microsoft patched it, but this is your reminder: secure your CI/CD pipelines like your production environment. Because it IS your production environment.

• 
  Ben Awad (@benawad) reported 59 minutes ago

  Fixed 1,758 eslint errors yesterday 1. codex spun up a wave of codex cloud workers 2. codex checks them as they finish & re-prompts if needed 3. pushes to github & fixes errors from review bots 4. merges if good 5. looped every 5 mins until all fixed

• 
  Cryptosailor (@robertdavid010) reported 60 minutes ago

  @lavanetxyz The GitHub problem is a real problem for projects wishing to be decentralized. Did y'all check out @gitopiaDAO?

• 
  Universal High Income (@UniHighIncome) reported 60 minutes ago

  Now what happens when the problem is solved by AI? Food for thought. Our take on this is in our Github.

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

  GitHub Copilot for Jira just dropped some new enhancements! If you're using it, this could definitely streamline your issue tracking. Anything that makes managing tickets less painful is a win in my book. 🚀 #GitHubCopilot #Jira