--- service: "YorkHost" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 1 checked_at: "2026-11-02T00:24:47.589Z" url: "https://instatus.com/now/yorkhost.fr" official_status_page: "https://status.yorkhost.fr" website: "https://yorkhost.fr" --- # Is YorkHost down? No, it's up. 0 reports in the last hour. ## Official updates - **RYZEN-GAME-NODE-11 is back up** (RESOLVED, 2026-11-01T19:21:59.000Z): RYZEN-GAME-NODE-11 is back up. This incident was automatically resolved by Instatus monitoring. - **PVE-10 appears to be unresponsive** (RESOLVED, 2026-11-01T09:00:00.000Z): ## Summary On November 1, 2026, starting around 10:00 AM, one of our virtualization nodes became unavailable after its memory was exhausted. Services hosted on this node were unreachable until the node was restarted. Service has been restored. The node's configuration has been corrected so that a similar situation no longer affects the whole node. ## Impact Services hosted on the affected node were interrupted from around 10:00 AM until the node was restarted in the afternoon. They then restarted automatically. Other nodes in our infrastructure were not affected. ## Timeline All times in Paris time (CET), November 1, 2026. | Time | Event | | -------- | ------------------------------------------------------------------------- | | 10:00 AM | Memory exhaustion begins on the node, hosted services become unreachable. | | 4:21 PM | Analysis of the situation in progress. | | 4:25 PM | Root cause identified, fix being applied. | | 4:34 PM | Fix applied, monitoring in progress. | | 4:40 PM | Incident resolved. | We apologize to the affected customers for the inconvenience. - **Client area migration** (NOTSTARTEDYET, 2026-10-30T18:00:00.000Z): We are migrating our client area ([clients.yorkhost.fr](http://clients.yorkhost.fr)) on October 30, 2026, from 7:00 PM to 3:00 AM (Paris time). No full outage is planned, but short interruptions may occur during this window: login, orders, payments, invoices or tickets may briefly be slow or unavailable. Your services (VPS, game servers, web hosting) keep running normally and are not affected by this operation. For anything urgent, our team remains available on Discord and [help.yorkhost.fr](http://help.yorkhost.fr). Thank you for your patience. - **PVE 08 issue** (RESOLVED, 2026-10-29T17:34:12.000Z): **Redémarrage inattendu d’un serveur d’hébergement** Un de nos serveurs d’hébergement en région parisienne a redémarré de façon inattendue, ce qui a brièvement interrompu les services qu’il hébergeait. Le serveur est de nouveau en ligne et les services sont rétablis. La cause est un mécanisme de protection de notre cluster, déclenché par une instabilité réseau sur un serveur distant. Nous l’avons désactivé pour que cela ne puisse plus se reproduire, et nous isolons le serveur à l’origine de l’instabilité. Nous nous excusons pour la gêne occasionnée. - **DNS resolution interrupted for some domains** (RESOLVED, 2026-10-26T01:00:00.000Z): **Summary** During the night of October 25 to 26, 2026, a file system error on the server hosting our primary nameserver ([ns1.yorkdns.com](http://ns1.yorkdns.com)) prevented it from answering queries. Our secondary nameserver ([ns2.yorkdns.com](http://ns2.yorkdns.com)) took over as intended, and the vast majority of domains remained reachable. However, some zones were not properly replicated to it: * **30 zones** had never been transferred to ns2\. While ns1 was unavailable, these domains no longer resolved. * **109 zones** were served by ns2, but in a version dating from October 22: changes made since then had not been propagated. No data was lost. **Timeline** (Paris time) | Time | Event | | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | Oct 22 | Release of a new version of our DNS management tool, introducing the two replication issues described below. No visible effect while ns1 was running. | | Oct 26, 02:00 | Start of incident: ns1 stops responding. ns2 takes over, except for the affected zones. | | 07:00 | First customer reports, investigation started. | | 10:00 | Cause of the ns1 outage identified, work in progress. | | 10:25 | ns1 repaired and back in service. All domains resolve again. | | 10:55 | Replication issue identified. The 30 missing zones are transferred to ns2. | | 11:13 | Fix for the 109 outdated zones validated, then applied to all of them. | | 11:25 | All 328 zones are identical on ns1 and ns2. | | 11:45 | Incident resolved. | **Root cause** The ns1 outage revealed two issues introduced on October 22: 1. **Wrong zone type**: our DNS management tool created new zones with the “Native” type instead of “Primary”. A Native zone is never announced to the secondary server, so it never receives it. 2. **Lowered serial number**: an update operation decreased the version number (serial) of 109 zones. A secondary server only accepts an update if this number increases, so ns2 kept the old version of these zones. Our monitoring checked the network availability of the servers, but neither their DNS answers nor the replication between them. These issues therefore remained unnoticed until the incident. **Resolution** The ns1 server was repaired and its configuration hardened. The zones were fixed, and a zone-by-zone comparison confirms that all 328 zones answer identically on both servers. **Prevention** * **Tool fix**: every zone is now created as a primary zone and announced to ns2 upon creation, then after every change. * **Monitoring**: probes that query ns1 and ns2 directly with real DNS requests, alerting us within one to two minutes if either stops responding. We apologise to all affected customers. For any question about a specific domain, our support team remains available. ## YorkHost outage FAQ ### Is YorkHost down right now? No, it's up. 0 reports in the last hour. ### Is YorkHost down for everyone or just me? It looks like it's just you. Reports for YorkHost are at their usual level, so try reloading, checking your connection, or signing out and back in. ### What problems are people reporting with YorkHost? Nobody has said what's broken with YorkHost in the last hour. If something isn't working for you, pick it above so others can see. ### When was the last YorkHost outage? Reports for YorkHost haven't spiked in the last 30 days. ### Does YorkHost have a status page? Yes. YorkHost posts updates on its official status page, which currently says operational. [Go to status page](https://status.yorkhost.fr/) ### What can I do if YorkHost isn't working? Check this page and YorkHost's status page for updates, and wait a few minutes before trying again. Skip reinstalling: if it's an outage, the fix is on their side. ### How do I report a YorkHost problem? Hit “I have an issue too” at the top of this page and pick what's broken. Your report shows on the live chart within a minute, and you can leave a comment to tell others what you're seeing. ### How does Instatus Now know? We combine reports from people on this page with YorkHost's official status page, which we check every minute.