<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>BeamMP Status - Incident history</title>
    <link>https://beammp.instatus.com</link>
    <description>BeamMP</description>
    <pubDate>Tue, 6 Oct 2026 15:49:12 +0000</pubDate>
    
<item>
  <title>Degraded performance on Auth/Backend</title>
  <description>
    Type: Incident
    

    Affected Components: Authentication, Backend
    Oct 6, 16:00:44 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 6, 15:49:12 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>16:00:44</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>15:49:12</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 15:49:12 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmuwutams01nl0wqsictj7y1r</link>
  <guid>https://beammp.instatus.com/incident/cmuwutams01nl0wqsictj7y1r</guid>
</item>

<item>
  <title>Issue with Auth/Backend/API</title>
  <description>
    Type: Incident
    Duration: 1 hour and 6 minutes

    Affected Components: Authentication, Backend
    Oct 3, 18:30:00 GMT+0 - Resolved - This incident has been resolved. Oct 3, 17:30:08 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 3, 17:23:54 GMT+0 - Identified - We have identified the cause of this incident and are working to get it resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 6 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>17:30:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Oct <var data-var='date'> 3</var>, <var data-var='time'>17:23:54</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of this incident and are working to get it resolved..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 3 Oct 2026 17:23:54 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmusnviwf01l813ry6vbqujg4</link>
  <guid>https://beammp.instatus.com/incident/cmusnviwf01l813ry6vbqujg4</guid>
</item>

<item>
  <title>Issues with Backend/Auth/API</title>
  <description>
    Type: Incident
    Duration: 31 minutes

    Affected Components: Authentication, Backend
    Sep 11, 23:39:38 GMT+0 - Resolved - This incident has been resolved. This was caused by a faulty config change that took out the database while trying to rectify performance issues. Thank you for your patience. Sep 11, 23:08:33 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 31 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>23:39:38</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved. This was caused by a faulty config change that took out the database while trying to rectify performance issues. Thank you for your patience..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>23:08:33</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 11 Sep 2026 23:08:33 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmtxkhzyo01en1mrzw4g5n7kr</link>
  <guid>https://beammp.instatus.com/incident/cmtxkhzyo01en1mrzw4g5n7kr</guid>
</item>

<item>
  <title>Backend/Auth Instability</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Authentication, Backend
    Aug 25, 22:23:20 GMT+0 - Resolved - We have reverted the changes and traffic is reverting to normal. Aug 25, 22:17:38 GMT+0 - Identified - Apologies for the service interruption. This was caused by a config change that we are working on rolling back. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>22:23:20</var> GMT+0</small><br><strong>Resolved</strong> -
  We have reverted the changes and traffic is reverting to normal..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>22:17:38</var> GMT+0</small><br><strong>Identified</strong> -
  Apologies for the service interruption. This was caused by a config change that we are working on rolling back..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 25 Aug 2026 22:17:38 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmt98719001qh10qvanhp13ki</link>
  <guid>https://beammp.instatus.com/incident/cmt98719001qh10qvanhp13ki</guid>
</item>

<item>
  <title>Backend Updates</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 7 minutes

    Affected Components: Authentication, Backend
    Aug 22, 15:07:11 GMT+0 - Completed - Maintenance has completed successfully, thank you for your patience. Keymaster remains offline at this time. The Backend and Authentication systems did not experience any downtime.

We will be scheduling follow-up maintenances for further works. Aug 22, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 22, 11:19:35 GMT+0 - Identified - We are planning for a scheduled maintenance during this time to update the backend systems. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>15:07:11</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully, thank you for your patience. Keymaster remains offline at this time. The Backend and Authentication systems did not experience any downtime.

We will be scheduling follow-up maintenances for further works..</p>
<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>11:19:35</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during this time to update the backend systems..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 22 Aug 2026 13:00:00 +0000</pubDate>
  <link>https://beammp.instatus.com/maintenance/cmt4ad7za0mo80zplpov7pj38</link>
  <guid>https://beammp.instatus.com/maintenance/cmt4ad7za0mo80zplpov7pj38</guid>
</item>

<item>
  <title>Backend Instability</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    Affected Components: Authentication, Backend
    Aug 16, 14:18:27 GMT+0 - Resolved - This incident has been resolved. Aug 16, 14:11:36 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring the result. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>14:18:27</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>14:11:36</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented a fix and are currently monitoring the result..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 16 Aug 2026 14:11:36 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmsvvvbyg0tlu0kqx8pil076n</link>
  <guid>https://beammp.instatus.com/incident/cmsvvvbyg0tlu0kqx8pil076n</guid>
</item>

<item>
  <title>New Zealand Official Servers – Temporary Shutdown</title>
  <description>
    Type: Incident
    Duration: 5 days, 17 hours and 15 minutes

    Affected Components: Australia Official Servers
    Aug 22, 11:20:29 GMT+0 - Resolved - This incident has been resolved. Aug 14, 22:45:16 GMT+0 - Monitoring - We have re-launched the servers which have now moved to AU and are currently monitoring them, please expect random restarts until we have confirmed they are good to go. Aug 14, 22:23:19 GMT+0 - Identified - We have found a new host and are at finalizing stage of brining the servers back online Jul 16, 18:05:32 GMT+0 - Investigating - We are currently reviewing our options for hosting the servers more reliably in the future. We apologise for the disruption and appreciate your patience while we work out the best way forward. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 17 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>11:20:29</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>22:45:16</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have re-launched the servers which have now moved to AU and are currently monitoring them, please expect random restarts until we have confirmed they are good to go..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>22:23:19</var> GMT+0</small><br><strong>Identified</strong> -
  We have found a new host and are at finalizing stage of brining the servers back online.</p>
<p><small>Jul <var data-var='date'> 16</var>, <var data-var='time'>18:05:32</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently reviewing our options for hosting the servers more reliably in the future. We apologise for the disruption and appreciate your patience while we work out the best way forward..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 16 Jul 2026 18:05:32 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmrntkrhg019g0rlkb1lv5ip8</link>
  <guid>https://beammp.instatus.com/incident/cmrntkrhg019g0rlkb1lv5ip8</guid>
</item>

<item>
  <title>Degraded Backend Performance</title>
  <description>
    Type: Incident
    Duration: 1 hour and 23 minutes

    Affected Components: Authentication, Backend
    Jul 15, 20:23:07 GMT+0 - Resolved - Traffic has recovered and services are back to normal. We&#039;ve introduced additional resiliency. Jul 15, 19:41:26 GMT+0 - Monitoring - We&#039;ve issued a further fix and are watching traffic recovery. Jul 15, 19:25:05 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the traffic recovery. Jul 15, 19:00:00 GMT+0 - Identified - We are working on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 23 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>20:23:07</var> GMT+0</small><br><strong>Resolved</strong> -
  Traffic has recovered and services are back to normal. We&#039;ve introduced additional resiliency..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>19:41:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  We&#039;ve issued a further fix and are watching traffic recovery..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>19:25:05</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the traffic recovery..</p>
<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are working on a fix for this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 15 Jul 2026 19:00:00 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cmrmgdsaz027y0spj4ll1pb3p</link>
  <guid>https://beammp.instatus.com/incident/cmrmgdsaz027y0spj4ll1pb3p</guid>
</item>

<item>
  <title>Outage of critical BeamMP Services</title>
  <description>
    Type: Incident
    Duration: 4 hours

    Affected Components: Main Website, Forum, Backend, Authentication
    Oct 30, 18:44:59 GMT+0 - Resolved - The issue was identified as a sudden, unexpected spike in TCP sockets on S5. This does not look like a DDoS attack. Oct 30, 18:30:00 GMT+0 - Resolved - All services are now back online. We are working to establish a cause for this. Oct 30, 18:26:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> , , , </p>
    <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>18:44:59</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue was identified as a sudden, unexpected spike in TCP sockets on S5. This does not look like a DDoS attack..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  All services are now back online. We are working to establish a cause for this..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>18:26:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 30 Oct 2022 18:26:00 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cl9vp68hs20882i4oekjh952k3</link>
  <guid>https://beammp.instatus.com/incident/cl9vp68hs20882i4oekjh952k3</guid>
</item>

<item>
  <title>Official Servers offline</title>
  <description>
    Type: Incident
    Duration: 9 hours

    Affected Components: Germany Official Servers
    Oct 30, 11:56:00 GMT+0 - Resolved - We have resolved the issue. S7 suffered a DDoS attack, which caused the system to crash and remain offline for hours. Oct 30, 02:56:00 GMT+0 - Investigating - We have noticed that all of the DE-hosted official servers are offline. We are working to investgate this. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>11:56:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We have resolved the issue. S7 suffered a DDoS attack, which caused the system to crash and remain offline for hours..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>02:56:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have noticed that all of the DE-hosted official servers are offline. We are working to investgate this..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 30 Oct 2022 02:56:00 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cl9vpdqwf22263i4oefnnrsmt7</link>
  <guid>https://beammp.instatus.com/incident/cl9vpdqwf22263i4oefnnrsmt7</guid>
</item>

<item>
  <title>Issues with BeamMP Mod download</title>
  <description>
    Type: Incident
    Duration: 21 hours

    Affected Components: Forum, Backend
    Oct 28, 22:27:00 GMT+0 - Resolved - The issue was identified as unexpected packet loss during a maintenance at Hetzner&#039;s core network between Germany and Finland. The issue is now resolved. Oct 28, 22:17:00 GMT+0 - Identified - We have identified the issue as a networking problem on S1. We are working towards a resolution. Oct 28, 22:06:00 GMT+0 - Investigating - We have seen issues with the BeamMP Mod download and the forum throwing errors. We are investigating this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>22:27:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue was identified as unexpected packet loss during a maintenance at Hetzner&#039;s core network between Germany and Finland. The issue is now resolved..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>22:17:00</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue as a networking problem on S1. We are working towards a resolution..</p>
<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>22:06:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have seen issues with the BeamMP Mod download and the forum throwing errors. We are investigating this issue..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 28 Oct 2022 22:27:00 +0000</pubDate>
  <link>https://beammp.instatus.com/incident/cl9ukd4x51764hpoddnq20215</link>
  <guid>https://beammp.instatus.com/incident/cl9ukd4x51764hpoddnq20215</guid>
</item>

  </channel>
  </rss>