Previous incidents

We are currently aware of an issue with DoseSpot’s Azure environment that may temporarily affect our ability to send prescriptions to partner pharmacies. This may result in delayed processing within the prescription queue.

All other systems and services remain operational and are not impacted by this issue. We are monitoring the situation closely and will provide updates as they become available.

Our hyperscale platform provider has confirmed that the regional network event impacting some systems in the US-East region has been fully resolved. Between late last night and this afternoon, the provider experienced increased error rates and network latency that affected multiple dependent services across their environment.

While MD Integrations’ infrastructure is not hosted in the impacted region, several upstream dependencies were indirectly affected, which may have caused temporary late...

We implemented a fix for the pharmacy submission issue and are now reprocessing affected prescriptions that are pending in the Processing folder.

Service should be fully operational again.

Our team is currently investigating two issues related to prescriptions:
1. Issues approving certain types of prescriptions, primarily service PDFs;
2. Slow processing queue;

We are currently investigating an issue that caused a few of our endpoints to respond with 500 status codes. Service has been restored but we are still investigating the root cause.

The root cause was identified as a missing restart after setting a server key, causing our AWS instance to restart on its own which in turns cause services not to properly initiate.

We’ve identified a problem with our WAF provider that’s temporarily blocking some customers, resulting in a 403 status code message. We’re collaborating closely with the service provider to pinpoint the root cause and resolve the issue promptly.