Kisi Outage History
Kisi is up right nowPingoru has recorded 53 incidents for Kisi: 11 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 15 of 720 (2%) |
| May 2026 | 0 | 7 of 744 (1%) |
| June 2026 | 2 | 11 of 720 (2%) |
| July 2026 | 1 | 26 of 744 (4%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 23 of 720 (3%) |
| October 2026 | 1 | 8 of 507 (2%) |
Incidents, newest first
Notice October 2, 2026 Unlock failures on some controllers and readers 8h 15m
Started Oct 02, 2026, 01:00 AM UTC· resolved Oct 02, 2026, 09:15 AM UTC
- resolved Oct 02, 2026, 04:58 AM UTC
Between 01:15 and 04:25 UTC on October 2, 2026, some Kisi controllers and readers gradually stopped accepting their configuration following a routine credential refresh from the Kisi cloud. Unlocks through affected devices failed during this time. Because devices were affected gradually rather than all at once, some doors at the same site kept working while others did not. We identified the cause and restored a working configuration to every affected device. All online devices have operated normally since 04:25 UTC. Devices that were offline during this period will pick up the corrected configuration automatically when they reconnect, so no action is needed on your side. We are rolling out a permanent fix to prevent this from happening again. We apologize for the disruption.
- postmortem Oct 06, 2026, 01:23 PM UTC
**What happened** Between 01:15 and 04:25 UTC on 2 October 2026, some Kisi controllers and readers couldn't unlock doors. Affected users saw a "door not found" message in the Kisi app, and some readers appeared dark or dimmed. The affected devices stayed online but had temporarily lost their door configuration. This was an availability issue only. Affected doors couldn't be unlocked through Kisi, but no one was given access they didn't already have, and no customer data was exposed. **What caused it** On 1 October we deployed a change to how our cloud service issues device credentials. Overnight, during routine scheduled maintenance, some devices received an updated configuration in a format they didn't accept. Instead of keeping their last working configuration, those devices discarded it, so they could no longer match unlock requests to their doors. The maintenance updates devices gradually over several hours. That's why the problem spread over time, and why doors at the same site could behave differently. **How we resolved it** We identified the cause at 03:33 UTC, stopped the maintenance, and restored a working configuration to every affected online device by 04:25 UTC. No on-site visits or hardware changes were needed. We fully reverted the original change at 09:15 UTC, well before the next scheduled maintenance. Devices that were offline during the incident recover automatically when they reconnect. **What we're changing** * Devices will keep their last working configuration if they receive one they can't use. This is coming in an upcoming device software update. * Configuration changes will be checked automatically against what devices accept before they roll out. * We're expanding monitoring of device configuration and unlock success. * Changes that can affect devices will get review across our cloud and hardware teams before release. We're sorry for the disruption this caused you and the people who rely on your doors. If you have questions or still see a device behaving unexpectedly, please contact Kisi Support.
Minor September 4, 2026 Delay in processing events 23h 5m
Started Sep 04, 2026, 01:30 AM UTC· resolved Sep 05, 2026, 12:35 AM UTC
- resolved Sep 04, 2026, 07:25 AM UTC
Between approximately 22:45 UTC on September 3 and 00:35 UTC on September 4, Marketplace event processing was delayed due to an interruption at our cloud provider. Processing has returned to normal. We regret the inconvenience.
Minor July 15, 2026 Cisco Meraki Snapshot API Unavailable 1d 2h ABC Ignite Integration, Cisco Meraki Integration, Glofox Integration, Google Calendar Integration and 4 more
Started Jul 15, 2026, 02:27 AM UTC· resolved Jul 16, 2026, 04:42 AM UTC
- identified Jul 15, 2026, 02:27 AM UTC
The issue has been identified and we are working on a fix.
- identified Jul 15, 2026, 06:27 AM UTC
We have recovered mostly on all integrations except Cisco Meraki integration. We are working on a fix.
- identified Jul 15, 2026, 08:36 AM UTC
Cisco Meraki API endpoint for fetching camera snapshots is not working as expected. We have contacted Cisco Meraki support.
- monitoring Jul 16, 2026, 03:38 AM UTC
Cisco Meraki has solved the issue on their end. We will enable snapshots processing on our end and monitor it. Reference: https://status.meraki.net/incidents/6lb0s9fbny1c
- resolved Jul 16, 2026, 04:42 AM UTC
Cisco Meraki Snapshots are working normally again. We have a backlog but it will be cleared in sometime.
Minor June 16, 2026 Mindbody integration issue 7h 31m Mindbody Integration
Started Jun 16, 2026, 09:20 AM UTC· resolved Jun 16, 2026, 04:52 PM UTC
- investigating Jun 16, 2026, 09:20 AM UTC
Mindbody API doesn't return any client information which subsequently led to revocation of access rights during the daily sync.
- identified Jun 16, 2026, 10:29 AM UTC
We have contacted the Mindbody support team and waiting for updates from their side. We are manually restoring access to as many as users as we can.
- identified Jun 16, 2026, 10:57 AM UTC
We are continuing to work on a fix for this issue.
- identified Jun 16, 2026, 11:00 AM UTC
We have restored access to all users who lost their access during the daily sync. Webhooks will continue to work as expected. We will pause daily syncs on Mindbody integration until the issue is resolved.
- resolved Jun 16, 2026, 04:52 PM UTC
Mindbody team has confirmed that they have fixed the issue. Daily sync should proceed as usual. If you notice any issues, please reach out to Kisi Support team.
Major June 12, 2026 API caching backend issue 3h 53m Endpoints, Background jobs, Events & Incidents
Started Jun 12, 2026, 10:19 AM UTC· resolved Jun 12, 2026, 02:12 PM UTC
- monitoring Jun 12, 2026, 10:19 AM UTC
Between 1:15 AM and 6:15 AM UTC our API experienced a resource overload incident affecting a small subset of resources that require access to our caching backend. A fix has been deployed and we are actively monitoring the situation. We are working on restoring metadata. The services that were affected: - Event webhook delivery - Intercom calls - Incident alerts - Camera snapshots
- resolved Jun 12, 2026, 02:12 PM UTC
This incident has been resolved.
Major April 30, 2026 Disruption in Events and Incidents 19h 4m Events & Incidents
Started Apr 30, 2026, 12:12 PM UTC· resolved May 01, 2026, 07:16 AM UTC
- investigating Apr 30, 2026, 12:12 PM UTC
We are currently experiencing issues in our events and incidents services due to an issue in our cloud services provider (GCP). We are actively working to mitigate the issue.
- monitoring Apr 30, 2026, 12:57 PM UTC
Our events and incidents services have been partially restored. We are working to restore missing events. Incidents dispatch may also be delayed.
- resolved May 01, 2026, 07:16 AM UTC
This incident has been resolved.
Major April 10, 2026 Disruption with Kisi Marketplace service 2h 54m ABC Ignite Integration, Cisco Meraki Integration, Glofox Integration, Google Calendar Integration and 5 more
Started Apr 10, 2026, 04:03 PM UTC· resolved Apr 10, 2026, 06:58 PM UTC
- investigating Apr 10, 2026, 04:03 PM UTC
We are currently investigating the issue. This affects all marketplace applications.
- investigating Apr 10, 2026, 04:05 PM UTC
We are continuing to investigate this issue.
- monitoring Apr 10, 2026, 04:46 PM UTC
We have deployed a new version that fixes the issue. We are monitoring the recovery of the service.
- resolved Apr 10, 2026, 06:58 PM UTC
Our systems have fully recovered.
Major March 25, 2026 VORTEX Tailgating feature is experiencing issues 8h 22m VORTEX Integration
Started Mar 25, 2026, 05:50 AM UTC· resolved Mar 25, 2026, 02:13 PM UTC
- identified Mar 25, 2026, 05:50 AM UTC
We are currently investigating the issue. It appears to be related to the VORTEX API. We have already reached out to the VORTEX team to address this matter.
- identified Mar 25, 2026, 10:49 AM UTC
VORTEX team is working on a fix for the issue.
- resolved Mar 25, 2026, 02:13 PM UTC
This incident has been resolved.
Major March 16, 2026 Failing video exports for VORTEX cameras 23h 25m VORTEX Integration
Started Mar 16, 2026, 08:05 PM UTC· resolved Mar 17, 2026, 07:30 PM UTC
- investigating Mar 16, 2026, 08:05 PM UTC
We are currently investigating this issue. We are coordinating with VORTEX team to resolve this issue as soon as possible.
- monitoring Mar 17, 2026, 12:15 PM UTC
The video exports from VORTEX cameras are working as expected now.
- resolved Mar 17, 2026, 07:30 PM UTC
This incident has been resolved.
Major March 12, 2026 Video exports are failing for VORTEX cameras 1d VORTEX Integration
Started Mar 12, 2026, 11:29 AM UTC· resolved Mar 13, 2026, 11:43 AM UTC
- investigating Mar 12, 2026, 11:29 AM UTC
We are currently investigating the issue. It appears to be related to the VORTEX API. We have already reached out to the VORTEX team to address this matter.
- monitoring Mar 12, 2026, 03:33 PM UTC
The video exports are functioning as intended. We will continue to monitor the situation closely.
- resolved Mar 13, 2026, 11:43 AM UTC
This incident has been resolved.
Notice October 30, 2025 Delayed hardware configuration synchronization 3h 40m
Started Oct 30, 2025, 01:10 PM UTC· resolved Oct 30, 2025, 04:50 PM UTC
- resolved Oct 30, 2025, 05:26 PM UTC
Between 13:10 and 16:50 UTC, customers may have experienced a delay in synchronization of reader, controller and door configurations from the cloud to the devices. The issue has since been resolved. All device configurations are now up-to-date.
Notice June 26, 2025 Post mortem: June 16 elevated error rates – Endpoints
Started Jun 26, 2025, 10:55 AM UTC· resolved Jun 26, 2025, 10:55 AM UTC
- resolved Jun 26, 2025, 10:55 AM UTC
On June 16, 2025, the Kisi production API experienced a temporary degradation in availability. Investigation revealed that the root cause was an unexpected behavior in Google Cloud Platform’s (GCP) Cloud Run during an internal stack migration and service redistribution process managed by GCP. According to GCP’s engineering response, a background migration and redistribution of workloads triggered a one-time instance restart in our Cloud Run service. This resulted in the application falling below its configured minimum instances temporarily, impacting our ability to serve requests reliably. While the redistribution process is part of GCP’s infrastructure optimization efforts, the side effect of under-scaling was not communicated in advance and not within our control. GCP has confirmed that a fix has been rolled out to address this issue and prevent recurrence in similar scenarios.
Notice June 16, 2025 Elevated error rates 50m
Started Jun 16, 2025, 05:58 PM UTC· resolved Jun 16, 2025, 06:49 PM UTC
- investigating Jun 16, 2025, 05:58 PM UTC
We’re currently investigating an increase in 5xx and 4xx errors affecting our public API. This may impact door unlocks, as well as access to the web and mobile dashboards. We’ll share more updates as we identify the root cause.
- investigating Jun 16, 2025, 06:29 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 16, 2025, 06:39 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 16, 2025, 06:49 PM UTC
The incident has been resolved. It lasted for approximately 30 minutes, from 17:15 to 17:45 UTC.
Major June 12, 2025 Events outage 2h 27m Endpoints, Background jobs
Started Jun 12, 2025, 06:30 PM UTC· resolved Jun 12, 2025, 08:57 PM UTC
- investigating Jun 12, 2025, 06:30 PM UTC
Google Cloud Platform is experiencing an outage. Unlocks are not affected, but there may be delays for event related processing (webhooks, event history, ...).
- resolved Jun 12, 2025, 08:57 PM UTC
Google Cloud Platform has restored service, and all of our affected systems are operating normally again.
Notice June 2, 2025 Delayed event processing –
Started Jun 02, 2025, 04:00 PM UTC· resolved Jun 02, 2025, 04:00 PM UTC
- resolved Jun 09, 2025, 11:27 AM UTC
The Event Service—Kisi’s core system for capturing and forwarding events—experienced a degradation after a recent feature deployment. An unclosed-connection bug gradually exhausted CPU and memory resources, throttling database writes. Our monitoring detected elevated error rates. A redeployment addressed the bug, but due to a large backlog some delayed event webhooks were unfortunately dropped. However, no events were lost. Service Impact: - Event visibility in the Kisi Admin Dashboard and via API was degraded during the degradation window (new events were not yet persisted). - Event Webhook deliveries and report generation were paused until full recovery. Next Steps: - We will adapt our system to process all event webhooks and event related jobs regardless of backlog size - We will isolate our event pipeline to avoid spillover effects from new functionality
Major October 22, 2024 Elevated API error rates – Endpoints
Started Oct 22, 2024, 09:00 AM UTC· resolved Oct 22, 2024, 09:00 AM UTC
- resolved Oct 22, 2024, 01:35 PM UTC
The most recent Kisi API release caused elevated error rates. The release has been rolled back and API error rates are back to normal. Unlocks were affected during this time.