Is KnotAPI down?

Last checked 7m ago
Current status
KnotAPI is up

No incidents right now.

Official status page: https://status.knotapi.com · Polled every 5 minutes · 3 components tracked

KnotAPI is operational right now. Last checked 7m ago; the most recent incident resolved 15d ago.

Real-time KnotAPI status, recent outages, and incident history — pulled directly from KnotAPI's official status page at https://status.knotapi.com every 5 minutes. Pingoru tracks 3 KnotAPI services and has captured 11 incidents in the last 90 days (99.26% uptime). Get email, Slack, Discord, or webhook alerts the moment KnotAPI reports a new incident — free for 5 monitors, no credit card.

Users who monitor KnotAPI also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
KnotAPI uptime 99.26% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started May 29, 2026, 05:01 PM UTC · Resolved Apr 07, 2026, 02:27 AM UTC
    Timeline · 6 updates
    • 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.

    • monitoring · May 29, 2026, 05:01 PM UTC

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

    • 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.

    • investigating · May 29, 2026, 05:01 PM UTC

      We are currently investigating this issue.

    • identified · May 29, 2026, 05:01 PM UTC

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

    • resolved · May 29, 2026, 05:01 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 1h 13m
    Started Apr 07, 2026, 01:13 AM UTC · Resolved Apr 07, 2026, 02:27 AM UTC
    Timeline · 6 updates
    • investigating · Apr 07, 2026, 12:57 AM UTC

      We are currently investigating this issue.

    • identified · Apr 07, 2026, 01:13 AM 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.

    • identified · Apr 07, 2026, 01:18 AM UTC

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

    • monitoring · Apr 07, 2026, 01:59 AM UTC

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

    • resolved · Apr 07, 2026, 02:27 AM UTC

      This incident has been resolved.

    • postmortem · Apr 07, 2026, 07:42 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.

    Latest: **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 thro…

See the full KnotAPI outage history

7 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse KnotAPI outage history →

Or sign up free to get alerts when KnotAPI breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 2 incidents View full outage history →