Craft.io Outage History

Craft.io is up right now

Craft.io had 2 outages in the last 2 years totaling 40m of downtime — averaging 0.1 incidents per month.

There were 2 Craft.io outages since October 29, 2025 totaling 40m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://craftio.statuspage.io

Minor October 29, 2025

Degraded Performance: Craft.io Applications (US Data Center)

Detected by Pingoru
Oct 29, 2025, 10:15 AM UTC
Resolved
Oct 29, 2025, 10:35 AM UTC
Duration
19m
Affected: Core App (US Data Center)Feedback Portal (US Data Center)
Timeline · 2 updates
  1. investigating Oct 29, 2025, 02:32 PM UTC

    We are currently investigating reports of degraded performance affecting Craft.io applications in US Datacenter. Users may experience slower response times or intermittent connectivity when accessing our services. Our engineering team is actively working to identify and resolve the root cause. We apologize for any inconvenience this may cause and appreciate your patience as we work to restore full performance. We will provide an update here within the next hour.

  2. resolved Oct 29, 2025, 02:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Degraded Performance: Craft.io Applications (EU Data Center)

Detected by Pingoru
Oct 29, 2025, 10:14 AM UTC
Resolved
Oct 29, 2025, 10:35 AM UTC
Duration
21m
Affected: Core App (EU Data Center)Feedback Portal (EU Data Center)
Timeline · 3 updates
  1. investigating Oct 29, 2025, 02:31 PM UTC

    We are currently investigating reports of degraded performance affecting Craft.io applications in EU Datacenter. Users may experience slower response times or intermittent connectivity when accessing our services. Our engineering team is actively working to identify and resolve the root cause. We apologize for any inconvenience this may cause and appreciate your patience as we work to restore full performance. We will provide an update here within the next hour.

  2. investigating Oct 29, 2025, 02:32 PM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 29, 2025, 02:33 PM UTC

    This incident has been resolved.

Read the full incident report →