Kikoff Outage History

Kikoff is up right now

Kikoff had 3 outages in the last 2 years totaling 2h 17m of downtime — averaging 0.1 incidents per month.

There were 3 Kikoff outages since August 7, 2024 totaling 2h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kikoff.com

Critical April 23, 2025

Email outage blocking emails including confirmation emails

Detected by Pingoru
Apr 23, 2025, 10:00 PM UTC
Resolved
Apr 23, 2025, 10:08 PM UTC
Duration
8m
Affected: Web AppMobile App
Timeline · 4 updates
  1. investigating Apr 23, 2025, 10:00 PM UTC

    Our email provider is down and all emails including confirmation emails cannot be sent. We will update this page as we get new information.

  2. investigating Apr 23, 2025, 10:04 PM UTC

    We are beginning to see emails reaching customers. We will continue to monitor.

  3. investigating Apr 23, 2025, 10:05 PM UTC

    We are continuing to investigate this issue.

  4. resolved Apr 23, 2025, 10:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 27, 2024

Service Disruption

Detected by Pingoru
Nov 27, 2024, 10:51 PM UTC
Resolved
Nov 27, 2024, 10:53 PM UTC
Duration
2m
Affected: Web AppMobile App
Timeline · 3 updates
  1. investigating Nov 27, 2024, 10:51 PM UTC

    We are seeing intermittent issues when logging in. We are investigating.

  2. investigating Nov 27, 2024, 10:53 PM UTC

    The issue has been resolved.

  3. resolved Nov 27, 2024, 10:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 30, 2024

Mobile app unavailable

Detected by Pingoru
Aug 30, 2024, 03:53 AM UTC
Resolved
Aug 30, 2024, 05:59 AM UTC
Duration
2h 6m
Affected: Mobile App
Timeline · 2 updates
  1. identified Aug 30, 2024, 03:53 AM UTC

    The issue has been identified and a fix is being implemented. The website is available while the fix is being deployed.

  2. resolved Aug 30, 2024, 05:59 AM UTC

    This incident has been resolved.

Read the full incident report →