KnotAPI Outage History

KnotAPI is up right now

KnotAPI had 9 outages in the last 2 years totaling 42m of downtime — averaging 0.4 incidents per month.

There were 9 KnotAPI outages since October 14, 2025 totaling 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.knotapi.com

Minor June 18, 2026

Service disruption on the Production API

Detected by Pingoru
Jun 18, 2026, 07:09 PM UTC
Resolved
Jun 18, 2026, 07:51 PM UTC
Duration
42m
Timeline · 4 updates
  1. investigating Jun 18, 2026, 07:09 PM UTC

    We are currently investigating a service disruption affecting the Production API. Requests may be failing or experiencing significant delays. The Development API is unaffected. We will provide updates as we learn more.

  2. identified Jun 18, 2026, 07:11 PM UTC

    The cause of the issue has been identified. Our team is actively working on a fix. We expect to have an update as soon as possible.

  3. monitoring Jun 18, 2026, 07:33 PM UTC

    A fix has been applied for the issue. We are monitoring to confirm full recovery before marking this incident as resolved.

  4. resolved Jun 18, 2026, 07:51 PM UTC

    This incident has been resolved. The system is operating normally. We apologize for any disruption this may have caused.

Read the full incident report →

Notice May 29, 2026

API Delays

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Oct 19, 2025, 02:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 29, 2026, 05:01 PM UTC

    This incident has been solved

Read the full incident report →

Notice May 29, 2026

CardSwitcher API Errors With JWE

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Nov 16, 2025, 04:10 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 29, 2026, 05:01 PM UTC

    We are currently investigating an issue with failures related to the /card route for those partners using a JWE to send card data.

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

    The issue has been rectified and was due to a 3rd party vendor outage. Systems are back to normal and we are monitoring actively.

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

    We are continuing to investigate this issue.

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

    This incident has been resolved.

Read the full incident report →

Notice May 29, 2026

Elevated error rate on /jwe/key API route

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Nov 18, 2025, 09:06 PM UTC
Duration
—
Timeline · 3 updates
  1. resolved May 29, 2026, 05:01 PM UTC

    This incident has been resolved.

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

    The team is actively investigating the issue. The scope is confined to partners using JWE encryption.

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

    A fix has been implemented and we are monitoring the results.

Read the full incident report →

Notice May 29, 2026

Elevated errors from 3rd party

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Nov 26, 2025, 06:25 PM UTC
Duration
—
Timeline · 3 updates
  1. identified May 29, 2026, 05:01 PM UTC

    The issue has been identified and a fix is being implemented.

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

    A fix has been implemented and we are monitoring the results.

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

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026

Elevated Latency / Errors on API

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Jan 22, 2026, 09:47 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring May 29, 2026, 05:01 PM UTC

    Monitoring the performance / success rate of the API.

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

    The incident has been resolved and the API is confirmed fully operational

Read the full incident report →

Major May 29, 2026

Elevated errors on API

Detected by Pingoru
May 29, 2026, 05:01 PM UTC
Resolved
Jan 16, 2026, 11:07 PM UTC
Duration
—
Timeline · 4 updates
  1. monitoring May 29, 2026, 05:01 PM UTC

    A fix has been implemented and we are monitoring the results.

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

    The issue has been identified and a fix is being implemented.

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

    This incident has been resolved.

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

    We are continuing to monitor for any further issues.

Read the full incident report →