Routific incident

Google Cloud Provider downtime affecting Routific services

Major Resolved View vendor source →

Routific experienced a major incident on June 12, 2025 affecting Routific API and Routific SaaS product and 1 more component, lasting 5h 19m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2025, 06:29 PM UTC
Resolved
Jun 12, 2025, 11:49 PM UTC
Duration
5h 19m
Detected by Pingoru
Jun 12, 2025, 06:29 PM UTC

Affected components

Routific APIRoutific SaaS productDriver Mobile AppNew Routific

Update timeline

  1. investigating Jun 12, 2025, 06:29 PM UTC

    One of our third party providers, Google Cloud Provider (GCP), is experiencing downtime and thus affecting some Routific services. Log in via Google SSO is not working at the moment, as well as the ability to schedule and optimize a route on the old and new Routific. There may be other services impacted. We are actively investigating and will post another update in 30 minutes time. Thank you for your patience.

  2. investigating Jun 12, 2025, 07:10 PM UTC

    We’re still observing issues with our optimization service. Google Cloud Platform has reported a major outage. We're actively monitoring the situation and will provide updates as we learn more.

  3. investigating Jun 12, 2025, 07:43 PM UTC

    Our platform continues to experience issues due to a major outage reported by Google Cloud Platform. We're closely monitoring the situation and will share updates as more information becomes available.

  4. investigating Jun 12, 2025, 08:28 PM UTC

    Our platform is still being impacted by an ongoing outage in Google Cloud Platform. We're observing continued signs that some GCP services remain down. We're actively monitoring their recovery efforts and will provide updates as more information becomes available.

  5. monitoring Jun 12, 2025, 09:18 PM UTC

    Services are starting to improve and we are seeing processes back to normal operations. We are continuing to monitor all systems closely for any further issues

  6. resolved Jun 12, 2025, 11:49 PM UTC

    This incident has been resolved.