Kisi 中断历史

1. 2026年7月15日 UTC 02:27identified

   这个问题已经确定,我们正在设法解决问题.

2. 2026年7月15日 UTC 06:27identified

   除了思科·梅拉基的一体化之外,我们主要在所有的一体化中恢复。 我们正在努力解决问题.

3. 2026年7月15日 UTC 08:36identified

   用于取相机快照的 Cisco Meraki API 端点没有预期效果 。 我们联系了思科·梅拉基的支持.

4. 2026年7月16日 UTC 03:38monitoring

   Cisco Meraki已经解决了问题 我们将允许我们端面的快照处理和监测。 参考:https://status.meraki.net/incidents/6lb0s9fbny1c (中文(简体) )

5. 2026年7月16日 UTC 04:42resolved

   思科·梅拉基快照又正常工作了 我们有积压的工作,但迟早会清理.

自动翻译自官方事件更新。

1. 2026年6月16日 UTC 09:20investigating

   Mindbody API doesn't return any client information which subsequently led to revocation of access rights during the daily sync.

2. 2026年6月16日 UTC 10:29identified

   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. 2026年6月16日 UTC 10:57identified

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

4. 2026年6月16日 UTC 11:00identified

   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. 2026年6月16日 UTC 16:52resolved

   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.

1. 2026年6月12日 UTC 10:19monitoring

   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. 2026年6月12日 UTC 14:12resolved

   This incident has been resolved.

1. 2026年4月30日 UTC 12:12investigating

   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. 2026年4月30日 UTC 12:57monitoring

   Our events and incidents services have been partially restored. We are working to restore missing events. Incidents dispatch may also be delayed.

3. 2026年5月1日 UTC 07:16resolved

   This incident has been resolved.

1. 2026年4月10日 UTC 16:03investigating

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

2. 2026年4月10日 UTC 16:05investigating

   We are continuing to investigate this issue.

3. 2026年4月10日 UTC 16:46monitoring

   We have deployed a new version that fixes the issue. We are monitoring the recovery of the service.

4. 2026年4月10日 UTC 18:58resolved

   Our systems have fully recovered.

1. 2026年3月25日 UTC 05:50identified

   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. 2026年3月25日 UTC 10:49identified

   VORTEX team is working on a fix for the issue.

3. 2026年3月25日 UTC 14:13resolved

   This incident has been resolved.

1. 2026年3月16日 UTC 20:05investigating

   We are currently investigating this issue. We are coordinating with VORTEX team to resolve this issue as soon as possible.

2. 2026年3月17日 UTC 12:15monitoring

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

3. 2026年3月17日 UTC 19:30resolved

   This incident has been resolved.

1. 2026年3月12日 UTC 11:29investigating

   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. 2026年3月12日 UTC 15:33monitoring

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

3. 2026年3月13日 UTC 11:43resolved

   This incident has been resolved.

1. 2025年10月30日 UTC 17:26resolved

   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.

1. 2025年6月26日 UTC 10:55resolved

   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.

1. 2025年6月16日 UTC 17:58investigating

   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. 2025年6月16日 UTC 18:29investigating

   We are continuing to investigate this issue.

3. 2025年6月16日 UTC 18:39monitoring

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

4. 2025年6月16日 UTC 18:49resolved

   The incident has been resolved. It lasted for approximately 30 minutes, from 17:15 to 17:45 UTC.

1. 2025年6月12日 UTC 18:30investigating

   Google Cloud Platform is experiencing an outage. Unlocks are not affected, but there may be delays for event related processing (webhooks, event history, ...).

2. 2025年6月12日 UTC 20:57resolved

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

1. 2025年6月9日 UTC 11:27resolved

   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

1. 2024年10月22日 UTC 13:35resolved

   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.

1. 2024年5月31日 UTC 08:33identified

   An issue is ongoing causing email delays for all customers. We have identified our email delivery service as the cause of this incident. See https://status.mailgun.com/incidents/30w5l1zqcw5r Currently, a majority of our outgoing emails are affected.

2. 2024年5月31日 UTC 09:01monitoring

   A fix has been implemented by our email delivery service provider and we are monitoring results. As of 08:30 UTC a majority of emails are being delivered.

3. 2024年5月31日 UTC 09:59resolved

   Fix implemented by our email service provider seems to have fixed the issue. All our outgoing emails have been delivered since 08:30 UTC.

1. 2024年5月27日 UTC 13:32identified

   We are investigating an issue causing email delays for all customers. The incident started 13:10 UTC, and is ongoing.

2. 2024年5月27日 UTC 13:38identified

   We have identified our email delivery service as the cause of this incident. See https://status.mailgun.com/incidents/8bn2px3nyfy4 Currently, a majority of our outgoing emails are affected.

3. 2024年5月27日 UTC 13:55monitoring

   A majority of emails are being delivered as of 13:52 UTC. We will continue to monitor the issue.

4. 2024年5月27日 UTC 14:47resolved

   Our email delivery provider has implemented a fix and is monitoring the results. Emails are being delivered successfully since 13:52 UTC.

1. 2024年4月11日 UTC 14:22identified

   The most recent Kisi API release caused elevated error rates. We are rolling back and expect the issue to be resolved in a minute or two. Unlocks are affected.

2. 2024年4月11日 UTC 14:23resolved

   The release has been rolled back. Unlock failure rates and API error rates are back to normal.

1. 2024年3月25日 UTC 00:15investigating

   The rate of failed Cisco Meraki camera snapshots is higher than normal, we are investigating the issue. We will provide an update by Monday, 2023-04-25 09:00 UTC with current details.

2. 2024年3月25日 UTC 10:15resolved

   Cisco Meraki camera snapshots are working normally. The elevated error rates could be attributed to a single Kisi organization.

1. 2024年3月7日 UTC 14:13resolved

   We experienced a short (less than 10 minutes) API outage. As a result, unlocks via cloud were failing and web dashboard was unavailable. Offline cache unlocks (https://docs.kisi.io/concepts/offline_support) were working as usual. The issue has now been resolved and we are doing everything to make sure it will not happen again.

1. 2024年1月25日 UTC 15:11monitoring

   We discovered an issue that caused in-app unlocks to fail for a small group of users that belong to groups with restrictions between 2024-01-24 11:12 UTC and 2024-01-25 14:19 UTC. Although we have resolved the underlying problem causing unlock failures, there was a misreporting of these failures as successes in the unlock events. We are actively addressing and correcting the affected events.

2. 2024年1月26日 UTC 10:48monitoring

   We are currently correcting the affected unlock events.

3. 2024年1月26日 UTC 14:53resolved

   All incorrect unlock events have been fixed.