Quiltt incident

Northflank third-party security incident

Ongoing since 10:50 PM UTC.

monitoring Oct 31, 2026, 01:58 AM UTC

We are monitoring a security incident disclosed today by Northflank, one of our infrastructure vendors. Northflank has advised customers to assume their environment variables were compromised. No customer traffic is served from Northflank — all customer-facing web traffic runs on our primary hosting providers. Background workers did run there with production database and Redis credentials. We have rotated every credential exposed to that environment. Our review of production database, network, application, and job queue logs found no evidence of unauthorized access to customer data. Customer-facing services have not been interrupted. We will post further updates here if anything changes.

Started
Oct 30, 2026, 10:50 PM UTC
Resolved
Ongoing
Duration
● 4h 52m
Detected by Pingoru
Oct 30, 2026, 10:50 PM UTC

Update timeline

  1. monitoring Oct 30, 2026, 10:50 PM UTC

    We are monitoring a security incident disclosed today by Northflank, one of our infrastructure vendors. Northflank has advised all customers to assume their environment variables were compromised. No customer traffic was served from Northflank — all customer-facing web traffic runs on our primary hosting providers. Background workers did run there with production database and Redis credentials. As a precaution we rotated every credential exposed to that environment, including those production database and Redis credentials, and we are reviewing access logs for any unauthorized use. Customer-facing services were not interrupted. We will update this incident as Northflank's investigation develops and our log review completes.

  2. monitoring Oct 31, 2026, 01:58 AM UTC

    We are monitoring a security incident disclosed today by Northflank, one of our infrastructure vendors. Northflank has advised customers to assume their environment variables were compromised. No customer traffic is served from Northflank — all customer-facing web traffic runs on our primary hosting providers. Background workers did run there with production database and Redis credentials. We have rotated every credential exposed to that environment. Our review of production database, network, application, and job queue logs found no evidence of unauthorized access to customer data. Customer-facing services have not been interrupted. We will post further updates here if anything changes.

Your product runs on more than Quiltt

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →