Last checked
Managed hosting and cloud services for websites and applications.
Experiencing an issue?
Czy Liquid Web nie działa?
Degraded performance
The current official status of Liquid Web cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Liquid Web in the last 24 hours. Last official check: .
Source: official status pageShare your experience to help others stay informed.
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Loading reports… · Last 24 hours
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Official status checked
Liquid Web is experiencing issues
Official provider statusOfficial maintenance active
Scheduled Maintenance on Object Storage — Liquid Web Systems Engineers will be performing maintenance on our Object Storage platform starting at 9:00 AM on Wednesday and will be performing routine maintenance during the next 24 hours. While this upgrade is expected to have no impact in the functionality of Object Storage, it is possible, though unexpected, that data transfers may progress more slowly or briefly stall, before automatically resuming Object Storage. We appreciate your patience as our Engineering team works to enhance the performance of our platform. If you have any further questions or concerns please reach out to our support teams [CC-13721]
Official provider statusOfficial incident active
Security Advisory: WordPress Security Update for CVE-2026-65640 — A security vulnerability, CVE-2026-65640, has been identified in WordPress that could allow an authenticated Author-level or higher user to achieve remote code execution through a malicious file upload on sites using Imagick and Ghostscript. The vulnerability has been addressed through updates across supported WordPress branches. Patched Versions: Customers should update to the following patched version for their respective WordPress branch: 7.0.4 6.9.7 6.8.8 6.7.7 6.6.7 6.5.10 6.4.10 6.3.10 6.2.11 6.1.12 6.0.14 5.9.16 5.8.15 5.7.17 5.6.19 5.5.20 5.4.21 5.3.23 5.2.26 5.1.24 5.0.27 4.9.31 4.8.30 4.7.35 Recommended Action: Customers are strongly encouraged to update WordPress core to the latest available patched version and ensure automatic updates are enabled where appropriate. Customers with automatic updates enabled should receive the applicable update automatically. However, we recommend verifying the currently running WordPress version to ensure the security update has been successfully applied. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please reach us via live chat or via a case. Additional information: https://wordpress.org/news/2026/08/wordpress-7-0-4-release/ https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-8vr3-7mxf-gx8w
Official provider statusOfficial incident active
Security Advisory: WordPress XSS2Shell Vulnerability (CVE-2026-64638) — A high-severity reflected XSS vulnerability, CVE-2026-64638, has been identified in the WordPress login interface. Exploitation requires a victim to visit a specially crafted URL and, under specific conditions, could potentially lead to PHP code execution. Impacted versions Impacted versions: WordPress 4.7 – 7.0.2 (every release on every branch) WordPress 4.6 and earlier — end of life, no patch available Fixed versions: WordPress 7.0.3 WordPress 6.9.6 WordPress 6.8.7 Equivalent minor releases on every remaining supported branch back to 4.7 Recommended Action Customers are strongly encouraged to update WordPress core and ensure automatic security updates are enabled where appropriate. Since exploitation requires user interaction, customers should also remain vigilant against phishing attempts and avoid clicking suspicious or unsolicited links. Customers with automatic security updates enabled should receive the applicable update automatically; however, we recommend verifying the currently running WordPress version. There is currently no reported evidence of widespread exploitation in the wild. We will continue to monitor the situation and provide further updates if required. If you need assistance or have any concerns, please contact our Support team.
Official provider status0 outage reports in the last 24 hours.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 28h 41m | Yes | Unknown | ||
| 65h 31m | Yes | Critical | ||
| 635h 49mOngoing | Yes | Unknown | ||
| 734h 8mOngoing | Yes | Unknown | ||
| 33m | Yes | Major | ||
| 137h 59m | Yes | Critical | ||
| 4h 24m | Yes | Major | ||
| 189h 15m | Yes | Major |
Planned work published by the official provider.
Liquid Web Systems Engineers will be performing maintenance on our Object Storage platform starting at 9:00 AM on Wednesday and will be performing routine maintenance during the next 24 hours. While this upgrade is expected to have no impact in the functionality of Object Storage, it is possible, though unexpected, that data transfers may progress more slowly or briefly stall, before automatically resuming Object Storage. We appreciate your patience as our Engineering team works to enhance the performance of our platform. If you have any further questions or concerns please reach out to our support teams [CC-13721]
Started 26 sie 2026, 13:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 13 sie 2026, 13:30 UTC · Resolved 13 sie 2026, 16:30 UTC
The scheduled maintenance has been postponed and will be rescheduled for a new time. We will post a new maintenance notice on the status page once the new schedule is confirmed. We apologize for any inconvenience and appreciate your understanding.
Podziel się swoimi przemyśleniami na temat Liquid Web
Bądź pierwszą osobą, która skomentuje!
Uptimus monitoruje Liquid Web przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 31 komponentów, 64 incydentów, 62 konserwacji i 28 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Liquid Web. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Otrzymuj alerty, gdy Liquid Web lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 64 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „GitHub Peformance Impact”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 31 komponentów Liquid Web: API, Chat, Cloud Load Balancers, LAN Network. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.
| Kryteria porównania | Uptimus | Downdetector |
|---|---|---|
| Zgłoszenia społeczności dotyczące Liquid Web |
Started 12 sie 2026, 13:30 UTC · Resolved 12 sie 2026, 16:30 UTC
The scheduled maintenance has been completed.
Started 3 sie 2026, 08:00 UTC · Resolved 3 sie 2026, 11:00 UTC
The scheduled maintenance has been completed.
Started 27 lip 2026, 08:00 UTC · Resolved 27 lip 2026, 16:00 UTC
The scheduled maintenance has been completed.
Started 23 lip 2026, 02:00 UTC · Resolved 23 lip 2026, 06:00 UTC
The scheduled maintenance has been completed.
Started 8 lip 2026, 07:30 UTC · Resolved 8 lip 2026, 08:30 UTC
The scheduled maintenance has been completed.
Started 8 lip 2026, 01:00 UTC · Resolved 8 lip 2026, 05:00 UTC
| Dostępne |
| Dostępne |
| Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awarii | Dostępne | Dostępne |
|---|
| Aktywność z 24 godzin i regionalna mapa awarii | Dostępne | Dostępne |
|---|
| Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier Android | Dostępne | Oddzielny produkt |
|---|
| Alerty e-mail, push i webhook z tego samego obszaru | Dostępne | Oddzielny produkt |
|---|
| Oficjalne aktualizacje i historia statusu Liquid Web | Dostępne | Oparte na zgłoszeniach |
|---|
| Stan komponentów i prace serwisowe pokazane osobno | Dostępne | Ograniczone publicznie |
|---|
Rate this service
No reviews yet
Sygnały społecznościowe
2 posts from X and Reddit.
A Chiller Failure in Phoenix Took Down Namecheap, Liquid Web and phoenixNAP. https://t.co/Pn9SVRKMJ0 #webhosting
Liquid Web/Nexcess is terrible - Use AWS instead - Phoenix data center outage right now
We host almost 100 business websites with Liquid Web/Nexcess cloud sites. All our websites are now down since this morning. They had an outage that lasted over 24 hours last month and they gave us our monthly hosting amount back. Even before this, we have had so many problems…