Letsencrypt logo

Is Letsencrypt Down?

SaaSLive status, outages, and incident history

No. Letsencrypt is up right now.

Every monitored Letsencrypt system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s1 active incident

Know the moment Letsencrypt breaks

Letsencrypt is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Letsencrypt status page
How we know: the official Letsencrypt status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Letsencrypt Status Summary

As of 16:52 UTC on 9 November 2026, Letsencrypt is operational. PulsAPI checked Letsencrypt's official status page and found 12 of 12 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 99.89% uptime for Letsencrypt, counting degraded performance as up. The latest incident, "HA Datacenter 1 IPv6 Connectivity", started on Nov 6, 2026 and is still open.

Cite as: PulsAPI, “Letsencrypt status”, checked 9 November 2026, 16:52 UTC. https://www.pulsapi.com/services/letsencrypt

Letsencrypt Component Status

The main Letsencrypt systems on this page. All 12 are operational right now.

12operational
*.c.lencr.org (Production) [Public Data Center]
Operational
acme-staging-v02.api.letsencrypt.org (Staging) [High Assurance Datacenter 1]
Operational
acme-v02.api.letsencrypt.org (Production) [High Assurance Datacenter 1]
Operational

9 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking acme-v02.api.letsencrypt.org (Production) [High Assurance Datacenter 2], log.sycamore.ct.letsencrypt.org [Public Data Center], log.twig.ct.letsencrypt.org [Public Data Center], log.willow.ct.letsencrypt.org [Public Data Center], portal-staging.letsencrypt.org (Staging) [High Assurance Datacenter 1], portal.letsencrypt.org (Production) [High Assurance Datacenter 1], portal.letsencrypt.org (Production) [High Assurance Datacenter 2], stg-*.c.lencr.org (Staging) [Public Data Center], Website [Public Data Center].

See all of them free

Component statuses may change independently during partial outages.

Recent Letsencrypt Outages & Incidents

Incident history from the official Letsencrypt status page, including resolution updates.

HA Datacenter 1 IPv6 ConnectivityStarted Nov 6, 2026Investigating

Let's Encrypt is aware of an IPv6 connectivity issue from HA Datacenter 1. We are engaged in communication with our upstream provider. Production API traffic has been shifted to HA Datacenter 2 and is functioning as intended. Staging will be affected for the duration of the incident. --- [2026-11-06T17:17:52.234Z] (100) We've identified the issue and are awaiting a fix from our upstream ISP. --- [2026-11-06T21:22:19.122Z] (100) We have executed a fix with our upstream network provider, and are shifting traffic back to HA Datacenter 1. Staging should return to normal.

Issuance disruptionResolved Oct 20, 2026 · 24 minResolved

We're seeing elevated rates of validation failures that shouldn't be happening. We're investigating, and expect to resolve the issue soon. --- [2026-10-20T00:41:27.039Z] (400) We've identified the problem that's affecting issuance success rates, and expect to solve it within the next few minutes.

Issuance disruptionResolved Oct 12, 2026 · 5h 57mResolved

We've identified an issue that's disrupting certificate issuance in production. We're working on it, and expect to resolve it quickly. --- [2026-10-12T17:47:45.433Z] (100) Issuance is back to normal. We're closely monitoring our service, and will continue to investigate and fix the cause of this disruption.

Upcoming maintenance

Announced by Letsencrypt. Planned work, not an outage.

Production Remote Validation MaintenanceScheduled for Nov 10, 2026 · 1h 0mScheduled

Scheduled Maintenance

Letsencrypt Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Letsencrypt incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 4 days with incidentsNov 9

Going further back: Letsencrypt uptime by month and every recorded Letsencrypt outage.

Live Letsencrypt Outage Reports

Problems reported by engineers using Letsencrypt. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Letsencrypt problems reported yet.

Something wrong with Letsencrypt on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Letsencrypt

Is Letsencrypt down? Letsencrypt reports its live service health at status.letsencrypt.org. Track Letsencrypt outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Letsencrypt uptime at 99.89%. Response times, incident history, and SLA tracking for Letsencrypt are available on the PulsAPI dashboard.

Letsencrypt Status FAQ

Is Letsencrypt down right now?

The verdict at the top of this page comes from the latest poll of the official Letsencrypt status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Letsencrypt is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Letsencrypt recovers.

How do I check Letsencrypt uptime history?

PulsAPI tracks Letsencrypt uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.89%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Letsencrypt changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Letsencrypt outages?

PulsAPI reads the official Letsencrypt status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Letsencrypt components?

Yes. PulsAPI monitors 12 individual Letsencrypt components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Letsencrypt goes down?

Yes. Create a free account and subscribe to Letsencrypt: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Letsencrypt to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Letsencrypt problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Letsencrypt?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Letsencrypt plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Letsencrypt with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services