Robocorp Outage History

Robocorp is up right now

Robocorp had 2 outages in the last 2 years totaling 21h 26m of downtime — averaging 0.1 incidents per month.

There were 2 Robocorp outages since October 20, 2025 totaling 21h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.robocorp.com

Critical November 18, 2025

Website and documentation impacted by Cloudflare issues

Detected by Pingoru
Nov 18, 2025, 02:11 PM UTC
Resolved
Nov 18, 2025, 05:09 PM UTC
Duration
2h 57m
Affected: Website and documentation
Timeline · 2 updates
  1. investigating Nov 18, 2025, 02:11 PM UTC

    Sema4.ai corporate website at https://sema4.ai and documentation at https://sema4.ai/docs are impacted by the ongoing Cloudflare outage. Please see https://www.cloudflarestatus.com/ for the most up-to-date status updates. We expect the issues to resolve once Cloudflare restores service.

  2. resolved Nov 18, 2025, 05:09 PM UTC

    Although Cloudflare still has open issues, our site has been back up and stable for a while. We will close this issue but continue monitoring the situation.

Read the full incident report →

Major October 20, 2025

Issues on US based deployments

Detected by Pingoru
Oct 20, 2025, 12:36 PM UTC
Resolved
Oct 21, 2025, 07:05 AM UTC
Duration
18h 28m
Affected: RobotsAPISSO integration
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 12:36 PM UTC

    We're monitoring issues on our US based deployments. Some of the services are recovering but at the moment there are issues with e.g. robot process run executions and scheduling.

  2. resolved Oct 21, 2025, 07:05 AM UTC

    The issue affecting our Control Room products in the U.S. region has been fully resolved. All services are now operating normally. Please note that scheduled runs and API triggers initiated during the outage period—between 11:40 PM PDT on October 19 and 3:55 PM PDT on October 20—were likely impacted and may not have executed. We recommend reviewing the status of affected runs in Control Room and manually re-running any missed processes as needed.

Read the full incident report →