Is Let's Encrypt down right now?
Checking…Verifying live status…
Our latest checks found Let's Encrypt responding normally. Live verification is running now.
Your report feeds the live outage-velocity detector. One click per 30 s.
Live latency (probe round-trip, ms)
User reports, last 24 hours
Outage history
last 30 days
Recent outages and issues we recorded for Let's Encrypt, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.
No problemsProblemsOutageNot monitored
What Let's Encrypt reported
last 30 days
Taken from Let's Encrypt's own published incident feed. These are their words about their own service, shown here so you can compare them with what we measured. Scheduled maintenance and test posts are filtered out.
Comments
Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.
Comments are loading in our built-in box because Disqus was blocked or unavailable. Spam and abuse are filtered automatically, and comments are hidden once 3 readers flag them.
How we check Let's Encrypt
No evidence of problems with Let's Encrypt. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.
Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Let's Encrypt's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Let's Encrypt normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.
Let's Encrypt (letsencrypt.org) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.
Common Let's Encrypt problems users report
- Certificate issuance requests timing out or returning errors
- Certificate renewal failing near expiration dates
- ACME API endpoints returning 5xx errors or no response
- Certificate revocation requests not processing
What to do when Let's Encrypt is not working
First check the banner above. If it shows evidence of problems, the fault is most likely on Let's Encrypt's side and waiting is usually the only option. If it shows nothing wrong, verify your ACME client is using the correct production endpoint URL, check that your domain's DNS resolves and is reachable for validation, ensure your firewall allows outbound HTTPS to Let's Encrypt's servers, and try using a different ACME client or validation method to isolate whether the issue is client-specific.
About Let's Encrypt
Let's Encrypt is a free, automated certificate authority that issues TLS/SSL certificates to secure websites. When Let's Encrypt is down, users cannot obtain new certificates, renew expiring ones, or revoke compromised certificates, leaving sites unable to establish HTTPS connections or forcing them offline when certificates expire.
Official Let's Encrypt resources
Cross-check an incident with the company's own channels:
- Official Let's Encrypt status pageTheir own incident dashboard
- Let's Encrypt help centerSupport articles and contact options
Frequently asked questions
Is Let's Encrypt down right now?
No. Our checks are finding no problems with Let's Encrypt right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Let's Encrypt continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.
What usually goes wrong with Let's Encrypt?
The problems visitors report most often on this page are SSL / certificate errors, API errors, DNS / site unreachable, can't connect, 5xx error pages and no response / timing out. Those are the options the report button offers for Let's Encrypt, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.
Why is Let's Encrypt not issuing certificates for me when this page says it is fine?
Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Let's Encrypt specifically, Let's Encrypt operates distributed ACME endpoints and validation infrastructure, so one region's validators or issuers can fail independently while others remain functional, or your ACME client may reach a degraded endpoint while others succeed. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.
How do I tell whether it is Let's Encrypt or my own connection?
For Let's Encrypt, attempt a test certificate issuance using the Let's Encrypt staging environment at https://acme-staging-v02.api.letsencrypt.org/directory with a tool like certbot in dry-run mode. A problem that follows you across networks and devices is very unlikely to be yours.
What should I do while Let's Encrypt is down?
If this page shows evidence of problems, the fault is most likely on Let's Encrypt's side. Specifically: do not repeatedly retry certificate issuance in rapid succession, as this can trigger rate limits that persist after service recovery and block legitimate requests for hours. Reporting it here helps other people see they are not alone.
How does status.buzz check Let's Encrypt?
Continuously, around the clock. Let's Encrypt does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe letsencrypt.org directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Let's Encrypt says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.
Does Let's Encrypt have an official status page?
Yes, at status.letsencrypt.org, and it is linked further up this page. That is Let's Encrypt's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.
Is status.buzz affiliated with Let's Encrypt?
No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Let's Encrypt or letsencrypt.org. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Let's Encrypt's own support, not us.
Other infrastructure services
Live status. Each dot updates automatically.
No comments yet. Be the first to describe what you're seeing.