WordFly Outage History

WordFly is up right now

WordFly had 3 outages in the last 2 years totaling 23h 44m of downtime — averaging 0.1 incidents per month.

There were 3 WordFly outages since April 23, 2026 totaling 23h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://updates.wordflystatus.com

Major September 2, 2026

Intermittent Timeouts

Detected by Pingoru
Sep 02, 2026, 08:35 PM UTC
Resolved
Sep 03, 2026, 07:40 PM UTC
Duration
23h 4m
Timeline · 2 updates
  1. investigating Sep 02, 2026, 08:35 PM UTC

    Some customers are experiencing intermittent timeouts when accessing WordFly, including the login page. We believe the cause is a network issue at one of our upstream internet carriers. We are actively working with them to restore normal access. WordFly's systems and your data are unaffected. Connecting from a different network (such as a mobile hotspot) usually restores access in the meantime. We will post new updates here as we make progress.

  2. resolved Sep 03, 2026, 07:40 PM UTC

    Customers are no longer reporting intermittent timeout issues. Our upstream internet carrier made changes at 7pm Pacific Wednesday night, and we started seeing immediate improvements. After monitoring overnight and throughout the morning, we are no longer seeing timeouts. Please reach out if you experience any new issues.

Read the full incident report →

Major April 23, 2026

General Slowness

Detected by Pingoru
Apr 23, 2026, 06:20 PM UTC
Resolved
Apr 23, 2026, 06:52 PM UTC
Duration
32m
Timeline · 2 updates
  1. investigating Apr 23, 2026, 06:20 PM UTC

    We are investigating slowness in the application. This is currently affecting list imports, delayed reporting, and loading in the app. We will post new updates as we make progress.

  2. resolved Apr 23, 2026, 06:52 PM UTC

    We have identified and resolved the issue. Application performance has returned to normal speeds. Opens and clicks are now updating at expected rates. Thank you for your patience while we investigated.

Read the full incident report →