MASV Outage History
MASV is up right nowPingoru has recorded 6 incidents for MASV: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 516 (0%) |
Incidents, newest first
Major November 18, 2025 Increased error rates when accessing the website 8h 31m Admin Console Network
Started Nov 18, 2025, 12:33 PM UTC· resolved Nov 18, 2025, 09:04 PM UTC
- investigating Nov 18, 2025, 12:33 PM UTC
Beginning at 11:48 UTC today, we observed an increased rate of errors when accessing the MASV web application and website. The cause has been identified as an operational issue at our service provider and a resolution is still underway. The MASV API, desktop app, and MASV Agent remain operational and transfers that are in progress are not affected.
- investigating Nov 18, 2025, 12:33 PM UTC
We are continuing to investigate this issue.
- identified Nov 18, 2025, 01:32 PM UTC
Our service provider has indicated that they have identified the issue and are implementing a fix.
- monitoring Nov 18, 2025, 04:31 PM UTC
We have observed a reduction in error rates following the deployment of a fix by our service provider. We will continue monitoring the health of the web app and website to ensure stability.
- resolved Nov 18, 2025, 09:04 PM UTC
We have observed continued system stability following the previous update. This incident has been resolved.
- postmortem Nov 25, 2025, 07:35 PM UTC
**Problem, Impact, and Resolution** On November 18, 2025, starting at 11:48 UTC we saw increased error rates accessing the MASV website and Web App due to an outage with a service provider. Our API, file delivery network, Desktop App, and MASV Agent, along with active uploads and downloads, remained functional. Stability improved by 14:42 UTC, errors ceased by 16:31 UTC, and the incident was resolved at 21:04 UTC after monitoring confirmed no further disruption. **Mitigation and Future Prevention** We take the reliability of our service seriously and are exploring ways to enhance platform resilience against major outages at any of our service providers. We are also developing additional customer support and communication channels.
Minor October 20, 2025 Increased error rates and latency 21h 10m MASV API and Services, MASV Delivery Network
Started Oct 20, 2025, 03:38 PM UTC· resolved Oct 21, 2025, 12:49 PM UTC
- identified Oct 20, 2025, 03:38 PM UTC
Beginning at 7:20 UTC today, we observed an increased rate of errors and high latency when accessing the service. The cause has been identified as an operational issue at our service provider and a resolution is still underway.
- identified Oct 20, 2025, 07:13 PM UTC
Our service provider is making progress towards resolution and we are seeing a reduction in errors and latency. We are continuing to monitor system health.
- monitoring Oct 20, 2025, 10:37 PM UTC
Our service provider has indicated that the majority of issues have been resolved and we have confirmed that error rates have subsided. We will continue monitoring the service overnight to ensure stability.
- resolved Oct 21, 2025, 12:49 PM UTC
We have observed continued system stability following the previous update. This incident has been resolved.
- postmortem Oct 21, 2025, 05:34 PM UTC
**Problem Description, Impact and Resolution** At 07:20 UTC on October 20, 2025 we observed an increased error rate and request latency for interactions with the MASV API. Our client applications for the web, desktop and service are designed to automatically retry failures of this nature relentlessly, meaning that uploads, transfers, and general account management functionality may have experienced delays, but would ultimately succeed. Our team quickly identified one of our service providers as the source of the instability. The service provider acknowledged the issue and our team took mitigation actions and monitored progress until the service provider resolved the issue. At 19:13 UTC, we observed a significant reduction in error rates and overall latency, with the issue fully resolved by 22:37 UTC. **Mitigation Steps and Future Preventative Measures** We take service reliability very seriously as we understand the critical role of our product in the workflows of our customers. We are taking steps to invest further in recovery mechanisms for transfers to cloud when a service issue is detected while also expanding our regional resiliency.