k-ID Outage History

k-ID is up right now

k-ID had 13 outages in the last 2 years totaling 101h 40m of downtime, averaging 0.5 incidents per month.

There were 13 k-ID outages since January 27, 2025 totaling 101h 40m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.k-id.com

Critical June 25, 2026

DNS Outage

Detected by Pingoru
Jun 25, 2026, 03:30 PM UTC
Resolved
Jun 25, 2026, 05:30 PM UTC
Duration
2h
Timeline · 1 update
  1. resolved Jun 25, 2026, 06:39 PM UTC

    A DNS outage occurred that blocked all services from being accessible. The issue was detected internally and resolved. All services are accessible.

Read the full incident report →

Major March 8, 2026

Family Connect and verifications are degraded

Detected by Pingoru
Mar 08, 2026, 02:48 AM UTC
Resolved
Mar 08, 2026, 06:46 AM UTC
Duration
3h 57m
Affected: Family Portal
Timeline · 3 updates
  1. investigating Mar 08, 2026, 02:48 AM UTC

    The Family Connect site and age verifications are down for some customers. We are investigating the issue.

  2. identified Mar 08, 2026, 03:41 AM UTC

    We have identified and cordoned the website traffic that was causing issues. Most customers should be healthy.

  3. resolved Mar 09, 2026, 06:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 7, 2026

Family Connect and verifications are unavailable

Detected by Pingoru
Mar 07, 2026, 03:23 AM UTC
Resolved
Mar 07, 2026, 05:49 AM UTC
Duration
2h 26m
Affected: Family Portal
Timeline · 4 updates
  1. investigating Mar 07, 2026, 03:23 AM UTC

    The Family Connect site and age verifications are current unavailable. We are investigating the issue.

  2. monitoring Mar 07, 2026, 04:08 AM UTC

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

  3. monitoring Mar 07, 2026, 04:22 AM UTC

    Family Connect and Verifications continue to appear healthy. We continue to monitor the system.

  4. resolved Mar 07, 2026, 05:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 19, 2026

Unable to log in to Compliance Studio

Detected by Pingoru
Feb 19, 2026, 04:58 PM UTC
Resolved
Feb 19, 2026, 06:53 PM UTC
Duration
1h 55m
Affected: Compliance Studio
Timeline · 4 updates
  1. investigating Feb 19, 2026, 04:58 PM UTC

    The external service we use for logging into Compliance Studio is experiencing an incident. This is affecting the ability to login to compliance studio. If already logged in, everything is working normally.

  2. identified Feb 19, 2026, 05:31 PM UTC

    The issue is from the service we use for managing sessions in Compliance Studio. They've shipped some fixes, so login is working better. Although they're not seeing full recovery yet. We're continuing to monitor.

  3. monitoring Feb 19, 2026, 06:38 PM UTC

    The upstream service has resolved the issue on their end. We're monitoring to make sure they stay stable.

  4. resolved Feb 19, 2026, 06:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

Email delivery to Microsoft domains are being blocked

Detected by Pingoru
Jan 29, 2026, 03:29 AM UTC
Resolved
Jan 29, 2026, 09:37 PM UTC
Duration
18h 8m
Affected: Family Portal
Timeline · 4 updates
  1. identified Jan 29, 2026, 03:29 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 29, 2026, 03:46 AM UTC

    Our email provider is having issues across all their customers. We are monitoring.

  3. monitoring Jan 29, 2026, 05:10 PM UTC

    We are seeing emails via our provider to Microsoft domains are being delivered. We will continue to monitor.

  4. resolved Jan 29, 2026, 09:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 9, 2025

Family Portal Outage/Degradation

Detected by Pingoru
Dec 09, 2025, 05:00 AM UTC
Resolved
Dec 10, 2025, 05:45 PM UTC
Duration
1d 12h
Affected: Family Portal
Timeline · 6 updates
  1. investigating Dec 09, 2025, 07:55 AM UTC

    We are currently investigating the issue. We are aware this affects verification requests.

  2. investigating Dec 09, 2025, 09:38 AM UTC

    Mitigating the issue for the majority of customers.

  3. investigating Dec 09, 2025, 09:38 AM UTC

    We are continuing to investigate this issue and identifying long term fix.

  4. identified Dec 09, 2025, 06:11 PM UTC

    Long term fix identified and a fix is being implemented. Mitigations are working and system has been stable for all customers.

  5. monitoring Dec 09, 2025, 09:38 PM UTC

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

  6. resolved Dec 10, 2025, 05:45 PM UTC

    The incident was resolved at Tuesday Dec 9, 9:30 UTC. We also successfully deployed the long term fix, and the monitoring shows that it is working as expected. Total impact duration was 4.5 hours.

Read the full incident report →

Major November 19, 2025

ID Scan Vendor Partial Outage

Detected by Pingoru
Nov 19, 2025, 05:38 AM UTC
Resolved
Nov 19, 2025, 07:55 AM UTC
Duration
2h 17m
Affected: Family Portal
Timeline · 3 updates
  1. investigating Nov 19, 2025, 05:38 AM UTC

    We are currently investigating this issue.

  2. investigating Nov 19, 2025, 08:20 AM UTC

    We are continuing to investigate this issue.

  3. resolved Nov 19, 2025, 08:23 AM UTC

    Our vendor has resolved a licensing issue and all systems are operational again.

Read the full incident report →

Major November 4, 2025

ID Scan Verification Intermittent Outage

Detected by Pingoru
Nov 04, 2025, 06:41 PM UTC
Resolved
Nov 04, 2025, 06:55 PM UTC
Duration
13m
Affected: Family Portal
Timeline · 4 updates
  1. investigating Nov 04, 2025, 06:41 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 04, 2025, 06:47 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 04, 2025, 06:47 PM UTC

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

  4. resolved Nov 04, 2025, 06:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 22, 2025

Face scan verification not working on some devices

Detected by Pingoru
Sep 22, 2025, 06:41 PM UTC
Resolved
Sep 22, 2025, 10:35 PM UTC
Duration
3h 53m
Affected: Family Portal
Timeline · 6 updates
  1. investigating Sep 22, 2025, 07:59 PM UTC

    We are currently investigating the issue.

  2. investigating Sep 22, 2025, 08:02 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 22, 2025, 09:10 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Sep 22, 2025, 09:11 PM UTC

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

  5. resolved Sep 22, 2025, 10:10 PM UTC

    This incident has been resolved.

  6. postmortem Sep 22, 2025, 10:23 PM UTC

    A 3rd-party vendor deployed a change to their staging environment for testing, which unexpectedly also affected their production environment and caused errors. * This resulted in users not being able to complete face scan verification during the incident. * Once identified, the change was reverted, resolving the issue.

Read the full incident report →

Major June 25, 2025

Credit Card verification failure on Trusted Adult Verification API

Detected by Pingoru
Jun 25, 2025, 11:30 PM UTC
Resolved
Jun 26, 2025, 03:47 PM UTC
Duration
16h 17m
Affected: Family Portal
Timeline · 4 updates
  1. investigating Jun 26, 2025, 02:53 PM UTC

    We are currently investigating this issue.

  2. identified Jun 26, 2025, 02:53 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 26, 2025, 03:36 PM UTC

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

  4. resolved Jun 26, 2025, 03:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2025

Age verification degraded

Detected by Pingoru
Jun 12, 2025, 06:40 PM UTC
Resolved
Jun 13, 2025, 12:26 AM UTC
Duration
5h 45m
Affected: Family Portal
Timeline · 5 updates
  1. identified Jun 12, 2025, 06:40 PM UTC

    Some age verification methods (document scan and personal details) are not working due to an ongoing Cloudflare incident (https://www.cloudflarestatus.com/)

  2. identified Jun 12, 2025, 07:23 PM UTC

    Cloudflare has identified the issue and is working on a recovery.

  3. monitoring Jun 12, 2025, 07:52 PM UTC

    We are continuing to wait for services to recover.

  4. monitoring Jun 12, 2025, 08:24 PM UTC

    We are seeing a recovery in the verification methods and will continue to monitor the status.

  5. resolved Jun 13, 2025, 12:26 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 26, 2025

ID Scan errors

Detected by Pingoru
Feb 26, 2025, 03:14 PM UTC
Resolved
Feb 26, 2025, 10:53 PM UTC
Duration
7h 38m
Affected: Family Portal
Timeline · 5 updates
  1. identified Feb 26, 2025, 08:09 PM UTC

    The ID Scan verification method is producing errors. End-users will need to select an alternative verification method.

  2. identified Feb 26, 2025, 08:10 PM UTC

    We have an identified an issue with our ID Scan verification method, which began erroring at 15:14 UTC. Other jurisdiction appropriate verification methods are still operational. We are working with a vendor to resolve the issue.

  3. monitoring Feb 26, 2025, 08:59 PM UTC

    A fix has been implemented and we are monitoring the results. ID verification method is working.

  4. resolved Feb 26, 2025, 10:53 PM UTC

    This incident has been resolved.

  5. postmortem Mar 04, 2025, 06:16 PM UTC

    ## Summary Two age verification methods \(ID scan and personal details\) were causing errors for a period of time, and for this time users were required to choose an alternate verification method. The root cause was a misconfiguration within one of our vendors. | **Impact** | **High** | | --- | --- | | Impact duration | 5h 43m | | Time to detect | 3h 46m | | Time to resolve | 1h 57 m | ‌ ## Remediations * The vendor has implemented improved blackbox monitoring in order to detect these outages faster. * k-ID has worked with the vendor to establish improved communication during incidents. * k-ID has implemented a mechanism for disabling verification methods that are known to be experiencing issues. * k-ID will implement monitoring and alerting on verification errors in order to improve our own time to detection.

Read the full incident report →

Critical January 27, 2025

Certificate Expired

Detected by Pingoru
Jan 27, 2025, 08:16 PM UTC
Resolved
Jan 27, 2025, 08:38 PM UTC
Duration
21m
Affected: Product APIFamily PortalCompliance Studio
Timeline · 5 updates
  1. identified Jan 27, 2025, 08:16 PM UTC

    The API is degraded due to an expired certificate. Team is replacing the certificate.

  2. monitoring Jan 27, 2025, 08:28 PM UTC

    The expired certificate has been replaced and is being deployed. We expect resolution within the next ten minutes. Also, we identified that the same certificate issue impacts Family Portal and Publisher Portal; the severity of impact has been updated to reflect this.

  3. monitoring Jan 27, 2025, 08:35 PM UTC

    Certificate deployment has completed for all components.

  4. resolved Jan 27, 2025, 08:38 PM UTC

    Traffic flow has returned to normal levels following the replacement of the certificate.

  5. postmortem Jan 28, 2025, 02:48 AM UTC

    Production SSL certificate expired due to an IAM permissions misconfiguration that prevented cert-manager from creating DNS records to verify our domain ownership. * Root cause was a syntax error in the IAM policy that was previously unknown to our product teams. The rule was updated manually with the correct syntax during the incident and has since been rectified in our infrastructure configuration. * We have added an alert for certificates two weeks prior to expiration. This will allow engineers to verify that automated certificate rotations are successful and intervene manually if required before the certificate expires. | **Impact** | **High** | | --- | --- | | Impact duration | 27m | | Time to detect | 2m | | Time to resolve | 25m |

Read the full incident report →