Make Status · History · Incident #6004
RESOLVEDEU1 - Scenarios failing at initialization with "Failed to verify account" error
Major · Started Jul 22, 2026 · 5: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'] . '/'; ?>
Make Status · History · Incident #6004
RESOLVEDMajor · Started Jul 22, 2026 · 5:30 PM
Duration
< 1m
Severity
Major
Detection lead
—
User reports
—
Summary
Between 17:29 and 17:34 CEST on 22nd of July, scenarios on the EU1 zone failed at initialization with a "Failed to verify account" error, affecting connections across all apps. Approximately 200 scenarios were automatically deactivated as a result and have since been re-enabled. We are actively working to prevent recurrence.
Started
Jul 22, 2026 · 5:30 PM
Resolved
Jul 22, 2026 · 5:30 PM
Duration
< 1m
Severity
Major
Event timeline
Resolved
Jul 29 · 4:23 PM MakeBetween 17:29 and 17:34 CEST on 22nd of July, scenarios on the EU1 zone failed at initialization with a "Failed to verify account" error, affecting connections across all apps. Approximately 200 scenarios were automatically deactivated as a result and have since been re-enabled. We are actively working to prevent recurrence.
Pattern
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. Pulsetic® is a registered trademark.