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 (56%)
• Errors (31%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	2 days ago
Inverness	Website Down	14 days ago
Quito	Sign in	15 days ago
Junín	Errors	15 days ago
Guadalajara	Errors	15 days ago
Paris	Website Down	15 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:

• 
  CodeRifts (@coderifts_dev) reported 4 minutes ago

  @DivyanshT91162 The scores need a date and a version beside them, and that is not a nitpick about rigor. A server's tool list and descriptions are fetched at connect rather than pinned, so 70/100 for GitHub MCP measures what it served on scan day. GitHub MCP ships releases; the score does not say which one it saw. Rescanning is cheap. Knowing whether what you run is what was scored is the part that makes the number useful.

• 
  0xfarhan (@toufiq_farhan) reported 4 minutes ago

  The problem: your API changes. PR gets merged. Nobody updates the docs. Weeks later someone hits that endpoint with no idea what params to send. I built api-sync to fix this paste a GitHub PR link, it finds the drift, generates the fix, commits it back.

• 
  Ngetich K Peter (@NgetichKPeter) reported 10 minutes ago

  Hey @GitHub , @Microsoft why is Kenya missing from the SMS 2FA options? It blocks us from properly securing our accounts or completing mandatory 2FA setup. Fix this or clarify the restrictions.

• 
  Ethan Reedy (@EthanReedy6) reported 11 minutes ago

  @thsottiaux Small fix to make projects short properly. There a long-standing GitHub issue on it.

• 
  𝖘𝖆𝖘𝖍 (@sash_solami) reported 12 minutes ago

  oh wow i just aped some vibecoded prediction market tool coin with fees generated to his github, the guy claimed and surely we bonded and all pumpfun callouts were so bullish and surely we went one candle down to 7k because dev was from africa and he already launched next github coin and all the pumpfun callooooooors got out and rotated and probably already forgot this coin existed except for myself cause i lost leftovers of my port on that stupid ******* ****, god i hate github coins and i hate pumpfun app, ts frying me

• 
  Iyọ̀ (@iyoolaoyabiyi) reported 16 minutes ago

  GitHub’s August 17 outage is a good example of why the foundational concepts we learn in software engineering have very real production consequences. A critical infrastructure component failed under peak traffic. During recovery, some Copilot services also started failing. Then something familiar happened. Clients retried the failed requests. Those retries created more traffic for systems that were already struggling to recover. The cycle looked something like: dependency fails then clients retry then dependency receives more load then recovery slows then more requests fail then clients retry again This is how something as simple as setting "retry the request three times" can be a systems problem. Retries are useful, but they need engineering controls. This is where concepts like exponential backoff, jitter, retry budgets, circuit breakers and idempotency start to matter. Exponential backoff increases the wait between retry attempts. Jitter adds randomness so thousands of clients do not retry at the same time. Retry budgets limit how much extra traffic retries are allowed to create. Circuit breakers stop requests temporarily when a dependency is clearly unhealthy. Idempotency makes repeated requests safe where retries could otherwise duplicate an operation. When designing an API integration, you should know: what failures are safe to retry, how many retries are acceptable, how long to wait between retries, how clients should spread retries over time, what happens when the dependency remains unavailable, and whether repeating the operation is still safe. GitHub is now standardising retry limits, retry budgets and variable timeouts across service-to-service interactions. These ideas can look theoretical when you first learn them. Then you see a production incident and realise they are really just descriptions of problems engineers eventually have to solve. Foundational concepts matter because when you go far enough and start building serious systems, production will eventually find these gaps in your understanding.

• 
  Zack (@Alaskan_Beard) reported 16 minutes ago

  @realradec I actually have a working server. I was trying to get it online before today but life. I'll have it up sometime this week. There's a version of it on my GitHub (AlaskanBeard) if anyone wants to host their own and all the missions are on the internet archive.

• 
  lasan (@las_nish) reported 16 minutes ago

  Comparisons of Free Trial Abuse Prevention Services If you're running a SaaS with a free trial or focusing on PLG, authentication and abuse prevention are not the same problem. - WorkOS: If you're already using WorkOS, WorkOS Radar is probably the first thing I'd look at. For a WorkOS stack, WorkOS AuthKit + Radar makes the most sense. You don't need to bolt another authentication system onto your app just to get abuse signals. - Auth0, Supabase Auth, Better Auth: These are primarily identity/authentication platforms. Integrating only these can't prevent free trial abuse. - Custom: Like the previous options, you need a custom way to prevent free trial abuse. Most free trial abuse methods involve disposable emails, Google dot variations, Google/Gmail domain variations, and plus addressing. That's why even when you block bots via Cloudflare Turnstile or CAPTCHA, you can still get these abusers. The industry standards: - Block free trial abuse using lists hosted on GitHub: This is a pain in the ***. If you don't want to pay money, you can use a service that offers a generous free tier. - WorkOS Radar: This is mainly used at the enterprise level. They focus more on WorkOS-related integrations rather than integrations with other providers. - ZeroBounce, NeverBounce, MillionVerifier, DeBounce: These are mainly used to clean/validate emails. There are 100s of alternatives, and most are similar with minor differences. They all have disposable email checking APIs. - UserCheck: This is also an email validation API, but they focus on blocking fake email addresses. It's better than a basic email verification API. - Autheona: This is in the same category as WorkOS Radar and UserCheck, but with more features. It also focuses on fake user detection and is growing with a real user base. Now, pricing: - WorkOS Radar: First 1,000 checks free, then $100 per 50 checks. No application-specific logic changes. Easy to integrate and manage. - ZeroBounce: 100 free validations in the free tier, then pay-as-you-go, starting at 2,000 for $39, and so on. - NeverBounce: No free trial or use case, $8 per 1,000 checks. - UserCheck: 1,000 API requests per month in the free plan. The rule-based engine is not included in the free plan, and you can get up to 1 request per second. - Autheona: 3,000 checks per month, with the rule-based policy engine included. Standard API request rate limitations apply, similar to paid plans. Now, use cases: - WorkOS Radar: Block disposable emails, plus addressing, and Google dot variations. - ZeroBounce, NeverBounce, etc.: Block disposable emails. - UserCheck: Block disposable emails, plus addressing, and Google dot variations; detect public emails; email suggestions; syntax validation; role detection. - Autheona: Everything included in UserCheck, plus business/free/government email identification, deliverability checks, fraud patterns, punycode and mixed-script checks, VPN detection, and bot detection (not necessary if you already use CAPTCHA, Cloudflare, etc.). Final decision from me: - Use WorkOS Radar if you're already in the WorkOS ecosystem. It's harder to integrate with other auth providers. - Use ZeroBounce-like APIs if you need basic disposable email checks. They're not as good if you need a better free tier. - Use UserCheck if you only need email-related validation and want to stay within the free plan. - Use Autheona if you need the most generous free tier available with a custom policy engine. All services take a maximum of a few hours to integrate and test. Both UserCheck and Autheona have a similar approach: integrate once and never touch the code again.

• 
  G S Bajaj (@gsbajaj) reported 17 minutes ago

  @GitHubHelp @github Urgent help. Our engg team has been hard-blocked on Actions and PR merges since last 10 days. Support ticket #4707509 has gone unanswered for several days. The payment page is frozen with a server-side Zuora lockout code. Please escalate!

• 
  kmdr (@kmdrfx) reported 17 minutes ago

  @jarrodwatts I use agents on VMs, they are long living though, so same issue. The other option would be to spin up a VM for a task, but then it has to do checkouts again has to set everything up, which sucks when GitHub or anything else is down. Then you think about preparing reusable images for the tasks, but these have to be maintened and it's hard to generalize. It's an awful rabbit hole as well. And I like my agents to be long living to use them for other stuff as well, have one per project and they evolve to be very project specific. To make all of the stuff you want to persist work with ephemeral VMs is madness imho.

• 
  jfmelo (@jfmelo_) reported 19 minutes ago

  github down again?

• 
  John Ruf (@JohnRuf6) reported 19 minutes ago

  like if you want to go down that rabbit hole you'd basically need a public-only researcher github where people are forced to host all of their projects and a strong norm that everyone works on the platform for all their projects for all time under this panopticon.

• 
  Mesut Celik (@mesutcelik) reported 19 minutes ago

  @GergelyOrosz That is pretty bad for @linear type of dashboards for issue tracking. You will ask your agent to generate what is going on in your team and it is going to generate something directly from github commits/PRs/Issues customized to your needs

• 
  Arsene Beatz (@ArseneBeatz) reported 19 minutes ago

  @github Hello, my name is Arsene My github account has been suspended. Am trying to log in and they are telling me that my account has been suspended due to a violation of terms of service. And I can’t directly contact Github support because of that issue. Can i get support @github

• 
  Basotho-Turkmen Jucheist 🇱🇸🇹🇲ꑭ🇰🇵 (@lemonel67) reported 21 minutes ago

  @tovarischsloth idhe problem kada, that's why edo 2-3 slop projects chesi github lo upload chese, vibe code cheyachu but I'd recommend adding in comments in between so u also know what the code does so it doesn't look like ur entirely bullshitting being real; lie on ur resume a little, it works

• 
  Vitali (@eheva87) reported 22 minutes ago

  @igus_ai @aridot_ Yes. If there are any issues, please file it in GitHub and I will prioritise

• 
  David Villegas (@labsdvx) reported 24 minutes ago

  @clairevo @joshkim @bot Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  Patrick ⚓️🇺🇸 (@lowtide1985) reported 25 minutes ago

  @stphnmaher It’s gonna be a little more involved than you think- If Canada’s goal is true technological independence from the United States, a Canadian sovereign cloud is only the first piece of an enormous puzzle: Canada would have to replace or become independent of Amazon/AWS, Microsoft, Google and Oracle for cloud; NVIDIA, AMD, Intel, Qualcomm, Broadcom, Marvell, Micron, Texas Instruments, Analog Devices and GlobalFoundries for processors, AI accelerators, memory, networking, communications and other semiconductors; Dell, HPE, Supermicro, IBM, Western Digital and Seagate for servers, storage and enterprise hardware; Cisco, Arista, Juniper/HPE, F5 and Ciena for networking and communications infrastructure; Microsoft, Apple, Google, Adobe, Salesforce, ServiceNow, Oracle, Workday, Intuit and Broadcom/VMware for operating systems, productivity, mobile platforms, databases, CRM, ERP, virtualization and enterprise applications; Palo Alto Networks, CrowdStrike, Fortinet, Zscaler, Okta, Cloudflare, Cisco and Microsoft for cybersecurity, identity and internet protection; OpenAI, Anthropic, Google, Meta, Microsoft and NVIDIA for frontier AI models, development platforms and AI infrastructure; GitHub/Microsoft, IBM/Red Hat, Docker, Datadog, Snowflake, MongoDB, Confluent, Elastic and HashiCorp/IBM for software development, containers, databases, data management and infrastructure automation; Visa, Mastercard, PayPal, Stripe, Apple and Google for major payment and digital-wallet infrastructure; Apple, Google and Qualcomm for smartphones and mobile ecosystems; Akamai and Cloudflare for content delivery and internet infrastructure; and, critically, Cadence and Synopsys for semiconductor-design software plus Applied Materials, Lam Research and KLA for the equipment needed to manufacture advanced chips. Even that doesn’t completely solve the problem, because Canadian, European, Japanese, Taiwanese and Korean products frequently incorporate American chips, software, patents, design tools or manufacturing equipment somewhere in their supply chains.

• 
  Manmeet Kaur Baxi (@manmeetkaurbaxi) reported 28 minutes ago

  @Google Three questions worth asking before a benchmark decides anything: 1. Does the benchmarking tool hold up at your real production QPS, not a demo load? 2. Do the benchmark prompts look like what your users type, or like a tidy GitHub issue?

• 
  Naomi June (@njkjh00) reported 31 minutes ago

  Beldex’s Electron Wallet has another security checkpoint worth watching. Aug 28 commit eef1f845: • wallet-directory fallback • explicit permission prompt • 7 files changed • +160 / -7 lines • branch: fix-security-review-findings GitHub shows the branch is still ahead of and behind master. That means something important: the security work is visible. the release is not there yet. Next checkpoints: review testing merge signed build release notes A security fix matters most when it reaches the software users actually install. @BeldexCoin

• 
  You (@sfdn__) reported 33 minutes ago

  @usekynix why github and linkedin link not working

• 
  tunct (@tunct101) reported 34 minutes ago

  I’ve claimed my Rialo points and connected all my socials. If you haven’t done it yet, it only takes a few steps: 1. Sign in with Google on the Rialo Playground 2. Open Connect next to your points balance 3. Connect your Discord + GitHub 4. Double-check that you linked the right accounts before claiming Done in a few minutes. How many points did you guys get? 👀 Drop your number below!

• 
  Devin Jameson (@devinjameson) reported 39 minutes ago

  OSS maintainers using coding agents: how do you stay organized? I want one place where I can group and sort issues, see PR size and status at a glance, and know which agent/session is working on each issue or PR. I typically have five or more agents running at once and it gets pretty overwhelming. Are you using GitHub Projects, a third-party tool, something custom? The clanker is telling me to try Conductor?

• 
  AuraAI (AI First) Local Superintelligence Project (@hvo_e_acc) reported 39 minutes ago

  @TunducR the reason for this is because the avatar project i was trying to animate, but i'd been having problems with the talking animation. i was able to incorporate choosing clothes and hairstyle, to some extent walking, but not to the extent of a replika or grok avatars. it's very basic. but, like i mentioned, i'll let you know once i set up my github. all this by the way is vibe coding with my local AI.

• 
  Max Niederhofer ❤️‍🔥 (@maxniederhofer) reported 50 minutes ago

  the reason i love @huggingface's microduck is not just the anthropomorphism, but that it's subsidiary in product form: entire RL stack on Github, just pushed down to whoever wants it <3

• 
  Donatello | AI, Tech & Wealth (@donatelloinvest) reported 52 minutes ago

  @github Notification fatigue becomes a security problem when important updates look like routine noise. Grouping dependency changes helps, but the review still needs boundaries: small batches, visible lockfile diffs and fast separation when tests fail.

• 
  Bounty (@bountyAIhunter) reported 53 minutes ago

  17,806 tokens gone before I typed anything. OpenClaw 2.0 landed overnight and the part nobody is posting about is what it does to a local model. It now finds your llama.cpp server on its own, and it raised the default context for llama.cpp to 64K. Both of those are good. Together they hide a bill. I pointed 2.0 at llama-server, sent one word, and read the prompt token count off the server log before the model answered anything: base system prompt + built-in tools 11,412 docked browser panel tools 2,847 github pr tools 1,206 3 MCP servers I already had 2,341 total before my first word 17,806 That is 27% of the new 64K default spent on the harness. Not on my code, not on my question. On a hosted model you pay for it and move on. On a local setup the window is the budget, and a quarter of it is booked before the session starts. What actually helped, in order: turned off two MCP servers I had not opened in a week -1,889 browser panel off until a task needs it -2,847 kept the github tools, they earn their 1,206 13,070 now. Same harness, same model, same 64K. Check yours in 30 seconds. Start llama-server with verbose logging, send one message from OpenClaw, then read the first request: grep n_prompt_tokens server.log | head -1 That number is your real starting line, not what the settings screen implies. Honest caveat: this is my install, my three MCP servers, Gemma 4 as the local default. Yours will be different and I want to know by how much. Post your first n_prompt_tokens and how many MCP servers you have connected.

• 
  Ryan Badger (@ryanseanbadger) reported 57 minutes ago

  Github Actions. Seems like a cool idea at first, then you hit the usage caps and have to login and increase limits. Then they fail because you hit those limits too. Then they fail because Github is down (again) Then you scrap it and do it all locally with Ai for free.

• 
  Alex Kulikov (@startupenko) reported 59 minutes ago

  So, building in silence obviously is not a beneficial way for me as I thought at first. I began vibecoding with the first version of GitHub Copilot, and I've built/rebuilt a ton of ****** apps. This current year was dedicated to edTech apps: Inlay (unit manager for teachers), DrawPaw (lesson presentations), and one more app WIP. Still ******* zero results. I left my Product Design career to create my independence, creating my own apps on my own rules. Instead, I trapped myself in a gravity problem—I left my product design ship but did not land the solopreneur ship yet. Still shipping continuously, in silence, rarely posting inconsistent chunks. So, again, I have no ******* idea what to tell about my journey. I'm not an engineer, neither the best designer, just an undying striver trying to create my own independence.

• 
  Atharva Verma (@atharva_again) reported 1 hour ago

  @raffichill just use github issues ffs