Destination "Productsup Server" Issues

Incident Overview
On May 12, we experienced a temporary service disruption affecting parts of our transport platform. This occurred during a configuration update aimed at improving our system’s routing capabilities.

Root Cause
The disruption was caused by a misconfiguration in our internal storage system. Although the change had passed staging tests, it behaved differently in production, leading to certain requests being misrouted.

Impact
During the incident, some clients were unable to access services hosted on specific subdomains of our transport platform and jobs couldn't write to destination "Productsup server". Normal operation resumed shortly after the change was rolled back.

Preventive Measures
To prevent this issue from recurring, we are:

• Improving our deployment validation processes.
• Enhancing staging to more closely reflect production conditions.
• Adding more automated checks to detect routing issues earlier.

Conclusion
The issue was resolved by reverting the configuration. Processes have been updated to prevent recurrence. All systems are operating normally.