Vasion incident

Instance creation hanging

Minor Resolved View vendor source →

Vasion experienced a minor incident on October 17, 2025 affecting MSP Portal and MSP Portal and 1 more component, lasting 20d 4h. The incident has been resolved; the full update timeline is below.

Started
Oct 17, 2025, 04:28 PM UTC
Resolved
Nov 06, 2025, 08:32 PM UTC
Duration
20d 4h
Detected by Pingoru
Oct 17, 2025, 04:28 PM UTC

Affected components

MSP PortalMSP PortalMSP PortalMSP PortalMSP PortalMSP Portal

Update timeline

  1. investigating Oct 17, 2025, 04:28 PM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2025, 02:29 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Nov 04, 2025, 06:15 PM UTC

    The MSP Portal team has identified the root cause and has a fix is planned to be included in the next upcoming release

  4. monitoring Nov 06, 2025, 04:31 PM UTC

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

  5. resolved Nov 06, 2025, 08:32 PM UTC

    This incident has been resolved.

  6. postmortem Nov 12, 2025, 05:55 PM UTC

    November 12, 2025 **MSP Portal: Instance creation hanging** ‌ **Issue Summary:** On October 17, 2025, some MSP partners experienced failures when attempting to create new customer instances through the MSP Portal. ‌ **Root Cause:** An internal data alignment issue caused our provisioning service to reject valid instance creation requests. Additionally, overly strict data validation rules incorrectly flagged some legitimate requests as invalid. ‌ **Resolution:** Our engineering team corrected the data alignment issue and implemented improved error handling to ensure the provisioning service processes instance creation requests successfully. ‌ **Mitigation:** We've adjusted the data validation rules to prevent false rejections while maintaining appropriate security standards. We've also added enhanced monitoring to detect similar issues before they impact customers. We also added better phone number validation that properly supports international numbers. **‌** **Conclusion:** This issue has been fully resolved, and the additional safeguards are now in place to prevent recurrence.