CARFAX CA incident

All Canadian registration records are temporarily offline

Major Resolved View vendor source →

CARFAX CA experienced a major incident on February 15, 2026 affecting Alberta Registration and Registration and 1 more component, lasting 3h 8m. The incident has been resolved; the full update timeline is below.

Started
Feb 15, 2026, 07:40 AM UTC
Resolved
Feb 15, 2026, 10:48 AM UTC
Duration
3h 8m
Detected by Pingoru
Feb 15, 2026, 07:40 AM UTC

Affected components

Alberta RegistrationRegistrationBritish Columbia RegistrationManitoba RegistrationNew Brunswick RegistrationReport CompletionReport CompletionNewfoundland RegistrationNorthwest Territories RegistrationNova Scotia Registration

Update timeline

  1. identified Feb 15, 2026, 07:40 AM UTC

    Severity 1 - 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 provincial registration data will be pending.

  2. identified Feb 15, 2026, 08:42 AM UTC

    Severity 1 - 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 provincial registration data will be pending.

  3. identified Feb 15, 2026, 09:14 AM UTC

    Severity 1 - 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 provincial registration data will be pending.

  4. identified Feb 15, 2026, 10:10 AM UTC

    Severity 1 - 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 provincial registration data will be pending.

  5. monitoring Feb 15, 2026, 10:34 AM UTC

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

  6. resolved Feb 15, 2026, 10:48 AM UTC

    This incident has been resolved.