Resolved after 17 hours 42 minutes, on October 16, 2026.
What happened: Starting around 20:50 UTC on October 16, 2026, some users in the US region couldn't sign in to Quickpass QTech chrome extension. They saw a "403 Forbidden" error, and some briefly saw a "Server Error, try again in 30 seconds" message. Over the next few days it affected a growing number of login attempts. Root cause: Our web application firewall uses a set of rules managed by our cloud provider. Those rules were updated on the provider's side, and one of them started wrongly flagging a normal part of our sign-in process as a threat. The firewall then blocked those login requests. We made no changes to our systems before the issue started. Security impact: There was no security breach, and no data was exposed or compromised. The firewall blocked legitimate traffic. Nothing got past it that shouldn't have. Our authentication systems were healthy throughout, and no customer or partner data was accessed. The only impact was that users couldn't log in. Resolution: We adjusted the firewall configuration so the sign-in process works again. All other protections stay fully in place. Logins were restored at 1:42 PM UTC, 19th Oct 2026.
Update timeline
- resolved Oct 19, 2026, 04:31 PM UTC
What happened: Starting around 20:50 UTC on October 16, 2026, some users in the US region couldn't sign in to Quickpass QTech chrome extension. They saw a "403 Forbidden" error, and some briefly saw a "Server Error, try again in 30 seconds" message. Over the next few days it affected a growing number of login attempts. Root cause: Our web application firewall uses a set of rules managed by our cloud provider. Those rules were updated on the provider's side, and one of them started wrongly flagging a normal part of our sign-in process as a threat. The firewall then blocked those login requests. We made no changes to our systems before the issue started. Security impact: There was no security breach, and no data was exposed or compromised. The firewall blocked legitimate traffic. Nothing got past it that shouldn't have. Our authentication systems were healthy throughout, and no customer or partner data was accessed. The only impact was that users couldn't log in. Resolution: We adjusted the firewall configuration so the sign-in process works again. All other protections stay fully in place. Logins were restored at 1:42 PM UTC, 19th Oct 2026.
- postmortem Oct 19, 2026, 04:31 PM UTC
What happened: Starting around 20:50 UTC on October 16, 2026, some users in the US region couldn't sign in to Quickpass QTech chrome extension. They saw a "403 Forbidden" error, and some briefly saw a "Server Error, try again in 30 seconds" message. Over the next few days it affected a growing number of login attempts. Root cause: Our web application firewall uses a set of rules managed by our cloud provider. Those rules were updated on the provider's side, and one of them started wrongly flagging a normal part of our sign-in process as a threat. The firewall then blocked those login requests. We made no changes to our systems before the issue started. Security impact: There was no security breach, and no data was exposed or compromised. The firewall blocked legitimate traffic. Nothing got past it that shouldn't have. Our authentication systems were healthy throughout, and no customer or partner data was accessed. The only impact was that users couldn't log in. Resolution: We adjusted the firewall configuration so the sign-in process works again. All other protections stay fully in place. Logins were restored at 1:42 PM UTC, 19th Oct 2026.
Your product runs on more than CyberQP
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services