Momentus Enterprise Asia Pacific TEST Connectivity Issues

Update timeline

1. identified May 06, 2026, 11:26 PM UTC

   What’s Happening: We are investigating reports of connectivity issues impacting the Momentus Enterprise Asia Pacific TEST environment. Impact: Some customers may experience intermittent access issues or an inability to connect to the TEST environment. What we’re doing: We have identified the issue and are actively working on implementing a solution to restore stable connectivity as quickly as possible. Customer action: No action is required at this time. We will provide further updates as more information becomes available. Next Update: Within 90 minutes or sooner if additional information becomes available.

2. identified May 07, 2026, 01:03 AM UTC

   We are continuing to work through this issue and actively investigating the impact across the Asia Pacific region. Progress has been made toward resolving the issue, and our teams continue working through all impacted environments. Further updates will be provided as more information becomes available.

3. monitoring May 07, 2026, 04:10 AM UTC

   We are seeing recovery across impacted environments as systems continue to come back online. Our teams remain actively engaged in monitoring, and we currently expect full mitigation by end of business AEST on 8 May.

4. resolved May 08, 2026, 09:41 PM UTC

   Issue has been resolved

5. postmortem May 20, 2026, 03:19 PM UTC

   **Service Disruption Notice — APAC Test Environments | May 6–8, 2025** On May 6, a subset of our APAC customers experienced disruptions to their Test environments, including errors when accessing the platform. We want to share what happened, how we resolved it, and the steps we are taking to prevent this in the future. **What Happened** We rolled out an infrastructure update to our Test environments in the APAC region. Prior to the broader rollout, we piloted the change and observed no issues. However, following the full rollout, unexpected performance issues were introduced that caused affected environments to become slow and unresponsive for some customers. **How We Resolved It** Upon identifying the issue on May 6, we made the decision to roll back all affected customers to the previous server configuration. The majority of customers were restored by May 7, with all remaining customers fully resolved by May 8. We are continuing to work with our cloud services partner to fully understand and address the root cause before attempting this rollout again. **Our Commitment Going Forward** We are taking the following steps to prevent a recurrence: * **Better pre-deployment testing:** We will validate infrastructure changes under realistic conditions before any future rollout. * **Extended canary deployments with deeper monitoring:** We will increase the duration of staged rollouts and apply deeper performance monitoring during that period to ensure issues are caught before changes are broadly deployed. * **Faster rollback decisions:** We are establishing clear criteria that will trigger an immediate rollback when needed, reducing resolution time. We sincerely apologize for the disruption this caused to your operations and appreciate your patience as we worked to resolve the issue. Providing a reliable and stable experience for our customers is our top priority, and we are committed to earning back your confidence.