Hostinger

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-21 23:36 UTC

   We are performing an emergency maintenance on server FR-990, located in France. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. monitoring 2026-10-21 23:55 UTC

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

3. resolved 2026-10-22 00:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-21 22:52 UTC

   We are performing an emergency maintenance on server 160, located in Singapore. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-21 23:38 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. identified 2026-10-21 17:44 UTC

   Our team is aware about ongoing PHP security vulnerabilities CVE-2026-109618 and CVE-2026-109619 (php2shell). After conducting tests in our hosting environments, we have confirmed out platform is not vulnerable php2shell. We additionally implemented an extra layer of protection...

2. identified 2026-10-21 19:12 UTC

   We have completed update work in our Agency Hosting infrastructure and continue working to finish PHP upgrades to remaining managed hosting servers. We'll provide further updates on progress. Thank you for your patience.

3. identified 2026-10-22 03:34 UTC

   All cPanel servers have been updated to the latest cPanel build, which includes the PHP fix (build 138.18), and the latest Alt-PHP version.

4. monitoring 2026-10-22 06:44 UTC

   PHP upgrades are now complete across all managed hosting servers.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. identified 2026-10-21 11:12 UTC

   We’re currently experiencing an issue with the cPanel license verification system, which may prevent access to cPanel and WHM on some servers. Websites, email, and databases are not affected and continue to operate normally. We’re working closely with the cPanel team to resolve...

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-21 10:50 UTC

   We are performing an emergency maintenance on server 1924, located in Lithuania. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. monitoring 2026-10-21 10:56 UTC

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

3. resolved 2026-10-21 10:58 UTC

   The incident has been resolved. Thank you for your patience and we apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-20 15:05 UTC

   We are performing an emergency maintenance on server 1756, located in the UK. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-20 15:17 UTC

   The issue is resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services were experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:19 UTC

   We are currently investigating this issue.

2. investigating 2026-10-20 06:39 UTC

   We are aware that Hostinger Dashboard and service API is currently not loading for some users, and related services such as Website Builder may also be unavailable. Our team is actively investigating and working on a fix. We will share an update as soon as possible.

3. investigating 2026-10-20 07:03 UTC

   Our team is still actively investigating and working on a fix. We will share an update as soon as possible.

4. identified 2026-10-20 07:20 UTC

   We've identified the cause of this issue. Our third-party cloud provider, Google Cloud, is having a network outage that is affecting Hostinger Dashboard, the service API, Website Builder, Kodee and checkout. Websites hosted with Hostinger are not affected and continue to work...

5. identified 2026-10-20 07:54 UTC

   Google notified us the outage was caused by a power failure at one of their data centers. They are working on restoring service but haven't given a recovery time yet. Hostinger Dashboard, the service API, Website Builder, Kodee and checkout are still unavailable. Websites hosted...

6. identified 2026-10-20 09:16 UTC

   Google has now confirmed this outage on its public status page and says its engineers are still working on it. They haven't given a recovery time yet. Hostinger Dashboard, the service API, Website Builder, Kodee and checkout are still unavailable. Websites hosted with Hostinger...

7. monitoring 2026-10-20 11:42 UTC

   Hostinger Dashboard and the service API are not fully available yet. Some users can't log in to Hostinger Dashboard, and hosting plans and their settings can't be managed at the moment. Websites hosted with Hostinger are not affected and continue to work normally. Our team is...

8. monitoring 2026-10-20 13:45 UTC

   Hostinger Dashboard and the service API are not fully available yet. Some users can't log in to Hostinger Dashboard, and hosting plans and their settings can't be managed at the moment. Websites hosted with Hostinger are not affected and continue to work normally. Our team is...

9. monitoring 2026-10-20 14:37 UTC

   A fix has been pushed and we are now monitoring the results. Hostinger Dashboard, API and hPanel should now be working as expected. We will provide another update when needed. We apologize for the inconvenience caused.

10. resolved 2026-10-20 14:40 UTC

    The issue has been fixed, everything is operating as expected.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-20 03:33 UTC

   We are currently experiencing degraded performance issues on server web1765. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. identified 2026-10-20 05:00 UTC

   A fix is being deployed to the server.

3. monitoring 2026-10-20 07:31 UTC

   The fix has been implemented successfully, and we are monitoring the situation.

4. resolved 2026-10-21 00:51 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-19 22:10 UTC

   We are performing an emergency maintenance on server 1404, located in India. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-19 22:21 UTC

   The incident has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-19 16:49 UTC

   We are performing an emergency maintenance on server 2220, located in India. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-19 17:02 UTC

   Incident is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Hostinger Reach, Hostinger Webmail

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-19 15:21 UTC

   Some customers are experiencing delays or failures when sending emails to external recipients, and their email logs may show a "mail transport unavailable" status. Our team is investigating, and we apologise for the disruption and will share an update as soon as we have more...

2. investigating 2026-10-19 15:26 UTC

   Some customers are experiencing delayed email delivery to external recipients, with logs showing "mail transport unavailable", caused by a temporary spike in email sending load. No emails have been lost and affected emails are expected to be delivered as email logs catch up; we...

3. resolved 2026-10-19 17:30 UTC

   Incident has been resolved. All services are fully operational.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-17 15:22 UTC

   We are performing an emergency maintenance on server 1198, located in Brazil. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. monitoring 2026-10-17 15:40 UTC

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

3. resolved 2026-10-17 15:48 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Hostinger VPS API

Failure mode: Security incident or emergency response to a vulnerability. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. identified 2026-10-16 11:20 UTC

   We are aware of CVE-2026-99999, a critical Linux kernel vulnerability (CVSS 9.3) publicly disclosed on 15 October 2026. It affects the host systems underlying all Hostinger VPS plans. We have been tracking it since publication and are patching our entire server fleet as quickly...

2. investigating 2026-10-17 16:22 UTC

   We are continuing to patch our server fleet against CVE-2026-99999. The rollout is proceeding in batches, and customer VPS are restarted as each batch is completed. We are keeping each interruption as brief as possible and will share a further update once patching is complete....

3. monitoring 2026-10-18 02:31 UTC

   The patch for CVE-2026-99999 has been applied to all VPS nodes and we are monitoring the results.

4. resolved 2026-10-18 07:44 UTC

   This incident has been resolved. The security update has been applied to all VPS host nodes and services are operating normally. Your VPS was briefly restarted during the maintenance. If any application isn’t running, please start it again and make sure it’s set to start...

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-15 15:06 UTC

   We are performing an emergency hardware maintenance on de-fra-pve-node760, located in DE-FRA (Germany). Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We...

2. investigating 2026-10-15 16:03 UTC

   We're currently investigating the issue, and will provide an update soon.

3. investigating 2026-10-15 17:04 UTC

   We're currently investigating the issue, and will provide an update soon

4. monitoring 2026-10-15 18:07 UTC

   We have applied a fix for the issue affecting node de-fra-pve-node760. We are continuing monitoring to confirm it is stable. We apologize for the inconvenience

5. resolved 2026-10-15 18:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-14 09:27 UTC

   We are performing an emergency maintenance on servers 2260, 2261 and 2264, located in Indonesia. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for...

2. resolved 2026-10-14 09:38 UTC

   The emergency maintenance tasks were successfully completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-14 03:23 UTC

   We are performing an emergency maintenance on server ID-2261, ID-2264, located in Indonesia. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-14 03:48 UTC

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

3. resolved 2026-10-14 06:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-14 02:29 UTC

   We are performing an emergency maintenance on server in-1497, located in the India. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-14 04:06 UTC

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

3. resolved 2026-10-14 04:38 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-14 01:16 UTC

   We are performing an emergency maintenance on server br-cam-pve-node2584, located in the Brazil. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for...

2. monitoring 2026-10-14 01:22 UTC

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

3. resolved 2026-10-14 01:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-13 18:56 UTC

   We are performing an emergency maintenance on server in-1497, located in India. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. monitoring 2026-10-13 20:34 UTC

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

3. resolved 2026-10-13 20:51 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-12 13:12 UTC

   We’re currently experiencing degraded performance on Hostinger Horizons. Publishing and Preview may be affected, so publishing changes or loading previews could be slower than usual or temporarily fail. Our team is working to restore normal performance. We apologize for any...

2. monitoring 2026-10-12 13:42 UTC

   A fix is being pushed and we are monitoring the results.

3. resolved 2026-10-12 14:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Managed OpenClaw, Managed Hermes, Hostinger Websites

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-12 12:47 UTC

   We are currently experiencing degraded performance issues on server US-100, located in the United States. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We...

2. identified 2026-10-12 13:01 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-10-12 13:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-12 01:27 UTC

   We are currently experiencing degraded performance issues on server web472. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. identified 2026-10-12 01:35 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-10-12 01:50 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-11 16:56 UTC

   We are performing an emergency maintenance on server UK-913. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.

2. resolved 2026-10-11 17:12 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-10 22:57 UTC

   We are performing an emergency maintenance on server 1577, located in Brazil. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-10 23:03 UTC

   The incident has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-09 17:35 UTC

   We are currently experiencing degraded performance issues on server u4s-105, located in the UK. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for...

2. monitoring 2026-10-09 17:51 UTC

   A fix is being pushed and we are monitoring the results.

3. resolved 2026-10-09 18:13 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-09 15:44 UTC

   We are performing an emergency maintenance on server 1596, located in Brazil. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-09 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Editor

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-09 12:47 UTC

   We are performing an urgent update on one of our servers running Hostinger Horizons sandbox environments. While it is in progress, editor functionalities might not be available, such as opening project in the Horizons editor, live preview, or applying AI edits. Published...

2. monitoring 2026-10-09 13:06 UTC

   The update is complete and the server is back in service. The Horizons editor and live preview are available again for the affected projects. We are monitoring the server to confirm services stability.

3. resolved 2026-10-09 14:32 UTC

   The maintenance has been completed and all services are available again.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-08 13:32 UTC

   We are currently investigating this issue.

2. investigating 2026-10-08 13:36 UTC

   We are investigating reports that customers on several Indian ISPs are unable to reach VPS hosted in our India location. The issue is limited to certain network paths; other networks are not affected. Our team is working on a fix and traffic is being rerouted to restore access....

3. monitoring 2026-10-08 14:07 UTC

   The issue appears to be resolved. We're continuing to monitor the situation.

4. resolved 2026-10-08 14:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-08 10:52 UTC

   We have identified an issue with the database service on server 1066, located in the US. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-08 11:00 UTC

   The database service on server 1066 in US has been restored and websites are loading normally again. No data loss was identified. We are monitoring the server to confirm stability.

3. monitoring 2026-10-08 13:11 UTC

   The incident has been resolved.

4. resolved 2026-10-08 13:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Editor

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-07 20:13 UTC

   Website publishing in Horizons is failing with the message “Publishing failed on our side. Try again later.” We are investigating the issue.

2. monitoring 2026-10-07 20:54 UTC

   We've applied a fix and are monitoring the results.

3. resolved 2026-10-07 21:16 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-07 18:26 UTC

   We are currently experiencing degraded performance issues on server 1530, located in BR. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-07 18:54 UTC

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

3. resolved 2026-10-07 19:01 UTC

   The issue has been fixed

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-07 02:52 UTC

   We've spotted that something has gone wrong with cPanel license checker system. We're currently investigating the issue, in contact with cPanel developer, and will provide an update soon.

2. monitoring 2026-10-07 14:20 UTC

   The issue has been identified and fixed. cPanel and WHM access has been restored on all affected servers and we are currently monitoring the service remains stable

3. resolved 2026-10-08 08:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Hostinger hPanel Backend, Hostinger hPanel Frontend

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 19:21 UTC

   You may not be able to reach or see continuous loading on the cPanel product hosted in Hana hosting. Please note, that no data will be lost and Your websites will not be affected. Thank You for Your patience.

2. monitoring 2026-10-06 19:35 UTC

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

3. resolved 2026-10-06 19:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-06 14:59 UTC

   We are investigating partial connectivity loss to our Mumbai data centre for some Indian clients. Impact: Customers on several Indian ISPs are unable to reach VPS hosted in our India location. Other networks are not affected.

2. monitoring 2026-10-06 15:10 UTC

   We have implemented a fix and monitoring the situation

3. resolved 2026-10-06 15:39 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-06 06:23 UTC

   We are currently experiencing degraded performance issues on server SG-1516, located in Singapore. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for...

2. monitoring 2026-10-06 06:36 UTC

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

3. resolved 2026-10-06 06:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-05 15:05 UTC

   We are performing an emergency maintenance on server br-cam-pve-node2521, located in the Brazil. Client VPS hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-05 15:30 UTC

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

3. resolved 2026-10-05 15:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-04 13:25 UTC

   We are performing an emergency maintenance on server DE-2151, located in Germany. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-10-04 13:37 UTC

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

3. resolved 2026-10-04 13:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-04 13:07 UTC

   We are performing an emergency maintenance on server DE-1814, located in Germany. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. resolved 2026-10-04 13:29 UTC

   Emergency maintenance tasks have been completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-02 11:41 UTC

   We are performing an emergency maintenance on server 1578, located in the us. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-02 12:02 UTC

   All functionality has been restored. Apologies for any inconvenience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-02 06:24 UTC

   We are performing an emergency maintenance on server web1530. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience caused.

2. resolved 2026-10-02 07:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. identified 2026-10-01 10:32 UTC

   We are performing an emergency maintenance on server 1009, located in the Us. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-10-01 10:45 UTC

   The incident has been resolved. Thank you for your patience and we apologize for the inconvenience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-30 20:52 UTC

   We are currently experiencing degraded performance issues on server 1698, located in DE. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-09-30 21:26 UTC

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

3. resolved 2026-09-30 21:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Editor

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-29 15:11 UTC

   We’re investigating a service disruption affecting customer websites on the Hostinger Horizons platform. Our team is working to identify the cause and restore normal operations as quickly as possible. We apologize for the inconvenience caused.

2. monitoring 2026-09-29 15:25 UTC

   AI Builder is stable again, we're currently monitoring.

3. resolved 2026-09-29 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-29 08:00 UTC

   We are performing an emergency maintenance on server 1544, located in the US. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-09-29 08:09 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-27 11:41 UTC

   We are performing an emergency maintenance on servers my-kul-u4s-node1, my-kul-u4s-node2, my-kul-u4s-node3, my-kul-u4s-node4, located in the Malaysia. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to...

2. monitoring 2026-09-27 12:19 UTC

   The issue has identified and a fix has implemented. We are monitoring the result for the next 1 hour.

3. resolved 2026-09-27 13:07 UTC

   The issue has resolved. Thank you for your patience and sorry for the inconvenience caused.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-26 12:57 UTC

   We are performing an emergency maintenance on server my-kul-u4s-node1, my-kul-u4s-node2, my-kul-u4s-node3 and my-kul-u4s-node4 located in the Malaysia. Client websites hosted on these servers could be temporarily inaccessible or might load slower than usual. Our team is...

2. monitoring 2026-09-26 13:14 UTC

   Issue identified and fix implemented. We are monitoring for the next 1 hour.

3. resolved 2026-09-26 14:12 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-25 15:38 UTC

   We are performing an emergency maintenance on Agency Node 9, located in BR. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. resolved 2026-09-25 17:26 UTC

   The issue affecting the websites has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-25 10:31 UTC

   We are performing an emergency maintenance on server US-900, located in the United States. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. identified 2026-09-25 12:36 UTC

   Our team has identified the issue and is working on a fix.

3. monitoring 2026-09-25 13:12 UTC

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

4. resolved 2026-09-25 13:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Affected: Domain Registration & Management System

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-24 19:43 UTC

   We are currently investigating an issue affecting DNS resolution for .shop domains. Some domains under this TLD may be unreachable or fail to resolve. Our team is actively investigating the issue and working toward a resolution. We will provide updates as more information...

2. resolved 2026-09-25 05:57 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-09-24 07:50 UTC

   We are performing an emergency maintenance on server 1476, located in the United Kingdom. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. identified 2026-09-24 09:28 UTC

   We have identified an issue with the server's database service and we are in the process of recovering it. During this process, client websites hosted on this server may show errors related to database connection. Our engineers are actively working to complete the recovery and...

3. identified 2026-09-24 16:04 UTC

   We continue progressing on the recovery process. Thank you for your patience.

4. monitoring 2026-09-24 20:11 UTC

   We have completed the recovery process and the MySQL service is fully operational once again. We're currently monitoring the server health and stability.

5. resolved 2026-09-24 21:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-23 20:31 UTC

   We are performing an emergency maintenance on server 1685, located in the United States. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. monitoring 2026-09-23 20:46 UTC

   A fix has been applied and we're currently monitoring the results.

3. resolved 2026-09-23 21:21 UTC

   The incident has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-23 20:29 UTC

   We are performing an emergency maintenance on server 1683, located in the us. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any inconvenience...

2. monitoring 2026-09-23 20:33 UTC

   We've pushed a fix and are monitoring the results.

3. resolved 2026-09-23 20:57 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-23 09:49 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-23 08:44 UTC

   We are performing an emergency maintenance on server US-903, located in the Phoenix, Arizona. Client websites hosted there could be temporarily inaccessible or might load slower than usual. Our team is currently working to restore normal performance levels. We apologize for any...

2. resolved 2026-09-23 10:20 UTC

   The emergency maintenance tasks have been completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 11:55 UTC

   The issue has been resolved. Network in the Asia region is showing no more issues and users shouldn't experience any packet loss or bad latency.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-22 08:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-21 16:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-21 07:11 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-20 15:57 UTC

   The incident has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-20 11:19 UTC

   The emergency maintenance tasks have been completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-19 02:02 UTC

   The issue has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-18 18:44 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-18 12:29 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-18 01:23 UTC

   The incident has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-17 19:23 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-17 07:34 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 16:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 04:48 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 02:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-14 15:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-13 16:37 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-11 16:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-10 17:24 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-10 20:34 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-09 21:35 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-10 06:28 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-09 13:42 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-09 12:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 15:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 17:55 UTC

   The incident has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 08:21 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 01:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 21:49 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 16:47 UTC

   The incident has been fixed

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-04 13:50 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-04 02:49 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-03 04:19 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-03 00:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-02 14:26 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-02 02:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-02 02:03 UTC

   Issue has been rolled out globally and errors resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 09:26 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 10:05 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 13:51 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-31 00:25 UTC

   We fixed all major issues resulting in increased 5xx errors.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-30 18:59 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-30 13:11 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-29 20:27 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-29 15:36 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-28 20:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 12:44 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-27 09:03 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-26 20:39 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-26 11:07 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-26 09:03 UTC

   The issue has been resolved, all services impacted regained functionality. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-26 01:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-25 20:39 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 16:23 UTC

   The problem has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 14:29 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 11:10 UTC

   Emergency maintenance has been completed, and we’re monitoring the recovery. We apologize for the inconvenience caused.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-24 09:00 UTC

   The impact from the issue is mitigated.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-23 14:42 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-23 03:25 UTC

   The issue resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-22 17:18 UTC

   The issue resolved. We apologize for any inconvenience caused. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-22 17:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-22 05:20 UTC

   The issue resolved. We apologize for any inconvenience caused. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-24 00:42 UTC

   The emergency cPanel transfer/migration for cpl31.main-hosting.eu has been completed successfully.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 04:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-19 18:50 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 21:31 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 17:33 UTC

   Resolved, thank you for the patience!

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-18 12:54 UTC

   Issue with custom code editing has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 06:59 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-14 19:26 UTC

   All issues resolved and service is back to fully operational. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-13 19:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-13 02:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-13 01:05 UTC

   The maintenance has been completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-12 20:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-11 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-10 18:27 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-08 21:36 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-08 06:34 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-07 12:32 UTC

   This incident has been resolved. Server is operating normally. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-06 16:25 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-06 08:17 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-06 00:50 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-05 14:32 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 23:48 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 12:11 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-04 10:18 UTC

   We've spotted the issue and fixed it. Websites should now publish correctly after clicking the "Publish/Update website" button again

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 11:44 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-01 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 16:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 14:37 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 06:50 UTC

   The impact of the issue is resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 01:54 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-29 01:14 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-25 20:27 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-24 18:42 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-24 07:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 14:00 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 21:07 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 15:50 UTC

   The incident has been fixed

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 13:13 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-22 12:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 11:41 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-19 19:36 UTC

   The impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-19 14:57 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-18 19:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-17 07:34 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-16 21:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 07:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-13 19:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-12 15:00 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-10 16:21 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-10 09:17 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 20:59 UTC

   Server is back to normal operation.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-09 11:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-08 22:12 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-07 14:05 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-06 10:26 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-04 23:06 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-03 23:04 UTC

   All issues for affected orders resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 19:05 UTC

   Website restoration is back to normal.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 19:06 UTC

   The issue has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 10:49 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 02:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-01 18:14 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-30 20:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-29 19:41 UTC

   Issue was resolved, thank you for the patience!

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-28 21:10 UTC

   The server is now stable.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-28 17:53 UTC

   Incident has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-27 07:12 UTC

   Our upstream provider has confirmed that the submarine cable repair work has been completed. Network stability for customers hosted in our Mumbai (India) datacenter has remained stable, and this incident is now resolved. Thank you for your patience and understanding.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-06-25 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-24 12:22 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-06-24 12:56 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-24 08:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-24 02:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-23 20:17 UTC

   The incident has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-23 10:02 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-23 03:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-07-28 14:00 UTC

   The issue is identified to be on the Movistar Telefonica ISP provider side. Provider was contacted and provided following instructions: "We ask that you instruct your users to contact our customer service team by first leaving a public message, followed by a private one. In the...

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-20 14:45 UTC

   The issue was resolved and services are back online. Thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-19 14:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-18 16:02 UTC

   The incident is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-18 09:38 UTC

   Issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-18 01:46 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-17 19:58 UTC

   Issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-17 15:11 UTC

   Issue is resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-16 13:51 UTC

   This incident was caused by a third-party provider issue outside of our control.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-14 18:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-13 20:52 UTC

   Features disabled until checking up with Printful. Users are informed via the UI

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-13 05:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-13 02:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-12 01:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-10 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-10 04:26 UTC

   Server is now up and accessible after emergency maintenance

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-09 13:37 UTC

   Server is now up and accessible after emergency maintenance.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-09 09:08 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-08 20:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-08 19:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-08 16:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-08 13:10 UTC

   Problem is mitigated. All systems are operational.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-07 03:09 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-06 11:24 UTC

   Server br-asc-pve-node172 is now up and accessible after emergency maintenance.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-05 10:13 UTC

   Problem is mitigated. All systems are operational.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-04 15:08 UTC

   The maintenance is completed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-04 14:36 UTC

   Issue resolved - all affected website builder got back to normal functioning

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-03 14:10 UTC

   This incident is now closed. The intermittent database connection errors reported earlier were related to a new server-side protection. Affected customers can follow the steps in our support article...

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-02 13:00 UTC

   Issue resolved - all affected website builder got back to normal functioning

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-06-01 13:20 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-31 12:25 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-27 18:28 UTC

   Issue resolved, order payments back to normal.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-26 07:54 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-25 05:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-24 16:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-24 03:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-24 01:29 UTC

   The third-party connectivity issues affecting the US-BOS region have been resolved, and all CDN services are operating normally. Thank you for your patience while we worked with our provider to fix this.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-22 21:48 UTC

   The server was fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-22 21:31 UTC

   Issue solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-21 02:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-18 16:08 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-18 14:57 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-19 07:22 UTC

   Issue has been solved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-17 03:25 UTC

   The issue has been resolved. We apologize for any inconvenience caused, and thanks for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-14 06:14 UTC

   Issue has been solved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-14 03:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-14 02:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-13 16:38 UTC

   The issue is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-13 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-11 14:13 UTC

   The service functionality is back to normal.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-29 06:35 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-09 09:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-09 07:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-09 03:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-09 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-07 17:47 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-07 14:38 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-06 07:37 UTC

   This incident has been resolved. The elevated temperature issue affecting servers in our Singapore data center has been fully mitigated, and all affected servers have returned to normal operating conditions. Services hosted in the Singapore region are now operating normally. We...

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-05 19:16 UTC

   The issue has been identified and resolved. We are continuing to monitor the situation to ensure stability.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-05 16:44 UTC

   The incident is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-05 15:10 UTC

   Webmail (Hostinger Mail) access has been restored and all services are operating normally. We are monitoring to ensure continued stability.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-05 15:10 UTC

   The issue affecting hPanel has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-05 17:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-04 14:10 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-04 16:07 UTC

   The incident is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-04 11:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-02 23:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-04 23:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-30 10:22 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-30 04:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-30 03:26 UTC

   Our emergency maintenance has been completed and all affected services have been fully restored. Traffic is now operating normally and no further issues have been observed. We thank you for your patience and apologize for any inconvenience caused during this time.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-30 03:09 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-30 03:32 UTC

   The impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-29 09:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-29 08:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-29 04:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-28 15:54 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-28 04:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-28 01:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-28 05:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

Names an upstream provider: AWS.

1. resolved 2026-05-06 06:13 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-27 08:18 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-26 22:10 UTC

   The issue is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-26 02:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-25 08:58 UTC

   Incident is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-23 23:27 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-23 21:52 UTC

   Incident is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-05-09 18:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-22 20:34 UTC

   The issue is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-22 09:26 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-21 01:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-20 19:05 UTC

   The incident is solved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-20 14:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-20 11:31 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-18 05:52 UTC

   This incident has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-18 01:52 UTC

   This incident has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-17 10:44 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-17 01:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-16 19:33 UTC

   Incident resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-16 16:12 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-16 15:38 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-15 22:38 UTC

   The incident was resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-14 10:07 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-12 02:26 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-21 09:18 UTC

   This incident has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-11 15:49 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-11 13:30 UTC

   This incident has been resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-11 07:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-10 11:32 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-10 04:29 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-09 22:22 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-09 21:35 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-10 13:17 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-20 13:45 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-09 13:01 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-07 20:57 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-07 19:16 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-07 13:33 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-07 13:38 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-07 09:51 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-05 20:38 UTC

   The incident is solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-05 17:22 UTC

   The issue is fixed

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-03 22:12 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-03 19:30 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-03 09:52 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-03 09:29 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-02 10:33 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-02 09:19 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 22:36 UTC

   The issue has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 22:31 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 22:30 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 22:30 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 17:37 UTC

   This incident is now resolved. No operations were disturbed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 12:55 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 11:26 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 11:41 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 10:15 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 11:13 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 07:18 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 06:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-04-01 05:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-31 19:13 UTC

   The issue is fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-31 16:48 UTC

   The issue has been fixed.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-31 13:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-31 08:22 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-30 08:24 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-30 05:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-29 01:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 19:54 UTC

   The issue has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-30 08:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 21:41 UTC

   All websites are functional and the issue has been solved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 19:17 UTC

   This incident has been resolved. All services are operating normally.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 16:53 UTC

   The fix has been deployed and preview environment operates normally.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 18:13 UTC

   The server is stable and load is back to regular levels.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 15:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 13:45 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 06:21 UTC

   Resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-27 12:46 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-26 15:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-26 08:15 UTC

   The issue resolved. We apologize for any inconvenience caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-26 02:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-26 07:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-26 11:25 UTC

   This incident has been largely resolved. The team is working on further mitigation to prevent such incidents in the future.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-25 19:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-25 04:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-24 19:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-23 14:02 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-25 07:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-23 02:08 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-23 02:07 UTC

   We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-22 23:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-21 16:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-21 08:19 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-20 19:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-20 15:00 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-20 06:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-20 01:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-20 01:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-18 16:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-18 01:06 UTC

   The issue resolved. We apologize for any inconvenience and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-25 15:08 UTC

   We already released a long-term solution. Issues with non-working sites should be resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-17 04:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-16 01:06 UTC

   The issue resolved. We apologize for any inconvenience and thank you for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-15 10:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-17 14:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-16 12:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-13 16:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-13 01:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-13 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-12 20:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-16 11:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-12 08:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-11 22:09 UTC

   The impact from the issue is over.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 20:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 14:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 08:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 05:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 04:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-08 02:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-07 20:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-07 22:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-07 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-07 12:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-06 15:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-06 17:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-12 12:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-06 06:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-05 22:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-05 16:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-05 13:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-05 19:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-04 20:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-04 17:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-04 12:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-04 05:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 22:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 21:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 18:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 16:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 16:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 15:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-03 03:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-02 19:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-02 14:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-02 06:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-01 11:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-01 07:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-01 03:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-28 21:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-28 14:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-27 21:49 UTC

   This incident has been resolved. Thanks for your patience.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-27 13:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-03-02 07:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-26 10:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-26 12:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-26 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-23 04:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-22 19:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-20 21:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-20 09:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-20 03:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-19 15:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-19 08:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-16 23:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.

1. resolved 2026-02-16 20:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Hostinger's status page.