Rockstar Mischief Status - Incident history https://rsm.instatus.com Rockstar Mischief Sat, 13 Jul 2024 11:37:06 +0000 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Affected Components: Microservices #1 Jul 13, 11:37:06 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Affected Components:

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>11:37:06</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sat, 13 Jul 2024 11:37:06 +0000 https://rsm.instatus.com/incident/clyk1xtit388191dzoj30jwi7uc https://rsm.instatus.com/incident/clyk1xtit388191dzoj30jwi7uc Website - Homepage isn't accessible at the moment (automated) Type: Incident Duration: 6 days, 15 hours and 56 minutes Affected Components: Homepage Jun 22, 05:44:34 GMT+0 - Investigating - Website - Homepage cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 22, 08:24:29 GMT+0 - Resolved - Website - Homepage is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 6 days, 15 hours and 56 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>05:44:34</var> GMT+0</small><br><strong>Investigating</strong> - Website - Homepage cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>08:24:29</var> GMT+0</small><br><strong>Resolved</strong> - Website - Homepage is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 22 Jun 2024 05:44:34 +0000 https://rsm.instatus.com/incident/clxpp3kj3657430o5n5smglfycr https://rsm.instatus.com/incident/clxpp3kj3657430o5n5smglfycr External Services - Microservices #1 isn't accessible at the moment Type: Incident Duration: 21 days, 15 hours and 55 minutes Affected Components: Microservices #1 Jun 18, 14:15:46 GMT+0 - Investigating - External Services - Microservices #1 We've been made aware of a possible service disruption. We will update you when we know more. Jul 13, 07:19:40 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 21 days, 15 hours and 55 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>14:15:46</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 We've been made aware of a possible service disruption. We will update you when we know more..</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>07:19:40</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 18 Jun 2024 14:15:46 +0000 https://rsm.instatus.com/incident/clxkhlkm91554150ehn2m1yymlhj https://rsm.instatus.com/incident/clxkhlkm91554150ehn2m1yymlhj External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 11 hours and 38 minutes Affected Components: Microservices #1 Mar 13, 11:34:44 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 18, 08:58:21 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 38 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 13</var>, <var data-var='time'>11:34:44</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>08:58:21</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 13 Mar 2024 11:34:44 +0000 https://rsm.instatus.com/incident/cltpq4ukx292824i3o5meg1hu24 https://rsm.instatus.com/incident/cltpq4ukx292824i3o5meg1hu24 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 9 days, 13 hours and 55 minutes Affected Components: Microservices #1 Mar 6, 17:13:52 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 13, 11:27:46 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 9 days, 13 hours and 55 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>17:13:52</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 13</var>, <var data-var='time'>11:27:46</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 6 Mar 2024 17:13:52 +0000 https://rsm.instatus.com/incident/cltg260km761428p4obcd11wl25 https://rsm.instatus.com/incident/cltg260km761428p4obcd11wl25 Website - Forums isn't accessible at the moment (automated) Type: Incident Duration: 4 hours and 51 minutes Affected Components: Forums Feb 28, 10:15:20 GMT+0 - Investigating - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 28, 10:20:10 GMT+0 - Resolved - Website - Forums is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 hours and 51 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>10:15:20</var> GMT+0</small><br><strong>Investigating</strong> - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>10:20:10</var> GMT+0</small><br><strong>Resolved</strong> - Website - Forums is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 28 Feb 2024 10:15:20 +0000 https://rsm.instatus.com/incident/clt5n4szm1180544ialppwn30ae8 https://rsm.instatus.com/incident/clt5n4szm1180544ialppwn30ae8 Website - Forums isn't accessible at the moment (automated) Type: Incident Duration: 1 day, 20 hours and 54 minutes Affected Components: Forums Jan 27, 18:38:44 GMT+0 - Resolved - Website - Forums is now operational! This update was created by an automated monitoring service. Jan 27, 17:53:51 GMT+0 - Investigating - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 day, 20 hours and 54 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>18:38:44</var> GMT+0</small><br><strong>Resolved</strong> - Website - Forums is now operational! This update was created by an automated monitoring service..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>17:53:51</var> GMT+0</small><br><strong>Investigating</strong> - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Sat, 27 Jan 2024 17:53:51 +0000 https://rsm.instatus.com/incident/clrwdf7ef1346883arol5izzlmyx https://rsm.instatus.com/incident/clrwdf7ef1346883arol5izzlmyx External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 29 days, 20 hours and 58 minutes Affected Components: Microservices #1 Dec 28, 01:13:51 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Feb 25, 09:10:48 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 29 days, 20 hours and 58 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>01:13:51</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>09:10:48</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 28 Dec 2023 01:13:51 +0000 https://rsm.instatus.com/incident/clqoihn4j924152iboj5ii3vsz3 https://rsm.instatus.com/incident/clqoihn4j924152iboj5ii3vsz3 External Services - Microservices #2 isn't accessible at the moment (automated) Type: Incident Duration: 13 hours and 29 minutes Affected Components: Microservices #2 Dec 7, 08:59:45 GMT+0 - Investigating - External Services - Microservices #2 cannot be accessed at the moment. This incident was created by an automated monitoring service. Dec 7, 09:13:13 GMT+0 - Resolved - External Services - Microservices #2 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 13 hours and 29 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>08:59:45</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #2 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>09:13:13</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #2 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 7 Dec 2023 08:59:45 +0000 https://rsm.instatus.com/incident/clpuyvwpi1595315hwov5zngth8i https://rsm.instatus.com/incident/clpuyvwpi1595315hwov5zngth8i External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 6 days, 22 hours and 8 minutes Affected Components: Microservices #1 Nov 8, 15:19:42 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Dec 26, 22:29:50 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 6 days, 22 hours and 8 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>15:19:42</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>22:29:50</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Wed, 8 Nov 2023 15:19:42 +0000 https://rsm.instatus.com/incident/clopwotrp169029gxokyugi3tos https://rsm.instatus.com/incident/clopwotrp169029gxokyugi3tos External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 21 days, 2 hours and 46 minutes Affected Components: Microservices #1 Oct 16, 18:55:52 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Nov 8, 10:58:37 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 21 days, 2 hours and 46 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 16</var>, <var data-var='time'>18:55:52</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>10:58:37</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 16 Oct 2023 18:55:52 +0000 https://rsm.instatus.com/incident/clnt9a7uq240933xyoipu6klos9 https://rsm.instatus.com/incident/clnt9a7uq240933xyoipu6klos9 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 11 days, 11 hours and 2 minutes Affected Components: Microservices #1 Sep 16, 15:23:25 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Oct 16, 05:58:27 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 11 days, 11 hours and 2 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>15:23:25</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Oct <var data-var='date'> 16</var>, <var data-var='time'>05:58:27</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 16 Sep 2023 15:23:25 +0000 https://rsm.instatus.com/incident/clmm6hgus177037i8my6l66gko3 https://rsm.instatus.com/incident/clmm6hgus177037i8my6l66gko3 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 4 days, 4 hours and 41 minutes Affected Components: Microservices #1 Sep 16, 11:46:00 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Aug 21, 13:41:20 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 days, 4 hours and 41 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>11:46:00</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>13:41:20</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Mon, 21 Aug 2023 13:41:20 +0000 https://rsm.instatus.com/incident/cllkxe0z476472hvlld102qi1w https://rsm.instatus.com/incident/cllkxe0z476472hvlld102qi1w External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 24 days and 2 minutes Affected Components: Microservices #1 Jul 21, 12:48:55 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Aug 21, 08:48:56 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 24 days and 2 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 21</var>, <var data-var='time'>12:48:55</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>08:48:56</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 21 Jul 2023 12:48:55 +0000 https://rsm.instatus.com/incident/clkckv7db1110907hpojvt0pokmc https://rsm.instatus.com/incident/clkckv7db1110907hpojvt0pokmc External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 23 days, 1 hour and 22 minutes Affected Components: Microservices #1 Jun 23, 07:04:23 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 23, 16:17:45 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 23 days, 1 hour and 22 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>07:04:23</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:17:45</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 23 Jun 2023 07:04:23 +0000 https://rsm.instatus.com/incident/clj888aid117990i9o9o50ciiu3 https://rsm.instatus.com/incident/clj888aid117990i9o9o50ciiu3 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 14 hours and 25 minutes Affected Components: Microservices #1 Jun 20, 16:13:40 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 21, 04:52:04 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 14 hours and 25 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>16:13:40</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>04:52:04</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 20 Jun 2023 16:13:40 +0000 https://rsm.instatus.com/incident/clj4hj3zs401131gkomea1ih0nw https://rsm.instatus.com/incident/clj4hj3zs401131gkomea1ih0nw Website - Forums isn't accessible at the moment (automated) Type: Incident Duration: 25 days, 4 hours and 10 minutes Affected Components: Forums May 29, 17:41:51 GMT+0 - Investigating - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 8, 18:34:01 GMT+0 - Resolved - Website - Forums is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 25 days, 4 hours and 10 minutes

Affected Components:

<p><small>May <var data-var='date'> 29</var>, <var data-var='time'>17:41:51</var> GMT+0</small><br><strong>Investigating</strong> - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>18:34:01</var> GMT+0</small><br><strong>Resolved</strong> - Website - Forums is now operational! This update was created by an automated monitoring service..</p> ]]> Mon, 29 May 2023 17:41:51 +0000 https://rsm.instatus.com/incident/cli94zscp11302748qn1wme813gf https://rsm.instatus.com/incident/cli94zscp11302748qn1wme813gf External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 9 days, 17 hours and 6 minutes Affected Components: Microservices #1 May 28, 04:13:13 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Jun 20, 16:06:18 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 9 days, 17 hours and 6 minutes

Affected Components:

<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>04:13:13</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Jun <var data-var='date'> 20</var>, <var data-var='time'>16:06:18</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Sun, 28 May 2023 04:13:13 +0000 https://rsm.instatus.com/incident/cli6wo0dx15436318xn1t164gz2l https://rsm.instatus.com/incident/cli6wo0dx15436318xn1t164gz2l External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 8 days, 6 hours and 39 minutes Affected Components: Microservices #1 May 12, 02:04:10 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 27, 10:10:48 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 8 days, 6 hours and 39 minutes

Affected Components:

<p><small>May <var data-var='date'> 12</var>, <var data-var='time'>02:04:10</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>10:10:48</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 12 May 2023 02:04:10 +0000 https://rsm.instatus.com/incident/clhjx0feg585167iwohvaimgzqc https://rsm.instatus.com/incident/clhjx0feg585167iwohvaimgzqc Website - Forums isn't accessible at the moment (automated) Type: Incident Duration: 3 days, 12 hours and 55 minutes Affected Components: Forums May 9, 16:34:09 GMT+0 - Investigating - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service. May 9, 17:59:04 GMT+0 - Resolved - Website - Forums is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 3 days, 12 hours and 55 minutes

Affected Components:

<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>16:34:09</var> GMT+0</small><br><strong>Investigating</strong> - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>May <var data-var='date'> 9</var>, <var data-var='time'>17:59:04</var> GMT+0</small><br><strong>Resolved</strong> - Website - Forums is now operational! This update was created by an automated monitoring service..</p> ]]> Tue, 9 May 2023 16:34:09 +0000 https://rsm.instatus.com/incident/clhghrofj158407j4ohxwux2rkz https://rsm.instatus.com/incident/clhghrofj158407j4ohxwux2rkz External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 1 day, 7 hours and 40 minutes Affected Components: Microservices #1 Apr 28, 09:01:14 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 12, 01:56:54 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 1 day, 7 hours and 40 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>09:01:14</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>01:56:54</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Fri, 28 Apr 2023 09:01:14 +0000 https://rsm.instatus.com/incident/clh0bquj3487656hxohrm5l1qm5 https://rsm.instatus.com/incident/clh0bquj3487656hxohrm5l1qm5 External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 10 days, 20 hours and 36 minutes Affected Components: Microservices #1 Apr 13, 05:23:14 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 25, 13:43:50 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 10 days, 20 hours and 36 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>05:23:14</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>13:43:50</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 13 Apr 2023 05:23:14 +0000 https://rsm.instatus.com/incident/clgeocqbt752174h7oe9tqidt4y https://rsm.instatus.com/incident/clgeocqbt752174h7oe9tqidt4y External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 3 hours and 27 minutes Affected Components: Microservices #1 Mar 30, 15:36:41 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Mar 30, 15:33:15 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 3 hours and 27 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>15:36:41</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>15:33:15</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> ]]> Thu, 30 Mar 2023 15:33:15 +0000 https://rsm.instatus.com/incident/clfv9za9011446780cog49w43oam https://rsm.instatus.com/incident/clfv9za9011446780cog49w43oam Website - Forums isn't accessible at the moment (automated) Type: Incident Duration: 4 hours and 53 minutes Affected Components: Forums Mar 25, 14:10:06 GMT+0 - Investigating - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 25, 14:14:59 GMT+0 - Resolved - Website - Forums is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 4 hours and 53 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>14:10:06</var> GMT+0</small><br><strong>Investigating</strong> - Website - Forums cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>14:14:59</var> GMT+0</small><br><strong>Resolved</strong> - Website - Forums is now operational! This update was created by an automated monitoring service..</p> ]]> Sat, 25 Mar 2023 14:10:06 +0000 https://rsm.instatus.com/incident/clfo1t3ea1589427ucn2vtbjzqtj https://rsm.instatus.com/incident/clfo1t3ea1589427ucn2vtbjzqtj External Services - Microservices #1 isn't accessible at the moment (automated) Type: Incident Duration: 26 days, 15 hours and 26 minutes Affected Components: Microservices #1 Mar 23, 07:01:36 GMT+0 - Investigating - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 28, 19:17:01 GMT+0 - Resolved - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service. Type: Incident

Duration: 26 days, 15 hours and 26 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>07:01:36</var> GMT+0</small><br><strong>Investigating</strong> - External Services - Microservices #1 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>19:17:01</var> GMT+0</small><br><strong>Resolved</strong> - External Services - Microservices #1 is now operational! This update was created by an automated monitoring service..</p> ]]> Thu, 23 Mar 2023 07:01:36 +0000 https://rsm.instatus.com/incident/clfkrmcat662090y9om9yg1shwh https://rsm.instatus.com/incident/clfkrmcat662090y9om9yg1shwh London Cabinet Maintenance Type: Maintenance Duration: 1 day and 18 hours Affected Components: London, UK (EU-West), Microservices #2, Homepage, Homepage API Aug 2, 11:00:00 GMT+0 - Identified - Our provider is performing a full-cabinet maintenance where they are moving all physical servers to a new cabinet in a new caged area of the data centre. During this time, the London CDN server and the microservices machine will be unavailable, and as such, this will also affect the Discord bots, website, and more. This will be fairly impactful but server #1 will be unaffected, unlike #2 which might experience chat slowness and more. As for the CDN server, traffic that would usually go to London will be redirected to New York (an hour before the machine is pulled) as to minimise the impact of the move. This is a rolling process, meaning that our other servers in London will also be affected by this at some point as they move their cabinets across too, including the one that server #2 is running on. An ETA that they have provided is 1-2 hours but it could easily take longer than that, so we won't be counting on it. Aug 2, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 4, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 day and 18 hours

Affected Components: , , ,

<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - Our provider is performing a full-cabinet maintenance where they are moving all physical servers to a new cabinet in a new caged area of the data centre. During this time, the London CDN server and the microservices machine will be unavailable, and as such, this will also affect the Discord bots, website, and more. This will be fairly impactful but server #1 will be unaffected, unlike #2 which might experience chat slowness and more. As for the CDN server, traffic that would usually go to London will be redirected to New York (an hour before the machine is pulled) as to minimise the impact of the move. This is a rolling process, meaning that our other servers in London will also be affected by this at some point as they move their cabinets across too, including the one that server #2 is running on. An ETA that they have provided is 1-2 hours but it could easily take longer than that, so we won't be counting on it..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 2 Aug 2022 11:00:00 +0000 https://rsm.instatus.com/maintenance/cl6c2a51347747xllovg655ej4 https://rsm.instatus.com/maintenance/cl6c2a51347747xllovg655ej4 CDN Maintenance Type: Maintenance Duration: 30 minutes Affected Components: London, UK (EU-West), New York, US (NA-East), Tokyo, JP (AS-East) Jul 13, 00:00:00 GMT+0 - Identified - We'll be updating and upgrading nodes in a rolling fashion during this maintenance period. Traffic will be automatically and gracefully moved to other available nodes in the network to prevent downtime. Jul 13, 00:30:00 GMT+0 - Completed - Maintenance has completed successfully Jul 13, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 30 minutes

Affected Components: , ,

<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - We'll be updating and upgrading nodes in a rolling fashion during this maintenance period. Traffic will be automatically and gracefully moved to other available nodes in the network to prevent downtime..</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Wed, 13 Jul 2022 00:00:00 +0000 https://rsm.instatus.com/maintenance/cl5iu5tu4732164qo7yh0j6txo https://rsm.instatus.com/maintenance/cl5iu5tu4732164qo7yh0j6txo CDN Maintenance Type: Maintenance Duration: 23 minutes Affected Components: London, UK (EU-West), New York, US (NA-East) Jul 11, 05:15:03 GMT+0 - Identified - Maintenance is now in progress. Jul 11, 05:12:08 GMT+0 - Identified - Our NA and EU CDN nodes will be undergoing maintenance to enable a CPU instruction set to harden security and improve performance. During this time, traffic will be re-routed to Tokyo until the maintenance is complete. Jul 11, 05:35:08 GMT+0 - Completed - Maintenance has been completed successfully :) Type: Maintenance

Duration: 23 minutes

Affected Components: ,

<p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>05:15:03</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>05:12:08</var> GMT+0</small><br><strong>Identified</strong> - Our NA and EU CDN nodes will be undergoing maintenance to enable a CPU instruction set to harden security and improve performance. During this time, traffic will be re-routed to Tokyo until the maintenance is complete..</p> <p><small>Jul <var data-var='date'> 11</var>, <var data-var='time'>05:35:08</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has been completed successfully :).</p> ]]> Mon, 11 Jul 2022 05:12:08 +0000 https://rsm.instatus.com/maintenance/cl5gahwwq125799roiio0u9cwn https://rsm.instatus.com/maintenance/cl5gahwwq125799roiio0u9cwn Infrastructure upgrades Type: Maintenance Duration: 10 hours Affected Components: New York, US (NA-East), FiveM - Freeroam #1 (NA-East) Jun 21, 09:00:00 GMT+0 - Identified - Our provider will be performing infrastructure upgrades to the core routing in New York and interruptions are to be expected during this time window. Jun 21, 17:16:35 GMT+0 - Identified - Our provider has extended the maintenance window by 2 hours with short notice. Jun 21, 19:00:00 GMT+0 - Completed - Maintenance has completed successfully. Jun 21, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 10 hours

Affected Components: ,

<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - Our provider will be performing infrastructure upgrades to the core routing in New York and interruptions are to be expected during this time window..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>17:16:35</var> GMT+0</small><br><strong>Identified</strong> - Our provider has extended the maintenance window by 2 hours with short notice..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Tue, 21 Jun 2022 09:00:00 +0000 https://rsm.instatus.com/maintenance/cl4njegn612807lin1ylteczy2 https://rsm.instatus.com/maintenance/cl4njegn612807lin1ylteczy2 Maintenance for Freeroam #1 Type: Maintenance Duration: 3 hours and 35 minutes Affected Components: FiveM - Freeroam #1 (NA-East) May 19, 06:05:18 GMT+0 - Completed - Maintenance has completed successfully. May 19, 03:28:41 GMT+0 - Identified - Maintenance is being extended by another hour due to unforeseen delays while migrating the backend cluster. May 19, 02:30:00 GMT+0 - Identified - We will finally be moving the server location to New York (US East) running the new specialized and upgraded hardware we've all been waiting for. Downtime is expected to take 30 minutes or less. May 19, 02:43:50 GMT+0 - Identified - We'll be extending the maintenance window to 1 hour to give us more time to set up supporting infrastructure and services in the new region. May 19, 04:04:18 GMT+0 - Identified - The CDN will be unavailable in Japan for the first hour or so that Freeroam #1 is back up. In other news, the backend is at 75% and it looks like we're on schedule to get this done within the next 25 minutes! :) May 19, 02:30:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 3 hours and 35 minutes

Affected Components:

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>06:05:18</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>03:28:41</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is being extended by another hour due to unforeseen delays while migrating the backend cluster..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br><strong>Identified</strong> - We will finally be moving the server location to New York (US East) running the new specialized and upgraded hardware we've all been waiting for. Downtime is expected to take 30 minutes or less..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>02:43:50</var> GMT+0</small><br><strong>Identified</strong> - We'll be extending the maintenance window to 1 hour to give us more time to set up supporting infrastructure and services in the new region..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>04:04:18</var> GMT+0</small><br><strong>Identified</strong> - The CDN will be unavailable in Japan for the first hour or so that Freeroam #1 is back up. In other news, the backend is at 75% and it looks like we're on schedule to get this done within the next 25 minutes! :).</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>02:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Thu, 19 May 2022 02:30:00 +0000 https://rsm.instatus.com/maintenance/cl3cdy0ts48640ljojpfcksonr https://rsm.instatus.com/maintenance/cl3cdy0ts48640ljojpfcksonr External services maintenance Type: Maintenance Duration: 5 minutes Affected Components: Microservices #2 May 11, 02:30:01 GMT+0 - Identified - Maintenance is now in progress May 11, 02:35:00 GMT+0 - Completed - Maintenance has completed successfully. May 11, 02:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance for hardware improvements on one of our external nodes. In-game chat on both Freeroam #1 and Freeroam #2 will be unavailable, as well as our Discord bots. This is expected to take ~5 minutes, if not less. Type: Maintenance

Duration: 5 minutes

Affected Components:

<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>02:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>02:35:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance for hardware improvements on one of our external nodes. In-game chat on both Freeroam #1 and Freeroam #2 will be unavailable, as well as our Discord bots. This is expected to take ~5 minutes, if not less..</p> ]]> Wed, 11 May 2022 02:30:00 +0000 https://rsm.instatus.com/maintenance/cl30yno4s82231kuofveea61rq https://rsm.instatus.com/maintenance/cl30yno4s82231kuofveea61rq External services maintenance Type: Maintenance Duration: 10 hours and 24 minutes Affected Components: Microservices #2, FiveM - Freeroam #1 (NA-East), FiveM - Freeroam #2 (EU-West) May 2, 13:05:54 GMT+0 - Identified - Maintenance is now in progress. May 2, 13:14:00 GMT+0 - Completed - Maintenance has completed successfully. May 2, 13:03:36 GMT+0 - Identified - We'll be doing immediate maintenance on one of our external services nodes. This will take 5 minutes to complete, but various in-game activities will be affected in the meantime. Type: Maintenance

Duration: 10 hours and 24 minutes

Affected Components: , ,

<p><small>May <var data-var='date'> 2</var>, <var data-var='time'>13:05:54</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>13:14:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>13:03:36</var> GMT+0</small><br><strong>Identified</strong> - We'll be doing immediate maintenance on one of our external services nodes. This will take 5 minutes to complete, but various in-game activities will be affected in the meantime..</p> ]]> Mon, 2 May 2022 13:03:36 +0000 https://rsm.instatus.com/maintenance/cl2oqhk0y22196gln84olkn6ih https://rsm.instatus.com/maintenance/cl2oqhk0y22196gln84olkn6ih CDN Maintenance for Asia / APAC Type: Maintenance Affected Components: FiveM - Freeroam #1 (NA-East), FiveM - Freeroam #2 (EU-West) Apr 19, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 19, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Apr 19, 08:00:00 GMT+0 - Identified - We'll be adding another 10Gbit/s of extra capacity to our CDN, in a brand new location: Tokyo, Japan. This will improve streaming speeds for players in that region, as well as Australia / New Zealand. Players in these regions should expect issues while we work out the kinks - this should take no longer than 30 minutes. Apr 19, 08:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Affected Components: ,

<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Identified</strong> - We'll be adding another 10Gbit/s of extra capacity to our CDN, in a brand new location: Tokyo, Japan. This will improve streaming speeds for players in that region, as well as Australia / New Zealand. Players in these regions should expect issues while we work out the kinks - this should take no longer than 30 minutes..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Tue, 19 Apr 2022 08:00:00 +0000 https://rsm.instatus.com/maintenance/cl25qhwt5370490s2n44ssx87hk https://rsm.instatus.com/maintenance/cl25qhwt5370490s2n44ssx87hk Maintenance for Freeroam #2 Type: Maintenance Duration: 22 hours and 6 minutes Affected Components: FiveM - Freeroam #2 (EU-West) Apr 18, 22:05:51 GMT+0 - Completed - Maintenance has completed successfully. Apr 18, 00:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 18, 00:00:00 GMT+0 - Identified - We'll be performing maintenance on server #2 to improve workflow and security. It's expected to take no longer than 30 minutes to complete. Apr 18, 00:52:00 GMT+0 - Identified - We'll be extending this maintenance window to upgrade server #2 and finally solve the lag and high ping issues that have been observed recently. Type: Maintenance

Duration: 22 hours and 6 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>22:05:51</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Identified</strong> - We'll be performing maintenance on server #2 to improve workflow and security. It's expected to take no longer than 30 minutes to complete..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>00:52:00</var> GMT+0</small><br><strong>Identified</strong> - We'll be extending this maintenance window to upgrade server #2 and finally solve the lag and high ping issues that have been observed recently..</p> ]]> Mon, 18 Apr 2022 00:00:00 +0000 https://rsm.instatus.com/maintenance/cl23sqtd51108959ghn4mqby37n1 https://rsm.instatus.com/maintenance/cl23sqtd51108959ghn4mqby37n1 Hardware improvements for Freeroam #2 Type: Maintenance Duration: 11 minutes Affected Components: FiveM - Freeroam #2 (EU-West), Cfx.re - Freeroam #2 Mar 27, 17:11:08 GMT+0 - Completed - Maintenance has completed successfully. Mar 27, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 27, 17:00:00 GMT+0 - Identified - We are planning to add more resources to Freeroam #2 to counter the issue with lag since moving to a new dedicated server. If this doesn't solve it then we'll look for another solution - we do hear your complaints! Type: Maintenance

Duration: 11 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>17:11:08</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>17:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning to add more resources to Freeroam #2 to counter the issue with lag since moving to a new dedicated server. If this doesn't solve it then we'll look for another solution - we do hear your complaints!.</p> ]]> Sun, 27 Mar 2022 17:00:00 +0000 https://rsm.instatus.com/maintenance/cl19ikoo2404867c1n1xa4alcpy https://rsm.instatus.com/maintenance/cl19ikoo2404867c1n1xa4alcpy Proxy maintenance for Freeroam #2 Type: Maintenance Duration: 1 day, 8 hours and 58 minutes Affected Components: FiveM - Freeroam #2 (EU-West), Cfx.re - Freeroam #2 Mar 23, 10:00:00 GMT+0 - Identified - The plan has changed and we are now doing a full server maintenance in light of the DDoS attacks today targeting server #2. Mar 24, 17:58:05 GMT+0 - Completed - Maintenance has completed successfully. Mar 23, 09:00:00 GMT+0 - Identified - We are planning to move Freeroam #2 onto our new proxy service, which should help in getting voice chat working again. From the start of the maintenance window, the server will be offline up until we're ready for testing. When we're ready for testing, the maintenance will still be marked as on-going. Assuming the move is successful, voice chat will be working again. But if any issues occur, we'll be swapping back over to our old provider. Mar 23, 18:07:04 GMT+0 - Identified - Server #2 is now online and open to testing once again. Let us know if you experience any issues :) Mar 23, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 23, 09:19:45 GMT+0 - Identified - We'll put this on pause for now until we can get the timeouts under control. Type: Maintenance

Duration: 1 day, 8 hours and 58 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> - The plan has changed and we are now doing a full server maintenance in light of the DDoS attacks today targeting server #2..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>17:58:05</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning to move Freeroam #2 onto our new proxy service, which should help in getting voice chat working again. From the start of the maintenance window, the server will be offline up until we're ready for testing. When we're ready for testing, the maintenance will still be marked as on-going. Assuming the move is successful, voice chat will be working again. But if any issues occur, we'll be swapping back over to our old provider..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>18:07:04</var> GMT+0</small><br><strong>Identified</strong> - Server #2 is now online and open to testing once again. Let us know if you experience any issues :).</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>09:19:45</var> GMT+0</small><br><strong>Identified</strong> - We'll put this on pause for now until we can get the timeouts under control..</p> ]]> Wed, 23 Mar 2022 09:00:00 +0000 https://rsm.instatus.com/maintenance/cl13baxu996559eeol64t54dj1 https://rsm.instatus.com/maintenance/cl13baxu996559eeol64t54dj1 Migration back to EU (Freeroam #1) Type: Maintenance Duration: 18 minutes Affected Components: Cfx.re - Freeroam #1, FiveM - Freeroam #1 (NA-East) Feb 19, 01:17:46 GMT+0 - Completed - Freeroam #1 has now been migrated back to EU (London, UK). Thanks for your patience :) Feb 19, 01:00:00 GMT+0 - Identified - We'll be migrating Freeroam #1 back over to one of our overclocked servers in London, UK. The testing that we've performed over the past few weeks has been successful and we now have a good upgrade candidate for the future, which we are already working on permanently acquiring. We'll most likely be returning to NA at a future date with even better hardware, probably on the East coast to balance the latency/ping between NA and EU players. Type: Maintenance

Duration: 18 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>01:17:46</var> GMT+0</small><br><strong>Completed</strong> - Freeroam #1 has now been migrated back to EU (London, UK). Thanks for your patience :).</p> <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> - We'll be migrating Freeroam #1 back over to one of our overclocked servers in London, UK. The testing that we've performed over the past few weeks has been successful and we now have a good upgrade candidate for the future, which we are already working on permanently acquiring. We'll most likely be returning to NA at a future date with even better hardware, probably on the East coast to balance the latency/ping between NA and EU players..</p> ]]> Sat, 19 Feb 2022 01:00:00 +0000 https://rsm.instatus.com/maintenance/ckzswnzn4128875g6ms3s93wo1u https://rsm.instatus.com/maintenance/ckzswnzn4128875g6ms3s93wo1u