Availity incident
Multiple Payers - BEACON HEALTH OPTIONS, MASSACHUSETTS BEHAVIORAL HEALTH PARTNERSHIP, MARYLAND PUBLIC BEHAVIORAL HEALTH SYSTEM - 270 - Eligibility and Benefits Inquiry B2B transactions are currently unavailable.
Availity experienced a notice incident on May 9, 2026 affecting BEACON HEALTH OPTIONS and MASSACHUSETTS BEHAVIORAL HEALTH PARTNERSHIP, lasting 3d 17h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 09, 2026, 04:34 AM UTC
We are seeing Eligibility and Benefits Inquiry transactions failing with timeout errors. Customers are receiving VT05_035 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.
- identified May 09, 2026, 06:22 AM UTC
We are seeing Eligibility and Benefits Inquiry transactions failing with timeout errors. Customers are receiving VT05_035 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.
- identified May 10, 2026, 10:16 PM UTC
We are seeing Eligibility and Benefits Inquiry transactions failing with timeout errors. Customers are receiving VT05_035 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.
- identified May 11, 2026, 03:36 PM UTC
We are seeing Eligibility and Benefits Inquiry transactions failing with timeout errors. Customers are receiving 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. 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.
- resolved May 12, 2026, 09:50 PM UTC
This incident has been resolved.