New Multi-region uptime checks and custom-domain status pages

Knock Outage History

Daily provider-status observations and published incident history for Knock.

Operational

Knock is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Knock for future changes.

93.1% of 58 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 96.7% 30 1

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

16 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

July 2026
Lag on data warehouse exports
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We're currently investigating a delay with our data warehouse exports. We will post an update soon.
Workflow run log delays
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating delays of availability of workflow run logs in the Dashboard and V1 API. Currently we're seeing delays of up to 18 minutes for some run logs.
Workflow processing and message delivery errors
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Workflow processing and message delivery is operational again. We are continuing to monitor closely.
identified
We've shipped a fix and are beginning to see recovery. We are continuing to monitor closely.
investigating
We're currently investigating errors processing notification workflows and sending messages for some customers.
Workflow engine outage
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and we're currently monitoring the service. All our services seem to be recovering. We're in the process of replaying any failed work that happened during the window. We expect there was no loss of workflows during this incident, but some work may have been delayed.
identified
We've identified the issue with the service and are actively working on a fix. We're seeing workflows and message deliveries process again at the usual rate.
investigating
We're currently investigating an issue with our service. We'll have an update soon.
July message data delayed
major Source not attested
Last archived state: resolved
View archived record details
monitoring
Message data synchronization into downstream customer data warehouse destinations is delayed for messages created after 8 PM ET on June 30, 2026. We have implemented a fix. We expect the issue to be fully resolved following the nightly synchronization job scheduled on July 2nd, 2026.
June 2026
Workflow run event log delays
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We're currently investigating an issue with some workflow logs being delayed.
resolved
We've completely recovered any lag on workflow logs and we are back to normal.
investigating
We're still investigating delays affecting workflow run event logs.
investigating
We're still investigating delays affecting workflow run event logs.
investigating
We're still investigating delays affecting workflow run event logs.
investigating
We are investigating delays processing workflow run event logs.
Elevated errors connecting to the Knock V1 Websocket API
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely.
investigating
We're currently investigating elevated error rates connecting to the V1 Websocket API. Realtime behavior for in-app feed and guides is degraded as a result.
Workflow run log delays
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are investigating delays in ingesting workflow run logs and triggering outbound webhooks from workflow run events.
Delayed processing of workflow logs
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We intermittently experienced delayed workflow logs between ~09:00 AM UTC and ~01:45 PM UTC today (2026/06/15). This was caused by some internal changes in how we fan out workflow logs, which caused consumers to get temporarily backlogged. The peak delay we experienced before processing workflow logs was around 15 minutes, but we intermittently saw delays of up to 5-6 minutes. This affected 1. Logs showing up in the dashboard. 2. Workflow batch mappings. We saw complete resolution at 01...
Elevated response times loading some log data
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving.
investigating
We're seeing elevated response times loading some log data. This is leading to slower page loads in the Dashboard and slower responses from some V1 API endpoints.