Prism Status - Incident history https://prismstatus.com Prism Sat, 3 Oct 2026 05:08:48 +0000 Service disruption: TX.1515 (node #85) Type: Incident Duration: 10 hours and 40 minutes Affected Components: DAL - Dallas, US Oct 3, 05:08:48 GMT+0 - Investigating - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 3, 15:48:22 GMT+0 - Resolved - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system. Type: Incident

Duration: 10 hours and 40 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>05:08:48</var> GMT+0</small><br><strong>Investigating</strong> - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>15:48:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system..</p> ]]> Sat, 3 Oct 2026 05:08:48 +0000 https://prismstatus.com/incident/cmurxpguf000c0xnru8q3uirs https://prismstatus.com/incident/cmurxpguf000c0xnru8q3uirs Service disruption: TX.1515 (node #85) Type: Incident Duration: 1 hour and 15 minutes Affected Components: DAL - Dallas, US Oct 3, 02:46:47 GMT+0 - Investigating - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 3, 04:01:21 GMT+0 - Resolved - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system. Type: Incident

Duration: 1 hour and 15 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>02:46:47</var> GMT+0</small><br><strong>Investigating</strong> - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>04:01:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system..</p> ]]> Sat, 3 Oct 2026 02:46:47 +0000 https://prismstatus.com/incident/cmursmub603f313o0mk5po3ff https://prismstatus.com/incident/cmursmub603f313o0mk5po3ff Service disruption: TX.1517 (node #115) Type: Incident Duration: 53 minutes Affected Components: DAL - Dallas, US Oct 2, 21:19:48 GMT+0 - Investigating - Our automated monitoring has detected that TX.1517 (node #115) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 2, 22:12:21 GMT+0 - Resolved - This incident is resolved. TX.1517 (node #115) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system. Type: Incident

Duration: 53 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>21:19:48</var> GMT+0</small><br><strong>Investigating</strong> - Our automated monitoring has detected that TX.1517 (node #115) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>22:12:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. TX.1517 (node #115) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system..</p> ]]> Fri, 2 Oct 2026 21:19:48 +0000 https://prismstatus.com/incident/cmurgyb5u04n10wlgq1wi1mg2 https://prismstatus.com/incident/cmurgyb5u04n10wlgq1wi1mg2 Service disruption: TX.1515 (node #85) Type: Incident Duration: 4 hours and 23 minutes Affected Components: DAL - Dallas, US Oct 2, 11:38:35 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1515 (node #85). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 2, 16:01:45 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1515 (node #85) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 4 hours and 23 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>11:38:35</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1515 (node #85). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>16:01:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1515 (node #85) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Fri, 2 Oct 2026 11:38:35 +0000 https://prismstatus.com/incident/cmuqwa84q00wv0wqqk2srmb8j https://prismstatus.com/incident/cmuqwa84q00wv0wqqk2srmb8j Service disruption: TX.1011 (node #16) Type: Incident Duration: 6 minutes Affected Components: DAL - Dallas, US Oct 1, 17:34:36 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 1, 17:40:45 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>17:34:36</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>17:40:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 1 Oct 2026 17:34:36 +0000 https://prismstatus.com/incident/cmuptk6g001dm1mnq8g3b25wd https://prismstatus.com/incident/cmuptk6g001dm1mnq8g3b25wd Service disruption: TX.1011 (node #16) Type: Incident Duration: 1 hour and 14 minutes Affected Components: DAL - Dallas, US Oct 1, 16:11:08 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 1, 17:24:45 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 1 hour and 14 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>16:11:08</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>17:24:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 1 Oct 2026 16:11:08 +0000 https://prismstatus.com/incident/cmupqlfro00tr1cs5yvw9u3zs https://prismstatus.com/incident/cmupqlfro00tr1cs5yvw9u3zs Service disruption: TX.1011 (node #16) Type: Incident Duration: 38 minutes Affected Components: DAL - Dallas, US Oct 1, 15:29:03 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 1, 16:06:45 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 38 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>15:29:03</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1011 (node #16). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>16:06:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1011 (node #16) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 1 Oct 2026 15:29:03 +0000 https://prismstatus.com/incident/cmupp3fd900cm13nqixhx1d96 https://prismstatus.com/incident/cmupp3fd900cm13nqixhx1d96 Service disruption: TX.1000 (node #9) Type: Incident Duration: 2 hours and 12 minutes Affected Components: DAL - Dallas, US Oct 1, 15:28:57 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1000 (node #9). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Oct 1, 17:40:45 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1000 (node #9) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 2 hours and 12 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>15:28:57</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1000 (node #9). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>17:40:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1000 (node #9) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 1 Oct 2026 15:28:57 +0000 https://prismstatus.com/incident/cmupp3f9j00ip1mqnswhi8ald https://prismstatus.com/incident/cmupp3f9j00ip1mqnswhi8ald Service disruption: LON-4 (node #98) Type: Incident Duration: 11 minutes Affected Components: LON - London, GB Sep 30, 14:58:34 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 30, 15:09:44 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>14:58:34</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>15:09:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Wed, 30 Sep 2026 14:58:34 +0000 https://prismstatus.com/incident/cmuo8juxu0a521mpasksyu4jm https://prismstatus.com/incident/cmuo8juxu0a521mpasksyu4jm Service disruption: LON-2 (node #33) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 30, 09:45:40 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 30, 09:51:43 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>09:45:40</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>09:51:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Wed, 30 Sep 2026 09:45:40 +0000 https://prismstatus.com/incident/cmunxd9e400rd1al5g4x4f5ly https://prismstatus.com/incident/cmunxd9e400rd1al5g4x4f5ly Service disruption: TX.1515 (node #85) Type: Incident Duration: 8 hours and 21 minutes Affected Components: DAL - Dallas, US Sep 30, 06:53:29 GMT+0 - Investigating - Our control panel is currently unable to connect to TX.1515 (node #85). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 30, 15:14:44 GMT+0 - Resolved - This incident is resolved. Our control panel can reach TX.1515 (node #85) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 8 hours and 21 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>06:53:29</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to TX.1515 (node #85). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>15:14:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach TX.1515 (node #85) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Wed, 30 Sep 2026 06:53:29 +0000 https://prismstatus.com/incident/cmunr7yxp057p0wpaaktx8ngv https://prismstatus.com/incident/cmunr7yxp057p0wpaaktx8ngv Service disruption: TX.1515 (node #85) Type: Incident Duration: 4 hours and 52 minutes Affected Components: DAL - Dallas, US Sep 30, 01:22:45 GMT+0 - Investigating - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 30, 06:14:43 GMT+0 - Resolved - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system. Type: Incident

Duration: 4 hours and 52 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>01:22:45</var> GMT+0</small><br><strong>Investigating</strong> - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>06:14:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system..</p> ]]> Wed, 30 Sep 2026 01:22:45 +0000 https://prismstatus.com/incident/cmunfbpp702jh13n0edz5a11o https://prismstatus.com/incident/cmunfbpp702jh13n0edz5a11o Service disruption: LON-4 (node #98) Type: Incident Duration: 11 minutes Affected Components: LON - London, GB Sep 29, 12:54:43 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 29, 13:05:42 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:54:43</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>13:05:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 29 Sep 2026 12:54:43 +0000 https://prismstatus.com/incident/cmumopo7u02fn13o4zj8mj5n9 https://prismstatus.com/incident/cmumopo7u02fn13o4zj8mj5n9 Service disruption: LON-6 (node #100) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 29, 12:54:37 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-6 (node #100). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 29, 13:00:44 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:54:37</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-6 (node #100). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>13:00:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 29 Sep 2026 12:54:37 +0000 https://prismstatus.com/incident/cmumoocby01wk13nl0ikeau0p https://prismstatus.com/incident/cmumoocby01wk13nl0ikeau0p Service disruption: LON-2 (node #33) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 29, 12:33:42 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 29, 12:39:42 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:33:42</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:39:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 29 Sep 2026 12:33:42 +0000 https://prismstatus.com/incident/cmumnxfwe052a13obndkr3rg0 https://prismstatus.com/incident/cmumnxfwe052a13obndkr3rg0 Service disruption: LON-1 (node #32) +2 more Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 29, 12:33:33 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-1 (node #32), LON-3 (node #64), LON-6 (node #100). The machines may still be online, but we can't manage or monitor the game servers hosted on them right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 29, 12:39:42 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-1 (node #32), LON-3 (node #64), LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:33:33</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-1 (node #32), LON-3 (node #64), LON-6 (node #100). The machines may still be online, but we can't manage or monitor the game servers hosted on them right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:39:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-1 (node #32), LON-3 (node #64), LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 29 Sep 2026 12:33:33 +0000 https://prismstatus.com/incident/cmumnxfzz052d13ob2f6329al https://prismstatus.com/incident/cmumnxfzz052d13ob2f6329al Service disruption: LON-2 (node #33) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 28, 15:26:34 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 28, 15:32:41 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>15:26:34</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>15:32:41</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Mon, 28 Sep 2026 15:26:34 +0000 https://prismstatus.com/incident/cmuleo0f900050xqwslco54qm https://prismstatus.com/incident/cmuleo0f900050xqwslco54qm Service disruption: LON-2 (node #33) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 26, 15:41:19 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 26, 15:47:27 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>15:41:19</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>15:47:27</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Sat, 26 Sep 2026 15:41:19 +0000 https://prismstatus.com/incident/cmuikb9wf01zy1bpmn5mdgizp https://prismstatus.com/incident/cmuikb9wf01zy1bpmn5mdgizp Service disruption: LON-6 (node #100) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 26, 15:41:14 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-6 (node #100). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 26, 15:47:27 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>15:41:14</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-6 (node #100). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>15:47:27</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Sat, 26 Sep 2026 15:41:14 +0000 https://prismstatus.com/incident/cmuikba0f0drp1mpi7hay4tro https://prismstatus.com/incident/cmuikba0f0drp1mpi7hay4tro Service disruption: TX.1515 (node #85) Type: Incident Duration: 26 minutes Affected Components: DAL - Dallas, US Sep 26, 02:12:47 GMT+0 - Investigating - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 26, 02:38:26 GMT+0 - Resolved - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system. Type: Incident

Duration: 26 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>02:12:47</var> GMT+0</small><br><strong>Investigating</strong> - Our automated monitoring has detected that TX.1515 (node #85) is unresponsive. It is no longer answering external health checks and our control panel can no longer connect to it. This may be due to a possible power, network, or hardware fault. Other nodes in this location are still online, so this is not a full-location outage. If your server is hosted on one of them it should be unaffected. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>02:38:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. TX.1515 (node #85) is back online and Docker is running the game servers normally again. This update was posted automatically by our monitoring system..</p> ]]> Sat, 26 Sep 2026 02:12:47 +0000 https://prismstatus.com/incident/cmuhrc8zo06s80wnpx13psd92 https://prismstatus.com/incident/cmuhrc8zo06s80wnpx13psd92 Service disruption: LON-4 (node #98) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 24, 18:04:27 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 24, 18:10:25 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>18:04:27</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>18:10:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 24 Sep 2026 18:04:27 +0000 https://prismstatus.com/incident/cmufujgx60ceh1argx1ti21bi https://prismstatus.com/incident/cmufujgx60ceh1argx1ti21bi Service disruption: LON-1 (node #32) +1 more Type: Incident Duration: 11 minutes Affected Components: LON - London, GB Sep 24, 17:59:03 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-1 (node #32), LON-6 (node #100). The machines may still be online, but we can't manage or monitor the game servers hosted on them right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 24, 18:10:25 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-1 (node #32), LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>17:59:03</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-1 (node #32), LON-6 (node #100). The machines may still be online, but we can't manage or monitor the game servers hosted on them right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>18:10:25</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-1 (node #32), LON-6 (node #100) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Thu, 24 Sep 2026 17:59:03 +0000 https://prismstatus.com/incident/cmufucxhj0c831mrgl9smhovt https://prismstatus.com/incident/cmufucxhj0c831mrgl9smhovt Service disruption: LON-1 (node #32) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 22, 21:25:20 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-1 (node #32). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 22, 21:31:21 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-1 (node #32) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>21:25:20</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-1 (node #32). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Other nodes in this location are unaffected. If your server is hosted on one of them it should be working normally. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>21:31:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-1 (node #32) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 22 Sep 2026 21:25:20 +0000 https://prismstatus.com/incident/cmud6ub7q053w1bnzq7nh2dc5 https://prismstatus.com/incident/cmud6ub7q053w1bnzq7nh2dc5 Service disruption: LON-2 (node #33) Type: Incident Duration: 11 minutes Affected Components: LON - London, GB Sep 22, 11:13:57 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 22, 11:25:21 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 11 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>11:13:57</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-2 (node #33). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>11:25:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-2 (node #33) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Tue, 22 Sep 2026 11:13:57 +0000 https://prismstatus.com/incident/cmucl0bpp1hs713ru7trvfzv7 https://prismstatus.com/incident/cmucl0bpp1hs713ru7trvfzv7 Service disruption: LON-4 (node #98) Type: Incident Duration: 6 minutes Affected Components: LON - London, GB Sep 20, 16:05:14 GMT+0 - Investigating - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system. Sep 20, 16:11:19 GMT+0 - Resolved - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system. Type: Incident

Duration: 6 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>16:05:14</var> GMT+0</small><br><strong>Investigating</strong> - Our control panel is currently unable to connect to LON-4 (node #98). The machine may still be online, but we can't manage or monitor the game servers hosted on it right now. Our technicians have been notified and are investigating; we'll post updates here as we learn more. This update was posted automatically by our monitoring system..</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>16:11:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident is resolved. Our control panel can reach LON-4 (node #98) again and game server management is back to normal. This update was posted automatically by our monitoring system..</p> ]]> Sun, 20 Sep 2026 16:05:14 +0000 https://prismstatus.com/incident/cmua0isyd16ny13pcilqh3eq7 https://prismstatus.com/incident/cmua0isyd16ny13pcilqh3eq7 Ashburn & New York Network Upgrades Type: Maintenance Duration: 2 hours Affected Components: ASH - Ashburn, US, NYC - New York, US Jul 19, 01:57:42 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Aug 8, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 8, 04:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: ,

<p><small>Jul <var data-var='date'> 19</var>, <var data-var='time'>01:57:42</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 8 Aug 2026 02:00:00 +0000 https://prismstatus.com/maintenance/cmrr5bnsw0scu0zlk8af0mhqv https://prismstatus.com/maintenance/cmrr5bnsw0scu0zlk8af0mhqv NAE-24 Migration Type: Maintenance Duration: 1 hour Affected Components: NYC - New York, US Jul 24, 18:18:09 GMT+0 - Identified - During this maintenance window, we will migrate all servers off node **NAE-24** to proactively perform hardware maintenance and replace one of the storage drives. No issues have been detected, and your data remains safe thanks to RAID drive redundancy. However, one of the two drives is approaching the end of its expected service life, so we are replacing it proactively to maintain reliability and prevent future issues. The maintenance window is expected to last no longer than **30 minutes**. Jul 26, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 26, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>18:18:09</var> GMT+0</small><br><strong>Identified</strong> - During this maintenance window, we will migrate all servers off node **NAE-24** to proactively perform hardware maintenance and replace one of the storage drives. No issues have been detected, and your data remains safe thanks to RAID drive redundancy. However, one of the two drives is approaching the end of its expected service life, so we are replacing it proactively to maintain reliability and prevent future issues. The maintenance window is expected to last no longer than **30 minutes**..</p> <p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 26 Jul 2026 06:00:00 +0000 https://prismstatus.com/maintenance/cmrz9jsih01eg1aqdrmqqywfs https://prismstatus.com/maintenance/cmrz9jsih01eg1aqdrmqqywfs Emergency Security Response Type: Maintenance Duration: 1 day, 6 hours and 59 minutes Affected Components: MTL - Montreal, QC, AMS - Amsterdam, NL, SYD - Sydney, AU, ASH - Ashburn, US, MIA - Miami, US, SIN - Singapore, SG, DAL - Dallas, US, FRA - Frankfurt, DE, LON - London, GB, NYC - New York, US, LAX - Los Angeles, US Jul 9, 08:53:50 GMT+0 - Identified - Earlier today we issued a patch for \[CVE-2026-43499\](<https://thecybersecguru.com/news/ghostlock-cve-2026-43499-linux-kernel-0day/>). To clean up related files/packages/etc and make final applications we're going to be restarting nodes over the next hour. This will result in a roughly 5 minute outage (all connections will drop and your server will restart) for your server during the rolling window (2AM PST - 3AM PST) This is a necessary measure for keeping our infrastructure secure. We normally don't restart machines on short notice (for obvious reasons) but this is a bit of an exception given that this directly affects our infrastructure and is being actively exploited across the wider web Jul 9, 09:00:52 GMT+0 - Identified - Maintenance is now in progress. Jul 10, 16:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 day, 6 hours and 59 minutes

Affected Components: , , , , , , , , , ,

<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>08:53:50</var> GMT+0</small><br><strong>Identified</strong> - Earlier today we issued a patch for \[CVE-2026-43499\](<https://thecybersecguru.com/news/ghostlock-cve-2026-43499-linux-kernel-0day/>). To clean up related files/packages/etc and make final applications we're going to be restarting nodes over the next hour. This will result in a roughly 5 minute outage (all connections will drop and your server will restart) for your server during the rolling window (2AM PST - 3AM PST) This is a necessary measure for keeping our infrastructure secure. We normally don't restart machines on short notice (for obvious reasons) but this is a bit of an exception given that this directly affects our infrastructure and is being actively exploited across the wider web.</p> <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>09:00:52</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 10 Jul 2026 15:00:00 +0000 https://prismstatus.com/maintenance/cmrd9say200rk1blamr9n0z61 https://prismstatus.com/maintenance/cmrd9say200rk1blamr9n0z61 FRA-7 Migration Type: Maintenance Duration: 1 hour Affected Components: FRA - Frankfurt, DE Jun 29, 22:40:55 GMT+0 - Identified - We will be migrating all servers from FRA-7 to FRA-9 so we can perform hardware upgrades on FRA-7. Servers affected by this migration have received a notice in the panel & will have the option to migrate before the deadline of July 1st. Migrating should cause 2-20 minutes of downtime depending on server size & will change your IP address. Subdomains will automatically update whereas the numerical one will be different. Jul 1, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 1, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Jun <var data-var='date'> 29</var>, <var data-var='time'>22:40:55</var> GMT+0</small><br><strong>Identified</strong> - We will be migrating all servers from FRA-7 to FRA-9 so we can perform hardware upgrades on FRA-7. Servers affected by this migration have received a notice in the panel & will have the option to migrate before the deadline of July 1st. Migrating should cause 2-20 minutes of downtime depending on server size & will change your IP address. Subdomains will automatically update whereas the numerical one will be different..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 1 Jul 2026 14:00:00 +0000 https://prismstatus.com/maintenance/cmqzsxf4u01ci0zphjmpp2rls https://prismstatus.com/maintenance/cmqzsxf4u01ci0zphjmpp2rls Backup Repository Maintenance Type: Maintenance Duration: 1 hour and 35 minutes Affected Components: Borg Mass Offsite Storage Repository Jun 30, 03:03:01 GMT+0 - Identified - **We will be performing maintenance on our self serve backup infrastructure** for the next 2 hours to migrate our spread of legacy backups from resticserver, pterodactyl s3, and nfs to our _new_ borg infrastructure. During this period, you will be able to create new backups but downloading & restoring previously created backups may fail intermittently. We have scheduled previous maintenance periods to address this but ran into various issues (i.e. providers thinking the transfer was a DoS, null routes, slow transfers, etc). Apparently it's quite hard to transfer nearly a hundred terabytes of un-deduplicated backups across the internet. Legacy clusters have been prepped in advance for this & have been uploading backups over the past few days. This maintenance is primarily for mass updating our node management daemons. This upgrade will (finally) significantly increase backup speed & will resolve issues with backup transfers/failures. Jun 30, 03:29:59 GMT+0 - Identified - Maintenance is now in progress. Jun 30, 05:05:00 GMT+0 - Completed - Maintenance has completed successfully Jun 30, 04:40:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour and 35 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>03:03:01</var> GMT+0</small><br><strong>Identified</strong> - **We will be performing maintenance on our self serve backup infrastructure** for the next 2 hours to migrate our spread of legacy backups from resticserver, pterodactyl s3, and nfs to our _new_ borg infrastructure. During this period, you will be able to create new backups but downloading & restoring previously created backups may fail intermittently. We have scheduled previous maintenance periods to address this but ran into various issues (i.e. providers thinking the transfer was a DoS, null routes, slow transfers, etc). Apparently it's quite hard to transfer nearly a hundred terabytes of un-deduplicated backups across the internet. Legacy clusters have been prepped in advance for this & have been uploading backups over the past few days. This maintenance is primarily for mass updating our node management daemons. This upgrade will (finally) significantly increase backup speed & will resolve issues with backup transfers/failures..</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>03:29:59</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>05:05:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>04:40:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 30 Jun 2026 03:05:00 +0000 https://prismstatus.com/maintenance/cmr02ah2r03jg0zn4mmmbsfmy https://prismstatus.com/maintenance/cmr02ah2r03jg0zn4mmmbsfmy Legacy Node Migrations (Ashburn, Dallas, Frankfurt, and Singapore) Type: Maintenance Duration: 3 hours Apr 5, 16:00:00 GMT+0 - Identified - Hello, We will be performing emergency migrations on the following machines: **Ashburn:** ASH-1, ASH-2, ASH-3, ASH-5, ASH-6, ASH-10, ASH-13, ASH-28, ASH-29, ASH-30 **Frankfurt:** FRA-1, FRA-2, FRA-3, FRA-4, FRA-5, FRA-6 **Dallas:** DAL-3 **Singapore:** SGP-1 These machines are running legacy deployments that are incompatible with our automated infrastructure management platform. Each machine will be manually reinstalled and redeployed to bring it in line with our current stack. **This process may result in an IP address change for affected servers.** The maintenance window is scheduled for **3 hours**, though the individual impact per server will range from approximately **5 to 30 minutes** of downtime. For servers in **Ashburn** and **Frankfurt**, users have the option to migrate ahead of time through the panel. We recommend doing so at your earliest convenience so you can make any necessary adjustments, such as updating DNS records or firewall rules, on your own schedule. Apr 5, 16:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 5, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

<p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - Hello, We will be performing emergency migrations on the following machines: **Ashburn:** ASH-1, ASH-2, ASH-3, ASH-5, ASH-6, ASH-10, ASH-13, ASH-28, ASH-29, ASH-30 **Frankfurt:** FRA-1, FRA-2, FRA-3, FRA-4, FRA-5, FRA-6 **Dallas:** DAL-3 **Singapore:** SGP-1 These machines are running legacy deployments that are incompatible with our automated infrastructure management platform. Each machine will be manually reinstalled and redeployed to bring it in line with our current stack. **This process may result in an IP address change for affected servers.** The maintenance window is scheduled for **3 hours**, though the individual impact per server will range from approximately **5 to 30 minutes** of downtime. For servers in **Ashburn** and **Frankfurt**, users have the option to migrate ahead of time through the panel. We recommend doing so at your earliest convenience so you can make any necessary adjustments, such as updating DNS records or firewall rules, on your own schedule..</p> <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>16:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 5 Apr 2026 16:00:00 +0000 https://prismstatus.com/maintenance/cmnkzfvvx01pkyn6vbi5ik16d https://prismstatus.com/maintenance/cmnkzfvvx01pkyn6vbi5ik16d FRANKFURT NETWORK UPGRADES Type: Maintenance Duration: 2 hours Affected Components: Frankfurt Database Functions Feb 13, 13:00:00 GMT+0 - Identified - We will be performing network maintenance on our Frankfurt infrastructure to onboard CDN77 as an additional transit provider and migrate the remaining nodes to Prism-owned IP subnets. This change is part of a broader network upgrade and will significantly improve DDoS protection, routing reliability, and latency consistency for services hosted in Frankfurt. What’s changing * All affected services will receive new IP addresses * Prism subdomains will update automatically. No action is required if you connect via a Prism hostname * If you connect using a raw IP address, you will need to update it once the migration is complete Impact * Brief network interruptions may occur during the IP transition * No data loss is expected * Services will resume automatically once routing propagates Benefits * Improved resilience against DDoS attacks * More stable and predictable routing * Better overall network performance in Frankfurt We will email all affected users with details and updated connection information ahead of the change. Feb 13, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 13, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components:

<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be performing network maintenance on our Frankfurt infrastructure to onboard CDN77 as an additional transit provider and migrate the remaining nodes to Prism-owned IP subnets. This change is part of a broader network upgrade and will significantly improve DDoS protection, routing reliability, and latency consistency for services hosted in Frankfurt. What’s changing * All affected services will receive new IP addresses * Prism subdomains will update automatically. No action is required if you connect via a Prism hostname * If you connect using a raw IP address, you will need to update it once the migration is complete Impact * Brief network interruptions may occur during the IP transition * No data loss is expected * Services will resume automatically once routing propagates Benefits * Improved resilience against DDoS attacks * More stable and predictable routing * Better overall network performance in Frankfurt We will email all affected users with details and updated connection information ahead of the change..</p> <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 13 Feb 2026 13:00:00 +0000 https://prismstatus.com/maintenance/cmldbkcrj0f881qtdcvokrefx https://prismstatus.com/maintenance/cmldbkcrj0f881qtdcvokrefx Backup Infrastructure Upgrade Type: Maintenance Duration: 4 hours Affected Components: Borg Mass Offsite Storage Repository, , Backup Infrastructure → Jan 31, 19:00:00 GMT+0 - Identified - We will be performing a major overhaul of our backup infrastructure to significantly improve backup and restore speeds, increase overall reliability, and introduce data deduplication to reduce storage overhead. This maintenance involves migrating several hundred terabytes of existing backup data to our new storage system. Due to the scale of the migration, this process may take an extended period to complete. During this time, backups may run slower than usual or be temporarily paused, but live services will remain unaffected. We will closely monitor the migration and provide updates if there are any changes to expected behavior. Once completed, customers can expect faster backups, quicker restores, and a more resilient backup platform going forward. Thank you for your patience while we make these long-term improvements. Jan 31, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 31, 23:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 4 hours

Affected Components: ,

<p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be performing a major overhaul of our backup infrastructure to significantly improve backup and restore speeds, increase overall reliability, and introduce data deduplication to reduce storage overhead. This maintenance involves migrating several hundred terabytes of existing backup data to our new storage system. Due to the scale of the migration, this process may take an extended period to complete. During this time, backups may run slower than usual or be temporarily paused, but live services will remain unaffected. We will closely monitor the migration and provide updates if there are any changes to expected behavior. Once completed, customers can expect faster backups, quicker restores, and a more resilient backup platform going forward. Thank you for your patience while we make these long-term improvements..</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>19:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 31 Jan 2026 19:00:00 +0000 https://prismstatus.com/maintenance/cmkywpejm0f4wtpjjgbgxur8b https://prismstatus.com/maintenance/cmkywpejm0f4wtpjjgbgxur8b ASH-8 Full Hardware Replacement (please check your email if you're on this node) Type: Maintenance Duration: 1 hour Jan 5, 17:30:00 GMT+0 - Identified - We will be migrating all services off **ASH-8** following a recent hardware failure. ASH-8 is legacy infrastructure and will be fully retired to prevent further instability. **Impact:** During the migration, affected servers will experience downtime while data is transferred and the service is brought back online. **This migration will require an IP change**. **Action required:** Please open a support ticket so we can schedule a migration time that works for you, coordinate any DNS/allowlist changes, and discuss compensation. If we do not hear from you, we will **automatically migrate your server on Monday during this maintenance window**. Jan 5, 17:30:01 GMT+0 - Identified - Maintenance is now in progress Jan 5, 18:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Identified</strong> - We will be migrating all services off **ASH-8** following a recent hardware failure. ASH-8 is legacy infrastructure and will be fully retired to prevent further instability. **Impact:** During the migration, affected servers will experience downtime while data is transferred and the service is brought back online. **This migration will require an IP change**. **Action required:** Please open a support ticket so we can schedule a migration time that works for you, coordinate any DNS/allowlist changes, and discuss compensation. If we do not hear from you, we will **automatically migrate your server on Monday during this maintenance window**..</p> <p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>17:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 5 Jan 2026 17:30:00 +0000 https://prismstatus.com/maintenance/cmjzfmyvq02patbuev28xhbee https://prismstatus.com/maintenance/cmjzfmyvq02patbuev28xhbee North America Database Maintenance Type: Maintenance Duration: 1 hour Affected Components: Borg Mass Offsite Storage Repository Jan 3, 02:00:00 GMT+0 - Identified - During this maintenance window, we will be migrating our NA database infrastructure and implementing onsite SSD caches at each location to increase backup throughput. Jan 3, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 3, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - During this maintenance window, we will be migrating our NA database infrastructure and implementing onsite SSD caches at each location to increase backup throughput..</p> <p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 3 Jan 2026 02:00:00 +0000 https://prismstatus.com/maintenance/cmjwdbm1701fsj336b6qmiw25 https://prismstatus.com/maintenance/cmjwdbm1701fsj336b6qmiw25 European Database Maintenance Type: Maintenance Duration: 1 hour Jan 2, 20:00:00 GMT+0 - Identified - During this maintenance window, we will be migrating our European database infrastructure and implementing onsite SSD caches at each location to increase backup throughput. Jan 2, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 2, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Identified</strong> - During this maintenance window, we will be migrating our European database infrastructure and implementing onsite SSD caches at each location to increase backup throughput..</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 2 Jan 2026 20:00:00 +0000 https://prismstatus.com/maintenance/cmjwd8i8u00on3whphacimius https://prismstatus.com/maintenance/cmjwd8i8u00on3whphacimius Panel Updates Type: Maintenance Duration: 10 minutes Affected Components: Game Panel (Replica Aggregate) Jan 2, 10:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Servers will remain accessible and joinable but will be unable to control during this window. Jan 2, 10:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 2, 10:10:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 10 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. Servers will remain accessible and joinable but will be unable to control during this window..</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jan <var data-var='date'> 2</var>, <var data-var='time'>10:10:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 2 Jan 2026 10:00:00 +0000 https://prismstatus.com/maintenance/cmjwdkl8600ognec8gamyvxnw https://prismstatus.com/maintenance/cmjwdkl8600ognec8gamyvxnw LON-1 / 2 Maintenance Type: Maintenance Duration: 3 hours and 29 minutes Dec 4, 17:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. The per node impact should be about \~10 minutes as we swap some hardware. Dec 4, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 4, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Dec 4, 20:06:49 GMT+0 - Identified - Maintenance is now in progress. Dec 4, 20:16:47 GMT+0 - Completed - lon1 is up Dec 4, 20:21:26 GMT+0 - Identified - lon2 is being worked on Dec 4, 20:28:40 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 3 hours and 29 minutes

<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time. The per node impact should be about \~10 minutes as we swap some hardware..</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>20:06:49</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>20:16:47</var> GMT+0</small><br><strong>Completed</strong> - lon1 is up.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>20:21:26</var> GMT+0</small><br><strong>Identified</strong> - lon2 is being worked on.</p> <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>20:28:40</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 4 Dec 2025 17:00:00 +0000 https://prismstatus.com/maintenance/cmiqdi6mn00qu11tti1gmtv51 https://prismstatus.com/maintenance/cmiqdi6mn00qu11tti1gmtv51 Singapore Migration Type: Maintenance Duration: 36 minutes Nov 29, 06:00:00 GMT+0 - Identified - We are upgrading the remaining OVH bound Singapore infrastructure from EPYC 4004 to EPYC 4005 chips. This will incur an IP change. Nov 29, 06:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 29, 06:35:53 GMT+0 - Completed - Maintenance has completed successfully & ahead of schedule :) Please check your servers to find their new IPSs. Type: Maintenance

Duration: 36 minutes

<p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are upgrading the remaining OVH bound Singapore infrastructure from EPYC 4004 to EPYC 4005 chips. This will incur an IP change..</p> <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>06:35:53</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully & ahead of schedule :) Please check your servers to find their new IPSs..</p> ]]> Sat, 29 Nov 2025 06:00:00 +0000 https://prismstatus.com/maintenance/cmifrdedc000vmdy59ib8bxr6 https://prismstatus.com/maintenance/cmifrdedc000vmdy59ib8bxr6 Game Panel Upgrades Type: Maintenance Duration: 3 hours Affected Components: Game Panel (Replica Aggregate) Nov 27, 03:40:00 GMT+0 - Identified - We are scheduling maintenance on our game panel to add new features and fix the bugs our clients have reported. The maintenance window is set for three hours, but the work will likely finish sooner. All servers will remain online during this time! Nov 27, 03:40:01 GMT+0 - Identified - Maintenance is now in progress Nov 27, 06:40:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 3 hours

Affected Components:

<p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>03:40:00</var> GMT+0</small><br><strong>Identified</strong> - We are scheduling maintenance on our game panel to add new features and fix the bugs our clients have reported. The maintenance window is set for three hours, but the work will likely finish sooner. All servers will remain online during this time!.</p> <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>03:40:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>06:40:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 27 Nov 2025 03:40:00 +0000 https://prismstatus.com/maintenance/cmiff0dgs002812mcqfc312xl https://prismstatus.com/maintenance/cmiff0dgs002812mcqfc312xl ASH-1 and ASH-2 Retirement Type: Maintenance Duration: 1 hour Nov 17, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 17, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully Nov 17, 05:00:00 GMT+0 - Identified - We are moving all clients off of our last (and oldest) rented Ashburn nodes, ASH-1 and ASH-2, to owned hardware now that we have finally gotten more rack space and can restock without concerns for future expansion. This will, of course incur an IP change so you'll need to update that on your end. All subdomains created on our platform will auto update. This affects a small minority of clients in Ashburn and if you'd like to see if you're affected, go to settings and refer to the node listing. Type: Maintenance

Duration: 1 hour

<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>05:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are moving all clients off of our last (and oldest) rented Ashburn nodes, ASH-1 and ASH-2, to owned hardware now that we have finally gotten more rack space and can restock without concerns for future expansion. This will, of course incur an IP change so you'll need to update that on your end. All subdomains created on our platform will auto update. This affects a small minority of clients in Ashburn and if you'd like to see if you're affected, go to settings and refer to the node listing..</p> ]]> Mon, 17 Nov 2025 05:00:00 +0000 https://prismstatus.com/maintenance/cmhpdtz7d0007b08q2aaqhk6i https://prismstatus.com/maintenance/cmhpdtz7d0007b08q2aaqhk6i DALLAS NETWORK UPGRADES! Type: Maintenance Duration: 1 hour and 41 minutes Nov 16, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 16, 05:10:33 GMT+0 - Completed - Maintenance has completed successfully. Nov 16, 05:38:40 GMT+0 - Identified - network will blip momentarily as we route outbound through GSL Nov 16, 05:40:34 GMT+0 - Completed - Maintenance has completed successfully. There shouldn't be any future impact. Nov 16, 04:00:00 GMT+0 - Identified - Now that we have a redundant fiber connection to GSL in Equinix Dallas, we're going to turn back always on mitigation and route all connections through GSL's private backbone for lower latency and direct peering. We expect the interruption from this cutover to be brief but have made the window 1 hour incase anything goes wrong. Type: Maintenance

Duration: 1 hour and 41 minutes

<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>05:10:33</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>05:38:40</var> GMT+0</small><br><strong>Identified</strong> - network will blip momentarily as we route outbound through GSL.</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>05:40:34</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully. There shouldn't be any future impact..</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - Now that we have a redundant fiber connection to GSL in Equinix Dallas, we're going to turn back always on mitigation and route all connections through GSL's private backbone for lower latency and direct peering. We expect the interruption from this cutover to be brief but have made the window 1 hour incase anything goes wrong..</p> ]]> Sun, 16 Nov 2025 04:00:00 +0000 https://prismstatus.com/maintenance/cmhtuk6r301z9ofrwyllng0hn https://prismstatus.com/maintenance/cmhtuk6r301z9ofrwyllng0hn Panel Upgrades Type: Maintenance Duration: 20 minutes Affected Components: Game Panel (Replica Aggregate) Nov 7, 17:00:00 GMT+0 - Identified - We will be moving our Panel to it's own dedicated machine due to capacity restraints. We expect an impact of \~10 minutes downtime during this cutover. Nov 7, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Nov 7, 17:20:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 20 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We will be moving our Panel to it's own dedicated machine due to capacity restraints. We expect an impact of \~10 minutes downtime during this cutover..</p> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Fri, 7 Nov 2025 17:00:00 +0000 https://prismstatus.com/maintenance/cmhk9873201i1zqqb13mdxjko https://prismstatus.com/maintenance/cmhk9873201i1zqqb13mdxjko Dallas Network Upgrades Type: Maintenance Duration: 4 hours and 47 minutes Oct 12, 15:00:00 GMT+0 - Identified - We're migrating our servers from Prime DA4 to Equinix DA2 for direct fiber cross connects to GSL + better networking. Servers will be down for a little bit within this 3 hour window (we estimate \~1h). Oct 12, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 12, 19:47:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 4 hours and 47 minutes

<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're migrating our servers from Prime DA4 to Equinix DA2 for direct fiber cross connects to GSL + better networking. Servers will be down for a little bit within this 3 hour window (we estimate \~1h)..</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>19:47:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Sun, 12 Oct 2025 15:00:00 +0000 https://prismstatus.com/maintenance/cmgncesvh0j4uzgft8laixzjf https://prismstatus.com/maintenance/cmgncesvh0j4uzgft8laixzjf London Hardware Upgrades Type: Maintenance Duration: 9 days, 7 hours and 19 minutes Oct 4, 15:00:00 GMT+0 - Identified - We're replacing old, legacy SKUs in London with new machines. If you're on LON1 or LON2, you'll be reassigned a new static IP during this migration (\~90% of servers on these machines are using our preexisting DNS so they're fine). Oct 4, 16:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 4, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 13, 20:23:23 GMT+0 - Identified - Maintenance is now in progress. Oct 13, 22:18:54 GMT+0 - Completed - IPs have been updated Type: Maintenance

Duration: 9 days, 7 hours and 19 minutes

<p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're replacing old, legacy SKUs in London with new machines. If you're on LON1 or LON2, you'll be reassigned a new static IP during this migration (\~90% of servers on these machines are using our preexisting DNS so they're fine)..</p> <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Oct <var data-var='date'> 4</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>20:23:23</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>22:18:54</var> GMT+0</small><br><strong>Completed</strong> - IPs have been updated.</p> ]]> Sat, 4 Oct 2025 15:00:00 +0000 https://prismstatus.com/maintenance/cmg87viuj0bxd125el8k2ngmt https://prismstatus.com/maintenance/cmg87viuj0bxd125el8k2ngmt ASH2 scheduled restart Type: Maintenance Duration: 10 minutes Sep 27, 03:10:00 GMT+0 - Completed - Maintenance has completed successfully Sep 27, 03:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Sep 27, 03:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 10 minutes

<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:10:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Sat, 27 Sep 2025 03:00:00 +0000 https://prismstatus.com/maintenance/cmfxek0lx006a6nm4p3exdvz8 https://prismstatus.com/maintenance/cmfxek0lx006a6nm4p3exdvz8 GSL Outbound Cutover Type: Maintenance Duration: 15 minutes Sep 8, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 8, 07:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Sep 8, 07:15:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 15 minutes

<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 8 Sep 2025 07:00:00 +0000 https://prismstatus.com/maintenance/cmfaktpa2004oefu14nqxbqzc https://prismstatus.com/maintenance/cmfaktpa2004oefu14nqxbqzc U.S. Database Infrastructure Maintenance Type: Maintenance Duration: 30 minutes Aug 31, 15:00:00 GMT+0 - Identified - During this time, we're going to be migrating our legacy client database infrastructure to our own. For most of you this will incur an ip change, and we will update legacy DNS to point to the new IPs. We only expect this disruption to take 5 minutes at max but you might need to update your configurations. Aug 31, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 31, 15:30:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 30 minutes

<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Identified</strong> - During this time, we're going to be migrating our legacy client database infrastructure to our own. For most of you this will incur an ip change, and we will update legacy DNS to point to the new IPs. We only expect this disruption to take 5 minutes at max but you might need to update your configurations..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 31 Aug 2025 15:00:00 +0000 https://prismstatus.com/maintenance/cmdxs80wo002abl6chwg0jwuk https://prismstatus.com/maintenance/cmdxs80wo002abl6chwg0jwuk DALLAS MAINTENANCE Type: Maintenance Duration: 2 hours Aug 31, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 31, 04:00:00 GMT+0 - Identified - We're going to be performing routine maintenance on the following nodes in Dallas (some of which are receiving a hardware upgrade!): * DAL5 * DAL7 * DAL12 If you're affected by any hardware upgrade related IP changes, we'll be sending you an email later today :) Aug 31, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're going to be performing routine maintenance on the following nodes in Dallas (some of which are receiving a hardware upgrade!): * DAL5 * DAL7 * DAL12 If you're affected by any hardware upgrade related IP changes, we'll be sending you an email later today :).</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sun, 31 Aug 2025 04:00:00 +0000 https://prismstatus.com/maintenance/cmeksmewm0038w2udu8zgs9x0 https://prismstatus.com/maintenance/cmeksmewm0038w2udu8zgs9x0 Singapore Upgrades & Migration Type: Maintenance Duration: 1 hour Aug 23, 17:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Aug 23, 18:00:00 GMT+0 - Completed - Maintenance has completed successfully Aug 23, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 1 hour

<p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Aug <var data-var='date'> 23</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Sat, 23 Aug 2025 17:00:00 +0000 https://prismstatus.com/maintenance/cme9h65xs00y5ehj41uxq4ouf https://prismstatus.com/maintenance/cme9h65xs00y5ehj41uxq4ouf