https://rewst.cronitorstatus.com/historyStatus Page - Incident Feeden-usTue, 05 May 2026 13:00:00 +0000https://rewst.cronitorstatus.com/history/ea7d28b4d2a09161[Investigating] 2026-05-05 13:00 UTC - "We're currently experiencing slower than normal workflow processing times in US. Our team is actively investigating and working to restore full performance. We'll provide updates as we learn more." [Monitoring] 2026-05-05 14:23 UTC [Resolved] 2026-05-05 20:00 UTCTue, 05 May 2026 13:00:00 +0000https://rewst.cronitorstatus.com/history/ea7d28b4d2a09161https://rewst.cronitorstatus.com/history/ac821cf6a3084f00[Unresolved] 2026-04-23 13:35 UTC - "New app builder apps are having issues provisioning. The team is investigating." [Identified] 2026-04-23 16:00 UTC [Monitoring] 2026-04-23 20:37 UTC [Resolved] 2026-04-24 00:45 UTC - "For any customers impacted during the incident window, we recommend navigating to settings, updating the domain name of their app, then changing it back to the desired state. This should resolve any provisioning issues. No action is required to fully resolve; the recommendation above is for a faster update. A fix is being rolled out that will automatically resolve any remaining affected sites."Thu, 23 Apr 2026 13:35:00 +0000https://rewst.cronitorstatus.com/history/ac821cf6a3084f00https://rewst.cronitorstatus.com/history/a0ddf2f42ad08fef[Identified] 2026-04-22 18:53 UTC - "We have identified an issue with a third-party authentication provider affecting login and application access in our EU, UK, and AU regions. Workflows are not impacted and continue to run normally. We are monitoring the situation and will provide updates as it progresses." [Resolved] 2026-04-22 19:42 UTCWed, 22 Apr 2026 18:53:50 +0000https://rewst.cronitorstatus.com/history/a0ddf2f42ad08fefhttps://rewst.cronitorstatus.com/history/c8a126420d973eb5[Investigating] 2026-04-20 07:15 UTC - "We are currently investigating an issue with delays in subworkflow processing" [Monitoring] 2026-04-20 11:50 UTC - "We have implemented a fix and have seen executions return to expected process times." [Resolved] 2026-04-20 12:03 UTC - "Process times have remained as expected"Mon, 20 Apr 2026 07:15:00 +0000https://rewst.cronitorstatus.com/history/c8a126420d973eb5https://rewst.cronitorstatus.com/history/15a8c360896ba80f[Unresolved] 2026-04-08 14:40 UTC - "We're currently experiencing slower than normal workflow processing times in US. Our team is actively investigating and working to restore full performance. We'll provide updates as we learn more." [Investigating] 2026-04-08 14:45 UTC [Identified] 2026-04-08 15:00 UTC [Monitoring] 2026-04-08 15:18 UTC [Resolved] 2026-04-08 15:35 UTCWed, 08 Apr 2026 14:40:22 +0000https://rewst.cronitorstatus.com/history/15a8c360896ba80fhttps://rewst.cronitorstatus.com/history/bcd4087eb21301ec[Investigating] 2026-04-03 15:04 UTC - "RoboRewsty is experiencing intermittent issues. Requests may occasionally fail, though should work after retrying. We're actively investigating." [Identified] 2026-04-03 15:33 UTC - "We've isolated the issue with RoboRewsty and are actively working on a resolution." [Resolved] 2026-04-03 15:51 UTCFri, 03 Apr 2026 15:04:27 +0000https://rewst.cronitorstatus.com/history/bcd4087eb21301echttps://rewst.cronitorstatus.com/history/7ba75d57f2fcd68c[Identified] 2026-04-02 17:21 UTC - "We're aware of an issue affecting App Builder apps in the US region. New apps will be unable to get certs. Our engineering team is working on a fix and we'll update you once service is restored." [Monitoring] 2026-04-02 18:09 UTC [Resolved] 2026-04-02 21:14 UTCThu, 02 Apr 2026 17:21:03 +0000https://rewst.cronitorstatus.com/history/7ba75d57f2fcd68chttps://rewst.cronitorstatus.com/history/73f0fe9a2ce39af0[Resolved] 2026-03-31 14:18 UTC - "On March 31, 2026, some customers in the US and UK regions experienced connectivity issues with the IT Glue integration when using the Rewst proxy. Requests to the IT Glue API were failing, resulting in workflow execution errors. Who was affected: Customers on prod-us and prod-uk with IT Glue integrations configured to use the Rewst proxy. Customers using a direct connection (Use Rewst IP = True) were not impacted. Root cause: Our proxy provider experienced an infrastructure issue that caused their gateway IP to become unresponsive in certain regions. This resulted in IT Glue API requests being rejected when routed through the proxy. Resolution: We worked with our proxy provider to identify the issue and provisioned a new gateway IP. The updated configuration was deployed across all environments and service was fully restored by 10:18 AM EDT. We apologize for the disruption and appreciate your patience."Tue, 31 Mar 2026 14:18:00 +0000https://rewst.cronitorstatus.com/history/73f0fe9a2ce39af0https://rewst.cronitorstatus.com/history/c623b64121e2f366[Unresolved] 2026-03-26 00:54 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-26 00:58 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 05:20 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 05:21 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 05:24 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 05:30 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 08:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 08:24 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 08:47 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 08:54 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 08:58 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 09:06 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 09:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 09:40 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 09:48 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 09:50 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 10:04 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 10:09 UTC - "Issue resolved on monitor recovery." [Unresolved] 2026-03-26 10:52 UTC - "Issue re-opened on monitor failure." [Resolved] 2026-03-26 10:59 UTC - "Issue resolved on monitor recovery." [Resolved] 2026-03-26 11:09 UTC - "Starting around 8:54 PM ET on March 25th, published App Builder apps on the rew.st domain became unreachable due to a domain registration lapse. The core Rewst platform was unaffected, but any app hosted on a rew.st subdomain could not be accessed. The issue was identified and the domain was renewed overnight. Apps began coming back online around 4:00 AM ET on March 26th. Some users experienced lingering issues due to cached DNS responses and may have needed to clear their DNS cache. We're putting monitoring in place to alert well in advance of any future domain expirations so this doesn't happen again."Thu, 26 Mar 2026 00:54:42 +0000https://rewst.cronitorstatus.com/history/c623b64121e2f366https://rewst.cronitorstatus.com/history/5c321eafea05432d[Identified] 2026-03-19 01:45 UTC - "We are currently experiencing a disruption to RoboRewsty caused by an issue with an upstream infrastructure provider. Our team is actively engaged with them and working toward resolution. We will continue to provide updates here." [Resolved] 2026-03-19 02:28 UTC [Resolved] 2026-03-19 19:23 UTCThu, 19 Mar 2026 01:45:40 +0000https://rewst.cronitorstatus.com/history/5c321eafea05432dhttps://rewst.cronitorstatus.com/history/7417de118584f0aa[Monitoring] 2026-03-17 16:08 UTC - "We're currently experiencing slower than normal workflow processing times in UK. Our team is actively investigating and working to restore full performance. We'll provide updates as we learn more." [Resolved] 2026-03-17 16:57 UTC - "Root cause: Workflow processing in the UK region was degraded due to a small number of workflows entering an unintended loop state, which caused a sudden spike in execution volume that affected processing times broadly. Our team identified and resolved the issue within the hour. We're implementing improvements to loop detection and rate limiting to reduce the impact of similar events in the future."Tue, 17 Mar 2026 16:08:59 +0000https://rewst.cronitorstatus.com/history/7417de118584f0aahttps://rewst.cronitorstatus.com/history/bb6ba6e7fbc1f04f[Unresolved] 2026-03-17 10:13 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-17 10:24 UTC - "Issue resolved on monitor recovery."Tue, 17 Mar 2026 10:13:43 +0000https://rewst.cronitorstatus.com/history/bb6ba6e7fbc1f04fhttps://rewst.cronitorstatus.com/history/f8f5dd7a9e02242c[Unresolved] 2026-03-17 09:30 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-17 09:40 UTC - "Issue resolved on monitor recovery."Tue, 17 Mar 2026 09:30:59 +0000https://rewst.cronitorstatus.com/history/f8f5dd7a9e02242chttps://rewst.cronitorstatus.com/history/576c3c7906cf63ce[Identified] 2026-03-17 00:50 UTC - "We're aware of an issue with the ITGlue integration, and have identified the cause. We're actively working to resolve the issue." [Monitoring] 2026-03-17 01:39 UTC [Resolved] 2026-03-17 01:41 UTCTue, 17 Mar 2026 00:50:49 +0000https://rewst.cronitorstatus.com/history/576c3c7906cf63cehttps://rewst.cronitorstatus.com/history/112f9e15aef8d405[Unresolved] 2026-03-15 01:31 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-15 01:41 UTC - "Issue resolved on monitor recovery."Sun, 15 Mar 2026 01:31:14 +0000https://rewst.cronitorstatus.com/history/112f9e15aef8d405https://rewst.cronitorstatus.com/history/fb3c82ac401c8286[Unresolved] 2026-03-13 04:16 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-13 04:33 UTC - "Issue resolved on monitor recovery."Fri, 13 Mar 2026 04:16:42 +0000https://rewst.cronitorstatus.com/history/fb3c82ac401c8286https://rewst.cronitorstatus.com/history/d5b4bdd12f121ebc[Investigating] 2026-03-05 16:31 UTC - "We're aware of an issue affecting apps in US. Our engineering team is working on a fix and we'll update you once service is restored." [Resolved] 2026-03-05 16:55 UTCThu, 05 Mar 2026 16:31:39 +0000https://rewst.cronitorstatus.com/history/d5b4bdd12f121ebchttps://rewst.cronitorstatus.com/history/3190966e97c54555[Unresolved] 2026-03-04 21:55 UTC - "Issue opened on monitor failure." [Resolved] 2026-03-04 22:05 UTC - "Issue resolved on monitor recovery."Wed, 04 Mar 2026 21:55:39 +0000https://rewst.cronitorstatus.com/history/3190966e97c54555https://rewst.cronitorstatus.com/history/0f7ed39dd9b3db30[Investigating] 2026-03-04 18:27 UTC - "We're currently experiencing slower than normal workflow processing times in US. Our team is actively investigating and working to restore full performance. We'll provide updates as we learn more." [Identified] 2026-03-04 18:47 UTC [Monitoring] 2026-03-04 19:19 UTC [Identified] 2026-03-04 20:08 UTC [Resolved] 2026-03-04 22:27 UTCWed, 04 Mar 2026 18:27:22 +0000https://rewst.cronitorstatus.com/history/0f7ed39dd9b3db30https://rewst.cronitorstatus.com/history/09c23fb23006f198[Unresolved] 2026-02-28 09:31 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-28 09:41 UTC - "Issue resolved on monitor recovery."Sat, 28 Feb 2026 09:31:17 +0000https://rewst.cronitorstatus.com/history/09c23fb23006f198https://rewst.cronitorstatus.com/history/758fcaff67ada546[Unresolved] 2026-02-27 05:27 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-27 05:34 UTC - "Issue resolved on monitor recovery."Fri, 27 Feb 2026 05:27:08 +0000https://rewst.cronitorstatus.com/history/758fcaff67ada546https://rewst.cronitorstatus.com/history/b5cf0602db9b15f6[Unresolved] 2026-02-22 19:59 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-22 20:24 UTC - "Issue resolved on monitor recovery."Sun, 22 Feb 2026 19:59:35 +0000https://rewst.cronitorstatus.com/history/b5cf0602db9b15f6https://rewst.cronitorstatus.com/history/84caca3eab0781ea[Unresolved] 2026-02-14 09:16 UTC - "Issue opened on monitor failure." [Resolved] 2026-02-14 09:35 UTC - "Issue resolved on monitor recovery."Sat, 14 Feb 2026 09:16:13 +0000https://rewst.cronitorstatus.com/history/84caca3eab0781eahttps://rewst.cronitorstatus.com/history/71e6b37146f2b3b5[Investigating] 2026-01-13 19:50 UTC - "We're currently experiencing slower than normal workflow processing times in US. Our team is actively investigating and working to restore full performance. We'll provide updates as we learn more." [Monitoring] 2026-01-13 20:14 UTC [Resolved] 2026-01-13 20:51 UTCTue, 13 Jan 2026 19:50:29 +0000https://rewst.cronitorstatus.com/history/71e6b37146f2b3b5https://rewst.cronitorstatus.com/history/b33218e3baefbe1f[Investigating] 2026-01-09 14:40 UTC - "Our engineering team is aware of intermittent issues with the SQL integration; the Rewst team is all hands on deck working on the fix. We'll post an update when it's been resolved." [Resolved] 2026-01-12 18:46 UTCFri, 09 Jan 2026 14:40:15 +0000https://rewst.cronitorstatus.com/history/b33218e3baefbe1fhttps://rewst.cronitorstatus.com/history/7588126c389046c0[Identified] 2026-01-09 08:23 UTC - "On 9th January at 08:00, 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." [Monitoring] 2026-01-09 11:49 UTC - "At 11:40, the team deployed a fix and executions appear to be returning to normal behaviour. We are monitoring the situation and will update accordingly." [Monitoring] 2026-01-09 12:17 UTC - "At 12:15, we are seeing all executions acting as normal. We will continue monitoring." [Resolved] 2026-01-09 12:30 UTC - "All systems have returned to normal."Fri, 09 Jan 2026 08:23:00 +0000https://rewst.cronitorstatus.com/history/7588126c389046c0https://rewst.cronitorstatus.com/history/1ad32d3865877b61[Investigating] 2026-01-08 19:19 UTC - "Our engineering team is aware of intermittent issues with the SQL integration; the Rewst team is all hands on deck working on the fix. We'll post an update when it's been resolved." [Resolved] 2026-01-08 23:03 UTC - "The SQL Integration issues from earlier have now been resolved. The Rewst team is working on an RCA, which will be available on request from your CS rep. No additional action is required for the integration to function normally."Thu, 08 Jan 2026 19:19:54 +0000https://rewst.cronitorstatus.com/history/1ad32d3865877b61https://rewst.cronitorstatus.com/history/cde0faca6266a101[Investigating] 2025-12-19 14:22 UTC - "We're seeing a slow down of processing of webhooks in the EU environment. Our engineering team is currently investigating the issue" [Resolved] 2025-12-19 14:57 UTC - "We’ve resolved the issue and fully processed the backlog. All functionality has been restored."Fri, 19 Dec 2025 14:22:23 +0000https://rewst.cronitorstatus.com/history/cde0faca6266a101https://rewst.cronitorstatus.com/history/e0d9fe347d2dfb93[Unresolved] 2025-12-18 20:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-18 20:42 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-18 20:49 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-18 21:14 UTC - "Issue resolved on monitor recovery."Thu, 18 Dec 2025 20:27:05 +0000https://rewst.cronitorstatus.com/history/e0d9fe347d2dfb93https://rewst.cronitorstatus.com/history/54817dfa4631b978[Unresolved] 2025-12-17 18:50 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-17 18:51 UTC - "Issue resolved on monitor recovery."Wed, 17 Dec 2025 18:50:09 +0000https://rewst.cronitorstatus.com/history/54817dfa4631b978https://rewst.cronitorstatus.com/history/f56892c76dae2f99[Unresolved] 2025-12-16 21:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-16 21:07 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-17 02:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-17 02:19 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-17 02:22 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-17 02:29 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-17 02:33 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-17 02:35 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-17 03:02 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-17 03:06 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-17 05:03 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-17 05:12 UTC - "Issue resolved on monitor recovery."Tue, 16 Dec 2025 21:04:10 +0000https://rewst.cronitorstatus.com/history/f56892c76dae2f99https://rewst.cronitorstatus.com/history/eae6ea12bc2923df[Unresolved] 2025-12-16 15:40 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-16 15:47 UTC - "Issue resolved on monitor recovery."Tue, 16 Dec 2025 15:40:12 +0000https://rewst.cronitorstatus.com/history/eae6ea12bc2923dfhttps://rewst.cronitorstatus.com/history/3ee663912a82d2bb[Unresolved] 2025-12-10 23:25 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-11 01:12 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-11 04:28 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-11 04:32 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-12-11 04:43 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-12-11 04:45 UTC - "Issue resolved on monitor recovery."Wed, 10 Dec 2025 23:25:15 +0000https://rewst.cronitorstatus.com/history/3ee663912a82d2bbhttps://rewst.cronitorstatus.com/history/5e7e8bbed57dc06a[Unresolved] 2025-12-05 09:16 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-05 09:26 UTC - "Issue resolved on monitor recovery."Fri, 05 Dec 2025 09:16:55 +0000https://rewst.cronitorstatus.com/history/5e7e8bbed57dc06ahttps://rewst.cronitorstatus.com/history/5bcc097656b7eaf5[Unresolved] 2025-12-02 21:39 UTC - "Issue opened on monitor failure." [Resolved] 2025-12-02 21:44 UTC - "Issue resolved on monitor recovery."Tue, 02 Dec 2025 21:39:17 +0000https://rewst.cronitorstatus.com/history/5bcc097656b7eaf5https://rewst.cronitorstatus.com/history/f985bab3c9f8ce36[Unresolved] 2025-11-21 21:24 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-21 21:27 UTC - "Issue resolved on monitor recovery."Fri, 21 Nov 2025 21:24:45 +0000https://rewst.cronitorstatus.com/history/f985bab3c9f8ce36https://rewst.cronitorstatus.com/history/4c26d99171be0a82[Unresolved] 2025-11-19 19:57 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-19 19:59 UTC - "Issue resolved on monitor recovery."Wed, 19 Nov 2025 19:57:02 +0000https://rewst.cronitorstatus.com/history/4c26d99171be0a82https://rewst.cronitorstatus.com/history/915eba7d158334d1[Unresolved] 2025-11-19 18:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-19 18:44 UTC - "Issue resolved on monitor recovery."Wed, 19 Nov 2025 18:41:43 +0000https://rewst.cronitorstatus.com/history/915eba7d158334d1https://rewst.cronitorstatus.com/history/780b4afdd49f8270[Unresolved] 2025-11-18 12:20 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-18 12:22 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-11-18 12:51 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-11-18 12:53 UTC - "Issue resolved on monitor recovery."Tue, 18 Nov 2025 12:20:18 +0000https://rewst.cronitorstatus.com/history/780b4afdd49f8270https://rewst.cronitorstatus.com/history/7fa9a0445d59fc4d[Unresolved] 2025-11-17 17:36 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-17 17:45 UTC - "Issue resolved on monitor recovery."Mon, 17 Nov 2025 17:36:03 +0000https://rewst.cronitorstatus.com/history/7fa9a0445d59fc4dhttps://rewst.cronitorstatus.com/history/aec24373593752a8[Unresolved] 2025-11-17 13:17 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-17 13:23 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-11-17 13:26 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-11-17 13:27 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-11-17 13:28 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-11-17 13:29 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-11-17 13:30 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-11-17 13:32 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-11-17 13:34 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-11-17 13:35 UTC - "Issue resolved on monitor recovery."Mon, 17 Nov 2025 13:17:16 +0000https://rewst.cronitorstatus.com/history/aec24373593752a8https://rewst.cronitorstatus.com/history/ac6128778d71b5c3[Unresolved] 2025-11-12 12:51 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-12 12:53 UTC - "Issue resolved on monitor recovery."Wed, 12 Nov 2025 12:51:32 +0000https://rewst.cronitorstatus.com/history/ac6128778d71b5c3https://rewst.cronitorstatus.com/history/3728f2bef248ae80[Monitoring] 2025-11-11 19:36 UTC - "We’re currently seeing an issue with our certificate provider, ZeroSSL, that’s preventing new certificates from being issued. This affects new app provisioning and may also impact certificate renewals for existing apps if the issue continues. We’re actively monitoring the situation and will provide updates as soon as we have more information." [Resolved] 2025-11-12 13:51 UTCTue, 11 Nov 2025 19:36:00 +0000https://rewst.cronitorstatus.com/history/3728f2bef248ae80https://rewst.cronitorstatus.com/history/9ce7cbc22f35bb26[Unresolved] 2025-11-11 19:26 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-11 19:29 UTC - "Issue resolved on monitor recovery."Tue, 11 Nov 2025 19:26:26 +0000https://rewst.cronitorstatus.com/history/9ce7cbc22f35bb26https://rewst.cronitorstatus.com/history/bff5c6f341031a7b[Unresolved] 2025-11-10 21:07 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-10 21:16 UTC - "Issue resolved on monitor recovery."Mon, 10 Nov 2025 21:07:58 +0000https://rewst.cronitorstatus.com/history/bff5c6f341031a7bhttps://rewst.cronitorstatus.com/history/bf3aea55d3f96d83[Unresolved] 2025-11-07 12:17 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-07 12:20 UTC - "Issue resolved on monitor recovery."Fri, 07 Nov 2025 12:17:41 +0000https://rewst.cronitorstatus.com/history/bf3aea55d3f96d83https://rewst.cronitorstatus.com/history/8a06397c5b48041e[Unresolved] 2025-11-06 23:47 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-07 00:35 UTC - "Issue resolved on monitor recovery."Thu, 06 Nov 2025 23:47:12 +0000https://rewst.cronitorstatus.com/history/8a06397c5b48041ehttps://rewst.cronitorstatus.com/history/0ae455ae908600d7[Unresolved] 2025-11-04 13:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-04 14:04 UTC - "Issue resolved on monitor recovery."Tue, 04 Nov 2025 13:54:35 +0000https://rewst.cronitorstatus.com/history/0ae455ae908600d7https://rewst.cronitorstatus.com/history/46b56265617940d3[Unresolved] 2025-11-04 10:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-11-04 10:04 UTC - "Issue resolved on monitor recovery."Tue, 04 Nov 2025 10:01:52 +0000https://rewst.cronitorstatus.com/history/46b56265617940d3https://rewst.cronitorstatus.com/history/7043a41af0fe38eb[Unresolved] 2025-10-31 20:51 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-31 20:54 UTC - "Issue resolved on monitor recovery."Fri, 31 Oct 2025 20:51:47 +0000https://rewst.cronitorstatus.com/history/7043a41af0fe38ebhttps://rewst.cronitorstatus.com/history/8dc51a4d53aca031[Unresolved] 2025-10-31 07:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-31 07:30 UTC - "Issue resolved on monitor recovery."Fri, 31 Oct 2025 07:27:45 +0000https://rewst.cronitorstatus.com/history/8dc51a4d53aca031https://rewst.cronitorstatus.com/history/159a63170898d432[Unresolved] 2025-10-30 00:15 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-30 01:10 UTC - "Issue resolved on monitor recovery."Thu, 30 Oct 2025 00:15:15 +0000https://rewst.cronitorstatus.com/history/159a63170898d432https://rewst.cronitorstatus.com/history/56881a5138106983[Unresolved] 2025-10-29 18:03 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-29 18:05 UTC - "Issue resolved on monitor recovery."Wed, 29 Oct 2025 18:03:20 +0000https://rewst.cronitorstatus.com/history/56881a5138106983https://rewst.cronitorstatus.com/history/08f9d083b84eea70[Unresolved] 2025-10-29 09:53 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-29 10:06 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-29 10:22 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-29 10:23 UTC - "Issue resolved on monitor recovery."Wed, 29 Oct 2025 09:53:25 +0000https://rewst.cronitorstatus.com/history/08f9d083b84eea70https://rewst.cronitorstatus.com/history/664a86806274989a[Unresolved] 2025-10-28 17:11 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-28 17:14 UTC - "Issue resolved on monitor recovery."Tue, 28 Oct 2025 17:11:57 +0000https://rewst.cronitorstatus.com/history/664a86806274989ahttps://rewst.cronitorstatus.com/history/cc6d37214bda7ab8[Unresolved] 2025-10-26 21:37 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-26 21:39 UTC - "Issue resolved on monitor recovery."Sun, 26 Oct 2025 21:37:08 +0000https://rewst.cronitorstatus.com/history/cc6d37214bda7ab8https://rewst.cronitorstatus.com/history/ec2959141a208fe7[Unresolved] 2025-10-24 15:06 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-24 15:09 UTC - "Issue resolved on monitor recovery."Fri, 24 Oct 2025 15:06:54 +0000https://rewst.cronitorstatus.com/history/ec2959141a208fe7https://rewst.cronitorstatus.com/history/114a8ab0a07e19e5[Unresolved] 2025-10-24 02:55 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-24 03:14 UTC - "Issue resolved on monitor recovery."Fri, 24 Oct 2025 02:55:51 +0000https://rewst.cronitorstatus.com/history/114a8ab0a07e19e5https://rewst.cronitorstatus.com/history/9ed90f63ab1853fb[Unresolved] 2025-10-21 15:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-21 15:23 UTC - "Issue resolved on monitor recovery."Tue, 21 Oct 2025 15:21:38 +0000https://rewst.cronitorstatus.com/history/9ed90f63ab1853fbhttps://rewst.cronitorstatus.com/history/bf43411132457dc4[Unresolved] 2025-10-21 12:32 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-21 12:34 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-21 12:58 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-21 12:59 UTC - "Issue resolved on monitor recovery."Tue, 21 Oct 2025 12:32:12 +0000https://rewst.cronitorstatus.com/history/bf43411132457dc4https://rewst.cronitorstatus.com/history/ab210cf142ea7a83[Unresolved] 2025-10-21 01:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-21 01:23 UTC - "Issue resolved on monitor recovery."Tue, 21 Oct 2025 01:21:31 +0000https://rewst.cronitorstatus.com/history/ab210cf142ea7a83https://rewst.cronitorstatus.com/history/f9bc23a6b28bb769[Unresolved] 2025-10-20 15:49 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-20 15:51 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-20 15:57 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-20 15:59 UTC - "Issue resolved on monitor recovery."Mon, 20 Oct 2025 15:49:21 +0000https://rewst.cronitorstatus.com/history/f9bc23a6b28bb769https://rewst.cronitorstatus.com/history/a4798b19cf07ba19[Unresolved] 2025-10-20 08:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-20 08:49 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-20 08:52 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-20 08:53 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-20 09:25 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-20 09:26 UTC - "Issue resolved on monitor recovery."Mon, 20 Oct 2025 08:46:55 +0000https://rewst.cronitorstatus.com/history/a4798b19cf07ba19https://rewst.cronitorstatus.com/history/d45db8a91e7fe1b7[Unresolved] 2025-10-17 14:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-17 14:05 UTC - "Issue resolved on monitor recovery."Fri, 17 Oct 2025 14:01:57 +0000https://rewst.cronitorstatus.com/history/d45db8a91e7fe1b7https://rewst.cronitorstatus.com/history/ad0472da4939418b[Unresolved] 2025-10-15 17:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-15 17:34 UTC - "Issue resolved on monitor recovery."Wed, 15 Oct 2025 17:31:43 +0000https://rewst.cronitorstatus.com/history/ad0472da4939418bhttps://rewst.cronitorstatus.com/history/6c58de11f1b3adf8[Unresolved] 2025-10-13 13:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-13 13:04 UTC - "Issue resolved on monitor recovery."Mon, 13 Oct 2025 13:01:33 +0000https://rewst.cronitorstatus.com/history/6c58de11f1b3adf8https://rewst.cronitorstatus.com/history/4d5c86edcc71be7b[Unresolved] 2025-10-12 22:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-12 22:55 UTC - "Issue resolved on monitor recovery."Sun, 12 Oct 2025 22:54:08 +0000https://rewst.cronitorstatus.com/history/4d5c86edcc71be7bhttps://rewst.cronitorstatus.com/history/7bb547908a395c11[Unresolved] 2025-10-11 03:28 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-11 03:29 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-11 03:35 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-11 03:36 UTC - "Issue resolved on monitor recovery."Sat, 11 Oct 2025 03:28:37 +0000https://rewst.cronitorstatus.com/history/7bb547908a395c11https://rewst.cronitorstatus.com/history/4055b24460b70cd0[Unresolved] 2025-10-11 00:16 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-11 00:19 UTC - "Issue resolved on monitor recovery."Sat, 11 Oct 2025 00:16:37 +0000https://rewst.cronitorstatus.com/history/4055b24460b70cd0https://rewst.cronitorstatus.com/history/c863aa666bf829f3[Unresolved] 2025-10-10 22:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-10 23:01 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-10 23:40 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 23:44 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-10 23:54 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 23:56 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-11 00:24 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-11 00:24 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-11 00:39 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-11 00:43 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-11 00:54 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-11 00:54 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-11 01:25 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-11 01:28 UTC - "Issue resolved on monitor recovery."Fri, 10 Oct 2025 22:54:14 +0000https://rewst.cronitorstatus.com/history/c863aa666bf829f3https://rewst.cronitorstatus.com/history/efec4a39a2e55763[Unresolved] 2025-10-10 22:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-10 22:44 UTC - "Issue resolved on monitor recovery."Fri, 10 Oct 2025 22:41:57 +0000https://rewst.cronitorstatus.com/history/efec4a39a2e55763https://rewst.cronitorstatus.com/history/fc296cbb40f58616[Unresolved] 2025-10-09 22:52 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-09 22:59 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-09 23:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 00:01 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-10 00:18 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 00:22 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-10 00:28 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 00:31 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-10 00:40 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-10 00:41 UTC - "Issue resolved on monitor recovery."Thu, 09 Oct 2025 22:52:29 +0000https://rewst.cronitorstatus.com/history/fc296cbb40f58616https://rewst.cronitorstatus.com/history/143c6d91776344af[Unresolved] 2025-10-09 06:19 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-09 06:24 UTC - "Issue resolved on monitor recovery."Thu, 09 Oct 2025 06:19:58 +0000https://rewst.cronitorstatus.com/history/143c6d91776344afhttps://rewst.cronitorstatus.com/history/d9020170277cb10e[Unresolved] 2025-10-09 01:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-09 01:53 UTC - "Issue resolved on monitor recovery."Thu, 09 Oct 2025 01:31:41 +0000https://rewst.cronitorstatus.com/history/d9020170277cb10ehttps://rewst.cronitorstatus.com/history/defd27adc2943fb7[Unresolved] 2025-10-08 23:13 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-08 23:18 UTC - "Issue resolved on monitor recovery."Wed, 08 Oct 2025 23:13:51 +0000https://rewst.cronitorstatus.com/history/defd27adc2943fb7https://rewst.cronitorstatus.com/history/186fab61d58e5892[Unresolved] 2025-10-08 15:33 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-08 15:34 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-08 15:46 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-08 15:49 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-08 16:05 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-08 16:12 UTC - "Issue resolved on monitor recovery."Wed, 08 Oct 2025 15:33:05 +0000https://rewst.cronitorstatus.com/history/186fab61d58e5892https://rewst.cronitorstatus.com/history/acb3cf6e2f2d7a9b[Unresolved] 2025-10-08 08:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-08 08:06 UTC - "Issue resolved on monitor recovery."Wed, 08 Oct 2025 08:04:22 +0000https://rewst.cronitorstatus.com/history/acb3cf6e2f2d7a9bhttps://rewst.cronitorstatus.com/history/e90b6e75eb0ea71a[Unresolved] 2025-10-08 06:16 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-08 06:18 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-08 06:27 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-08 06:30 UTC - "Issue resolved on monitor recovery."Wed, 08 Oct 2025 06:16:37 +0000https://rewst.cronitorstatus.com/history/e90b6e75eb0ea71ahttps://rewst.cronitorstatus.com/history/f86e188349e37a3f[Unresolved] 2025-10-08 03:23 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-08 03:26 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-10-08 03:34 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-10-08 03:35 UTC - "Issue resolved on monitor recovery."Wed, 08 Oct 2025 03:23:59 +0000https://rewst.cronitorstatus.com/history/f86e188349e37a3fhttps://rewst.cronitorstatus.com/history/50e25366a9b331ca[Unresolved] 2025-10-07 08:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-07 08:44 UTC - "Issue resolved on monitor recovery."Tue, 07 Oct 2025 08:41:50 +0000https://rewst.cronitorstatus.com/history/50e25366a9b331cahttps://rewst.cronitorstatus.com/history/675c3209fe1d52fd[Unresolved] 2025-10-06 20:42 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-06 20:44 UTC - "Issue resolved on monitor recovery."Mon, 06 Oct 2025 20:42:18 +0000https://rewst.cronitorstatus.com/history/675c3209fe1d52fdhttps://rewst.cronitorstatus.com/history/1e1ed4bcb46be0d1[Unresolved] 2025-10-03 18:42 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-03 18:44 UTC - "Issue resolved on monitor recovery."Fri, 03 Oct 2025 18:42:21 +0000https://rewst.cronitorstatus.com/history/1e1ed4bcb46be0d1https://rewst.cronitorstatus.com/history/ea77d1ffc72dfdcb[Unresolved] 2025-10-03 13:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-03 13:44 UTC - "Issue resolved on monitor recovery."Fri, 03 Oct 2025 13:41:48 +0000https://rewst.cronitorstatus.com/history/ea77d1ffc72dfdcbhttps://rewst.cronitorstatus.com/history/508a89aaa9f78a1e[Unresolved] 2025-10-02 11:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-10-02 11:44 UTC - "Issue resolved on monitor recovery."Thu, 02 Oct 2025 11:41:54 +0000https://rewst.cronitorstatus.com/history/508a89aaa9f78a1ehttps://rewst.cronitorstatus.com/history/69d156b2d03fd3cd[Unresolved] 2025-09-29 01:35 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-29 01:36 UTC - "Issue resolved on monitor recovery."Mon, 29 Sep 2025 01:35:24 +0000https://rewst.cronitorstatus.com/history/69d156b2d03fd3cdhttps://rewst.cronitorstatus.com/history/40a06a6289935bd1[Unresolved] 2025-09-26 09:06 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-26 09:09 UTC - "Issue resolved on monitor recovery."Fri, 26 Sep 2025 09:06:33 +0000https://rewst.cronitorstatus.com/history/40a06a6289935bd1https://rewst.cronitorstatus.com/history/0a0003db277f68fe[Unresolved] 2025-09-23 17:07 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-24 04:59 UTC - "Issue resolved on monitor recovery."Tue, 23 Sep 2025 17:07:18 +0000https://rewst.cronitorstatus.com/history/0a0003db277f68fehttps://rewst.cronitorstatus.com/history/514a03029697b5d0[Unresolved] 2025-09-22 13:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-22 13:29 UTC - "Issue resolved on monitor recovery."Mon, 22 Sep 2025 13:27:40 +0000https://rewst.cronitorstatus.com/history/514a03029697b5d0https://rewst.cronitorstatus.com/history/c812280f3c3d6da4[Unresolved] 2025-09-22 12:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-22 12:05 UTC - "Issue resolved on monitor recovery."Mon, 22 Sep 2025 12:02:34 +0000https://rewst.cronitorstatus.com/history/c812280f3c3d6da4https://rewst.cronitorstatus.com/history/83a6a48d6af9fe3e[Unresolved] 2025-09-19 13:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-19 13:04 UTC - "Issue resolved on monitor recovery."Fri, 19 Sep 2025 13:02:11 +0000https://rewst.cronitorstatus.com/history/83a6a48d6af9fe3ehttps://rewst.cronitorstatus.com/history/19d8679b800a05e2[Unresolved] 2025-09-18 18:56 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-18 18:59 UTC - "Issue resolved on monitor recovery."Thu, 18 Sep 2025 18:56:58 +0000https://rewst.cronitorstatus.com/history/19d8679b800a05e2https://rewst.cronitorstatus.com/history/fc503d4e618d5a7b[Unresolved] 2025-09-17 21:05 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-17 21:10 UTC - "Issue resolved on monitor recovery."Wed, 17 Sep 2025 21:05:02 +0000https://rewst.cronitorstatus.com/history/fc503d4e618d5a7bhttps://rewst.cronitorstatus.com/history/19fa69706fde9106[Unresolved] 2025-09-17 17:52 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-17 17:55 UTC - "Issue resolved on monitor recovery."Wed, 17 Sep 2025 17:52:17 +0000https://rewst.cronitorstatus.com/history/19fa69706fde9106https://rewst.cronitorstatus.com/history/9b13dfedd4db097e[Unresolved] 2025-09-16 14:17 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-16 14:19 UTC - "Issue resolved on monitor recovery."Tue, 16 Sep 2025 14:17:14 +0000https://rewst.cronitorstatus.com/history/9b13dfedd4db097ehttps://rewst.cronitorstatus.com/history/974bba79eda60a1e[Unresolved] 2025-09-16 12:41 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-16 12:44 UTC - "Issue resolved on monitor recovery."Tue, 16 Sep 2025 12:41:49 +0000https://rewst.cronitorstatus.com/history/974bba79eda60a1ehttps://rewst.cronitorstatus.com/history/c5a70e6347175866[Unresolved] 2025-09-15 15:51 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-15 15:54 UTC - "Issue resolved on monitor recovery."Mon, 15 Sep 2025 15:51:37 +0000https://rewst.cronitorstatus.com/history/c5a70e6347175866https://rewst.cronitorstatus.com/history/0fe17001c77efdec[Unresolved] 2025-09-12 17:11 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-12 17:13 UTC - "Issue resolved on monitor recovery."Fri, 12 Sep 2025 17:11:41 +0000https://rewst.cronitorstatus.com/history/0fe17001c77efdechttps://rewst.cronitorstatus.com/history/3648a9f578ab246c[Unresolved] 2025-09-12 10:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-12 10:29 UTC - "Issue resolved on monitor recovery."Fri, 12 Sep 2025 10:27:29 +0000https://rewst.cronitorstatus.com/history/3648a9f578ab246chttps://rewst.cronitorstatus.com/history/ac0be39e54c0752b[Unresolved] 2025-09-12 08:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-12 08:29 UTC - "Issue resolved on monitor recovery."Fri, 12 Sep 2025 08:27:09 +0000https://rewst.cronitorstatus.com/history/ac0be39e54c0752bhttps://rewst.cronitorstatus.com/history/639ead3b1a495ffc[Unresolved] 2025-09-09 13:13 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-09 13:16 UTC - "Issue resolved on monitor recovery."Tue, 09 Sep 2025 13:13:19 +0000https://rewst.cronitorstatus.com/history/639ead3b1a495ffchttps://rewst.cronitorstatus.com/history/80155dc48551e691[Unresolved] 2025-09-09 10:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-09 10:04 UTC - "Issue resolved on monitor recovery."Tue, 09 Sep 2025 10:02:14 +0000https://rewst.cronitorstatus.com/history/80155dc48551e691https://rewst.cronitorstatus.com/history/e9ca4b3fabd7a7d1[Unresolved] 2025-09-08 10:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-08 10:04 UTC - "Issue resolved on monitor recovery."Mon, 08 Sep 2025 10:01:45 +0000https://rewst.cronitorstatus.com/history/e9ca4b3fabd7a7d1https://rewst.cronitorstatus.com/history/082870420ffb83cf[Unresolved] 2025-09-08 08:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-08 08:24 UTC - "Issue resolved on monitor recovery."Mon, 08 Sep 2025 08:21:52 +0000https://rewst.cronitorstatus.com/history/082870420ffb83cfhttps://rewst.cronitorstatus.com/history/839304681bf4d258[Unresolved] 2025-09-05 15:01 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-05 15:04 UTC - "Issue resolved on monitor recovery."Fri, 05 Sep 2025 15:01:59 +0000https://rewst.cronitorstatus.com/history/839304681bf4d258https://rewst.cronitorstatus.com/history/fd8bf92fd71b895e[Unresolved] 2025-09-03 22:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-03 22:05 UTC - "Issue resolved on monitor recovery."Wed, 03 Sep 2025 22:02:45 +0000https://rewst.cronitorstatus.com/history/fd8bf92fd71b895ehttps://rewst.cronitorstatus.com/history/32c5b4401ed9ffe3[Unresolved] 2025-09-03 13:19 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-03 13:21 UTC - "Issue resolved on monitor recovery."Wed, 03 Sep 2025 13:19:00 +0000https://rewst.cronitorstatus.com/history/32c5b4401ed9ffe3https://rewst.cronitorstatus.com/history/75b7e5a4a51159d1[Unresolved] 2025-09-03 09:47 UTC - "Issue opened on monitor failure." [Resolved] 2025-09-03 09:49 UTC - "Issue resolved on monitor recovery."Wed, 03 Sep 2025 09:47:03 +0000https://rewst.cronitorstatus.com/history/75b7e5a4a51159d1https://rewst.cronitorstatus.com/history/56eee9e4c96bde3e[Unresolved] 2025-08-28 19:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-28 19:24 UTC - "Issue resolved on monitor recovery."Thu, 28 Aug 2025 19:21:09 +0000https://rewst.cronitorstatus.com/history/56eee9e4c96bde3ehttps://rewst.cronitorstatus.com/history/355a632c5cecf7ba[Unresolved] 2025-08-28 15:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-28 15:34 UTC - "Issue resolved on monitor recovery."Thu, 28 Aug 2025 15:31:46 +0000https://rewst.cronitorstatus.com/history/355a632c5cecf7bahttps://rewst.cronitorstatus.com/history/977eced73ed7afa0[Unresolved] 2025-08-25 14:16 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-25 14:19 UTC - "Issue resolved on monitor recovery."Mon, 25 Aug 2025 14:16:55 +0000https://rewst.cronitorstatus.com/history/977eced73ed7afa0https://rewst.cronitorstatus.com/history/fd17278f4448fb9e[Unresolved] 2025-08-22 07:34 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-22 07:36 UTC - "Issue resolved on monitor recovery."Fri, 22 Aug 2025 07:34:07 +0000https://rewst.cronitorstatus.com/history/fd17278f4448fb9ehttps://rewst.cronitorstatus.com/history/9e4d0a496460adf8[Unresolved] 2025-08-19 13:47 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-19 13:50 UTC - "Issue resolved on monitor recovery."Tue, 19 Aug 2025 13:47:37 +0000https://rewst.cronitorstatus.com/history/9e4d0a496460adf8https://rewst.cronitorstatus.com/history/89a450b2eb5a3fc6[Unresolved] 2025-08-14 20:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-14 20:48 UTC - "Issue resolved on monitor recovery."Thu, 14 Aug 2025 20:46:47 +0000https://rewst.cronitorstatus.com/history/89a450b2eb5a3fc6https://rewst.cronitorstatus.com/history/9f2470edec9ebb9c[Unresolved] 2025-08-13 19:12 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-13 19:14 UTC - "Issue resolved on monitor recovery."Wed, 13 Aug 2025 19:12:00 +0000https://rewst.cronitorstatus.com/history/9f2470edec9ebb9chttps://rewst.cronitorstatus.com/history/12b47f8f028ce5fd[Unresolved] 2025-08-11 16:42 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-11 16:46 UTC - "Issue resolved on monitor recovery."Mon, 11 Aug 2025 16:42:52 +0000https://rewst.cronitorstatus.com/history/12b47f8f028ce5fdhttps://rewst.cronitorstatus.com/history/c49a205471fa6dc5[Unresolved] 2025-08-08 03:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-08 03:38 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-08-08 03:42 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-08-08 03:46 UTC - "Issue resolved on monitor recovery." [Resolved] 2025-08-08 18:17 UTC - "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."Fri, 08 Aug 2025 03:31:41 +0000https://rewst.cronitorstatus.com/history/c49a205471fa6dc5https://rewst.cronitorstatus.com/history/7b1300dab286d030[Unresolved] 2025-08-07 20:32 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-07 20:34 UTC - "Issue resolved on monitor recovery."Thu, 07 Aug 2025 20:32:26 +0000https://rewst.cronitorstatus.com/history/7b1300dab286d030https://rewst.cronitorstatus.com/history/a7058706ee469599[Unresolved] 2025-08-06 16:12 UTC - "Issue opened on monitor failure." [Identified] 2025-08-06 16:17 UTC [Identified] 2025-08-06 16:17 UTC - "The 3rd party LMS provider has identified the issue and is in the process of remediation" [Monitoring] 2025-08-06 17:26 UTC [Resolved] 2025-08-06 17:27 UTC - "Issue resolved on monitor recovery."Wed, 06 Aug 2025 16:12:54 +0000https://rewst.cronitorstatus.com/history/a7058706ee469599https://rewst.cronitorstatus.com/history/1f46d9031aa63d1c[Unresolved] 2025-07-29 00:11 UTC - "Issue opened on monitor failure." [Resolved] 2025-07-29 00:31 UTC - "Issue resolved on monitor recovery." [Resolved] 2025-07-29 13:12 UTC - "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."Tue, 29 Jul 2025 00:11:19 +0000https://rewst.cronitorstatus.com/history/1f46d9031aa63d1chttps://rewst.cronitorstatus.com/history/e5d158e694633d4f[Unresolved] 2025-07-17 18:09 UTC - "Issue opened on monitor failure." [Resolved] 2025-07-17 18:21 UTC - "Issue resolved on monitor recovery." [Resolved] 2025-07-17 18:27 UTC - "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." [Resolved] 2025-07-17 18:51 UTC - "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."Thu, 17 Jul 2025 18:09:07 +0000https://rewst.cronitorstatus.com/history/e5d158e694633d4fhttps://rewst.cronitorstatus.com/history/c3f2e42cd2bdef61[Unresolved] 2025-07-11 02:50 UTC - "Issue opened on monitor failure." [Resolved] 2025-07-11 03:14 UTC - "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."Fri, 11 Jul 2025 02:50:49 +0000https://rewst.cronitorstatus.com/history/c3f2e42cd2bdef61https://rewst.cronitorstatus.com/history/1b51472815b7c801[Investigating] 2025-07-07 21:10 UTC - "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] 2025-07-07 21:25 UTC - "Resolved"Mon, 07 Jul 2025 21:10:00 +0000https://rewst.cronitorstatus.com/history/1b51472815b7c801https://rewst.cronitorstatus.com/history/c7b46b0e57a88551[Resolved] 2025-06-12 06:45 UTC - "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."Thu, 12 Jun 2025 06:45:00 +0000https://rewst.cronitorstatus.com/history/c7b46b0e57a88551https://rewst.cronitorstatus.com/history/99e9b88a18680ea0[Unresolved] 2025-06-10 22:40 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-10 22:44 UTC - "Issue resolved on monitor recovery."Tue, 10 Jun 2025 22:40:53 +0000https://rewst.cronitorstatus.com/history/99e9b88a18680ea0https://rewst.cronitorstatus.com/history/b7bd458cae92e78e[Unresolved] 2025-06-06 13:08 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-06 13:13 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-06 13:30 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-06 14:04 UTC - "Issue resolved on monitor recovery."Fri, 06 Jun 2025 13:08:41 +0000https://rewst.cronitorstatus.com/history/b7bd458cae92e78ehttps://rewst.cronitorstatus.com/history/ed1ca2039bed2138[Identified] 2025-06-06 12:15 UTC - "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" [Monitoring] 2025-06-06 14:00 UTC [Resolved] 2025-06-06 14:15 UTCFri, 06 Jun 2025 12:15:00 +0000https://rewst.cronitorstatus.com/history/ed1ca2039bed2138https://rewst.cronitorstatus.com/history/bffb4c7c809f12b0[Unresolved] 2025-06-05 13:06 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-05 13:25 UTC - "Issue resolved on monitor recovery."Thu, 05 Jun 2025 13:06:48 +0000https://rewst.cronitorstatus.com/history/bffb4c7c809f12b0https://rewst.cronitorstatus.com/history/169ff9c0321d90a9[Unresolved] 2025-06-04 20:49 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-04 20:52 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-04 21:02 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-04 21:04 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-04 21:51 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-04 21:52 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-04 22:07 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-04 22:09 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-04 22:22 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-04 22:23 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-06-04 22:50 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-06-04 22:51 UTC - "Issue resolved on monitor recovery."Wed, 04 Jun 2025 20:49:36 +0000https://rewst.cronitorstatus.com/history/169ff9c0321d90a9https://rewst.cronitorstatus.com/history/2517e6e6acc2cdd8[Unresolved] 2025-06-01 16:49 UTC - "Issue opened on monitor failure." [Resolved] 2025-06-01 17:05 UTC - "Issue resolved on monitor recovery."Sun, 01 Jun 2025 16:49:32 +0000https://rewst.cronitorstatus.com/history/2517e6e6acc2cdd8https://rewst.cronitorstatus.com/history/335b1707a2e00415[Unresolved] 2025-05-28 10:19 UTC - "Issue opened on monitor failure." [Resolved] 2025-05-28 10:30 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-05-28 11:05 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-05-28 11:13 UTC - "Issue resolved on monitor recovery."Wed, 28 May 2025 10:19:01 +0000https://rewst.cronitorstatus.com/history/335b1707a2e00415https://rewst.cronitorstatus.com/history/010edb6ce949d037[Unresolved] 2025-05-23 15:06 UTC - "Issue opened on monitor failure." [Resolved] 2025-05-23 15:16 UTC - "Issue resolved on monitor recovery."Fri, 23 May 2025 15:06:04 +0000https://rewst.cronitorstatus.com/history/010edb6ce949d037https://rewst.cronitorstatus.com/history/4a9f32fab9f72916[Unresolved] 2025-05-01 16:42 UTC - "Issue opened on monitor failure." [Resolved] 2025-05-01 16:52 UTC - "Issue resolved on monitor recovery."Thu, 01 May 2025 16:42:12 +0000https://rewst.cronitorstatus.com/history/4a9f32fab9f72916https://rewst.cronitorstatus.com/history/8e7e53ad91acaae9[Unresolved] 2025-05-01 12:55 UTC - "Issue opened on monitor failure." [Resolved] 2025-05-01 12:57 UTC - "Issue resolved on monitor recovery." [Unresolved] 2025-05-01 13:04 UTC - "Issue re-opened on monitor failure." [Resolved] 2025-05-01 13:05 UTC - "Issue resolved on monitor recovery."Thu, 01 May 2025 12:55:48 +0000https://rewst.cronitorstatus.com/history/8e7e53ad91acaae9https://rewst.cronitorstatus.com/history/b3585049151c95dd[Unresolved] 2025-04-24 15:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-24 15:09 UTC - "Issue resolved on monitor recovery."Thu, 24 Apr 2025 15:04:49 +0000https://rewst.cronitorstatus.com/history/b3585049151c95ddhttps://rewst.cronitorstatus.com/history/c064b470e2002df5[Unresolved] 2025-04-17 01:17 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-17 01:19 UTC - "Issue resolved on monitor recovery."Thu, 17 Apr 2025 01:17:55 +0000https://rewst.cronitorstatus.com/history/c064b470e2002df5https://rewst.cronitorstatus.com/history/86ebb7b8bdd733ca[Investigating] 2025-04-09 14:21 UTC - "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." [Identified] 2025-04-09 15:30 UTC [Resolved] 2025-04-10 00:10 UTC - "Patch released"Wed, 09 Apr 2025 14:21:00 +0000https://rewst.cronitorstatus.com/history/86ebb7b8bdd733cahttps://rewst.cronitorstatus.com/history/b05ea93e3852cc2c[Unresolved] 2025-04-04 18:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-04 18:45 UTC - "Issue resolved on monitor recovery."Fri, 04 Apr 2025 18:31:04 +0000https://rewst.cronitorstatus.com/history/b05ea93e3852cc2chttps://rewst.cronitorstatus.com/history/dbfda31de6f2bdec[Unresolved] 2025-04-03 19:02 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-03 19:04 UTC - "Issue resolved on monitor recovery."Thu, 03 Apr 2025 19:02:29 +0000https://rewst.cronitorstatus.com/history/dbfda31de6f2bdechttps://rewst.cronitorstatus.com/history/5ec6f4649e77ee9f[Unresolved] 2025-04-03 16:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-03 16:23 UTC - "Issue resolved on monitor recovery."Thu, 03 Apr 2025 16:21:19 +0000https://rewst.cronitorstatus.com/history/5ec6f4649e77ee9fhttps://rewst.cronitorstatus.com/history/bebb78cc46041934[Investigating] 2025-04-03 16:15 UTC - "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." [Resolved] 2025-04-04 06:39 UTC - "Identified and patched issue with Organizations list query causing database performance issues."Thu, 03 Apr 2025 16:15:00 +0000https://rewst.cronitorstatus.com/history/bebb78cc46041934https://rewst.cronitorstatus.com/history/077eab72db7942fa[Unresolved] 2025-04-02 21:07 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-02 21:14 UTC - "Issue resolved on monitor recovery."Wed, 02 Apr 2025 21:07:49 +0000https://rewst.cronitorstatus.com/history/077eab72db7942fahttps://rewst.cronitorstatus.com/history/4b5e72fb38631e6b[Unresolved] 2025-02-19 15:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-19 15:36 UTC - "Issue resolved on monitor recovery."Wed, 19 Feb 2025 15:31:53 +0000https://rewst.cronitorstatus.com/history/4b5e72fb38631e6bhttps://rewst.cronitorstatus.com/history/d6931f20946a646c[Unresolved] 2025-02-18 00:54 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-18 01:04 UTC - "Issue resolved on monitor recovery."Tue, 18 Feb 2025 00:54:29 +0000https://rewst.cronitorstatus.com/history/d6931f20946a646chttps://rewst.cronitorstatus.com/history/f940c5089182f9be[Unresolved] 2025-02-17 17:15 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-17 17:26 UTC - "Issue resolved on monitor recovery."Mon, 17 Feb 2025 17:15:43 +0000https://rewst.cronitorstatus.com/history/f940c5089182f9behttps://rewst.cronitorstatus.com/history/c952fb2f4939788d[Investigating] 2025-02-17 10:11 UTC - "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." [Resolved] 2025-02-17 18:02 UTC - "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."Mon, 17 Feb 2025 10:11:00 +0000https://rewst.cronitorstatus.com/history/c952fb2f4939788dhttps://rewst.cronitorstatus.com/history/3c6fab8579ba05e4[Unresolved] 2025-02-17 07:31 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-17 07:36 UTC - "Issue resolved on monitor recovery."Mon, 17 Feb 2025 07:31:36 +0000https://rewst.cronitorstatus.com/history/3c6fab8579ba05e4https://rewst.cronitorstatus.com/history/e706c521ab3e2337[Unresolved] 2025-02-14 12:09 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-14 12:11 UTC - "Issue resolved on monitor recovery."Fri, 14 Feb 2025 12:09:35 +0000https://rewst.cronitorstatus.com/history/e706c521ab3e2337https://rewst.cronitorstatus.com/history/9dc808546b58c167[Unresolved] 2025-02-12 14:27 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-12 14:40 UTC - "Issue resolved on monitor recovery."Wed, 12 Feb 2025 14:27:33 +0000https://rewst.cronitorstatus.com/history/9dc808546b58c167https://rewst.cronitorstatus.com/history/0ea41f656330ae48[Unresolved] 2025-02-12 10:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-12 10:26 UTC - "Issue resolved on monitor recovery."Wed, 12 Feb 2025 10:04:36 +0000https://rewst.cronitorstatus.com/history/0ea41f656330ae48https://rewst.cronitorstatus.com/history/aa61f84c38bd20b7[Unresolved] 2025-02-11 06:43 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-11 06:50 UTC - "Issue resolved on monitor recovery."Tue, 11 Feb 2025 06:43:50 +0000https://rewst.cronitorstatus.com/history/aa61f84c38bd20b7https://rewst.cronitorstatus.com/history/e77c02f130824ae8[Unresolved] 2025-02-10 21:25 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-10 21:26 UTC - "Issue resolved on monitor recovery."Mon, 10 Feb 2025 21:25:36 +0000https://rewst.cronitorstatus.com/history/e77c02f130824ae8https://rewst.cronitorstatus.com/history/6d49f5b1d658bfcf[Unresolved] 2025-02-03 23:04 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-03 23:11 UTC - "Issue resolved on monitor recovery."Mon, 03 Feb 2025 23:04:36 +0000https://rewst.cronitorstatus.com/history/6d49f5b1d658bfcfhttps://rewst.cronitorstatus.com/history/b2e6f8b138d91b7d[Unresolved] 2025-02-01 17:05 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-01 17:08 UTC - "Issue resolved on monitor recovery."Sat, 01 Feb 2025 17:05:17 +0000https://rewst.cronitorstatus.com/history/b2e6f8b138d91b7dhttps://rewst.cronitorstatus.com/history/c42fddaa4b3792ae[Unresolved] 2025-02-01 11:44 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-01 11:51 UTC - "Issue resolved on monitor recovery."Sat, 01 Feb 2025 11:44:26 +0000https://rewst.cronitorstatus.com/history/c42fddaa4b3792aehttps://rewst.cronitorstatus.com/history/66345d4fc233800a[Unresolved] 2025-02-01 06:43 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-01 06:44 UTC - "Issue resolved on monitor recovery."Sat, 01 Feb 2025 06:43:09 +0000https://rewst.cronitorstatus.com/history/66345d4fc233800ahttps://rewst.cronitorstatus.com/history/786be71ad0b9ac8f[Unresolved] 2025-02-01 02:00 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-01 02:05 UTC - "Issue resolved on monitor recovery."Sat, 01 Feb 2025 02:00:55 +0000https://rewst.cronitorstatus.com/history/786be71ad0b9ac8fhttps://rewst.cronitorstatus.com/history/f4bd35eed3031078[Unresolved] 2025-01-29 07:57 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-29 08:27 UTC - "Issue resolved on monitor recovery."Wed, 29 Jan 2025 07:57:30 +0000https://rewst.cronitorstatus.com/history/f4bd35eed3031078https://rewst.cronitorstatus.com/history/02bcdcf412c127ea[Unresolved] 2025-01-27 16:33 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-27 16:35 UTC - "Issue resolved on monitor recovery."Mon, 27 Jan 2025 16:33:36 +0000https://rewst.cronitorstatus.com/history/02bcdcf412c127eahttps://rewst.cronitorstatus.com/history/4a94513182fed70f[Unresolved] 2025-01-27 16:06 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-27 16:16 UTC - "Issue resolved on monitor recovery."Mon, 27 Jan 2025 16:06:01 +0000https://rewst.cronitorstatus.com/history/4a94513182fed70fhttps://rewst.cronitorstatus.com/history/9138c09eb422d18f[Unresolved] 2025-01-18 05:35 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-18 06:42 UTC - "Issue resolved on monitor recovery."Sat, 18 Jan 2025 05:35:58 +0000https://rewst.cronitorstatus.com/history/9138c09eb422d18fhttps://rewst.cronitorstatus.com/history/ff864517a09c2cdb[Unresolved] 2025-01-10 00:46 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-10 01:41 UTC - "Issue resolved on monitor recovery."Fri, 10 Jan 2025 00:46:15 +0000https://rewst.cronitorstatus.com/history/ff864517a09c2cdbhttps://rewst.cronitorstatus.com/history/db153133912e45a5[Unresolved] 2025-01-10 00:12 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-10 01:19 UTC - "Issue resolved on monitor recovery."Fri, 10 Jan 2025 00:12:24 +0000https://rewst.cronitorstatus.com/history/db153133912e45a5https://rewst.cronitorstatus.com/history/fd1fe8c8db0a53bc[Unresolved] 2025-01-09 05:35 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-09 05:48 UTC - "Issue resolved on monitor recovery."Thu, 09 Jan 2025 05:35:29 +0000https://rewst.cronitorstatus.com/history/fd1fe8c8db0a53bchttps://rewst.cronitorstatus.com/history/56766601061fd19f[Unresolved] 2025-01-08 00:53 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-08 01:09 UTC - "Issue resolved on monitor recovery."Wed, 08 Jan 2025 00:53:45 +0000https://rewst.cronitorstatus.com/history/56766601061fd19fhttps://rewst.cronitorstatus.com/history/016902044972fb43[Unresolved] 2025-01-04 17:14 UTC - "Issue opened on monitor failure." [Resolved] 2025-01-04 17:23 UTC - "Issue resolved on monitor recovery."Sat, 04 Jan 2025 17:14:03 +0000https://rewst.cronitorstatus.com/history/016902044972fb43https://rewst.cronitorstatus.com/history/dc30143a9f480faa[Unresolved] 2024-12-30 00:15 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-30 00:39 UTC - "Issue resolved on monitor recovery."Mon, 30 Dec 2024 00:15:22 +0000https://rewst.cronitorstatus.com/history/dc30143a9f480faahttps://rewst.cronitorstatus.com/history/5e48275ac747253f[Unresolved] 2024-12-27 17:44 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-27 17:54 UTC - "Issue resolved on monitor recovery."Fri, 27 Dec 2024 17:44:02 +0000https://rewst.cronitorstatus.com/history/5e48275ac747253fhttps://rewst.cronitorstatus.com/history/f75fafa74c7b291b[Unresolved] 2024-12-26 00:14 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-26 01:22 UTC - "Issue resolved on monitor recovery."Thu, 26 Dec 2024 00:14:33 +0000https://rewst.cronitorstatus.com/history/f75fafa74c7b291bhttps://rewst.cronitorstatus.com/history/cc4dbc7fb5eb78bc[Unresolved] 2024-12-26 00:11 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-26 01:03 UTC - "Issue resolved on monitor recovery."Thu, 26 Dec 2024 00:11:36 +0000https://rewst.cronitorstatus.com/history/cc4dbc7fb5eb78bchttps://rewst.cronitorstatus.com/history/4da954c8b58eaa5e[Unresolved] 2024-12-13 15:56 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-13 16:16 UTC - "Issue resolved on monitor recovery."Fri, 13 Dec 2024 15:56:23 +0000https://rewst.cronitorstatus.com/history/4da954c8b58eaa5ehttps://rewst.cronitorstatus.com/history/5d568390fa2c20d9[Unresolved] 2024-12-09 20:47 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-09 20:57 UTC - "Issue resolved on monitor recovery."Mon, 09 Dec 2024 20:47:30 +0000https://rewst.cronitorstatus.com/history/5d568390fa2c20d9https://rewst.cronitorstatus.com/history/b8008dad974cdd31[Unresolved] 2024-12-02 07:16 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-02 07:26 UTC - "Issue resolved on monitor recovery."Mon, 02 Dec 2024 07:16:24 +0000https://rewst.cronitorstatus.com/history/b8008dad974cdd31https://rewst.cronitorstatus.com/history/93c8ca3300504453[Unresolved] 2024-12-02 05:05 UTC - "Issue opened on monitor failure." [Resolved] 2024-12-02 05:20 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-12-02 05:36 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-12-02 05:41 UTC - "Issue resolved on monitor recovery."Mon, 02 Dec 2024 05:05:20 +0000https://rewst.cronitorstatus.com/history/93c8ca3300504453https://rewst.cronitorstatus.com/history/0d4e73ed1e68d580[Unresolved] 2024-11-25 16:54 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-25 17:38 UTC - "Issue resolved on monitor recovery."Mon, 25 Nov 2024 16:54:24 +0000https://rewst.cronitorstatus.com/history/0d4e73ed1e68d580https://rewst.cronitorstatus.com/history/f8a42925dc90353d[Identified] 2024-11-22 17:00 UTC - "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." [Resolved] 2024-11-23 01:47 UTC - "Pax8 actions are successfully executing"Fri, 22 Nov 2024 17:00:00 +0000https://rewst.cronitorstatus.com/history/f8a42925dc90353dhttps://rewst.cronitorstatus.com/history/71a63dea13b689fd[Unresolved] 2024-11-20 22:12 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-20 22:28 UTC - "Issue resolved on monitor recovery."Wed, 20 Nov 2024 22:12:51 +0000https://rewst.cronitorstatus.com/history/71a63dea13b689fdhttps://rewst.cronitorstatus.com/history/bd337c30751f7ea2[Unresolved] 2024-11-17 20:43 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-17 21:14 UTC - "Issue resolved on monitor recovery."Sun, 17 Nov 2024 20:43:45 +0000https://rewst.cronitorstatus.com/history/bd337c30751f7ea2https://rewst.cronitorstatus.com/history/4ba947df3750b9b6[Unresolved] 2024-11-17 00:12 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-17 00:33 UTC - "Issue resolved on monitor recovery."Sun, 17 Nov 2024 00:12:33 +0000https://rewst.cronitorstatus.com/history/4ba947df3750b9b6https://rewst.cronitorstatus.com/history/dce12077cfcb654d[Investigating] 2024-11-13 23:33 UTC - "Live App Builder sites are unavailable." [Resolved] 2024-11-14 00:38 UTC - "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."Wed, 13 Nov 2024 23:33:00 +0000https://rewst.cronitorstatus.com/history/dce12077cfcb654dhttps://rewst.cronitorstatus.com/history/f168c0c05712a8d5[Unresolved] 2024-11-10 00:04 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-10 00:16 UTC - "Issue resolved on monitor recovery."Sun, 10 Nov 2024 00:04:55 +0000https://rewst.cronitorstatus.com/history/f168c0c05712a8d5https://rewst.cronitorstatus.com/history/fe1e4146133fdc5d[Unresolved] 2024-11-06 16:00 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-06 16:12 UTC - "Issue resolved on monitor recovery." [Resolved] 2024-11-06 21:27 UTC - "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."Wed, 06 Nov 2024 16:00:31 +0000https://rewst.cronitorstatus.com/history/fe1e4146133fdc5dhttps://rewst.cronitorstatus.com/history/8814516fc521e7c2[Unresolved] 2024-11-01 20:40 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-01 21:05 UTC - "Issue resolved on monitor recovery."Fri, 01 Nov 2024 20:40:34 +0000https://rewst.cronitorstatus.com/history/8814516fc521e7c2https://rewst.cronitorstatus.com/history/b831590a1d9e2c36[Unresolved] 2024-11-01 14:33 UTC - "Issue opened on monitor failure." [Resolved] 2024-11-01 16:31 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-11-01 16:56 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-11-01 17:58 UTC - "Issue resolved on monitor recovery."Fri, 01 Nov 2024 14:33:31 +0000https://rewst.cronitorstatus.com/history/b831590a1d9e2c36https://rewst.cronitorstatus.com/history/530dac25b98a5979[Investigating] 2024-11-01 14:25 UTC - "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." [Identified] 2024-11-01 17:04 UTC - "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." [Resolved] 2024-11-01 21:12 UTC - "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."Fri, 01 Nov 2024 14:25:00 +0000https://rewst.cronitorstatus.com/history/530dac25b98a5979https://rewst.cronitorstatus.com/history/349a5a38543188f5[Unresolved] 2024-10-28 20:56 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-28 21:05 UTC - "Issue resolved on monitor recovery."Mon, 28 Oct 2024 20:56:13 +0000https://rewst.cronitorstatus.com/history/349a5a38543188f5https://rewst.cronitorstatus.com/history/fb905651cd1765b5[Unresolved] 2024-10-15 00:13 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-15 00:39 UTC - "Issue resolved on monitor recovery."Tue, 15 Oct 2024 00:13:55 +0000https://rewst.cronitorstatus.com/history/fb905651cd1765b5https://rewst.cronitorstatus.com/history/a73a6f47d2b169a0[Unresolved] 2024-10-14 10:33 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-14 10:42 UTC - "Issue resolved on monitor recovery."Mon, 14 Oct 2024 10:33:18 +0000https://rewst.cronitorstatus.com/history/a73a6f47d2b169a0https://rewst.cronitorstatus.com/history/3bdc6582cf1668ba[Unresolved] 2024-10-13 15:18 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-13 15:55 UTC - "Issue resolved on monitor recovery."Sun, 13 Oct 2024 15:18:45 +0000https://rewst.cronitorstatus.com/history/3bdc6582cf1668bahttps://rewst.cronitorstatus.com/history/4ed5aa04e9c10e79[Unresolved] 2024-10-10 14:39 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-10 15:00 UTC - "Issue resolved on monitor recovery."Thu, 10 Oct 2024 14:39:36 +0000https://rewst.cronitorstatus.com/history/4ed5aa04e9c10e79https://rewst.cronitorstatus.com/history/cf2d18f3583fea59[Unresolved] 2024-10-10 00:14 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-10 00:24 UTC - "Issue resolved on monitor recovery."Thu, 10 Oct 2024 00:14:45 +0000https://rewst.cronitorstatus.com/history/cf2d18f3583fea59https://rewst.cronitorstatus.com/history/96f04b73877f37f7[Unresolved] 2024-10-04 19:20 UTC - "Issue opened on monitor failure." [Resolved] 2024-10-04 19:40 UTC - "Issue resolved on monitor recovery."Fri, 04 Oct 2024 19:20:08 +0000https://rewst.cronitorstatus.com/history/96f04b73877f37f7https://rewst.cronitorstatus.com/history/7c19e92b7db362a0[Unresolved] 2024-09-30 22:46 UTC - "Issue opened on monitor failure." [Resolved] 2024-09-30 23:08 UTC - "Issue resolved on monitor recovery."Mon, 30 Sep 2024 22:46:38 +0000https://rewst.cronitorstatus.com/history/7c19e92b7db362a0https://rewst.cronitorstatus.com/history/dda707f9be23b9a0[Unresolved] 2024-09-25 11:00 UTC - "Issue opened on monitor failure." [Resolved] 2024-09-25 12:12 UTC - "Issue resolved on monitor recovery."Wed, 25 Sep 2024 11:00:29 +0000https://rewst.cronitorstatus.com/history/dda707f9be23b9a0https://rewst.cronitorstatus.com/history/ee89c60a28f8108e[Unresolved] 2024-09-21 17:36 UTC - "Issue opened on monitor failure." [Resolved] 2024-09-21 17:46 UTC - "Issue resolved on monitor recovery."Sat, 21 Sep 2024 17:36:48 +0000https://rewst.cronitorstatus.com/history/ee89c60a28f8108ehttps://rewst.cronitorstatus.com/history/0604da97321e6288[Unresolved] 2024-09-09 04:19 UTC - "Issue opened on monitor failure." [Resolved] 2024-09-09 05:04 UTC - "Issue resolved on monitor recovery."Mon, 09 Sep 2024 04:19:26 +0000https://rewst.cronitorstatus.com/history/0604da97321e6288https://rewst.cronitorstatus.com/history/3ebb7927dc087469[Unresolved] 2024-08-25 00:15 UTC - "Issue opened on monitor failure." [Resolved] 2024-08-25 00:28 UTC - "Issue resolved on monitor recovery."Sun, 25 Aug 2024 00:15:28 +0000https://rewst.cronitorstatus.com/history/3ebb7927dc087469https://rewst.cronitorstatus.com/history/d928843b2fb06d5c[Unresolved] 2024-08-13 10:37 UTC - "Issue opened on monitor failure." [Resolved] 2024-08-13 10:57 UTC - "Issue resolved on monitor recovery."Tue, 13 Aug 2024 10:37:33 +0000https://rewst.cronitorstatus.com/history/d928843b2fb06d5chttps://rewst.cronitorstatus.com/history/a1c02b34f2080d17[Unresolved] 2024-08-10 01:29 UTC - "Issue opened on monitor failure." [Resolved] 2024-08-10 02:20 UTC - "Issue resolved on monitor recovery."Sat, 10 Aug 2024 01:29:25 +0000https://rewst.cronitorstatus.com/history/a1c02b34f2080d17https://rewst.cronitorstatus.com/history/37846b79c7931285[Investigating] 2024-08-07 16:22 UTC - "We have detected an issue that is affecting workflows that update PSA tickets. We are actively looking into the issue and will provide a solution and updates as soon as possible. We apologize for any inconvenience." [Identified] 2024-08-07 17:50 UTC - "The action affected is: ConnectWise Update Service Ticket (v1). Workflows that contain this action are failing. This also affects crates that use this action, such as User Onboarding and User Offboarding V1 and V2. Once the recovery process is complete, we will re-run all failed New User Workflows." [Resolved] 2024-08-07 19:39 UTC - "We are pleased to inform you that the issue affecting workflows containing the ConnectWise Update Service Ticket (v1) action has been successfully resolved. Normal functionality has resumed. All services should now be operating as expected. We will now begin re-running the New User Workflows that failed today. We apologize for any inconvenience caused during this period and appreciate your patience and understanding. If you encounter any further issues or have any questions, please do not hesitate to reach out to our support team."Wed, 07 Aug 2024 16:22:04 +0000https://rewst.cronitorstatus.com/history/37846b79c7931285https://rewst.cronitorstatus.com/history/e7be46338834f867[Unresolved] 2024-08-07 00:12 UTC - "Issue opened on monitor failure." [Resolved] 2024-08-07 00:22 UTC - "Issue resolved on monitor recovery."Wed, 07 Aug 2024 00:12:00 +0000https://rewst.cronitorstatus.com/history/e7be46338834f867https://rewst.cronitorstatus.com/history/c642ba2744c6f560[Unresolved] 2024-07-17 14:12 UTC - "Issue opened on monitor failure." [Resolved] 2024-07-17 14:22 UTC - "Issue resolved on monitor recovery."Wed, 17 Jul 2024 14:12:04 +0000https://rewst.cronitorstatus.com/history/c642ba2744c6f560https://rewst.cronitorstatus.com/history/ebfb1d39e2ff9f70[Investigating] 2024-07-17 10:53 UTC - "Forms users are reporting the inability to log in to Rewst or very long wait times for logging in." [Investigating] 2024-07-17 12:36 UTC - "Performance for forms-only user logins has been improved, but we are still working on permanent resolution." [Identified] 2024-07-17 14:22 UTC - "We have identified an issue within our forms trigger that could potentially be the source of the intermittent login delays. A fix has been applied to address this, and we are actively monitoring the situation to ensure the effectiveness of the solution. Please report any further login delays." [Identified] 2024-07-17 14:25 UTC - "This issue is also being tracked on our docs site here: https://docs.rewst.help/updates/issue-alerts" [Monitoring] 2024-07-17 15:46 UTC [Investigating] 2024-07-18 08:17 UTC - "We are continuing to see some issues and are continuing to investigate" [Monitoring] 2024-07-18 10:32 UTC - "The root cause has been identified and a temporary measure has been put in place to resolve the issue. We will update further once a permanent fix has been deployed, but the platform should now be running as expected." [Resolved] 2024-07-19 19:29 UTC - "This issue has been successfully resolved and we are closing this alert."Wed, 17 Jul 2024 10:53:00 +0000https://rewst.cronitorstatus.com/history/ebfb1d39e2ff9f70https://rewst.cronitorstatus.com/history/66dddbb39e02d8f0[Unresolved] 2024-07-09 02:07 UTC - "Issue opened on monitor failure." [Resolved] 2024-07-09 02:25 UTC - "Issue resolved on monitor recovery."Tue, 09 Jul 2024 02:07:28 +0000https://rewst.cronitorstatus.com/history/66dddbb39e02d8f0https://rewst.cronitorstatus.com/history/906a332756dc1755[Unresolved] 2024-06-24 09:01 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-24 09:02 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-06-24 09:06 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-06-24 09:26 UTC - "Issue resolved on monitor recovery."Mon, 24 Jun 2024 09:01:00 +0000https://rewst.cronitorstatus.com/history/906a332756dc1755https://rewst.cronitorstatus.com/history/2026eb4b9ed3b54a[Unresolved] 2024-06-24 07:01 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-24 07:10 UTC - "Issue resolved on monitor recovery."Mon, 24 Jun 2024 07:01:29 +0000https://rewst.cronitorstatus.com/history/2026eb4b9ed3b54ahttps://rewst.cronitorstatus.com/history/f174ec41166b0abe[Unresolved] 2024-06-22 00:29 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-22 00:40 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-06-22 00:55 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-06-22 01:11 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-06-22 01:47 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-06-22 01:51 UTC - "Issue resolved on monitor recovery."Sat, 22 Jun 2024 00:29:33 +0000https://rewst.cronitorstatus.com/history/f174ec41166b0abehttps://rewst.cronitorstatus.com/history/262c2235eb48e5fb[Unresolved] 2024-06-21 00:02 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-21 00:11 UTC - "Issue resolved on monitor recovery."Fri, 21 Jun 2024 00:02:21 +0000https://rewst.cronitorstatus.com/history/262c2235eb48e5fbhttps://rewst.cronitorstatus.com/history/3992a76366c6d5fc[Unresolved] 2024-06-14 06:06 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-14 06:07 UTC - "Issue resolved on monitor recovery."Fri, 14 Jun 2024 06:06:37 +0000https://rewst.cronitorstatus.com/history/3992a76366c6d5fchttps://rewst.cronitorstatus.com/history/65ba1dc06a8f83b2[Unresolved] 2024-06-12 03:31 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-12 03:47 UTC - "Issue resolved on monitor recovery."Wed, 12 Jun 2024 03:31:07 +0000https://rewst.cronitorstatus.com/history/65ba1dc06a8f83b2https://rewst.cronitorstatus.com/history/04dce0964b7a4fea[Unresolved] 2024-06-08 23:46 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-08 23:56 UTC - "Issue resolved on monitor recovery."Sat, 08 Jun 2024 23:46:41 +0000https://rewst.cronitorstatus.com/history/04dce0964b7a4feahttps://rewst.cronitorstatus.com/history/0cad38cd0a5f88ab[Unresolved] 2024-06-07 18:56 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-07 20:18 UTC - "Issue resolved on monitor recovery."Fri, 07 Jun 2024 18:56:10 +0000https://rewst.cronitorstatus.com/history/0cad38cd0a5f88abhttps://rewst.cronitorstatus.com/history/a2e43ec57b89866c[Unresolved] 2024-06-07 08:46 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-07 09:06 UTC - "Issue resolved on monitor recovery."Fri, 07 Jun 2024 08:46:37 +0000https://rewst.cronitorstatus.com/history/a2e43ec57b89866chttps://rewst.cronitorstatus.com/history/5da786fbecdc5a7d[Unresolved] 2024-06-05 16:19 UTC - "Issue opened on monitor failure." [Resolved] 2024-06-05 16:33 UTC - "Issue resolved on monitor recovery."Wed, 05 Jun 2024 16:19:00 +0000https://rewst.cronitorstatus.com/history/5da786fbecdc5a7dhttps://rewst.cronitorstatus.com/history/50db61abca6f76e2[Unresolved] 2024-05-22 06:05 UTC - "Issue opened on monitor failure." [Resolved] 2024-05-22 06:06 UTC - "Issue resolved on monitor recovery."Wed, 22 May 2024 06:05:25 +0000https://rewst.cronitorstatus.com/history/50db61abca6f76e2https://rewst.cronitorstatus.com/history/956f329f7b9eebbd[Unresolved] 2024-04-30 20:06 UTC - "Issue opened on monitor failure." [Investigating] 2024-04-30 20:16 UTC [Investigating] 2024-04-30 20:16 UTC [Identified] 2024-04-30 20:16 UTC - "App running, engine work in progress" [Resolved] 2024-04-30 20:19 UTC - "Failed migration from new feature deployment - we are back to normal operations. We were able to fix the migration issue without rolling back. The status page will update automatically when it determines we are back." [Resolved] 2024-04-30 20:19 UTCTue, 30 Apr 2024 20:06:00 +0000https://rewst.cronitorstatus.com/history/956f329f7b9eebbdhttps://rewst.cronitorstatus.com/history/89ab94fb0328e31c[Unresolved] 2024-04-23 16:26 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-23 16:46 UTC - "Issue resolved on monitor recovery."Tue, 23 Apr 2024 16:26:26 +0000https://rewst.cronitorstatus.com/history/89ab94fb0328e31chttps://rewst.cronitorstatus.com/history/8a2dbbe873e326c4[Unresolved] 2024-04-12 01:06 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-12 01:26 UTC - "Issue resolved on monitor recovery." [Unresolved] 2024-04-12 01:47 UTC - "Issue re-opened on monitor failure." [Resolved] 2024-04-12 01:48 UTC - "Issue resolved on monitor recovery."Fri, 12 Apr 2024 01:06:36 +0000https://rewst.cronitorstatus.com/history/8a2dbbe873e326c4https://rewst.cronitorstatus.com/history/7830cc364aab3926[Unresolved] 2024-04-09 18:02 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-09 18:22 UTC - "Issue resolved on monitor recovery."Tue, 09 Apr 2024 18:02:34 +0000https://rewst.cronitorstatus.com/history/7830cc364aab3926https://rewst.cronitorstatus.com/history/f3e261fad0e2a55e[Unresolved] 2024-04-04 20:15 UTC - "Issue opened on monitor failure." [Resolved] 2024-04-04 20:36 UTC - "Issue resolved on monitor recovery."Thu, 04 Apr 2024 20:15:47 +0000https://rewst.cronitorstatus.com/history/f3e261fad0e2a55e