Instance reporting "400 Bad Request"

Update timeline

1. investigating Feb 09, 2026, 02:03 AM UTC

   We are currently investigating this issue.

2. investigating Feb 09, 2026, 02:31 AM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 09, 2026, 02:42 AM UTC

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

4. resolved Feb 09, 2026, 04:02 AM UTC

   This incident has been resolved.

5. postmortem Feb 11, 2026, 09:36 PM UTC

   **Service Interruption** ‌ **Issue Summary:** On 08 Feb 2025 between 23:30 UTC and 09 Feb 2025 02:00 UTC \(4:30 PM MT - 7:00 PM MT\), the Vasion platform experienced intermittent service disruptions affecting a small subset of customers due to unusually high traffic volumes. ‌ **Root Cause:** The platform encountered an unexpected surge in traffic that exceeded normal operating capacity. This volume of requests overwhelmed specific components of our infrastructure, resulting in intermittent slowdowns and brief service outages for a limited number of affected customers. ‌ **Resolution:** Our operations team quickly identified the source of the elevated traffic and blocked abusive IPs to restore normal service levels. The service was fully restored by 02:00 UTC \(7:00 PM MT\). ‌ **Mitigation:** To prevent similar disruptions in the future, we are enhancing traffic monitoring and rate-limiting controls. These measures will enable our systems to detect and respond to abnormal traffic patterns more quickly, ensuring continued service availability even during unexpected traffic spikes. **‌** **Conclusion:** We recognize the critical importance of uninterrupted service to your business and sincerely apologize for any inconvenience this disruption caused to the affected customers. We are committed to maintaining the highest levels of service reliability and have taken concrete steps to strengthen our infrastructure's resilience against similar events in the future.