Resolved Notice - Central service WSO2- facing issues with traffic routed through WSO2

Update timeline

1. investigating Mar 07, 2026, 07:07 PM UTC

   We are facing issues with traffic routed through wso2. Any services leveraged through this will be impacted. We are actively investigating the problem and will provide updates as more information becomes available. Services impacted: WSO2 Services #INC48815572

2. identified Mar 07, 2026, 08:07 PM UTC

   We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572

3. identified Mar 07, 2026, 09:21 PM UTC

   We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. we're working with a customer facing issues on their end. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572

4. identified Mar 07, 2026, 11:35 PM UTC

   We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. we're working with a customer facing issues on their end. We will continue to monitor performance with will provide updates accordingly. Services impacted: WSO2 Services; Central Prescriber, DEA Validation, APIs #INC48815572

5. identified Mar 08, 2026, 12:39 AM UTC

   We are seeing alleviation with traffic routed through WSO2. You should now be able to search prescribers, perform DEA validation, and leverage any APIs that go through WSO2. We will continue to monitor performance and provides next update at 20:45:00 CT. #INC48815572

6. resolved Mar 08, 2026, 02:26 AM UTC

   We restarted WSO2 to clear out failed connections and monitored performance while working with customers. #INC48815572