Tebra incident

ERA Processing Recovery

Critical Resolved View vendor source →

Tebra experienced a critical incident on July 22, 2026 affecting Billing (PM), lasting 6d 20h. The incident has been resolved; the full update timeline is below.

Started
Jul 22, 2026, 06:18 PM UTC
Resolved
Jul 29, 2026, 03:03 PM UTC
Duration
6d 20h
Detected by Pingoru
Jul 22, 2026, 06:18 PM UTC

Affected components

Billing (PM)

Update timeline

  1. monitoring Jul 22, 2026, 06:18 PM UTC

    TriZetto experienced an issue over the weekend that delayed delivery of ERAs to Tebra. TriZetto has implemented updates to address the issue, and our teams are actively partnering to process the remaining delayed records. ERA processing is expected to return to normal within 2–3 business days, and recovery efforts are underway. Due to the volume of delayed ERAs, it will take additional time for all remaining records to be fully processed and delivered. We appreciate your patience and understanding as we continue working with TriZetto to complete recovery.

  2. monitoring Jul 28, 2026, 03:35 PM UTC

    The recent ERA processing delays affecting remittances dated July 18 through July 22 have been resolved. Most impacted ERAs have now been successfully delivered to your account. A small volume of ERAs from this period may still require manual retrieval. If you have already submitted a support case for missing remittances, our team is currently reviewing those inquiries to identify and address any remaining exceptions as quickly as possible. If you find that an ERA from the July 18–July 22 timeframe is still missing and you have not yet contacted us, please submit a case through our standard support channels for further investigation. For any missing ERAs dated outside of this specific incident, please continue to follow our standard reporting procedures to ensure a prompt review. We appreciate your patience as we worked with our clearinghouse partner to restore service and resolve these processing delays.

  3. resolved Jul 29, 2026, 03:03 PM UTC

    This incident has been resolved.