Momentus Outage History

Started Sep 04, 2026, 09:14 AM UTC· resolved Sep 04, 2026, 09:08 PM UTC

1. investigating Sep 04, 2026, 09:14 AM UTC

   We are currently experiencing a widespread issue with SendGrid that began around midnight. This is affecting customers globally and may impact email delivery and related services. Our teams are actively monitoring the situation and working with the provider to restore full functionality as quickly as possible. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work toward a resolution.

2. investigating Sep 04, 2026, 09:14 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 04, 2026, 12:22 PM UTC

   We are continuing to monitor the ongoing SendGrid service issue that is impacting customers globally. Our teams remain engaged and are closely tracking the situation. We will provide further updates as soon as additional information becomes available. Thank you for your patience and understanding.

4. monitoring Sep 04, 2026, 03:17 PM UTC

   We continue to monitor an ongoing issue with our email delivery provider, SendGrid, that is affecting emails being delivered to Microsoft-hosted email services. Based on updates from the provider, we are seeing a recovery in our services for customer sending to Microsoft and MS 365 supported recipients, and we'll continue to monitor. We are closely monitoring updates from SendGrid and will provide additional information as it becomes available.

5. resolved Sep 04, 2026, 09:08 PM UTC

   SendGrid engineers have monitored the issue and confirmed the issue with email deliveries to Microsoft has recovered to normal levels. All services are now operating normally at this time.

Read the full incident report →

Started Aug 24, 2026, 02:54 PM UTC· resolved Aug 25, 2026, 02:13 PM UTC

1. investigating Aug 24, 2026, 02:54 PM UTC

   We are currently investigating an issue related to a recent upgrade to our monitoring system. This update was planned and tested in our lower environments prior to release; however, once deployed at production scale, it resulted in a higher-than-expected demand on system resources, which may be causing degraded performance for some customers. To mitigate impact, we have begun rolling back this change to restore the system to its previous stable state. We have also opened a critical priority ticket with our monitoring vendor to investigate the underlying cause and prevent recurrence. We will continue to provide updates as the rollback progresses and as we learn more from our vendor's investigation. We apologize for any disruption this may have caused and appreciate your patience while we work to resolve this.

2. identified Aug 24, 2026, 05:39 PM UTC

   We have completed the rollback of a recent monitoring update in the North America region. Customers in this region should now notice significantly improved performance. We are continuing this rollback process for the Asia Pacific region and will provide updates as it progresses. We apologize for any inconvenience this may have caused and appreciate your patience.

3. monitoring Aug 24, 2026, 08:04 PM UTC

   We have now completed the rollback of a recent monitoring update in both the North America and Asia Pacific regions. Customers in these regions should notice significantly improved performance. We are continuing to monitor performance to confirm resolution as we work to address in each region. The EMEA region rollback is scheduled to complete after hours this evening. We will provide a final update once this is complete. We're sorry for any disruption this may have caused and thank you for bearing with us.

4. resolved Aug 25, 2026, 02:13 PM UTC

   Rollback of recent monitoring update has completed - all regions should be experiencing significantly improved performance.

Read the full incident report →

Started May 07, 2026, 09:31 AM UTC· resolved May 08, 2026, 09:42 PM UTC

1. investigating May 07, 2026, 09:31 AM UTC

   We are experiencing an issue with a server. Users may encounter a “Report Server is not supported” message, experience login issues, or notice general degraded performance. Our team is actively investigating the root cause and will provide updates as soon as they become available.

2. investigating May 07, 2026, 11:09 AM UTC

   We are continuing to investigate the server issue. Some users may experience errors or degraded performance. Our team is actively working to identify the root cause and will provide further updates as progress is made.

3. identified May 07, 2026, 03:14 PM UTC

   We are continuing to investigate the server issue. Users should no longer experience errors or degraded performance. We will continue to monitor the system closely and are working on a fix. We will provide further updates as progress is made.

4. monitoring May 08, 2026, 06:34 AM UTC

   Users should no longer experience errors or degraded performance. We will continue to monitor the system closely and are working on a fix. We will provide further updates as progress is made.

5. monitoring May 08, 2026, 11:39 AM UTC

   Users should no longer experience errors or degraded performance. We will continue to monitor the system closely and are working on a fix. Please reach out to support if you encounter any issues.

6. monitoring May 08, 2026, 09:34 PM UTC

   We are continuing to monitor for any further issues.

7. resolved May 08, 2026, 09:42 PM UTC

   Issue has been resolved

Read the full incident report →

Started May 06, 2026, 11:26 PM UTC· resolved May 08, 2026, 09:41 PM UTC

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.

Read the full incident report →

Started May 06, 2026, 09:54 AM UTC· resolved May 06, 2026, 02:01 PM UTC

1. investigating May 06, 2026, 09:54 AM UTC

   We are experiencing an issue with a server. Users may encounter a “Report Server is not supported” message, experience login issues, or notice general degraded performance. Our team is actively investigating the root cause and will provide updates as soon as they become available.

2. identified May 06, 2026, 10:19 AM UTC

   We have identified the issue affecting the server. Some users may continue to experience errors or degraded performance. If you are impacted, please reach out to Support. Our team is working on a fix and will provide further updates as progress is made.

3. identified May 06, 2026, 11:04 AM UTC

   The server is now stable. Users should no longer experience errors or degraded performance. We will continue to monitor the system closely as we are working on a fix. We will provide further updates as progress is made.

4. identified May 06, 2026, 01:25 PM UTC

   We are continuing to monitor the environment closely. Some users may still experience intermittent issues. Our team is actively following up and working toward a fix. We will provide further updates as progress is made.

5. resolved May 06, 2026, 02:01 PM UTC

   The issue affecting the server has been fully resolved. Systems are operating normally, and users should no longer experience errors or degraded performance. Thank you for your patience.

Read the full incident report →

Started May 06, 2026, 08:22 AM UTC· resolved May 06, 2026, 08:56 AM UTC

1. investigating May 06, 2026, 08:22 AM UTC

   We are currently experiencing an issue with the report server. Users may see a “Report Server is not supported” message when attempting to access reports. Our team is actively investigating the root cause. If you require immediate assistance, please reach out to Support. Further updates will be provided shortly.

2. monitoring May 06, 2026, 08:43 AM UTC

   The issue affecting the report server has been resolved. Users should no longer encounter the “Report Server is not supported” message. We will continue to monitor the system to ensure stability. If you experience any further issues, please reach out to Support

3. resolved May 06, 2026, 08:56 AM UTC

   The issue affecting the report server has been fully resolved. All systems are operating normally. If you experience any further issues, please reach out to Support,

Read the full incident report →

Started Apr 24, 2026, 06:01 PM UTC· resolved Apr 27, 2026, 12:18 PM UTC

1. identified Apr 24, 2026, 06:01 PM UTC

   Our team has been made aware of an issue caused by an ongoing Microsoft Azure (Entra) incident that is causing a disruption in service to our US customers. Some users may experience periods of brief service interruption while Microsoft investigates and resolves the issue on their side. Momentus is continueing to monitoring the situation and will keep our status page updated as progress is made this afternoon. Please contact Support if you have any questions. Microsoft's status page may be found here: https://azure.status.microsoft/en-us/status

2. resolved Apr 27, 2026, 12:18 PM UTC

   Our team has been monitoring an issue related to a Microsoft Azure (Entra) incident that caused intermittent service disruptions for some US customers. Microsoft has taken steps to mitigate the issue, and service has stabilized. We will continue to monitor closely, but at this time the incident is considered resolved. We appreciate your patience while this was being addressed. Please contact Support if you continue to experience any issues or have questions.

Read the full incident report →

Started Mar 25, 2026, 10:10 AM UTC· resolved Mar 25, 2026, 10:36 AM UTC

1. investigating Mar 25, 2026, 10:10 AM UTC

   We are currently experiencing an issue impacting access to ELITE EMEA instance. Our technical teams are actively investigating the issue. Further updates will be shared as soon as more information is available.

2. identified Mar 25, 2026, 10:20 AM UTC

   Access to the ELITE EMEA instance has been successfully restored. Our teams continue to investigate the underlying issue. Thank you for your patience.

3. resolved Mar 25, 2026, 10:36 AM UTC

   The issue affecting access to the ELITE EMEA instance has been resolved. All systems are functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Started Mar 09, 2026, 02:23 PM UTC· resolved Mar 10, 2026, 04:51 AM UTC

1. investigating Mar 09, 2026, 02:23 PM UTC

   We are currently investigating an issue impacting our AI-powered support tools, including the in-Zendesk chatbot, in-app chatbot (Elite), and Ask Mo Support (Enterprise). Core Elite and Enterprise application functionality remains fully operational.

2. identified Mar 09, 2026, 04:45 PM UTC

   The issue has been identified and a fix is underway.

3. identified Mar 09, 2026, 08:25 PM UTC

   Issues with the bot in Zendesk have been resolved. Our team is still working to resolve the issue with Ask Mo. We will provide more updates when we have them.

4. resolved Mar 10, 2026, 04:51 AM UTC

   All Support AI services have been restored.

Read the full incident report →

Started Mar 05, 2026, 03:09 AM UTC· resolved Mar 05, 2026, 02:28 PM UTC

1. investigating Mar 05, 2026, 03:09 AM UTC

   We’re investigating reports of users not being able to access Momentus Elite in our North America region. Our team is actively investigating the cause. No action required at this time. We will provide an update as soon as possible.

2. identified Mar 05, 2026, 03:44 AM UTC

   We have identified the issue, and our team is currently working on implementing a solution.

3. identified Mar 05, 2026, 03:58 AM UTC

   The site is now operational. However, please be advised that the API Services are currently offline. Our team is actively working to resolve this issue as soon as possible.

4. identified Mar 05, 2026, 05:06 AM UTC

   We are working on fixing the API issue. We will provide an update as soon as the issue is fixed. Elite application is now operational, and we are continuing to monitor performance to ensure reliability. If you're still experiencing issues getting signed in, please reach out to Support at [email protected].

5. monitoring Mar 05, 2026, 02:12 PM UTC

   We have identified the cause of the issue impacting access to Momentus Elite in the North America region API and have implemented a fix. Our team is actively monitoring the service to ensure continued stability, but all services should be operating normally. Please reach out to our Support team at [email protected] if you're still encountering any issues getting signed into Momentus Elite or accessing our Open API.

6. resolved Mar 05, 2026, 02:28 PM UTC

   The issue impacting access to Momentus Elite in the North America region Open API service has been resolved. Our team has confirmed that services are operating normally and will continue to monitor the platform to ensure ongoing stability. If you continue to experience any issues, please contact our Support team at [email protected] for assistance.

Read the full incident report →

Started Mar 04, 2026, 08:09 PM UTC· resolved Mar 04, 2026, 08:27 PM UTC

1. investigating Mar 04, 2026, 08:09 PM UTC

   We’re investigating reports of some users not being able to access Momentus Elite in our North America region. Some customers may experience a blank page when trying to sign in. Our team is actively investigating the cause. No action required at this time. We will provide an update as soon as possible.

2. monitoring Mar 04, 2026, 08:18 PM UTC

   We have identified the cause of the issue impacting access to Momentus Elite in our North America region. Some customers may have experienced a blank page when attempting to sign in. Our team has implemented a fix and is actively monitoring the system to ensure stability. No action is required at this time. We will provide additional updates if necessary.

3. resolved Mar 04, 2026, 08:27 PM UTC

   An unexpected restart of a primary database server in the North America region caused a temporary service disruption. During this time, some users encountered a blank page when attempting to sign in to Momentus Elite. Service has now been stabilized, and we are continuing to monitor performance to ensure reliability. If you're still experiencing issues getting signed in, please reach out to Support at [email protected].

Read the full incident report →

Started Feb 20, 2026, 12:55 AM UTC· resolved Feb 20, 2026, 01:27 AM UTC

1. investigating Feb 20, 2026, 12:55 AM UTC

   Please be advised that the Momentus Elite AP instance is currently down and impacting AP regions only. Our team is investigating and will provide updates as soon as possible.

2. investigating Feb 20, 2026, 12:58 AM UTC

   We are continuing to investigate this issue.

3. identified Feb 20, 2026, 01:11 AM UTC

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

4. resolved Feb 20, 2026, 01:27 AM UTC

   The service disruption affecting APAC has been fully resolved. All systems are now operating normally. We will continue monitoring to ensure stability. Thank you for your patience. Please report any continued issues to our Support team using [email protected] using #helpnow

Read the full incident report →

Started Jan 26, 2026, 03:00 PM UTC· resolved Jan 26, 2026, 03:21 PM UTC

1. investigating Jan 26, 2026, 03:00 PM UTC

   We’re investigating reports of login issues from users in the US region. Some customers may experience a blank login screen when trying to access Momentus Elite. Our team is actively investigating the cause. No action required at this time. We will update again as we learn more.

2. identified Jan 26, 2026, 03:06 PM UTC

   The issue causing login problems has been identified, and databases should be coming back online. This can take a little more time before all clients can successfully log in.

3. monitoring Jan 26, 2026, 03:08 PM UTC

   We are monitoring all accounts to make sure all come back online. We will update again once all clients have access to their accounts.

4. resolved Jan 26, 2026, 03:21 PM UTC

   The issue with logging into Momentus Elite has been fully resolved. We apologize for any disruptions this caused.

Read the full incident report →

Started Jan 19, 2026, 02:03 PM UTC· resolved Jan 20, 2026, 09:45 AM UTC

1. investigating Jan 19, 2026, 02:03 PM UTC

   We are currently experiencing degraded performance across the system affecting users in the EMEA region. Our team is actively investigating the issue and working to restore normal performance as quickly as possible. Further updates will be provided as soon as they become available. Thank you for your patience and understanding.

2. investigating Jan 19, 2026, 02:04 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 19, 2026, 02:38 PM UTC

   Our team is still actively investigating the performance issue affecting users in the EMEA region. We are working to identify the root cause and will provide additional updates as soon as new information becomes available. Thank you for your continued patience.

4. identified Jan 19, 2026, 03:49 PM UTC

   We have identified the underlying cause of the performance issues affecting users in the EMEA region. Our team is now working on implementing a fix to restore normal service levels. Further updates will be shared as we make progress. Thank you for your continued patience.

5. identified Jan 19, 2026, 05:44 PM UTC

   We have identified the root cause of the performance issues impacting users in the EMEA region. Our team is continuing to work on a permanent fix to fully restore normal service levels. At this stage, remediation efforts are still in progress, we will share another update as soon as we move into the next stage of the process. Thank you for your patience and understanding while we work to resolve the issue.

6. monitoring Jan 20, 2026, 07:11 AM UTC

   A fix has been implemented, and system performance in the EMEA region is now improving. We are currently monitoring the situation to ensure stability and confirm that the issue has been fully resolved. We will provide a final update once we verify that all services are operating normally. Thank you for your patience throughout this incident.

7. resolved Jan 20, 2026, 09:45 AM UTC

   The performance issue affecting users in the EMEA region has been resolved. All services are functioning as expected, and users should no longer experience degraded performance. We will continue to closely monitor the system to ensure stability and confirm that no further impact occurs. Thank you for your patience and cooperation throughout this incident.

Read the full incident report →

Started Jan 19, 2026, 11:51 AM UTC· resolved Jan 19, 2026, 12:30 PM UTC

1. investigating Jan 19, 2026, 11:51 AM UTC

   We are currently experiencing Errors across the system . Our team is actively investigating the issue. We will provide you with further updates as soon as they are available. Only EMEA region is affected Thank you for your patience and understanding.

2. identified Jan 19, 2026, 12:01 PM UTC

   We have identified the root cause of the system errors currently impacting users in the EMEA region. Our team is now working on a fix to restore full service functionality. We will share further updates as progress continues. Thank you for your patience.

3. monitoring Jan 19, 2026, 12:07 PM UTC

   A fix has been implemented for the issue affecting users in the EMEA region, and we are currently monitoring system performance to ensure full stability. We will provide another update once we confirm that the issue is fully resolved. Thank you for your continued patience.

4. resolved Jan 19, 2026, 12:30 PM UTC

   The issue affecting users in the EMEA region has now been fully resolved. System functionality has returned to normal, and all services are operating as expected. Thank you for your patience and understanding

Read the full incident report →

Started Jan 14, 2026, 11:57 AM UTC· resolved Jan 14, 2026, 03:11 PM UTC

1. investigating Jan 14, 2026, 11:57 AM UTC

   We are currently experiencing degraded performance across the system Users may notice slower response times or intermittent delays. Our team is actively investigating the issue and working to restore normal performance as quickly as possible. Thank you for your patience and understanding.

2. monitoring Jan 14, 2026, 12:17 PM UTC

   The earlier performance degradation has been resolved, and services are operating normally. Our team will continue to monitor the systems closely to ensure stability. Thank you for your patience. Next Update: Only if there are significant changes.

3. resolved Jan 14, 2026, 03:11 PM UTC

   An application caused the overall CPU usage to spike. Additionally, the Anti-Malware Service Executable was running concurrently, contributing to sustained high CPU utilization which caused the performance degradation. The servers are now stable, however we are keeping the CPU usage under observation,

Read the full incident report →

Started Jan 09, 2026, 10:30 AM UTC· resolved Jan 09, 2026, 10:45 AM UTC

1. investigating Jan 09, 2026, 10:30 AM UTC

   We are currently experiencing an outage impacting EMEA regions only. Our teams are actively investigating and working toward resolution. Further updates will be shared as available.

2. identified Jan 09, 2026, 10:36 AM UTC

   We have identified the issue and our Teams are actively working to resolve it We will provide further updates when available.

3. resolved Jan 09, 2026, 10:45 AM UTC

   The EMEA outage has been successfully resolved. All services are now back online and operating normally. Thank you for your understanding.

Read the full incident report →

Started Jan 05, 2026, 12:31 AM UTC· resolved Jan 05, 2026, 04:11 AM UTC

1. investigating Jan 05, 2026, 12:31 AM UTC

   We are currently investigating an issue impacting customers in Australia and New Zealand.

2. identified Jan 05, 2026, 01:31 AM UTC

   We have identified the issue affecting customers in Australia and New Zealand and are actively working to resolve it.

3. monitoring Jan 05, 2026, 01:42 AM UTC

   The issue impacting Australia and New Zealand Enterprise customers appears to be resolved. We are continuing to monitor the environment to ensure stability

4. resolved Jan 05, 2026, 04:11 AM UTC

   The service disruption affecting Australia and New Zealand clients has been fully resolved. All systems are now operating normally. Thank you for your patience and understanding. If you experience any further issues, please don't hesitate to contact our Support team.

Read the full incident report →

Started Dec 05, 2025, 09:20 PM UTC· resolved Dec 06, 2025, 12:49 PM UTC

1. identified Dec 05, 2025, 09:20 PM UTC

   Our SRE (Site Reliability Engineering) Team is currently working to address an issue with the Priava site certificate.

2. identified Dec 05, 2025, 11:30 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Dec 05, 2025, 11:30 PM UTC

   Our team is in the final stages of preparing the new certificate for application. Servers will need to be restarted after the certificate has been applied - this will result in down time of about 15 minutes.

4. monitoring Dec 06, 2025, 01:39 AM UTC

   All web instances for all regions have been addressed and client sites are available for users. API calls might still be affected as we continue to resolve this issue.

5. monitoring Dec 06, 2025, 03:07 AM UTC

   Americas region is now completely operational. Other regions may continue to experience degraded performance with API calls as we continue to monitor and address.

6. resolved Dec 06, 2025, 12:49 PM UTC

   All regions' API calls are completely operational - the issue is fully now resolved.

Read the full incident report →

Started Nov 25, 2025, 03:14 PM UTC· resolved Nov 25, 2025, 05:27 PM UTC

1. investigating Nov 25, 2025, 03:14 PM UTC

   We are currently experiencing an API outage that is affecting integrations with Momentus Elite. Our team is actively working to resolve the issue and restore normal functionality as quickly as possible. We will provide updates as soon as more information is available. Thank you for your patience and understanding. If you have any immediate concerns, please contact our support team.

2. identified Nov 25, 2025, 04:01 PM UTC

   The cause of the API outage impacting Elite integrations has been identified. Our team is actively working on resolving the issue, and more updates will follow as we make progress. Please don't hesitate to reach out to Support with any questions.

3. monitoring Nov 25, 2025, 04:42 PM UTC

   A fix for the API outage affecting Elite integrations has been deployed. We are monitoring the results to ensure full restoration of service. If you continue to experience any issues, please contact our support team for assistance.

4. resolved Nov 25, 2025, 05:27 PM UTC

   The issue affecting Elite integrations has been fully resolved, and all services are operating normally. We have closed the incident. If you experience any further issues, please reach out to our support team.

Read the full incident report →

Started Nov 13, 2025, 09:51 PM UTC· resolved Nov 13, 2025, 11:02 PM UTC

1. investigating Nov 13, 2025, 09:51 PM UTC

   We are currently investigating elevated errors and degraded performance affecting some Enterprise customers. Impacted users may experience intermittent 504 errors and slow response times. We will provide an update as soon as we have more information. This issue is currently limited to customers in the US region. Other regions remain fully operational.

2. monitoring Nov 13, 2025, 10:32 PM UTC

   The issue impacting US Enterprise customers appears to be resolved. We are continuing to monitor the environment to ensure stability.

3. resolved Nov 13, 2025, 11:02 PM UTC

   Our monitoring has indicated that our systems are currently stable and response times have returned to normal. The issue has been resolved. If you continue to have issues with performance after clearing your cache and restarting your browser, please enter a Support ticket.

Read the full incident report →

Started Oct 29, 2025, 07:11 PM UTC· resolved Oct 30, 2025, 02:33 AM UTC

1. investigating Oct 29, 2025, 07:11 PM UTC

   We are currently investigating issues affecting sites under the *.ungerboeck.io domain. This is due to an ongoing service outage with Microsoft Azure. As a result, Digital Signage feeds and certain customer automations may be temporarily unavailable. You can monitor Azure’s status directly at https://azure.status.microsoft/en-us/status. We will provide updates as more information becomes available.

2. monitoring Oct 29, 2025, 08:44 PM UTC

   Services may have degraded performance, but access is currently being restored.

3. monitoring Oct 30, 2025, 12:45 AM UTC

   The PowerApps dependency issue has been mitigated. Customers have confirmed that the mitigation is effective, and no further impact has been reported.

4. resolved Oct 30, 2025, 02:33 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 07:07 PM UTC· resolved Oct 23, 2025, 08:25 PM UTC

1. identified Oct 23, 2025, 07:07 PM UTC

   We are aware of an unexpected service disruption currently affecting Momentus Priava for customers in the APAC region. Our engineering team is actively investigating the issue and working to restore full service as quickly as possible.

2. monitoring Oct 23, 2025, 07:21 PM UTC

   We’re pleased to confirm that the earlier service disruption affecting Momentus Priava in the APAC region has been resolved. All systems are now operating normally, and service should be fully restored. Our team will continue to closely monitor performance to ensure stability. If you are still experiencing any issues, please don’t hesitate to contact our Support Team. Thank you for your patience and understanding while we worked to restore service.

3. monitoring Oct 23, 2025, 08:24 PM UTC

   The earlier issue impacting Momentus Priava in the APAC region has now been resolved. Services are operating normally. Our team will continue to monitor the platform to ensure ongoing stability. If you are still experiencing any problems, please reach out to our Support Team. Thank you for your patience and understanding.

4. resolved Oct 23, 2025, 08:25 PM UTC

   The earlier issue impacting Momentus Priava in the APAC region has now been resolved. Services are operating normally. Our team will continue to monitor the platform to ensure ongoing stability. If you are still experiencing any problems, please reach out to our Support Team. Thank you for your patience and understanding.

Read the full incident report →

Started Oct 21, 2025, 12:52 AM UTC· resolved Oct 21, 2025, 11:53 AM UTC

1. investigating Oct 21, 2025, 12:52 AM UTC

   Earlier today, the AWS servers were down which affected multiple cloud services for many companies in the US. One of the services that it affected is one that Momentus utilizes called Launch Darkly. This tool assists in loading the new User Interface when clients log into their Prod Enterprise environments. Now that the AWS servers are operational, Launch Darkly's servers need to catch up. As of 7:50pm Central, they were still experiencing a high level of requests and were working through their backlog as quickly as possible. We will provide an update once we have one.

2. monitoring Oct 21, 2025, 01:15 AM UTC

   We are awaiting the results of the Launch Darkly status page to confirm their system is operational.

3. monitoring Oct 21, 2025, 02:29 AM UTC

   We are still waiting on an update from Launch Darkly. In the meantime, we discovered a workaround for some customers that will pull up the New UX and load a little bit faster when you login. Please try to access your site to see if you are able to login to your sie and receive the new UX. If it does not work for you, then we will continue to wait for the next update from Launch Darkly.

4. monitoring Oct 21, 2025, 05:12 AM UTC

   Launch Darkly has reported that their server-side streaming API is still experiencing a partial outage, resulting in elevated error rates for some users. They are working with AWS to restore full service, and our team continues to monitor the situation closely. During this time, some users may continue to experience intermittent timeouts or connection issues. We will provide further updates as they become available.

5. monitoring Oct 21, 2025, 06:44 AM UTC

   Launch Darkly are in the process of deploying additional load balancer units that are about to go online, they expect them to successfully handle the increased volume in traffic and restore services. During this time, some users may continue to experience intermittent timeouts or connection issues. We will provide further updates as they become available. Thank you for you patience

6. monitoring Oct 21, 2025, 07:38 AM UTC

   Launch darkly stated to see signs of recovery, Their initial load balancer unit was upgrading and has begun handling traffic successfully. The additional load balancer is online and is beginning to handle traffic. At the moment, Enterprise may still experience delays and slowness. We will provide further updates as they become available.

7. monitoring Oct 21, 2025, 08:18 AM UTC

   Launch Darkly confirmed that their Servers are back online. We will continue monitoring through out the day, in case of changes or issues we will provide an immediate update.

8. monitoring Oct 21, 2025, 09:16 AM UTC

   LaunchDarkly has confirmed that their servers are now back online, healthy, and stable. We will continue to monitor the situation throughout the day to ensure continued stability. If you experience any issues, please don’t hesitate to reach out to our support team. We sincerely thank you for your patience and understanding during this unforeseen incident, which was beyond our control.

9. resolved Oct 21, 2025, 11:53 AM UTC

   LaunchDarkly has confirmed that their servers are now fully operational, healthy, and stable. Our team will continue to monitor the situation throughout the day to ensure continued performance. If you encounter any further issues, please reach out to our support team. We appreciate your patience and understanding during this unexpected incident, which was beyond our control.

Read the full incident report →

Started Oct 20, 2025, 11:50 AM UTC· resolved Oct 20, 2025, 11:24 PM UTC

1. monitoring Oct 20, 2025, 11:50 AM UTC

   Following the AWS outage earlier today, most of our services are now operational. We are actively monitoring performance to ensure full stability across all systems. While AWS has reported significant recovery, we are still awaiting full resolution confirmation. In the meantime, users may experience intermittent performance issues or slowness. We’ll continue to provide updates as needed. Thank you for your continued patience.

2. monitoring Oct 20, 2025, 11:50 AM UTC

   We are continuing to monitor for any further issues.

3. monitoring Oct 20, 2025, 01:09 PM UTC

   We are actively monitoring performance to ensure full stability across all systems. While AWS has made significant progress, we are still awaiting full resolution confirmation. As a result, users may continue to experience performance degradation and slowness in some areas.

4. monitoring Oct 20, 2025, 02:00 PM UTC

   While AWS are still working to resolve this issue, we are still observing performance and slowness issues across parts of our system. We’ll continue to provide updates as needed. Thank you for your continued patience

5. monitoring Oct 20, 2025, 03:14 PM UTC

   We are still monitoring performance, our team is working to mitigate these effects and ensure a smooth return to full functionality.

6. monitoring Oct 20, 2025, 04:00 PM UTC

   AWS are still working to resolve this issue, we are still observing performance and slowness issues across parts of our system. We’ll continue to provide updates as needed. Thank you for your continued patience

7. monitoring Oct 20, 2025, 04:53 PM UTC

   AWS is working towards implementing a fix for the degraded performance that should mitigate and resolve the issues. In the meantime, we are continuing to work internally towards a resolution.

8. monitoring Oct 20, 2025, 05:44 PM UTC

   AWS continues to implement fixes to mitigate the performance issues and early tests are showing positive results in restoring connectivity. Once they have completed implementing these fixes, they expect launch errors and network connectivity issues to subside. We will provide more updates soon.

9. monitoring Oct 20, 2025, 06:27 PM UTC

   AWS continues to see progress within the mitigations that they are launching. They plan to provide another update by 12pm Pacific. Updates will be passed along as soon as we have them.

10. monitoring Oct 20, 2025, 07:23 PM UTC

    AWS continues to see improvement across the services that they have implemented their mitigation measures to, but there are still a few services that haven't been resolved yet. They are continuing to implement additional fixes to these services in the hopes of restoring them to their expected working state soon.

11. monitoring Oct 20, 2025, 08:10 PM UTC

    AWS continues to see improvement across the services that they have implemented their mitigation measures to. Error rates have slowed and continue to improve. Another update will be provided by 2:00 PM PDT.

12. monitoring Oct 20, 2025, 08:58 PM UTC

    AWS continues to implement their fixes and see improvement across the affected services and regions. They are also implementing monitoring to ensure that the services reach pre-event performance levels before declaring that the issue has been fully resolved. We will provide additional updates as we have them.

13. monitoring Oct 20, 2025, 09:58 PM UTC

    The latest update from AWS reveals that they are continuing to implement different aspects of their recovery and, while seeing improvements within some of the previously affected services, they have a backlog of events that they expect will be resolved in the next 2 hours. While they continue working on their end, our Site Reliability team at Momentus has noted that they are not observing any major impact on our services related to today’s AWS outage. We will continue to monitor the environment closely and provide updates.

14. monitoring Oct 20, 2025, 11:22 PM UTC

    AWS has confirmed that the earlier issues affecting multiple services have now been fully resolved. All impacted services have returned to normal operation, and performance has stabilized across the affected regions. Our Site Reliability team at Momentus has not observed any ongoing impact to our systems, and all services are functioning as expected. We will continue to monitor closely and share any follow-up information once AWS provides their post-event summary.

15. resolved Oct 20, 2025, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →