It seems the service no longer exists.
The official status page is not reachable.
IsDown continuously monitor the official Catalytic status page for ongoing outages. Check the stats for the latest 30 days and a list of the last Catalytic outages.
Number of Outages
0
Average Downtime
0 mins
Total Downtime
0 mins
Since last incident
207 days
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Catalytic, and never miss an outage again.
Minor · 7 months ago · lasted about 5 hours
We are investigating an issue with slow action and batch processing
Minor · about 1 year ago · lasted about 1 hour
We are investigating decreased task processing throughput in the Catalytic platform.
Minor · over 1 year ago · lasted 2 months
We are seeing slow performance in batch ("Start a workflow for each row") and looping actions. We've identified the issue and are working on resolving now.
Minor · over 1 year ago · lasted 2 months
We are investigating an issue leading to slow action processing and slow workflow performance. We will provide additional updates when we have more information.
Minor · over 1 year ago · lasted 3 months
We are investigating an issue with our cloud provider that is impacting connectivity to our primary database. We are seeing intermittent issues connecting to our database which is causing failures in loading pages, degraded performance, and occasional fix tasks. We will provide an update when we have more information.
Minor · over 1 year ago · lasted 4 months
Our cloud provider is experiencing an incident that is disrupting other services. We have not seen any disruptions to our service but are closely monitoring and working with our cloud provider to resolve. We will update this issue if we identify any Catalytic issues related to the cloud provider incident.
Minor · over 1 year ago · lasted 6 months
We have identified an issue with our `Start an instance for each row` actions, where they are not consistently beginning all of their subprocesses. We have taken corrective action and are closely monitoring. We apologize for the inconvenience and will provide an update once fully resolved.
Minor · almost 2 years ago · lasted 8 months
We are investigating an issue where our `Start an instance for each row` actions are not always completing. The sub-instances are beginning, but the actual action task is failing to be marked as `complete`. If you are experiencing this issue, you can safely `Force complete` the action task in your task detail screen. We will post updates as we identify what is causing this issue. We apologize for any inconvenience.
Get notified only when an outage impacts a certain component.
The data and notifications you need, in the tools you already use.
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Catalytic, and never miss an outage again.
Try it out! How much time you'll save your team, by having the outages information close to them?