Incidents reported on status page for Kiflo https://status.kiflo.com/ https://d1lppblt9t2x15.cloudfront.net/logos/fe4fb69a6b8a62d78df4db6a48aa4aec.png https://status.kiflo.com/ en https://status.kiflo.com/incident/740500 Thu, 09 Oct 2025 16:10:00 -0000 https://status.kiflo.com/incident/740500#f5169aaf4898c8e9b0cd366968b67d50ede2c199e84732b78173bcc077a57416 Our cloud provider has resolved the issue. Availability should now be back to normal, with latencies returning to expected levels. We’ll continue to monitor closely to ensure full stability. https://status.kiflo.com/incident/740500 Thu, 09 Oct 2025 16:10:00 -0000 https://status.kiflo.com/incident/740500#f5169aaf4898c8e9b0cd366968b67d50ede2c199e84732b78173bcc077a57416 Our cloud provider has resolved the issue. Availability should now be back to normal, with latencies returning to expected levels. We’ll continue to monitor closely to ensure full stability. https://status.kiflo.com/incident/740500 Thu, 09 Oct 2025 10:16:00 -0000 https://status.kiflo.com/incident/740500#f77917172bba1d06c1571bbc488b3b72905466b8a33b776138144a36b410e16e Some customers may experience intermittent performance degradation or brief interruptions when accessing services in Europe and Africa. Our cloud provider is actively working on a resolution, and we will provide the next update within 60 minutes or sooner if new information becomes available. https://status.kiflo.com/incident/740500 Thu, 09 Oct 2025 10:16:00 -0000 https://status.kiflo.com/incident/740500#f77917172bba1d06c1571bbc488b3b72905466b8a33b776138144a36b410e16e Some customers may experience intermittent performance degradation or brief interruptions when accessing services in Europe and Africa. Our cloud provider is actively working on a resolution, and we will provide the next update within 60 minutes or sooner if new information becomes available. https://status.kiflo.com/ Tue, 26 Aug 2025 02:08:13 +0000 https://status.kiflo.com/#2abae88e647da2231d14ce7a1eab192f66dabedb9a7890caf6ce61c4e86fae5d api.kiflo.com recovered https://status.kiflo.com/ Tue, 26 Aug 2025 02:03:24 +0000 https://status.kiflo.com/#2abae88e647da2231d14ce7a1eab192f66dabedb9a7890caf6ce61c4e86fae5d api.kiflo.com went down https://status.kiflo.com/ Sun, 03 Aug 2025 17:05:54 +0000 https://status.kiflo.com/#36a457e92d79427f223bbcd05f84bfed217bec04763e1f1349741405c41e5d3f api.kiflo.com recovered https://status.kiflo.com/ Sun, 03 Aug 2025 17:00:56 +0000 https://status.kiflo.com/#36a457e92d79427f223bbcd05f84bfed217bec04763e1f1349741405c41e5d3f api.kiflo.com went down https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 20:08:00 -0000 https://status.kiflo.com/incident/406137#6293ba2482fe6cc67c079cfe0414a861f9b94ecac857745853ff27ed807db282 The services affected by the current incident have been resolved. **What do we know so far? According to our cloud provider, an unexpected usage spike caused network components to perform below acceptable thresholds, resulting in intermittent errors, timeouts, and latency spikes. The initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated their DDoS protection mechanisms. However, initial investigations suggest that an error in implementing their defenses amplified the impact of the attack rather than mitigating it. **What happens next? Our team will conduct an internal retrospective to thoroughly understand the incident and gather insights for future improvements. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 20:08:00 -0000 https://status.kiflo.com/incident/406137#6293ba2482fe6cc67c079cfe0414a861f9b94ecac857745853ff27ed807db282 The services affected by the current incident have been resolved. **What do we know so far? According to our cloud provider, an unexpected usage spike caused network components to perform below acceptable thresholds, resulting in intermittent errors, timeouts, and latency spikes. The initial trigger event was a Distributed Denial-of-Service (DDoS) attack, which activated their DDoS protection mechanisms. However, initial investigations suggest that an error in implementing their defenses amplified the impact of the attack rather than mitigating it. **What happens next? Our team will conduct an internal retrospective to thoroughly understand the incident and gather insights for future improvements. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 19:50:00 -0000 https://status.kiflo.com/incident/406137#468c0253ce9bb55df69d43e15c68e089e698655ac7a57136e08f1ef5eca1d1c9 The mitigation approach taken by our cloud provider has successfully reduced the impacts on Kiflo. We will continue to monitor this closely. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 19:50:00 -0000 https://status.kiflo.com/incident/406137#468c0253ce9bb55df69d43e15c68e089e698655ac7a57136e08f1ef5eca1d1c9 The mitigation approach taken by our cloud provider has successfully reduced the impacts on Kiflo. We will continue to monitor this closely. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 16:14:00 -0000 https://status.kiflo.com/incident/406137#0ed217daf88b41c8ee193b801218a70acf508bbc06b82335fac802bb9b261157 Our cloud provider has implemented networking configuration changes and has performed failovers to alternate networking paths to provide relief. Their monitoring telemetry shows improvement in service availability from approximately 14:10 UTC onwards, and they continue to monitor to ensure full recovery. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 16:14:00 -0000 https://status.kiflo.com/incident/406137#0ed217daf88b41c8ee193b801218a70acf508bbc06b82335fac802bb9b261157 Our cloud provider has implemented networking configuration changes and has performed failovers to alternate networking paths to provide relief. Their monitoring telemetry shows improvement in service availability from approximately 14:10 UTC onwards, and they continue to monitor to ensure full recovery. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 14:32:00 -0000 https://status.kiflo.com/incident/406137#2595719f2cd97df4c285097dae73fc7ce47e4dd975bab5640f82ddcbc1215dcc Multiple engineering teams from our cloud provider are engaged to diagnose and resolve the issue as soon as possible. They've identified multiple workstreams and are working to mitigate impacted workstreams by performing failover operations. More details will be provided as they become available. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 14:32:00 -0000 https://status.kiflo.com/incident/406137#2595719f2cd97df4c285097dae73fc7ce47e4dd975bab5640f82ddcbc1215dcc Multiple engineering teams from our cloud provider are engaged to diagnose and resolve the issue as soon as possible. They've identified multiple workstreams and are working to mitigate impacted workstreams by performing failover operations. More details will be provided as they become available. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 12:56:00 -0000 https://status.kiflo.com/incident/406137#11aba2539997e2198ff47510a7059a928b964c1bb434657c118878434645bbea Our cloud provider is experiencing issues with its network infrastructure. Kiflo services might be degraded. More details will be provided as they become available. https://status.kiflo.com/incident/406137 Tue, 30 Jul 2024 12:56:00 -0000 https://status.kiflo.com/incident/406137#11aba2539997e2198ff47510a7059a928b964c1bb434657c118878434645bbea Our cloud provider is experiencing issues with its network infrastructure. Kiflo services might be degraded. More details will be provided as they become available.