DoseSpot Outage History

DoseSpot is up right now

DoseSpot had 3 outages in the last 2 years totaling 920h 4m of downtime — averaging 0.1 incidents per month.

There were 3 DoseSpot outages since May 7, 2026 totaling 920h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dosespot.com

Minor August 6, 2026

pVerify | Payer down notification 08/06/2026

Detected by Pingoru
Aug 06, 2026, 01:30 PM UTC
Resolved
Aug 10, 2026, 05:00 PM UTC
Duration
4d 3h
Affected: pVerify Premium (pVerify Premium)pVerify API Management (pVerify API Management)pVerify Partner (pVerify Partner)pVerify API (pVerify API)
Timeline · 2 updates
  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...

  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:...

Read the full incident report →

Minor May 14, 2026

Investigating pVerify MBI Lookup Error message

Detected by Pingoru
May 14, 2026, 04:00 AM UTC
Resolved
Jun 17, 2026, 04:00 AM UTC
Duration
34d
Affected: pVerify Premium (pVerify Premium)pVerify API Management (pVerify API Management)pVerify Partner (pVerify Partner)pVerify API (pVerify API)
Timeline · 7 updates
  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...

  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: ...

  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...

  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...

  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...

  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....

  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...

Read the full incident report →

Minor May 7, 2026

Incident Notification: Case Submission via Community Site

Detected by Pingoru
May 07, 2026, 04:15 PM UTC
Resolved
May 07, 2026, 08:49 PM UTC
Duration
4h 34m
Timeline · 2 updates
  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 →