Lyrical Host Outage History

Lyrical Host is up right now

Lyrical Host had 3 outages in the last 2 years totaling 2h 42m of downtime — averaging 0.1 incidents per month.

There were 3 Lyrical Host outages since February 6, 2026 totaling 2h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.lyricalhost.com

Minor July 9, 2026

Website connectivity

Detected by Pingoru
Jul 09, 2026, 10:32 AM UTC
Resolved
Jul 09, 2026, 12:35 PM UTC
Duration
2h 3m
Affected: Your ServicesWordPress Hosting Platform
Timeline · 2 updates
  1. investigating Jul 09, 2026, 10:32 AM UTC

    A small minority of customers may be seeing downtime for their websites as we are in the process of replacing a faulty hardware component. Please sit tight and thank you for your patience as we carry out this unanticipated work.

  2. resolved Jul 09, 2026, 12:35 PM UTC

    This has now been fixed; thank you for your patience!

Read the full incident report →

Major April 27, 2026

Connection errors

Detected by Pingoru
Apr 27, 2026, 01:41 PM UTC
Resolved
Apr 27, 2026, 01:44 PM UTC
Duration
2m
Affected: Lyrical HostLyrical Host Hub
Timeline · 2 updates
  1. investigating Apr 27, 2026, 01:41 PM UTC

    Customers may have difficulty accessing the Lyrical Host Hub and website - please sit tight as we work on fixing this ASAP! Thank you for your patience :)

  2. resolved Apr 27, 2026, 01:44 PM UTC

    :)

Read the full incident report →

Major February 6, 2026

Database errors

Detected by Pingoru
Feb 06, 2026, 09:37 PM UTC
Resolved
Feb 06, 2026, 10:13 PM UTC
Duration
36m
Affected: Your ServicesWordPress Hosting Platform
Timeline · 2 updates
  1. investigating Feb 06, 2026, 09:37 PM UTC

    Some customers may be seeing database errors while trying to access their websites. Please rest assured that we are working on it and service is expected to resume shortly. Thank you for your patience.

  2. resolved Feb 06, 2026, 10:13 PM UTC

    This is now fixed; thank you for your patience!

Read the full incident report →