isitdownrightnow.app
  1. Home
  2. Services
  3. Let's Encrypt
Let's Encrypt letsencrypt.org

Is Let's Encrypt down right now? Live status and outage tracker

No, Let's Encrypt is up.

No outage detected, and no user reports in the last hour.

Live Data refreshes every 5 minutes
Not working for you? Official status pageStatus page
User reports, last 24 hours, 15 minutes a segment: 96 flowing, 0 slow (elevated), 0 jammed (outage)

User reports, last 24 hours

No reports in this window

No problem reports came in for Let's Encrypt in the last hour, and at this time of day there are usually almost none. There has been no spike in reports since 18 October. These are user reports from the US, where most people report Let's Encrypt problems.

Around the world right now: normal in 71 other countries. By country

No user reports came in for Let's Encrypt in the past 24 hours, and its uptime over that window is 100.00%. No 15-minute window had any reports at all, so the chart above stays flat.
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
0
No reports
Last 24 hours

Let's Encrypt outages and problems

No user reports came in for Let's Encrypt in the past 24 hours, and its uptime over that window is 100.00%.

No 15-minute window had any reports at all, so the chart above stays flat.

No problems detected in the last 24 hoursReports for Let's Encrypt stayed at their usual level the whole time.
Report categories

What people can report about Let's Encrypt

People who report a problem with Let's Encrypt to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:

  • Hosting
  • Login
  • Domains
  • DNS
  • API
  • Dashboard / Console
  • Storage and Backup
  • Databases
World map

Let's Encrypt reports around the world

In the last 24 hours, 0 problem reports about Let's Encrypt came in from 0 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 00
The UK Normal 00
Mexico Normal 00
The Netherlands Normal 00
Germany Normal 00
Belgium Normal 00
France Normal 00
Russia Normal 00
Italy Normal 00
India Normal 00
Spain Normal 00
Canada Normal 00

Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Let's Encrypt problem spikes, last 30 days

Since 18 October, Let's Encrypt had no outage spikes or periods of elevated reports.

  • Sat 3 Oct: no data
  • Sun 4 Oct: no data
  • Mon 5 Oct: no data
  • Tue 6 Oct: no data
  • Wed 7 Oct: no data
  • Thu 8 Oct: no data
  • Fri 9 Oct: no data
  • Sat 10 Oct: no data
  • Sun 11 Oct: no data
  • Mon 12 Oct: no data
  • Tue 13 Oct: no data
  • Wed 14 Oct: no data
  • Thu 15 Oct: no data
  • Fri 16 Oct: no data
  • Sat 17 Oct: no data
  • Sun 18 Oct: 1 report
  • Mon 19 Oct: 0 reports
  • Tue 20 Oct: 0 reports
  • Wed 21 Oct: no data
  • Thu 22 Oct: 0 reports
  • Fri 23 Oct: 0 reports
  • Sat 24 Oct: 0 reports
  • Sun 25 Oct: 0 reports
  • Mon 26 Oct: 0 reports
  • Tue 27 Oct: 0 reports
  • Wed 28 Oct: 0 reports
  • Thu 29 Oct: 0 reports
  • Fri 30 Oct: 0 reports
  • Sat 31 Oct: 0 reports
  • Sun 1 Nov: no data

By country

Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.

  • France1
  • Nigeria1
  • The UAE0
  • Argentina0
  • Austria0
  • Australia0
  • Azerbaijan0
  • Bangladesh0

Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 18 October 2026. Monthly reports for all services

Troubleshooting

How to fix Let's Encrypt not working

Let's Encrypt is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach letsencrypt.org over your own connection, right now. Nothing is sent to us or stored.

  1. Check the Let's Encrypt status page

    Open the official status page before you change any configuration; it reports API and validation incidents that can block issuance or renewal for any client. If it lists an active incident, wait for the fix and retry.

  2. Check the certificate expiry date

    Open the site in Chrome, click View site information beside the address bar, then open Connection is secure and Certificate is valid to read the expiry date. An expired certificate usually shows a warning before the page loads, so renew with your ACME client and reload the web server.

  3. Test renewal with a dry run

    Run `sudo certbot renew --dry-run` on the server that holds the certificate; the staging test shows whether the ACME challenge and account credentials still work without using a real issuance. Fix any challenge failure it prints before you run a real renewal.

  4. Fix the ACME challenge path or DNS

    If your client uses the HTTP challenge, it fetches a file from `/.well-known/acme-challenge/` over port 80, so allow inbound TCP 80 and confirm the web server serves that path without a redirect. For DNS validation, query `dig TXT _acme-challenge.<your-domain>` and correct any missing or wrong record; repeated failures can also hit the 'too many failed authorizations recently' limit.

While Let's Encrypt is down: what to use instead

  • ZeroSSL Use it when you need another ACME certificate authority for a website or server.
  • Google Trust Services Choose it when your certificate tool supports its ACME endpoint and you want another public certificate provider.
  • Cloudflare Universal SSL Use it when your domain runs through Cloudflare and you need browser encryption without issuing a certificate on your server.
  • Sectigo Use it when you need a commercial certificate authority for a site that cannot wait for Let's Encrypt to return.
Your device

Fix Let's Encrypt on Windows, Mac, Android and iPhone

Let's Encrypt on Windows

Fix
Fix Let's Encrypt certificate errors on Windows by running Windows Update to update your root certificates, or manually import the ISRG Root X1 certificate into the Windows Certificate Manager.
Check
To check if Let's Encrypt is down on Windows, visit their official status page or test if you get SSL connection errors on websites that use Let's Encrypt certificates.
Command Prompt
ping letsencrypt.orgTest whether Let's Encrypt's servers reply
nslookup letsencrypt.orgCheck that Let's Encrypt's DNS resolves
tracert letsencrypt.orgTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Let's Encrypt on Mac

Fix
Resolve Let's Encrypt trust issues on macOS by updating your operating system or manually importing and setting the ISRG Root X1 certificate to 'Always Trust' in Keychain Access.
Check
Verify if Let's Encrypt is down on a Mac by checking the official Let's Encrypt status page or inspecting certificate details in Safari or Keychain Access.
Terminal
ping -c 4 letsencrypt.orgTest whether Let's Encrypt's servers reply
nslookup letsencrypt.orgCheck that Let's Encrypt's DNS resolves
traceroute letsencrypt.orgTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Let's Encrypt on Android

Fix
Fix Let's Encrypt certificate issues on Android by installing the latest system updates, or use the Firefox browser which uses its own updated root certificate store.
Check
Determine if Let's Encrypt is down on Android by checking if multiple secure websites fail to load with SSL warnings, or by visiting the Let's Encrypt status site.

Let's Encrypt on iPhone and iPad

Fix
Fix Let's Encrypt connection errors on iOS by updating your iPhone or iPad to the latest iOS version to refresh the system's trusted root certificates.
Check
Check if Let's Encrypt is down on iOS by checking if Safari displays 'Certificate Not Trusted' warnings on Let's Encrypt-secured websites.
About

What happens when Let's Encrypt goes down

Let's Encrypt is a free, automated certificate authority that issues TLS certificates for websites and other internet services. Site owners and hosting providers rely on it to keep HTTPS working, so an outage interrupts new certificate orders and renewals.

Orders and renewals fail first. Your ACME client usually shows a timeout or a server error with no useful detail, and validation can fail because the service cannot complete the HTTP or DNS challenge checks that prove you control the domain. Existing certificates keep serving traffic until they expire; the visible break comes later, as browser warnings and blocked pages on sites that could not renew. Trouble is often partial: one endpoint or validation path fails while other requests still go through, and regional network problems can make it look worse than it is.

Servers and network

Let's Encrypt IP address, servers and network

IPv4 addresses
35.157.26.135
Show all 2
  • 63.176.8.218
IPv6 addresses
2a05:d014:58f:6200::258
Show all 2
  • 2a05:d014:58f:6200::259
Network
AS16509 · Amazon.com, Inc., registered in the United States
Served through
Netlify
DNS hosted by
Cloudflare
HTTPS certificate
Issued by Let's Encrypt, valid until 3 Dec 2026 (32 days)
HTTP/3
Not advertised
Our check
Answered in 29 ms

Checked from our server in Frankfurt, Germany, 4 days ago, for letsencrypt.org. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from letsencrypt.org. Fastest from Singapore (18 ms), slowest from Tokyo (1,324 ms). Every location connected through Amazon.com, Inc. (AS16509), using 5 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp21 ms63.176.8.218
ViennaAustriaUp60 ms35.157.26.135
MilanItalyUp45 ms35.157.26.135
ParisFranceUp53 ms63.176.8.218
AmsterdamNetherlandsUp40 ms35.157.26.135
MadridSpainUp118 ms63.176.8.218
WarsawPolandUp122 ms35.157.26.135
Los AngelesUSAUp54 ms13.52.188.95
São PauloBrazilUp24 ms54.232.119.62
SingaporeSingaporeUp18 ms52.74.6.109
TokyoJapanUp1,324 ms63.176.8.218

Checked with check-host.net from its servers in these cities 4 days ago, for letsencrypt.org. Time is how long each server took to load the page.

Questions

Let's Encrypt FAQ

Is Let's Encrypt down right now?
The status at the top of this page shows whether user problem reports for Let's Encrypt are above their usual level, counted in 15-minute windows over the last 24 hours. If the count is normal, the trouble is probably on your end. Check that your server's clock is correct, that port 80 or 443 is reachable from the public internet, and that your ACME client is pointed at the right directory URL. Certbot failures that mention a timeout or a refused connection usually mean a firewall or DNS record is blocking the validation request before it ever reaches Let's Encrypt.

Why does Certbot say the challenge failed with a connection refused error?
Let's Encrypt validates your domain by fetching a file over HTTP from the address your DNS points to, so a refused connection means nothing answered on port 80. Common causes are a firewall rule, a web server listening only on localhost, or a DNS record pointing at the wrong IP. Confirm the domain resolves to the machine you think it does, then test the challenge path from outside your network before you run Certbot again.

My certificate expired and renewal keeps failing. What should I check?
Renewal runs on a timer, so the first thing to look at is the renewal log rather than the certificate itself. If the log shows validation errors, the domain's DNS or firewall probably changed since the last successful run. If it shows rate limit messages, stop retrying and wait, because repeated failed attempts can lock you out for a while. The help centre at https://letsencrypt.org/docs/ explains the limit windows.

Does Let's Encrypt check whether my site is reachable from multiple locations?
No, and neither does this site. The status here comes only from user problem reports, and it never pings or probes a service from anywhere. Let's Encrypt's own validation does reach your server from outside your network, which is why a site that loads fine for you can still fail the challenge. The official status page at https://letsencrypt.status.io/ covers their side of that process.

Is the Let's Encrypt outage the reason my browser shows a certificate warning?
An expired or misissued certificate is already on your server, so an outage at Let's Encrypt will not create a new warning in a browser that was working before. A warning means the certificate your server presented does not match the domain or is past its expiry date. Fix the certificate on the server side; the certificate authority being unavailable only stops you from getting a fresh one.
For your site

Put the Let's Encrypt status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

Let's Encrypt status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/letsencrypt/"><img src="https://isitdownrightnow.app/badge/letsencrypt.svg" alt="Let&#039;s Encrypt status" height="20"></a>
Markdown, for README files
[![Let's Encrypt status](https://isitdownrightnow.app/badge/letsencrypt.svg)](https://isitdownrightnow.app/services/letsencrypt/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track Let's Encrypt

The status on this page comes from user-submitted problem reports for Let's Encrypt, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Let's Encrypt, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Let's Encrypt's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services

See all 500+ services

Problems elsewhere right now

Strips: user reports, last 6 hours, 15 minutes a segment.