Kisi Outage History
Kisi is up right nowKisi had 11 outages in the last 2 years totaling 99h 31m of downtime — averaging 0.5 incidents per month.
There were 11 Kisi outages since October 30, 2025 totaling 99h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.
Delay in processing events
Timeline · 1 update
- 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.
Cisco Meraki Snapshot API Unavailable
Affected: ABC Ignite IntegrationCisco Meraki IntegrationGlofox IntegrationGoogle Calendar IntegrationGoogle Directory IntegrationMicrosoft Teams IntegrationMindbody IntegrationVORTEX Integration
Timeline · 5 updates
- 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.
Mindbody integration issue
Affected: Mindbody Integration
Timeline · 5 updates
- 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.
API caching backend issue
Affected: EndpointsBackground jobsEvents & Incidents
Timeline · 2 updates
- 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.
Disruption in Events and Incidents
Affected: Events & Incidents
Timeline · 3 updates
- 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.
Disruption with Kisi Marketplace service
Affected: ABC Ignite IntegrationCisco Meraki IntegrationGlofox IntegrationGoogle Calendar IntegrationGoogle Directory IntegrationMicrosoft Teams IntegrationMindbody IntegrationSlack IntegrationVORTEX Integration
Timeline · 4 updates
- 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.
VORTEX Tailgating feature is experiencing issues
Affected: VORTEX Integration
Timeline · 3 updates
- 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.
Failing video exports for VORTEX cameras
Affected: VORTEX Integration
Timeline · 3 updates
- 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.
Video exports are failing for VORTEX cameras
Affected: VORTEX Integration
Timeline · 3 updates
- 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.
Delayed hardware configuration synchronization
Timeline · 1 update
- 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.