CARFAX CA incident

Alberta Liens Unavailable

Major Resolved View vendor source →

CARFAX CA experienced a major incident on January 14, 2026 affecting Alberta Liens and Liens and 1 more component, lasting 21h 9m. The incident has been resolved; the full update timeline is below.

Started
Jan 14, 2026, 10:57 PM UTC
Resolved
Jan 15, 2026, 08:07 PM UTC
Duration
21h 9m
Detected by Pingoru
Jan 14, 2026, 10:57 PM UTC

Affected components

Alberta LiensLiensReport CompletionLien Completion

Update timeline

  1. identified Jan 14, 2026, 10:57 PM UTC

    Severity 2 - We have identified an issue with one of our providers and we are awaiting a fix. Vehicle History Reports are available, but reports run through any CARFAX Canada product or website containing Alberta lien data will be pending.

  2. identified Jan 15, 2026, 02:35 AM UTC

    Severity 2 - We have identified an issue with one of our providers and we are awaiting a fix. Vehicle History Reports are available, but reports run through any CARFAX Canada product or website containing Alberta lien data will be pending.

  3. investigating Jan 15, 2026, 01:44 PM UTC

    Severity 2 - We have identified an issue with one of our providers and are working on a fix. Vehicle History Reports are available, but reports run through any CARFAX Canada product or website containing Alberta lien data will be pending.

  4. investigating Jan 15, 2026, 02:33 PM UTC

    Severity 2 - We are currently investigation this issue. Vehicle History Reports are available, but reports run through any CARFAX Canada product or website containing Alberta lien data will be pending.

  5. identified Jan 15, 2026, 04:03 PM UTC

    Severity 2 - We have identified the issue and are working towards a fix. Vehicle History Reports are available, but reports run through any CARFAX Canada product or website containing Alberta lien data will be pending.

  6. monitoring Jan 15, 2026, 06:37 PM UTC

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

  7. resolved Jan 15, 2026, 08:07 PM UTC

    This incident has been resolved.