Liquid Web incident

Liquid Web Customer Portal Experiencing Issues

Major Resolved View vendor source →

Liquid Web experienced a major incident on November 19, 2025 affecting Management Portal, lasting 5h 39m. The incident has been resolved; the full update timeline is below.

Started
Nov 19, 2025, 03:57 PM UTC
Resolved
Nov 19, 2025, 09:36 PM UTC
Duration
5h 39m
Detected by Pingoru
Nov 19, 2025, 03:57 PM UTC

Affected components

Management Portal

Update timeline

  1. investigating Nov 19, 2025, 03:57 PM UTC

    We are currently experiencing an issue affecting access to the Customer Portal. Our teams are actively investigating the cause and working to restore full functionality as quickly as possible. At this time, customers may be unable to log in, and instead will see a maintenance page upon logging in. We will provide updates as soon as more information becomes available. We appreciate your patience while we work to resolve this.

  2. identified Nov 19, 2025, 04:06 PM UTC

    Our team has identified the underlying issue impacting the Customer Portal and is working on a fix. Access may remain limited during this time. We will share another update shortly.

  3. identified Nov 19, 2025, 04:18 PM UTC

    Our teams are actively investigating and working to restore full functionality as quickly as possible. In the meantime, clients can still open new support cases by emailing us directly at [email protected], or by replying to a previous case via email for any new issues. Our Support Team will continue to assist from there.

  4. monitoring Nov 19, 2025, 04:24 PM UTC

    Access to the Customer Portal has been restored, and functionality should now be coming back online. Our teams have applied the necessary fixes and will continue to closely monitor performance and stability to ensure the portal remains fully operational. If you continue to experience any issues accessing the portal, please reach out to Support. Thank you for your patience while we worked through this incident.

  5. resolved Nov 19, 2025, 09:36 PM UTC

    This incident has been resolved.