KnotAPI incident

Increased latency on infrastructure

Notice Resolved

KnotAPI experienced a notice incident on May 29, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 05:01 PM UTC
Resolved
Apr 07, 2026, 02:27 AM UTC
Duration
Detected by Pingoru
May 29, 2026, 05:01 PM UTC

Update timeline

  1. identified May 29, 2026, 05:01 PM UTC

    The issue has been identified at the infra level. Specifically, the issue is related to Google Cloud Tasks in the us-central1 region of Google Cloud Platform and is affecting other businesses.

  2. monitoring May 29, 2026, 05:01 PM UTC

    We have switched cloud regions as google cloud tasks has a confirmed outage on this region.

  3. resolved May 29, 2026, 05:01 PM UTC

    **April 6, 2026** Duration: 2 hours, 40 minutes \(7:19 PM – 9:59 PM EDT\) ‌ **What happened** On April 6, 2026 at approximately 7:19 PM EDT, we identified that tasks submitted through our platform were not being processed. This affected all product offerings. ‌ **Root cause** The incident was caused by a regional outage in Google Cloud Tasks, which is responsible for the queuing infrastructure we use to scale our services. ‌ **Timeline** * 7:19 PM - Issue identified by our team. * 7:19 PM – 9:30 PM - Investigation and mitigation efforts, including temporarily migrating regions and temporarily disabling certain merchant integrations to prevent user impact. * ~9:59 PM - Confirmed the issue was resolved and systems were working as intended. Began processing the backlog. * 11:07 PM - Monitoring was successful. Incident resolved. ‌ **Impact** * Tasks submitted during the incident window experienced significant processing delays. * All queued tasks were eventually processed once the alternate region was operational. * A small number of card switches could not be retried automatically. Affected users can simply re-initiate their card switch to complete the process.

  4. investigating May 29, 2026, 05:01 PM UTC

    We are currently investigating this issue.

  5. identified May 29, 2026, 05:01 PM UTC

    We are continuing to work on a fix for this issue.

  6. resolved May 29, 2026, 05:01 PM UTC

    This incident has been resolved.