Previous incidents

We received reports that some of our endpoints are timing out, which may have caused alerts being sent from our Status Page. We're currently investigating this issue.

After further investigation, it seems like the timeouts were related to a minor network instability and affected only a small subset of partners. We will keep monitoring the situation.

We are investigating an issue with the processing queue being stuck and failing to be processed by Dosespot.

From our preliminary investigation we detected that Dosespot is not sending us webhooks for processed encounters. We are running an endpoint manually to check prescription status so encounters are moved forward. We have also opened a ticket with Dosespot to hotfix it.

Dosespot issued a hotfix to address this issue. Cases in processing should now be moved to Completed auto...

We identified some of the prescriptions submitted today are failing to due to a Dosespot/Surescripts error. We are monitoring the queue and have a ticket open with Dosespot so they can fix this issue as soon as possible. We will be resubmitting any encounters with errors automatically once the issue is resolved.

The issue seems to be resolved. Resubmitting prescriptions should make them go through the pharmacy successfully.

We just introduced a few new monitors for server health. Please bare with us as these might generate false positive notifications. We'll be monitoring them for the next few days to make sure they work properly.

Some of our customers are currently experiencing a degradation of service. Our team is currently investigating the cause. Early findings suggest an issue with our application framework failing to close idle connections which leads to a lock on our database.

We identified an issue with idle connections not closing properly. We've issued a fix to automatically close those and we'll be monitoring database availability throughout the day to ensure stability.

We just deployed a new f...

As we publish new changes to our platform, we identified an issue that degraded our database performance unexpectedly. Our team is investigating the issue and it should be resolved in the next few minutes.

We resolved the deadlock affecting our release and changes are now live. Service has been restored successfully.