Minor impactResolvedCloud

Render incident: Slow/failing wildcard certificates related to LetsEncrypt incident

Render reported this minor-impact incident on its official status page on Jun 18, 2026, 21:06 UTC. It was resolved after 3h 11m.

Right now Render is degraded. Live Render status →

🔔 Get alerted when Render has issuesFree · email alerts · no credit card
Jun 18, 2026, 21:06 UTC
started
Jun 19, 2026, 00:17 UTC
resolved
3h 11m
duration
Minor
impact

Affected components

  • Custom Domains

Timeline

updates from Render's status page ↗
  1. resolvedJun 19, 2026, 00:17 UTC

    We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.

  2. monitoringJun 18, 2026, 23:15 UTC

    We are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.

  3. identifiedJun 18, 2026, 21:06 UTC

    We are seeing slow or failing issuance of wildcard certificates due to an ongoing incident with the LetsEncrypt certificate authority. We are actively monitoring the situation on our end.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Render's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Render have incidents?

Render reported 16 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 1h 31m. See Render's uptime and incident history

← Previous: Stuck queued deploys (Jun 11, 2026)Next: External connections to Postgres services may terminate intermittently (Jun 23, 2026) →
Render incident on Jun 18, 2026: Slow/failing wildcard certificates related to LetsEncrypt incident · APIStatus.watch