Outage in Vetspire

SEV-2 Client/Patient/Chart Configuration

Resolved Minor
March 11, 2025 - Started about 2 months ago - Lasted 6 days
Official incident page

Need to monitor Vetspire outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Vetspire, and never miss an outage again.
Start Free Trial

Outage Details

We're all looking into a possible issue with Client/Patient/Chart Configuration
Components affected
Vetspire Web UI
Latest Updates ( sorted recent to last )
RESOLVED about 1 month ago - at 03/17/2025 04:45PM

We’re happy to share that the issue has now been fully resolved. After thorough testing and validation, all affected organizations have been successfully processed and are back to normal operations.

We sincerely appreciate your patience and understanding throughout this process. Our team recognizes how disruptive these situations can be and remains committed to continuously improving system stability and response times.

Thank you again for your trust and partnership. If you experience any lingering issues or have further questions, please don’t hesitate to reach out to our support team.

MONITORING about 2 months ago - at 03/15/2025 09:11PM

We have successfully identified the issue and are actively implementing a fix. Client, patient, and chart configurations have been validated, and the issue has been resolved for several organizations. We are monitoring the results and will continue addressing additional organizations over the weekend, with any remaining cases resolved at the beginning of the week.

MONITORING about 2 months ago - at 03/15/2025 06:29PM

We have successfully identified the issue and have started to implement a fix. We have validated client/patient/chart configurations and have resolved the issue for several organizations and are monitoring the results. We will continue to resolve more organizations over the weekend, and any remaining will be resolved at the beginning of the week.

MONITORING about 2 months ago - at 03/15/2025 05:15PM

We have successfully identified the issue and have started to implement a fix. We have validated client/patient/chart configurations and have resolved the issue for several organizations and are monitoring the results. We will continue to resolve more organizations over the weekend, and any remaining will be resolved at the beginning of the week.

MONITORING about 2 months ago - at 03/14/2025 09:31PM

We have successfully identified the issue and have started to implement a fix. We have validated client/patient/chart configurations and have resolved the issue for several organizations and are monitoring the results. We will continue to resolve more organizations over the weekend, and any remaining will be resolved at the beginning of the week.

MONITORING about 2 months ago - at 03/14/2025 08:22PM

A fix has been implemented and we are monitoring the results.

IDENTIFIED about 2 months ago - at 03/14/2025 11:47AM

We appreciate your patience as our development team works to resolve this issue. The team is actively finalizing the restoration for affected organizations this morning.

We will continue to provide updates as progress is made and share more information as soon as it becomes available. Thank you for your understanding!

IDENTIFIED about 2 months ago - at 03/14/2025 12:52AM

We appreciate your patience as we continue working through the final steps of this process. Our team is still running tests on the script with larger datasets to confirm that everything functions as expected. This is the last piece we need to validate before proceeding with processing the remaining organizations tomorrow morning GMT.

We’ll continue providing updates as we progress and will share more information as soon as we have it. Thank you again for your understanding!

IDENTIFIED about 2 months ago - at 03/13/2025 10:01PM

We appreciate your patience as we continue working through the final steps of this process. Our team is still running tests on the script with larger datasets to confirm that everything functions as expected. This is the last piece we need to validate before proceeding with processing the remaining organizations tomorrow morning GMT.

We’ll continue providing updates as we progress and will share more information as soon as we have it. Thanks again for your understanding!

IDENTIFIED about 2 months ago - at 03/13/2025 07:28PM

We appreciate your patience as we continue working through the final steps of this process. Our team is still running tests on the script with larger datasets to confirm everything functions as expected. This is the last piece we need to validate before proceeding with processing the remaining orgs tomorrow morning GMT.

We’ll continue providing updates as we progress and will share more information as soon as we have it. Thanks again for your understanding!

IDENTIFIED about 2 months ago - at 03/13/2025 06:17PM

We understand how important this is and appreciate your patience while we continue working through the resolution process. Our team is actively testing the script against larger datasets, ensuring everything runs smoothly before moving forward. Since this is the last variable we need to account for, if all goes well, we expect to process the remaining orgs tomorrow morning GMT.

We’ll keep you posted with further updates as we make progress. Thanks again for bearing with us!

IDENTIFIED about 2 months ago - at 03/13/2025 04:16PM

We are continuing to work through the resolution process for the affected organizations. The team is currently testing the resolution against larger datasets, as this is the final remaining unknown that needs to be accounted for. If all looks good, we will proceed with processing the remainder of the orgs tomorrow morning GMT. Our team remains actively engaged in resolving this issue as efficiently as possible, and further updates will be provided as progress continues.

IDENTIFIED about 2 months ago - at 03/13/2025 02:02PM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience and we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/13/2025 12:41PM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience and we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/13/2025 11:10AM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience and we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/13/2025 01:55AM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience and will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/13/2025 01:00AM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience and we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/13/2025 12:02AM

The issue has been identified, and we are continuing to work towards a resolution. We appreciate your patience—we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/12/2025 10:42PM

The issue has been identified, and we are continuing to work towards a resolution. Thank you for your patience—we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/12/2025 09:38PM

We are continuing to work towards a resolution. Thank you for your patience—we will provide updates as soon as more information is available.

IDENTIFIED about 2 months ago - at 03/12/2025 08:37PM

We are continuing to work towards a resolution. Thank you for your patience—we will provide updates as soon as possible.

IDENTIFIED about 2 months ago - at 03/12/2025 02:32PM

The data issues has been identified in the encounter sections. The Development team is actively working on the next steps to rewrite the affected encounters with the correct data.

IDENTIFIED about 2 months ago - at 03/11/2025 07:05PM

It appears that this issue is affecting a very small portion of Vetspire users and we're working on a solution

INVESTIGATING about 2 months ago - at 03/11/2025 07:04PM

We're all looking into a possible issue with Client/Patient/Chart Configuration

Be the first to know when Vetspire and other third-party services go down

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 3969 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook