Is there an Robocorp outage?
Robocorp status: Systems Active
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Robocorp and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Robocorp and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Robocorp.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API | Active |
| Robots | Active |
View the latest incidents for Robocorp and check for official updates:
Description: We encountered a spike in errors on our rate limiting system during 05:30 EET - 07:30 EET (8:30PM - 10:30PM PDT). The situation is back to normal. The issue may have impacted process related operations like starting, stopping, and listing processes. The system has been patched to prevent similar issues in the future.
Status: Resolved
Impact: None | Started At: March 22, 2023, 8:06 a.m.
Description: We encountered a spike in errors on our rate limiting system during 05:30 EET - 07:30 EET (8:30PM - 10:30PM PDT). The situation is back to normal. The issue may have impacted process related operations like starting, stopping, and listing processes. The system has been patched to prevent similar issues in the future.
Status: Resolved
Impact: None | Started At: March 22, 2023, 8:06 a.m.
Description: The situation is back to normal. Approximately 10% of requests to the task data subsystem between 6:54 UTC and 7:54 UTC were failing with HTTP status code 500. Impacted step runs may have failed depending on which actions the robot has taken. Run failure notifications have been operational during the time, thus surfacing the issue to robot operators. The failed work items can be retried from the control room. We apologize for the inconvenience.
Status: Resolved
Impact: Major | Started At: Nov. 11, 2022, 8:04 a.m.
Description: The situation is back to normal. Approximately 10% of requests to the task data subsystem between 6:54 UTC and 7:54 UTC were failing with HTTP status code 500. Impacted step runs may have failed depending on which actions the robot has taken. Run failure notifications have been operational during the time, thus surfacing the issue to robot operators. The failed work items can be retried from the control room. We apologize for the inconvenience.
Status: Resolved
Impact: Major | Started At: Nov. 11, 2022, 8:04 a.m.
Description: We encountered a significant spike in errors from AWS services during 14:35 EET - 14:37 EET (5.35 - 5.37 Pacific Time). The situation is back to normal. Based on the inspection of dead-letter-queues, all failures in customer workloads were automatically recovered via retry mechanisms.
Status: Resolved
Impact: None | Started At: Nov. 2, 2022, 1:11 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
