Availity incident

Multiple Payers - BCBS SOUTH CAROLINA, BCBS South Carolina, BCBS SOUTH CAROLINA FEDERAL EMPLOYEE PROGRAM, BCBS SOUTH CAROLINA - Multiple Transactions - Eligibility and Benefits Inquiry and Claim Status Inquiry transactions are currently unavailable.

Notice Resolved View vendor source →

Availity experienced a notice incident on June 11, 2026 affecting BCBS SOUTH CAROLINA and BCBS South Carolina and 1 more component, lasting 8d 17h. The incident has been resolved; the full update timeline is below.

Started
Jun 11, 2026, 09:26 AM UTC
Resolved
Jun 20, 2026, 02:33 AM UTC
Duration
8d 17h
Detected by Pingoru
Jun 11, 2026, 09:26 AM UTC

Affected components

BCBS SOUTH CAROLINABCBS South CarolinaBCBS SOUTH CAROLINA FEDERAL EMPLOYEE PROGRAM

Update timeline

  1. identified Jun 11, 2026, 09:26 AM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with Timeout/Invalid Response errors. Customers are receiving timeout/timeout errors. Next Steps and ETA for resolution: There is no after hours support for this payer. We will continue to monitor and send updates as available. Availity continues to monitor for resolution.

  2. identified Jun 11, 2026, 05:52 PM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with timeout/timeout errors. Customers are receiving Timeout/Invalid Response 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 Jun 12, 2026, 01:09 PM UTC

    We are seeing Eligibility and Benefits Inquiry and Claim Status Inquiry transactions failing with timeout/timeout errors. Customers are receiving Timeout/Invalid Response 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 Jun 20, 2026, 02:33 AM UTC

    This incident has been resolved.