Thunkable Outage History

Thunkable is up right now

Thunkable had 2 outages in the last 2 years totaling 15h 30m of downtime — averaging 0.1 incidents per month.

There were 2 Thunkable outages since June 12, 2025 totaling 15h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.thunkable.com

Critical November 18, 2025

Thunkable Platform Service Disruption

Detected by Pingoru
Nov 18, 2025, 12:10 PM UTC
Resolved
Nov 18, 2025, 03:10 PM UTC
Duration
3h
Affected: Thunkable DesignerThunakble WebsiteMobile Web App Hosting
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 12:10 PM UTC

    We are currently experiencing platform issues due to an ongoing incident with Cloudflare Global Network. You can follow the official Cloudflare Global Network status here: https://www.cloudflarestatus.com/ We’ll continue to monitor the situation and share updates as needed. Thank you for your continued patience.

  2. resolved Nov 18, 2025, 03:10 PM UTC

    Cloudflare has resolved the issue. We will continue to monitor this situation and provide updates if the issue re-surfaces. Thank you for your patience.

Read the full incident report →

Notice August 7, 2025

Platform and Live App Outage

Detected by Pingoru
Aug 07, 2025, 11:41 PM UTC
Resolved
Aug 08, 2025, 12:11 PM UTC
Duration
12h 29m
Affected: Thunkable DesigneriOS Live AppAndroid Live App
Timeline · 4 updates
  1. investigating Aug 07, 2025, 11:40 PM UTC

    We are currently experiencing an outage affecting both the Thunkable platform and published live apps. Our engineering team is actively investigating the issue and working to restore full service as quickly as possible. We will provide updates here as soon as more information is available. Thank you for your patience and understanding.

  2. monitoring Aug 07, 2025, 11:41 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Aug 08, 2025, 04:52 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 08, 2025, 12:11 PM UTC

    This incident has been resolved.

Read the full incident report →