Availity incident

Multiple Payers - CAREFIRST BLUECROSS BLUESHIELD, 45282, RIVERSIDE HEALTH MARYLAND, CAREFIRST MEDICARE ADVANTAGE, CAREFIRSTBCBS, BCDCC - Multiple Transactions - We have been notified by the payer CareFirst of a system issue which is affecting their abi...

Notice Resolved View vendor source →

Availity experienced a notice incident on July 4, 2026 affecting CAREFIRST BLUECROSS BLUESHIELD and 45282 and 1 more component, lasting 6d 13h. The incident has been resolved; the full update timeline is below.

Started
Jul 04, 2026, 04:56 AM UTC
Resolved
Jul 10, 2026, 06:27 PM UTC
Duration
6d 13h
Detected by Pingoru
Jul 04, 2026, 04:56 AM UTC

Affected components

CAREFIRST BLUECROSS BLUESHIELD45282RIVERSIDE HEALTH MARYLANDCAREFIRST MEDICARE ADVANTAGECAREFIRSTBCBSBCDCC

Update timeline

  1. identified Jul 04, 2026, 04:56 AM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with AAA*42/Timeout/Invalid Response errors. Customers are receiving AAA*42/AV01/VT05_035 errors. Next Steps and ETA for resolution: We have reached out to the payer to report this issue. We will continue to monitor and send updates as available. Availity continues to monitor for resolution.

  2. identified Jul 07, 2026, 09:50 AM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with AAA*42/Timeout/Invalid Response errors. Customers are receiving AAA*42/AV01/VT05_035 errors. Next Steps and ETA for resolution: We have reached out to the payer to report this issue. We will continue to monitor and send updates as available. Availity continues to monitor for resolution.

  3. identified Jul 07, 2026, 10:54 AM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with AAA*42/timeout/timeout errors. Customers are receiving AAA*42/AV01/VT05_035 errors. Next Steps and ETA for resolution: We have reached out to the payer to report this issue. We will continue to monitor and send updates as available. Availity continues to monitor for resolution.

  4. resolved Jul 10, 2026, 06:27 PM UTC

    This incident has been resolved.