Runway Status · History · Incident #4051
RESOLVEDIssues affecting Aleph 2.0 generations
Major · Started May 26, 2026 · 7:30 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'] . '/'; ?>
Runway Status · History · Incident #4051
RESOLVEDMajor · Started May 26, 2026 · 7:30 PM
Duration
< 1m
Severity
Major
Detection lead
—
User reports
—
Summary
We identified and resolved an issue impacting Aleph 2.0 generations. The incident lasted for approximately 2 hours.
Started
May 26, 2026 · 7:30 PM
Resolved
May 26, 2026 · 7:30 PM
Duration
< 1m
Severity
Major
Event timeline
Resolved
May 26 · 10:10 PM RunwayWe identified and resolved an issue impacting Aleph 2.0 generations. The incident lasted for approximately 2 hours.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT