Kisi Outage History

Kisi is up right now

Kisi had 13 outages in the last 2 years totaling 76h 35m of downtime — averaging 0.5 incidents per month.

There were 13 Kisi outages since October 22, 2024 totaling 76h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kisi.io

Minor June 16, 2026

Mindbody integration issue

Detected by Pingoru
Jun 16, 2026, 09:20 AM UTC
Resolved
Jun 16, 2026, 04:52 PM UTC
Duration
7h 31m
Affected: Mindbody Integration
Timeline · 5 updates
  1. 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.

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

  3. identified Jun 16, 2026, 10:57 AM UTC

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

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

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

Read the full incident report →

Major June 12, 2026

API caching backend issue

Detected by Pingoru
Jun 12, 2026, 10:19 AM UTC
Resolved
Jun 12, 2026, 02:12 PM UTC
Duration
3h 53m
Affected: EndpointsBackground jobsEvents & Incidents
Timeline · 2 updates
  1. 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

  2. resolved Jun 12, 2026, 02:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 30, 2026

Disruption in Events and Incidents

Detected by Pingoru
Apr 30, 2026, 12:12 PM UTC
Resolved
May 01, 2026, 07:16 AM UTC
Duration
19h 4m
Affected: Events & Incidents
Timeline · 3 updates
  1. 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.

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

  3. resolved May 01, 2026, 07:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 10, 2026

Disruption with Kisi Marketplace service

Detected by Pingoru
Apr 10, 2026, 04:03 PM UTC
Resolved
Apr 10, 2026, 06:58 PM UTC
Duration
2h 54m
Affected: ABC Ignite IntegrationCisco Meraki IntegrationGlofox IntegrationGoogle Calendar IntegrationGoogle Directory IntegrationMicrosoft Teams IntegrationMindbody IntegrationSlack IntegrationVORTEX Integration
Timeline · 4 updates
  1. investigating Apr 10, 2026, 04:03 PM UTC

    We are currently investigating the issue. This affects all marketplace applications.

  2. investigating Apr 10, 2026, 04:05 PM UTC

    We are continuing to investigate this issue.

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

  4. resolved Apr 10, 2026, 06:58 PM UTC

    Our systems have fully recovered.

Read the full incident report →

Major March 25, 2026

VORTEX Tailgating feature is experiencing issues

Detected by Pingoru
Mar 25, 2026, 05:50 AM UTC
Resolved
Mar 25, 2026, 02:13 PM UTC
Duration
8h 22m
Affected: VORTEX Integration
Timeline · 3 updates
  1. 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.

  2. identified Mar 25, 2026, 10:49 AM UTC

    VORTEX team is working on a fix for the issue.

  3. resolved Mar 25, 2026, 02:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Failing video exports for VORTEX cameras

Detected by Pingoru
Mar 17, 2026, 12:15 PM UTC
Resolved
Mar 17, 2026, 07:30 PM UTC
Duration
7h 15m
Affected: VORTEX Integration
Timeline · 3 updates
  1. 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.

  2. monitoring Mar 17, 2026, 12:15 PM UTC

    The video exports from VORTEX cameras are working as expected now.

  3. resolved Mar 17, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026

Video exports are failing for VORTEX cameras

Detected by Pingoru
Mar 12, 2026, 11:29 AM UTC
Resolved
Mar 13, 2026, 11:43 AM UTC
Duration
1d
Affected: VORTEX Integration
Timeline · 3 updates
  1. 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.

  2. monitoring Mar 12, 2026, 03:33 PM UTC

    The video exports are functioning as intended. We will continue to monitor the situation closely.

  3. resolved Mar 13, 2026, 11:43 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 30, 2025

Delayed hardware configuration synchronization

Detected by Pingoru
Oct 30, 2025, 05:26 PM UTC
Resolved
Oct 30, 2025, 05:26 PM UTC
Duration
—
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice June 26, 2025

Post mortem: June 16 elevated error rates

Detected by Pingoru
Jun 26, 2025, 10:55 AM UTC
Resolved
Jun 26, 2025, 10:55 AM UTC
Duration
—
Affected: Endpoints
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice June 16, 2025

Elevated error rates

Detected by Pingoru
Jun 16, 2025, 05:58 PM UTC
Resolved
Jun 16, 2025, 06:49 PM UTC
Duration
50m
Timeline · 4 updates
  1. 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.

  2. investigating Jun 16, 2025, 06:29 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 16, 2025, 06:39 PM UTC

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

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

Read the full incident report →

Major June 12, 2025

Events outage

Detected by Pingoru
Jun 12, 2025, 06:30 PM UTC
Resolved
Jun 12, 2025, 08:57 PM UTC
Duration
2h 27m
Affected: EndpointsBackground jobs
Timeline · 2 updates
  1. 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, ...).

  2. resolved Jun 12, 2025, 08:57 PM UTC

    Google Cloud Platform has restored service, and all of our affected systems are operating normally again.

Read the full incident report →

Notice June 2, 2025

Delayed event processing

Detected by Pingoru
Jun 02, 2025, 04:00 PM UTC
Resolved
Jun 02, 2025, 04:00 PM UTC
Duration
—
Timeline · 1 update
  1. 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

Read the full incident report →

Major October 22, 2024

Elevated API error rates

Detected by Pingoru
Oct 22, 2024, 09:00 AM UTC
Resolved
Oct 22, 2024, 09:00 AM UTC
Duration
—
Affected: Endpoints
Timeline · 1 update
  1. 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.

Read the full incident report →