Render Status · History · Incident #4783
RESOLVEDSlow/failing wildcard certificates related to LetsEncrypt incident
Minor · Started Jun 18, 2026 · 9:06 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Render Status · History · Incident #4783
RESOLVEDMinor · Started Jun 18, 2026 · 9:06 PM
Duration
3h 11m
Severity
Minor
Detection lead
—
User reports
—
Summary
We have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.
Started
Jun 18, 2026 · 9:06 PM
Resolved
Jun 19, 2026 · 12:17 AM
Duration
3h 11m
Severity
Minor
Event timeline
Identified
Jun 18 · 9:06 PM RenderWe 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.
Monitoring
Jun 18 · 11:15 PM RenderWe are no longer observing any impact from the LetsEncrypt incident. We continue to monitor.
Resolved
Jun 19 · 12:17 AM RenderWe have observed no further impact from the upstream LetsEncrypt issue over the last 4 hours. All Render systems are fully operational.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026