KnotAPI Outage History

KnotAPI is up right now

Pingoru has recorded 19 incidents for KnotAPI: 11 in the last 12 months and 2 in the last 90 days.

Source: status.knotapi.com

19incidents recorded
11last 12 months
2last 90 days
34 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking KnotAPI in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202621 of 720 (0%)
May 202600 of 744 (0%)
June 202621 of 720 (0%)
July 202600 of 744 (0%)
August 202611 of 744 (0%)
September 202610 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 30 (0%)

Incidents, newest first

Critical September 15, 2026 Service disruption on the Production API 18m Production API, Development API

Started Sep 15, 2026, 02:25 PM UTC· resolved Sep 15, 2026, 02:43 PM UTC

  1. identified Sep 15, 2026, 02:25 PM UTC

    Investigating service disruption on the Production API.

  2. monitoring Sep 15, 2026, 02:43 PM UTC

    The issue has been remediated and we are monitoring performance.

  3. resolved Sep 15, 2026, 02:46 PM UTC

    The incident is now resolved.

Read the full incident report →

Minor August 15, 2026 Service disruption on the Production API 59m Production API

Started Aug 15, 2026, 01:05 AM UTC· resolved Aug 15, 2026, 02:04 AM UTC

  1. investigating Aug 15, 2026, 01:05 AM UTC

    Webhook deliveries are currently delayed. We are investigating and will provide updates as we learn more.

  2. monitoring Aug 15, 2026, 01:15 AM UTC

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

  3. resolved Aug 15, 2026, 02:04 AM UTC

    This incident has been resolved and the system is operating normally.

Read the full incident report →

Major June 26, 2026 Service disruption on the Production API 41m

Started Jun 26, 2026, 09:28 PM UTC· resolved Jun 26, 2026, 10:09 PM UTC

  1. investigating Jun 26, 2026, 09:28 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 26, 2026, 09:40 PM UTC

    The cause of the issue has been identified and is related to a 3rd party service vendor. Our team is actively working on a fix. We expect to have an update as soon as possible.

  3. monitoring Jun 26, 2026, 09:58 PM UTC

    A fix has been applied for the issue, which was related to a 3rd party service provider. We are monitoring to confirm full recovery before marking this incident as resolved.

  4. resolved Jun 26, 2026, 10:09 PM UTC

    This incident has been resolved and the system is operating normally. Card switch attempts during the service disruption have retroactively succeeded.

Read the full incident report →

Minor June 18, 2026 Service disruption on the Production API 42m

Started Jun 18, 2026, 07:09 PM UTC· resolved Jun 18, 2026, 07:51 PM UTC

  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 April 7, 2026 Increased latency on infrastructure –

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

  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.

Read the full incident report →

Critical April 7, 2026 Increased latency on infrastructure 1h 13m

Started Apr 07, 2026, 01:13 AM UTC· resolved Apr 07, 2026, 02:27 AM UTC

  1. investigating Apr 07, 2026, 12:57 AM UTC

    We are currently investigating this issue.

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

  3. identified Apr 07, 2026, 01:18 AM UTC

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

  4. monitoring Apr 07, 2026, 01:59 AM UTC

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

  5. resolved Apr 07, 2026, 02:27 AM UTC

    This incident has been resolved.

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

Read the full incident report →

Minor January 22, 2026 Elevated Latency / Errors on API 22m Production API, Development API

Started Jan 22, 2026, 09:25 PM UTC· resolved Jan 22, 2026, 09:47 PM UTC

  1. monitoring Jan 22, 2026, 09:25 PM UTC

    Monitoring the performance / success rate of the API.

  2. resolved Jan 22, 2026, 09:47 PM UTC

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

Read the full incident report →

Major January 16, 2026 Elevated errors on API 9m Production API

Started Jan 16, 2026, 10:57 PM UTC· resolved Jan 16, 2026, 11:07 PM UTC

  1. identified Jan 16, 2026, 10:57 PM UTC

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

  2. monitoring Jan 16, 2026, 10:59 PM UTC

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

  3. monitoring Jan 16, 2026, 11:06 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 16, 2026, 11:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 26, 2025 Elevated errors from 3rd party 26m

Started Nov 26, 2025, 05:58 PM UTC· resolved Nov 26, 2025, 06:25 PM UTC

  1. identified Nov 26, 2025, 05:58 PM UTC

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

  2. monitoring Nov 26, 2025, 06:12 PM UTC

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

  3. resolved Nov 26, 2025, 06:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025 Elevated error rate on /jwe/key API route 25m Production API

Started Nov 18, 2025, 08:40 PM UTC· resolved Nov 18, 2025, 09:06 PM UTC

  1. investigating Nov 18, 2025, 08:40 PM UTC

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

  2. monitoring Nov 18, 2025, 08:54 PM UTC

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

  3. resolved Nov 18, 2025, 09:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 16, 2025 CardSwitcher API Errors With JWE 21m Production API

Started Nov 16, 2025, 03:48 PM UTC· resolved Nov 16, 2025, 04:10 PM UTC

  1. investigating Nov 16, 2025, 03:48 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. investigating Nov 16, 2025, 04:01 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 16, 2025, 04: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.

  4. resolved Nov 16, 2025, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 19, 2025 API Delays –

Started Oct 19, 2025, 02:30 AM UTC· resolved Oct 19, 2025, 02:30 AM UTC

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

    This incident has been solved

Read the full incident report →

Major October 19, 2025 API Delays –

Started Oct 19, 2025, 02:30 AM UTC· resolved Oct 19, 2025, 02:30 AM UTC

  1. resolved Oct 18, 2025, 04:09 AM UTC

    This incident has been solved

Read the full incident report →

Notice October 14, 2025 Load Pressure-Induced API Outage –

Started Oct 14, 2025, 06:30 PM UTC· resolved Oct 14, 2025, 06:30 PM UTC

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

    This incident has been resolved

Read the full incident report →

Major October 14, 2025 Load Pressure-Induced API Outage –

Started Oct 14, 2025, 06:30 PM UTC· resolved Oct 14, 2025, 06:30 PM UTC

  1. resolved Oct 14, 2025, 09:57 PM UTC

    This incident has been resolved

Read the full incident report →

Critical June 12, 2025 Google Cloud Platform Outage –

Started Jun 12, 2025, 09:12 PM UTC· resolved Jun 12, 2025, 09:12 PM UTC

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

    We are continuing to monitor the GCP outage, which has now been identified as a near-global outage on many major services. More information here: https://status.cloud.google.com/

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

    We are experiencing an outage impacting users caused by an upstream issue with our subprocessor Google Cloud Platform. The team is actively working to mitigate the issue and converting impacted users in affected flows to alternative paths to restore service where possible. Updates will be posted here as progress is made.

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

    We are continuing to monitor for any further issues.

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

    This incident has been resolved.

Read the full incident report →

Notice April 25, 2025 Production CardSwitcher Outage –

Started Apr 25, 2025, 01:08 AM UTC· resolved Apr 25, 2025, 01:08 AM UTC

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

    The issue has a resolution and a fix can be expected within the next 30 minutes.

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

    This incident has been resolved.

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

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

  4. 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 March 5, 2025 Increased latency –

Started Mar 05, 2025, 07:58 PM UTC· resolved Mar 05, 2025, 07:58 PM UTC

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

    There was a brief outage affecting the API performance

Read the full incident report →

Notice March 4, 2025 Trouble Loading or using CardSwitcher –

Started Mar 04, 2025, 11:00 PM UTC· resolved Mar 04, 2025, 11:00 PM UTC

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

    CardSwitcher down time related to Google Cloud Related Service Issue

Read the full incident report →