DoseSpot Outage History

Started Oct 22, 2026, 05:32 PM UTC· resolved Oct 22, 2026, 05:32 PM UTC

1. resolved Oct 22, 2026, 05:32 PM UTC

   Status: Resolved. No action required. On October 21, 2026, the PHP project released fixes for two critical security vulnerabilities in PHP, a programming language widely used on websites. These flaws could allow an attacker to run unauthorized code on an affected web server without logging in. We reviewed our hosted cloud environments and code and did not identify any affected software. Our website provider has also confirmed that our marketing sites have been patched. We are continuing to monitor our third-party providers for any reported impact. If our assessment changes, we will update this page

Read the full incident report →

Started Aug 06, 2026, 01:30 PM UTC· resolved Aug 10, 2026, 05:00 PM UTC

1. identified Aug 06, 2026, 01:30 PM UTC

   We are writing to notify you that we are observing unusualy high connection errors for Blue Plans EDI transactions. Incident Summary Since August 5, 2026, late business hours , we have observed a high volume of "Unable to Respond" (AAA03) errors on Blue Plans transactions. The issue is intermittent, and error rates have not shown a consistent pattern. Current Status Our systems are designed to automatically reroute transactions through redundant connection paths when error rates are high on a given route. If this does not resolve the issue then this behavior points to the issue originating on the payer side. We are actively monitoring transaction volumes and error rates, and are reaching out the affected payers and trading partners. Action Needed No action is needed on your end at this time. Rejected transactions due to connection errors are not billed to customers. Next Update We will provide an update as soon as we hear back from the payers, or once the issue is resolved. You can monitor the payer failure percentages at this link - https://apimgmt.pverify.com/Home/PayerStatusStatistics Please contact payer for any additional information on resolution.

2. resolved Aug 10, 2026, 05:00 PM UTC

   Incident Summary Since August 5, 2026, late business hours , we have observed a high volume of "Unable to Respond" (AAA03) errors on Blue Plans transactions. The issue is intermittent, and error rates have not shown a consistent pattern. Current status: The spike is error rates for Blue plans has been resolved. No reports on the root cause from the payer and is back to usual tranasction success rates. Thank you for your patience - You can monitor the payer failure percentages at this link - https://apimgmt.pverify.com/Home/PayerStatusStatistics

Read the full incident report →

Started May 14, 2026, 04:00 AM UTC· resolved Jun 17, 2026, 04:00 AM UTC

1. investigating May 14, 2026, 04:00 AM UTC

   We want to make you aware that we are currently experiencing an unusual spike in MBI lookup failures returning “Error Reason: No MBI Found Follow-up Action: Please Correct and Resubmit.” Our team is actively investigating the issue and working with downstream partners. This is being treated as a high priority, and any impacted transactions will be reprocessed promptly once resolved. We will provide another update as soon as more information becomes available. Thank you for your patience and understanding. In the meantime, if you are using our ID/MBI services, please confirm your NPI has been attested to both Unique IDs (FinThrive and Inovalon). Additional information can be found here: https://go.dosespot.com/provider-attestation-action-required-for-cms-compliance

2. investigating May 15, 2026, 03:54 PM UTC

   We are writing to provide you with an update regarding the software incident that began on 5/14/2026. Our team has been actively working to address the issue and ensure that services are restored as quickly as possible. Incident Details: Issue: We want to make you aware that we are currently experiencing an unusual spike in MBI lookup failures returning "Error Reason: No MBI Found Follow-up Action: Please Correct and Resubmit." This is also impacting Insurance Discovery success rates for scenarios where MBI is not available. Affected Services: pVerify MBI Lookup Current Status: Our team is actively investigating the root cause and working to get a resolution as soon as possible. We will provide another update as soon as more information becomes available. Please check our status page for updates. In the meantime, please wait for further guidance from our team. Thank you for your patience and understanding. In the meantime, we encourage you to complete CMS NPI attestation as per instructions found here: https://go.dosespot.com/provider-attestation-action-required-for-cms-compliance Thank you for your understanding. Best regards, DoseSpot

3. investigating May 15, 2026, 09:17 PM UTC

   May 18, 2026, 12:43 PM Investigating We are writing to provide you with an update regarding the 3rd-party software incident that began on 5/14/2026. Our team has been actively working with the 3rd-party partner to address the issue. Incident Details: We have identified that the issue is due to the 3rd party's service being down. We are awaiting an update about service being restored. We continue to experience an unusual spike in MBI lookup failures returning: “Error Reason: No MBI Found. Follow-up Action: Please Correct and Resubmit.” In addition, clients may receive incomplete Insurance Discovery results when an MBI is unavailable. Affected Services: pVerify MBI Lookup Current Status: The 3rd-party partner has communicated that an update will be provided Wednesday, May 20. In the meantime, we are pursuing all avenues for resolution as quickly as possible. Please continue to monitor our status page for updates. In the meantime, we encourage providers to complete CMS NPI attestation using the instructions found here: https://go.dosespot.com/provider-attestation-action-required-for-cms-compliance We apologize for the inconvenience this may be causing and appreciate your patience as we work to resolve the issue. Your experience is our top priority, and we are committed to keeping you informed throughout this process. If you have any questions or concerns, please create a case through our community site or contact us at [email protected] Thank you for your understanding. Best regards, The pVerify Team

4. investigating May 20, 2026, 04:00 AM UTC

   We are writing to provide you with an update regarding the 3rd-party software incident that began on 5/14/2026. Our team has been actively working with the 3rd-party partner to address the issue. Incident Details: We have identified that the issue is due to the 3rd party's service being down. We are awaiting an update about service being restored. We continue to experience an unusual spike in MBI lookup failures returning: “Error Reason: No MBI Found. Follow-up Action: Please Correct and Resubmit.” In addition, clients may receive incomplete Insurance Discovery results when an MBI is unavailable. Affected Services: pVerify MBI Lookup In the meantime, we are pursuing all avenues for resolution as quickly as possible. Please continue to monitor our status page for updates. In the meantime, we encourage providers to complete CMS NPI attestation using the instructions found here: https://go.dosespot.com/provider-attestation-action-required-for-cms-compliance We apologize for the inconvenience this may be causing and appreciate your patience as we work to resolve the issue. Your experience is our top priority, and we are committed to keeping you informed throughout this process. If you have any questions or concerns, please create a case through our community site or contact us at [email protected] Thank you for your understanding. Best regards, The pVerify Team

5. investigating May 29, 2026, 04:00 AM UTC

   We continue to work toward resolution for the ongoing third-party software incident that began on May 14, 2026. Incident Details: We have identified that the issue is due to the 3rd party's service being down. We are awaiting an update about service being restored. We continue to experience an unusual spike in MBI lookup failures returning: “Error Reason: No MBI Found. Follow-up Action: Please Correct and Resubmit.” In addition, clients may receive incomplete Insurance Discovery results when an MBI is unavailable. Affected Services: pVerify MBI Lookup In the meantime, we are pursuing all avenues for resolution as quickly as possible. Please continue to monitor our status page for updates. In the meantime, we encourage providers to complete CMS NPI attestation using the instructions found here: https://go.dosespot.com/provider-attestation-action-required-for-cms-compliance We apologize for the inconvenience this may be causing and appreciate your patience as we work to resolve the issue. Your experience is our top priority, and we are committed to keeping you informed throughout this process. If you have any questions or concerns, please create a case through our community site or contact us at [email protected] Thank you for your understanding. Best regards, The pVerify Team

6. investigating Jun 15, 2026, 01:18 PM UTC

   We continue to work toward resolution for the ongoing third-party software incident that began on May 14, 2026. Current Status: We are seeing improvements with the restoration of pVerify’s MBI Lookup and have been notified by our third-party processor that a fix is underway. You should see gradual improvements to your MBI Lookup service. We continue to monitor the success rates of MBI lookup transactions and will immediately escalate any errors to our third-party provider. If you are experiencing a specific issue or continued loss of service, please create a case through our community site or contact us at [email protected]. We apologize for the inconvenience this may be causing and appreciate your patience as we continue to resolve this issue. Your experience is our top priority, and we are committed to keeping you informed throughout this process. Thank you for your understanding. Best regards, The pVerify Team

7. resolved Jun 17, 2026, 04:00 AM UTC

   We are pleased to share that the ongoing third-party software incident impacting MBI Lookup that began on May 14, 2026 has been fully resolved. Current Status: Our third-party processor has notified us that pVerify's MBI Lookup service is fully restored. You should now be able to use MBI Lookup as normal. We continue to monitor the success rates of MBI Lookup transactions and will immediately escalate any discrepancies to our third-party provider. If you are experiencing a specific issue or continued loss of service, please create a case through our community site or contact us at [email protected]. Your experience is our top priority, and we are committed to keeping you informed. Thank you for your understanding and apologize for the inconvenience. Best regards, The pVerify Team

Read the full incident report →

Started May 07, 2026, 04:15 PM UTC· resolved May 07, 2026, 08:49 PM UTC

1. identified May 07, 2026, 04:15 PM UTC

   We are aware of an issue currently affecting case submissions, and our team is actively working to identify and resolve the problem. We apologize for the inconvenience and appreciate your patience. For any urgent needs, please contact Phone Support for immediate assistance. Thank you

2. resolved May 07, 2026, 08:49 PM UTC

   The issue affecting case submissions has been resolved, and submissions should now be functioning as expected. We appreciate your patience while our team worked to identify and resolve the issue. Thank you

Read the full incident report →