All Systems Operational

About This Site

Status Page of the Workato US Region

Check status of other Workato regions:
- Workato EU (Europe Region)
- Workato SG (Singapore Region)
- Workato JP (Japan Region)
- Workato AU (Australia Region)

Recipe runtime Operational
90 days ago
99.99 % uptime
Today
Recipe job execution ? Operational
90 days ago
99.99 % uptime
Today
On-premise connectivity Operational
90 days ago
100.0 % uptime
Today
API gateway Operational
90 days ago
99.99 % uptime
Today
Webhook ingestion Operational
90 days ago
99.99 % uptime
Today
Workbot Operational
90 days ago
99.98 % uptime
Today
Workbot for Slack Operational
90 days ago
99.95 % uptime
Today
Workbot for Teams Operational
90 days ago
99.99 % uptime
Today
Workbot for Workplace Operational
90 days ago
99.99 % uptime
Today
Website Operational
90 days ago
99.99 % uptime
Today
Email notifications ? Operational
90 days ago
99.99 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Website
Fetching
Past Incidents
Apr 19, 2024

No incidents reported today.

Apr 18, 2024

No incidents reported.

Apr 17, 2024
Resolved - After further monitoring, this incident is now considered resolved. Customers should now be able to connect to SAP Concur's SFTP instance and run jobs successfully. Failed jobs may be rerun as required, and any recipes with the SFTP trigger that stopped due to trigger errors must be restarted. If you continue to experience any issues, please contact Workato Support at support.workato.com.
Apr 17, 10:31 PDT
Monitoring - SAP Concur has reverted the change, and customers should now be able to connect to the SAP Concur SFTP server successfully. We are continuing to monitor for any additional impact.
Apr 17, 10:21 PDT
Update - We are continuing to work on a resolution for the SFTP connection issue. We will provide additional information as soon as it is available.
Apr 17, 09:31 PDT
Identified - We are currently working to resolve an issue affecting our customers who are connecting to SAP Concur SFTP servers. These customers are experiencing SFTP connection issues due to SAP Concur's latest security release, introduced yesterday. The SAP Concur release affected an additional part of server communication and changed the host key verification algorithms. Since the release, only two types of algorithms continue to be supported by SAP Concur SFTP servers, and none are currently supported by Workato. This change was not anticipated by Workato since the official AWS docs state that up to 6 algorithms are supported. https://docs.aws.amazon.com/transfer/latest/userguide/security-policies.html#security-policy-transfer-2022-03.

We will provide additional information as soon as it becomes available.

Apr 17, 07:31 PDT
Apr 16, 2024

No incidents reported.

Apr 15, 2024

No incidents reported.

Apr 14, 2024
Resolved - After further monitoring, this incident is now considered resolved. The Email by Workato connector is delivering emails as expected and has cleared the backlog of undelivered emails. Customers may have observed that emails sent from the Workato domain, such as error notifications, team invitations, and password reset emails, were delayed or sent out of order. If you continue to experience any mail delivery issues, please contact Workato Support at support.workato.com.
Apr 14, 16:08 PDT
Monitoring - Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.
Apr 14, 15:45 PDT
Investigating - We are currently investigating an issue affecting the delivery of emails sent by the Email by Workato connector. We will provide additional information as soon as it becomes available.
Apr 14, 15:36 PDT
Apr 13, 2024

No incidents reported.

Apr 12, 2024

No incidents reported.

Apr 11, 2024
Resolved - Certain customers on the Workato platform may have experienced job failures between 10:03 UTC and 15:00 UTC due to an issue with an internal database. A small number of jobs may have failed with an error message of "Internal Error," and the job details page for the failed job will display "No data to show" regardless of the workspace's configured data retention period. Customers may be able to repeat any failed jobs but are advised to inspect any connected applications for changes as jobs may have been partially executed and take appropriate corrective measures. We apologize for any inconvenience caused and are taking remediation steps to prevent this issue in the future. Please contact Workato Support at support.workato.com or your assigned CSM if you require further assistance.
Apr 11, 03:00 PDT
Apr 10, 2024

No incidents reported.

Apr 9, 2024

No incidents reported.

Apr 8, 2024

No incidents reported.

Apr 7, 2024

No incidents reported.

Apr 6, 2024

No incidents reported.

Apr 5, 2024
Resolved - After further monitoring, this incident is now considered resolved. If you continue to experience any issues, please contact Workato Support at support.workato.com.
Apr 5, 12:54 PDT
Monitoring - Our team has taken steps to remediate the incident and is seeing improvement. We will provide additional information as soon as it is available.
Apr 5, 10:14 PDT
Update - We are continuing to investigate the issue and will provide additional information as soon as it is available.
Apr 5, 09:39 PDT
Update - We are continuing to investigate the issue and will provide additional information as soon as it is available.
Apr 5, 08:53 PDT
Investigating - We are currently investigating an incident affecting our platform. We will provide additional information on all affected components as soon as it becomes available.
Apr 5, 08:04 PDT
Resolved - After further monitoring, this incident is now considered resolved. Workato platform has been restored to full functionality. If you continue to experience any issues, please contact Workato Support at support.workato.com
Apr 5, 04:56 PDT
Monitoring - Our team has taken steps to remediate the incident and is seeing improvement. We are continuing to monitor for any additional impact.
Apr 5, 04:54 PDT
Identified - We have identified the underlying cause of the incident and we are working to take remediating steps. We will provide more updates shortly.
Apr 5, 04:28 PDT