Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Incident Summary On August 7, 2025, between 11:31 PM to 11:36 PM ET and 11:42 PM to 11:46 PM ET, customers experienced a service degradation. During this window, workflows did not initiate, however, workflows that were in process did complete as expected. Root Cause A platform deployment on August 7 (AU - 1:12PM ET, EU - 1:35PM ET, UK - 1:46PM ET, US - 5:25PM ET) introduced a configuration change that caused event handlers to enqueue but not execute once the deployment completed. This initially surfaced through customer reports related to permission errors when creating new app builder pages—an early symptom of the underlying issue. Upon investigation, it became clear that the event system as a whole was failing to drain enqueued messages. Once message draining was initiated, this caused resource saturation, and resulted in a broader platform performance degradation.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

The 3rd party LMS provider has identified the issue and is in the process of remediation

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

We experienced a temporary service interruption in our AU region due to a backend issue related to scheduled data operations. The issue has been resolved, and we’ve implemented automation improvements and monitoring to prevent recurrence.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

On July 17th at 2:09 pm ET, we detected a platform outage affecting US region workflow processing. We are investigating the issue urgently and will update you with further information soon.

From 2:09 pm ET to 2:21 pm ET, there was a platform outage affecting the US region. Workflow executions were paused while the outage was resolved, and have since resumed as normal.

Issue opened on monitor failure.

Issue resolved on monitor recovery. July 11, 2025 U.S. Outage – Post-Incident Summary Early this morning, a workflow configuration triggered a recursive loop that saturated one of our processing queues, causing a temporary disruption in the U.S. region from 10:50 AM to 11:14 AM EST. The issue was quickly identified and isolated, and service was fully restored within 24 minutes. We've confirmed the root cause and are accelerating rollout of platform-level protections — including rate limiting and recursion safeguards — to prevent this class of issue in the future.

On July 7th, between 5:10 PM and 5:25 PM EST, our platform experienced a temporary disruption due to an uncoordinated update to our internal messaging system (RabbitMQ). This affected the execution of workflows, resulting in stuck or failed runs during that window. We quickly identified the issue and activated a fallback mechanism to restore functionality while our team corrected the underlying configuration. Impact was limited to specific workflows dependent on that message queue, and services were fully restored by 5:25 PM EST. All messages that were enqueued during the time period between message queue failover have been triggered to process. This event highlighted an area for internal process improvement, and we’re already implementing safeguards to ensure future updates and changes are handled with proper coordination and validation across all services.

Resolved

Starting June 12 at approximately 2:45 PM ET, Rewst workflows and services may experience degraded performance due to widespread service disruptions affecting large scale internet hosting providers such as Cloudflare, Google Cloud Platform (GCP), and Amazon Web Services (AWS). These third-party outages impact a range of connected services and integrations, which may have caused delays or failures in workflow executions that rely on those integrations. We recommend reviewing your workflows, particularly those involving email processing, webhook triggers, or cloud service APIs, to identify any affected runs or retries that may require attention.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

On 6th June at around 9 am ET time, we detected that workflow processing in Rewst is experiencing significant delays. Users may experience longer than usual wait times for workflows to process. We are currently investigating the issue and will provide more information as soon as it is available. If you would like any failed workflows to be reprocessed, please reach out to our support team at roc@rewst.io

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Our monitoring system has detected that authentication for some integrations in Rewst are experiencing failures. We are currently investigating the issue and will provide more information as soon as it is available.

Patch released

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

As of April 3, 2025 at 12:15 PM EDT, Rewst has identified an issue that is causing service degradation in the US instance. We are actively working to resolve the issue. We will update you when a permanent fix is implemented.

Identified and patched issue with Organizations list query causing database performance issues.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

We are aware of performance issues affecting app.rewst.io in the US region and are actively investigating the root cause. We will share updates as we have them.

We’ve resolved the recent performance issues on app.rewst.io in the US region and are working on a permanent fix. Thank you for your patience.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Shortly before 12:00 PM EST today, we became aware of an issue affecting users of the Pax8 integration on the US East instance of Rewst. This issue is resulting in "429 - Too Many Requests" errors being returned from the Pax8 integration. This issue prevents users from making changes to the Pax8 integration and running workflows utilizing the integration. This will affect users running our User Onboarding and User Offboarding crates that utilize the Pax8 Integration. Our team is actively collaborating with Pax8 to resolve the issue as quickly as possible. We are continuously monitoring the affected services to evaluate the extent and progression of the problem. We greatly appreciate your patience and understanding during this time. Updates will be shared as more information becomes available.

Pax8 actions are successfully executing

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Live App Builder sites are unavailable.

We were performing upgrades across all Rewst instances to how we provision domains for live sites. The upgrades were successful in all of our instances, but failed in prod US at 6:33 PM EST. We were troubleshooting for 50 minutes and managed to roll back at 7:23PM bringing rew.st domains back up. There was additional work needed to get custom domains back, which was completed at 7:38PM.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

On November 6, 2024, from 10:53 AM EST to 11:40 AM EST, an unintended disruption occurred in our production environment, impacting workflow processing for our US customers. While working towards a resolution, there were failures of workflows running at the time. This temporarily affected real-time processing across parts of our application. The issue was resolved and workflows are running as normal. Thank you for your understanding as we work to strengthen our safeguards. We are committed to maintaining the reliability and resilience of our platform and will continue to enhance our processes to prevent such incidents in the future.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue re-opened on monitor failure.

Issue resolved on monitor recovery.

Rewst is experiencing performance degradation affecting user experience. Workflows are running, however the user interface experience and workflow execution speeds are degraded. We are investigating and we will share more information as it becomes available.

We have identified the root cause of the performance issues impacting user experience on the Rewst platform. Our team has initiated remediation efforts and we are observing initial improvements in both user interface responsiveness and workflow execution speeds. We will continue to monitor the situation closely and provide further updates as progress is made. Thank you for your patience and understanding.

Update: The performance issues affecting Rewst’s user experience and workflow execution speeds have been fully resolved. Our team has completed remediation efforts, and all systems are now operating as expected. We appreciate your patience and understanding throughout the process.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.

Issue opened on monitor failure.

Issue resolved on monitor recovery.