<?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>thebackend Status - Incident history</title>
    <link>https://status.thebackend.io</link>
    <description>thebackend</description>
    <pubDate>Tue, 27 Oct 2026 01:00:00 +0000</pubDate>
    
<item>
  <title>Second Half 2026 Server Maintenance Notice - October 27 (Tue)</title>
  <description>
    Type: Maintenance
    

    Affected Components: Logs, Match, Database, Bills, Users, Terms and Privacy, Friends, Posts, Guilds, Push Notifications, Console, GameInfo, Inquiries, Cash, Charts, Probability, Chat, Notice, Cloud Save, Rank, Function, Events, Version Control, Coupons
    Oct 2, 08:30:06 GMT+0 - Identified - Hello, This is team BACKND.

We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please refer to the details below, including the maintenance schedule and its expected impact.  
We kindly ask for your understanding, as this maintenance is essential to providing a stable service.

  
## **■ Maintenance Schedule**

* **October 27, 2026 (Tuesday) 01:00 \~ 05:00 (UTC)**
* Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided through the maintenance status page.

## **■ Maintenance Details**

* Server infrastructure inspection
* API server optimization
* Console authentication system enhancement

## **■ Impact of Maintenance**

* **Project access restriction**: Communication with BACKND server will be restricted during maintenance, and all projects will be switched to ‘Under Maintenance’ status.
* **Console access restriction**: BACKND console access and usage will be temporarily suspended. The console will provide guidance on the maintenance status.
* **Players access allowlist restriction**: The “Players Allow Access” feature will not function during the maintenance period.

## **■ Project Status Transition Schedule**

* **October 27 (Tue) 01:00 (UTC)** \- All projects switched to ‘Under Maintenance’ status
* **October 27 (Tue) 05:00 (UTC)** \- All projects restored to pre-maintenance status  
   * If maintenance finishes early or is extended, status will be restored at the actual completion time  
   * Completion will be announced through console notifications

⚠️ **Since all projects will be switched to maintenance status,** 
**please make sure to notify your players in advance if your game is in live service.**

**While in maintenance status, all requests except Temporary Announcement retrieval will fail.** 
**If the client does not handle this properly, requests may be retried repeatedly, causing a surge in API calls,** 
**or the game state may remain abnormal, leading to further issues such as players reporting data rollbacks.**

**To ensure stable service operation, please make sure to implement appropriate handling for maintenance errors,** 
**such as restricting gameplay or prompting players to reconnect.**

  
We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).

We will do our best to complete the maintenance as quickly and efficiently as possible.  
Thank you. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>08:30:06</var> GMT+0</small><br><strong>Identified</strong> -
  Hello, This is team BACKND.

We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please refer to the details below, including the maintenance schedule and its expected impact.  
We kindly ask for your understanding, as this maintenance is essential to providing a stable service.

  
## **■ Maintenance Schedule**

* **October 27, 2026 (Tuesday) 01:00 \~ 05:00 (UTC)**
* Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided through the maintenance status page.

## **■ Maintenance Details**

* Server infrastructure inspection
* API server optimization
* Console authentication system enhancement

## **■ Impact of Maintenance**

* **Project access restriction**: Communication with BACKND server will be restricted during maintenance, and all projects will be switched to ‘Under Maintenance’ status.
* **Console access restriction**: BACKND console access and usage will be temporarily suspended. The console will provide guidance on the maintenance status.
* **Players access allowlist restriction**: The “Players Allow Access” feature will not function during the maintenance period.

## **■ Project Status Transition Schedule**

* **October 27 (Tue) 01:00 (UTC)** \- All projects switched to ‘Under Maintenance’ status
* **October 27 (Tue) 05:00 (UTC)** \- All projects restored to pre-maintenance status  
   * If maintenance finishes early or is extended, status will be restored at the actual completion time  
   * Completion will be announced through console notifications

⚠️ **Since all projects will be switched to maintenance status,** 
**please make sure to notify your players in advance if your game is in live service.**

**While in maintenance status, all requests except Temporary Announcement retrieval will fail.** 
**If the client does not handle this properly, requests may be retried repeatedly, causing a surge in API calls,** 
**or the game state may remain abnormal, leading to further issues such as players reporting data rollbacks.**

**To ensure stable service operation, please make sure to implement appropriate handling for maintenance errors,** 
**such as restricting gameplay or prompting players to reconnect.**

  
We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).

We will do our best to complete the maintenance as quickly and efficiently as possible.  
Thank you..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 27 Oct 2026 01:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/maintenance/cmuqpd6zp00oq0wmyabqgzwpv</link>
  <guid>https://status.thebackend.io/maintenance/cmuqpd6zp00oq0wmyabqgzwpv</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Posts
    Sep 3, 09:20:21 GMT+0 - Resolved - This incident has been resolved. Sep 3, 09:14:11 GMT+0 - Investigating - An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue. 
  </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>Sep <var data-var='date'> 3</var>, <var data-var='time'>09:20:21</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 3</var>, <var data-var='time'>09:14:11</var> GMT+0</small><br><strong>Investigating</strong> -
  An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 3 Sep 2026 09:14:11 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmtlb66pf05rd1aphnqy0jeex</link>
  <guid>https://status.thebackend.io/incident/cmtlb66pf05rd1aphnqy0jeex</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: GameInfo
    Sep 1, 05:33:14 GMT+0 - Resolved - This incident has been resolved. Sep 1, 05:26:00 GMT+0 - Investigating - An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>05:33:14</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 1</var>, <var data-var='time'>05:26:00</var> GMT+0</small><br><strong>Investigating</strong> -
  An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 05:26:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmti89ye70bj11mmvnuq2o6ws</link>
  <guid>https://status.thebackend.io/incident/cmti89ye70bj11mmvnuq2o6ws</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 1 hour and 30 minutes

    Affected Components: Users, Cloud Save
    Aug 27, 09:15:00 GMT+0 - Resolved - The country code related errors affecting some accounts have been resolved, and all services are now fully operational.  
We have confirmed normal operation of login/authentication, Cloud Save, and the Realtime servers.  
We apologize for the inconvenience. Aug 27, 08:43:00 GMT+0 - Identified - Cloud Save and the Realtime servers have been restored.  
The country code related errors affecting some accounts are still being addressed, and we will provide an update as soon as the issue is resolved.  
We apologize for the inconvenience. Aug 27, 07:59:06 GMT+0 - Identified - The login/authentication servers have been restored.  
However, we have identified an issue where some accounts are experiencing country code related errors, and we are currently working on it.  
Cloud Save and the Realtime servers remain affected, and the BACKND server team is continuing recovery work.  
We will share further updates on this page as soon as they are available.  
We apologize for the inconvenience caused by this server issue. Aug 27, 07:45:00 GMT+0 - Investigating - An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>09:15:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The country code related errors affecting some accounts have been resolved, and all services are now fully operational.  
We have confirmed normal operation of login/authentication, Cloud Save, and the Realtime servers.  
We apologize for the inconvenience..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>08:43:00</var> GMT+0</small><br><strong>Identified</strong> -
  Cloud Save and the Realtime servers have been restored.  
The country code related errors affecting some accounts are still being addressed, and we will provide an update as soon as the issue is resolved.  
We apologize for the inconvenience..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>07:59:06</var> GMT+0</small><br><strong>Identified</strong> -
  The login/authentication servers have been restored.  
However, we have identified an issue where some accounts are experiencing country code related errors, and we are currently working on it.  
Cloud Save and the Realtime servers remain affected, and the BACKND server team is continuing recovery work.  
We will share further updates on this page as soon as they are available.  
We apologize for the inconvenience caused by this server issue..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>07:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 27 Aug 2026 07:45:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmtb8225b078w0kpk5patz97a</link>
  <guid>https://status.thebackend.io/incident/cmtb8225b078w0kpk5patz97a</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 20 hours

    Affected Components: GameInfo
    Aug 25, 00:17:00 GMT+0 - Resolved - 금일 08:55\~09:17 동안 게임 정보 관련 요청에서 에러가 발생했습니다.

서버 요청량이 급증하면서 오토스케일링이 작동했으나, 서버 확장 속도가 요청 증가 속도를 따라가지 못해 일시적인 쓰로틀링과 500번대 오류가 발생했습니다.

현재는 서버 확장이 완료되어 정상화된 상태입니다.  
서비스 이용에 불편을 드려 죄송합니다. Aug 24, 23:56:00 GMT+0 - Resolved - An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>00:17:00</var> GMT+0</small><br><strong>Resolved</strong> -
  금일 08:55\~09:17 동안 게임 정보 관련 요청에서 에러가 발생했습니다.

서버 요청량이 급증하면서 오토스케일링이 작동했으나, 서버 확장 속도가 요청 증가 속도를 따라가지 못해 일시적인 쓰로틀링과 500번대 오류가 발생했습니다.

현재는 서버 확장이 완료되어 정상화된 상태입니다.  
서비스 이용에 불편을 드려 죄송합니다..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>23:56:00</var> GMT+0</small><br><strong>Resolved</strong> -
  An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Aug 2026 23:56:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmt7x1f2y0cop0knhn632nt7t</link>
  <guid>https://status.thebackend.io/incident/cmt7x1f2y0cop0knhn632nt7t</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 5 hours and 10 minutes

    Affected Components: Chat
    Aug 10, 07:10:00 GMT+0 - Resolved - This incident has been resolved. Aug 10, 02:00:15 GMT+0 - Investigating - We have confirmed that the chat menu is currently inaccessible on the console, and we are responding urgently.

It has been confirmed that using in-game chat is not a problem.

The server team is promptly taking action to identify the cause and restore service, and,

We will promptly guide you through the process on this page.

We apologize for the inconvenience caused by the server issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>07:10:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>02:00:15</var> GMT+0</small><br><strong>Investigating</strong> -
  We have confirmed that the chat menu is currently inaccessible on the console, and we are responding urgently.

It has been confirmed that using in-game chat is not a problem.

The server team is promptly taking action to identify the cause and restore service, and,

We will promptly guide you through the process on this page.

We apologize for the inconvenience caused by the server issue..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 10 Aug 2026 02:00:15 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmsml3p8n0h250zrp91nyo49c</link>
  <guid>https://status.thebackend.io/incident/cmsml3p8n0h250zrp91nyo49c</guid>
</item>

<item>
  <title>Function Server issues detected.</title>
  <description>
    Type: Incident
    Duration: 2 hours and 33 minutes

    Affected Components: Function
    Jul 26, 14:08:00 GMT+0 - Resolved - Service stabilization confirmed and internal notification completed. Jul 26, 11:35:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 33 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>14:08:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Service stabilization confirmed and internal notification completed..</p>
<p><small>Jul <var data-var='date'> 26</var>, <var data-var='time'>11:35:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 26 Jul 2026 11:35:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cms1wj7oh0an70rml92eas9ct</link>
  <guid>https://status.thebackend.io/incident/cms1wj7oh0an70rml92eas9ct</guid>
</item>

<item>
  <title>User Authentication and Function Server issues detected.</title>
  <description>
    Type: Incident
    Duration: 1 hour and 45 minutes

    Affected Components: Users, Function
    Jul 22, 10:35:00 GMT+0 - Resolved - Service stabilization confirmed and internal notification completed. Jul 22, 08:50:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 45 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>10:35:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Service stabilization confirmed and internal notification completed..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>08:50:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 22 Jul 2026 08:50:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmrw9a9vn00rd0zo3mm1g9adp</link>
  <guid>https://status.thebackend.io/incident/cmrw9a9vn00rd0zo3mm1g9adp</guid>
</item>

<item>
  <title>Console Issue Detected</title>
  <description>
    Type: Incident
    Duration: 3 hours and 28 minutes

    Affected Components: Console, Community
    Jul 14, 04:26:00 GMT+0 - Resolved - This incident has been resolved. Jul 14, 03:34:08 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jul 14, 00:57:43 GMT+0 - Identified - An abnormal condition has been detected on the console, and we are currently responding urgently.

The BACKND server team is actively investigating and taking swift action to restore service.

Progress updates will be shared promptly on this page.

We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>04:26:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>03:34:08</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>
<p><small>Jul <var data-var='date'> 14</var>, <var data-var='time'>00:57:43</var> GMT+0</small><br><strong>Identified</strong> -
  An abnormal condition has been detected on the console, and we are currently responding urgently.

The BACKND server team is actively investigating and taking swift action to restore service.

Progress updates will be shared promptly on this page.

We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 14 Jul 2026 00:57:43 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmrjxzblk05kq1fmpw4jvyjmu</link>
  <guid>https://status.thebackend.io/incident/cmrjxzblk05kq1fmpw4jvyjmu</guid>
</item>

<item>
  <title>First Half 2026 Server Maintenance Notice - April 28 (Tue)</title>
  <description>
    Type: Maintenance
    Duration: 5 hours and 12 minutes

    Affected Components: Logs, Posts, Match, Database, Bills, Users, Terms and Privacy, Friends, Guilds, Push Notifications, Console, GameInfo, Inquiries, Cash, Charts, Probability, Chat, Notice, Cloud Save, Rank, Function, Events, Version Control, Coupons
    Apr 28, 06:12:00 GMT+0 - Completed - Maintenance has completed successfully Apr 28, 04:16:03 GMT+0 - Identified - We would like to inform you regarding the ongoing scheduled maintenance.

During the infrastructure work currently in progress,

the data replication process for ensuring data stability is taking longer than expected.

As a result, the maintenance end time has been extended as follows.

---

■ Updated Maintenance Schedule (UTC)

* Previous: April 28, 2026 (Tue) 01:00 \~ 05:00 (UTC)
* Updated: April 28, 2026 (Tue) 01:00 \~ 07:00 (UTC)

---

■ Project Status Restoration (UTC)

* April 28, 2026 (Tue) 07:00 (UTC)  
→ All projects will be restored to their pre-maintenance state

※ If the maintenance ends earlier or is further extended,

the project status will be restored based on the actual completion time.

※ A completion notice will be provided via the console announcement once maintenance is finished.

---

We sincerely apologize for the inconvenience caused by the extended maintenance.

We will do our best to complete the work as quickly as possible.

Thank you. Apr 28, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 28, 01:00:00 GMT+0 - Identified - Hello, This is team BACKND.

We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please refer to the details below, including the maintenance schedule and its expected impact.  
We kindly ask for your understanding, as this maintenance is essential to providing a stable service.

## **■ Maintenance Schedule**

* **April 28, 2026 (Tuesday) 01:00 \~ 05:00 (UTC)**
* Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided through the maintenance status page.

## **■ Maintenance Details**

**Backend Infrastructure Enhancement and Optimization**

* Database system enhancement: DB management system optimization and infrastructure migration to improve data processing efficiency
* Server infrastructure performance improvement: Computing resource upgrade and resource reallocation for authentication, chat, and world servers
* Network and load balancing optimization: Network configuration optimization to improve inter-server communication efficiency

## **■ Impact of Maintenance**

* **Project access restriction**: Communication with BACKND server will be restricted during maintenance, and all projects will be switched to &#039;Under Maintenance&#039; status.
* **Console access restriction**: BACKND console access and usage will be temporarily suspended. The console will provide guidance on the maintenance status.
* **Players access allowlist restriction**: The &quot;Players Allow Access&quot; feature will not function during the maintenance period.

## **■ Project Status Transition Schedule**

* **April 28 (Tue) 01:00 (UTC)** \- All projects switched to &#039;Under Maintenance&#039; status
* **April 28 (Tue) 05:00 (UTC)** \- All projects restored to pre-maintenance status  
   * If maintenance finishes early or is extended, status will be restored at the actual completion time  
   * Completion will be announced through console notifications

**⚠️ Since project status will be switched to maintenance mode, we recommend informing players within your games about this scheduled maintenance.**

We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).

We will do our best to complete the maintenance as quickly and efficiently as possible.  
Thank you. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>06:12:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>04:16:03</var> GMT+0</small><br><strong>Identified</strong> -
  We would like to inform you regarding the ongoing scheduled maintenance.

During the infrastructure work currently in progress,

the data replication process for ensuring data stability is taking longer than expected.

As a result, the maintenance end time has been extended as follows.

---

■ Updated Maintenance Schedule (UTC)

* Previous: April 28, 2026 (Tue) 01:00 \~ 05:00 (UTC)
* Updated: April 28, 2026 (Tue) 01:00 \~ 07:00 (UTC)

---

■ Project Status Restoration (UTC)

* April 28, 2026 (Tue) 07:00 (UTC)  
→ All projects will be restored to their pre-maintenance state

※ If the maintenance ends earlier or is further extended,

the project status will be restored based on the actual completion time.

※ A completion notice will be provided via the console announcement once maintenance is finished.

---

We sincerely apologize for the inconvenience caused by the extended maintenance.

We will do our best to complete the work as quickly as possible.

Thank you..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Hello, This is team BACKND.

We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please refer to the details below, including the maintenance schedule and its expected impact.  
We kindly ask for your understanding, as this maintenance is essential to providing a stable service.

## **■ Maintenance Schedule**

* **April 28, 2026 (Tuesday) 01:00 \~ 05:00 (UTC)**
* Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided through the maintenance status page.

## **■ Maintenance Details**

**Backend Infrastructure Enhancement and Optimization**

* Database system enhancement: DB management system optimization and infrastructure migration to improve data processing efficiency
* Server infrastructure performance improvement: Computing resource upgrade and resource reallocation for authentication, chat, and world servers
* Network and load balancing optimization: Network configuration optimization to improve inter-server communication efficiency

## **■ Impact of Maintenance**

* **Project access restriction**: Communication with BACKND server will be restricted during maintenance, and all projects will be switched to &#039;Under Maintenance&#039; status.
* **Console access restriction**: BACKND console access and usage will be temporarily suspended. The console will provide guidance on the maintenance status.
* **Players access allowlist restriction**: The &quot;Players Allow Access&quot; feature will not function during the maintenance period.

## **■ Project Status Transition Schedule**

* **April 28 (Tue) 01:00 (UTC)** \- All projects switched to &#039;Under Maintenance&#039; status
* **April 28 (Tue) 05:00 (UTC)** \- All projects restored to pre-maintenance status  
   * If maintenance finishes early or is extended, status will be restored at the actual completion time  
   * Completion will be announced through console notifications

**⚠️ Since project status will be switched to maintenance mode, we recommend informing players within your games about this scheduled maintenance.**

We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).

We will do our best to complete the maintenance as quickly and efficiently as possible.  
Thank you..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 28 Apr 2026 01:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/maintenance/cmlj6xtfe01b7hrhpn9vstqnd</link>
  <guid>https://status.thebackend.io/maintenance/cmlj6xtfe01b7hrhpn9vstqnd</guid>
</item>

<item>
  <title>Console Issue Detected</title>
  <description>
    Type: Incident
    Duration: 8 minutes

    Affected Components: Console
    Apr 27, 05:58:40 GMT+0 - Resolved - This incident has been resolved. Apr 27, 05:50:18 GMT+0 - Investigating - An abnormal condition has been detected in the console, and we are currently responding urgently.

The BACKND team is actively investigating and taking swift action to restore normal console functionality.

Progress updates will be shared promptly on this page.

We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>05:58:40</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>05:50:18</var> GMT+0</small><br><strong>Investigating</strong> -
  An abnormal condition has been detected in the console, and we are currently responding urgently.

The BACKND team is actively investigating and taking swift action to restore normal console functionality.

Progress updates will be shared promptly on this page.

We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Apr 2026 05:50:18 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmogs35nb16h5pv2721siv4hn</link>
  <guid>https://status.thebackend.io/incident/cmogs35nb16h5pv2721siv4hn</guid>
</item>

<item>
  <title>Recurring Mail Identifier Processing Issue (Resolved)</title>
  <description>
    Type: Incident
    Duration: 1 day, 1 hour and 30 minutes

    Affected Components: Console
    Apr 16, 07:00:00 GMT+0 - Resolved - We would like to inform you about an issue where recurring mails were not properly registered between April 15 and April 16.

The issue has been identified and resolved, and the service is now operating normally.

■ Incident Period

April 15, 2026 (Wed) 05:30 \~ April 16, 2026 (Thu) 07:00 (UTC)

■ Cause and Resolution

An issue occurred where the mail identifier for recurring mails sent during the affected period was not processed correctly, resulting in subsequent schedules not being registered.

We have fixed the mail identifier processing logic so that recurring schedules are now registered correctly.

Recurring mails that were interrupted during the affected period will not be automatically restored.

Please re-register the recurring mails to ensure normal operation.

We sincerely apologize for any inconvenience caused. Apr 15, 05:30:00 GMT+0 - Investigating - We would like to inform you about an issue where recurring mails were not properly registered between April 15 and April 16.

The issue has been identified and resolved, and the service is now operating normally.

■ Incident Period

April 15, 2026 (Wed) 05:30 \~ April 16, 2026 (Thu) 07:00 (UTC)

■ Cause and Resolution

An issue occurred where the mail identifier for recurring mails sent during the affected period was not processed correctly, resulting in subsequent schedules not being registered.

We have fixed the mail identifier processing logic so that recurring schedules are now registered correctly.

Recurring mails that were interrupted during the affected period will not be automatically restored.

Please re-register the recurring mails to ensure normal operation.

We sincerely apologize for any inconvenience caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We would like to inform you about an issue where recurring mails were not properly registered between April 15 and April 16.

The issue has been identified and resolved, and the service is now operating normally.

■ Incident Period

April 15, 2026 (Wed) 05:30 \~ April 16, 2026 (Thu) 07:00 (UTC)

■ Cause and Resolution

An issue occurred where the mail identifier for recurring mails sent during the affected period was not processed correctly, resulting in subsequent schedules not being registered.

We have fixed the mail identifier processing logic so that recurring schedules are now registered correctly.

Recurring mails that were interrupted during the affected period will not be automatically restored.

Please re-register the recurring mails to ensure normal operation.

We sincerely apologize for any inconvenience caused..</p>
<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>05:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We would like to inform you about an issue where recurring mails were not properly registered between April 15 and April 16.

The issue has been identified and resolved, and the service is now operating normally.

■ Incident Period

April 15, 2026 (Wed) 05:30 \~ April 16, 2026 (Thu) 07:00 (UTC)

■ Cause and Resolution

An issue occurred where the mail identifier for recurring mails sent during the affected period was not processed correctly, resulting in subsequent schedules not being registered.

We have fixed the mail identifier processing logic so that recurring schedules are now registered correctly.

Recurring mails that were interrupted during the affected period will not be automatically restored.

Please re-register the recurring mails to ensure normal operation.

We sincerely apologize for any inconvenience caused..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 15 Apr 2026 05:30:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmo2cfwj807q62rf6shn1hekj</link>
  <guid>https://status.thebackend.io/incident/cmo2cfwj807q62rf6shn1hekj</guid>
</item>

<item>
  <title>Server Issue Detected</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    Affected Components: Guilds
    Mar 17, 01:19:00 GMT+0 - Resolved - This incident has been resolved. Mar 17, 01:09:00 GMT+0 - Investigating - An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>01:19:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>01:09:00</var> GMT+0</small><br><strong>Investigating</strong> -
  An abnormal condition has been detected on the server, and we are currently responding urgently.  
The BACKND server team is actively investigating and taking swift action to restore service.  
Progress updates will be shared promptly on this page.  
We sincerely apologize for the inconvenience caused by this issue..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 17 Mar 2026 01:09:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmmtxarno02edpsb905hd2qlt</link>
  <guid>https://status.thebackend.io/incident/cmmtxarno02edpsb905hd2qlt</guid>
</item>

<item>
  <title>Intermittent Failures in CDN Chart and Probability Features</title>
  <description>
    Type: Incident
    Duration: 40 minutes

    Affected Components: Charts, Probability
    Mar 3, 03:11:00 GMT+0 - Resolved - We identified intermittent failures affecting the CDN chart and probability features.

Immediate action was taken from 11:32 to 11:40.

During the deployment process, additional intermittent failures occurred for a short period until the fix was fully applied to the servers.

We sincerely apologize for any inconvenience this may have caused. Mar 3, 02:31:00 GMT+0 - Investigating - We identified intermittent failures affecting the CDN chart and probability features.

Immediate action was taken from 11:32 to 11:40.

During the deployment process, additional intermittent failures occurred for a short period until the fix was fully applied to the servers.

We sincerely apologize for any inconvenience this may have caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>03:11:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We identified intermittent failures affecting the CDN chart and probability features.

Immediate action was taken from 11:32 to 11:40.

During the deployment process, additional intermittent failures occurred for a short period until the fix was fully applied to the servers.

We sincerely apologize for any inconvenience this may have caused..</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>02:31:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We identified intermittent failures affecting the CDN chart and probability features.

Immediate action was taken from 11:32 to 11:40.

During the deployment process, additional intermittent failures occurred for a short period until the fix was fully applied to the servers.

We sincerely apologize for any inconvenience this may have caused..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 3 Mar 2026 02:31:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmmada34o0012fgysmxp84w7q</link>
  <guid>https://status.thebackend.io/incident/cmmada34o0012fgysmxp84w7q</guid>
</item>

<item>
  <title>We have checked the server abnormality and are responding urgently.</title>
  <description>
    Type: Incident
    Duration: 2 hours and 5 minutes

    Affected Components: Posts, Charts, Chat, Probability, Inquiries, Cloud Save, Rank, Guilds, Community, GameInfo, Function, Push Notifications, Users, Events, Logs, Terms and Privacy, Version Control, Console, Status Page, Bills, Coupons, Friends, Notice, Match, Cash
    Oct 8, 00:59:00 GMT+0 - Resolved - This incident has been resolved. Oct 8, 00:50:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 7, 23:40:00 GMT+0 - Investigating - We have checked the server abnormality and are responding urgently. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>00:59:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>00:50:00</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'> 7</var>, <var data-var='time'>23:40:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We have checked the server abnormality and are responding urgently..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 7 Oct 2025 23:40:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmgh8xw9c0562ivk60f359ub2</link>
  <guid>https://status.thebackend.io/incident/cmgh8xw9c0562ivk60f359ub2</guid>
</item>

<item>
  <title>Function Authentication Request Errors</title>
  <description>
    Type: Incident
    Duration: 1 hour and 48 minutes

    Affected Components: Function
    Sep 17, 01:18:00 GMT+0 - Resolved - On September 17, 2025, between 08:30 and 10:18 (KST), intermittent errors occurred in login and token refresh requests for Backnd Function.  
The issue was caused by a side effect during an authentication server logic update, which affected some new servers under canary deployment.  
A rollback was applied, and the service is now fully restored.  
We sincerely apologize for the inconvenience caused. Sep 16, 23:30:00 GMT+0 - Investigating - We are currently experiencing intermittent errors with login and token refresh requests in the Backnd Function service.  
Our server team is investigating the root cause, and we will provide updates as they become available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>01:18:00</var> GMT+0</small><br><strong>Resolved</strong> -
  On September 17, 2025, between 08:30 and 10:18 (KST), intermittent errors occurred in login and token refresh requests for Backnd Function.  
The issue was caused by a side effect during an authentication server logic update, which affected some new servers under canary deployment.  
A rollback was applied, and the service is now fully restored.  
We sincerely apologize for the inconvenience caused..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently experiencing intermittent errors with login and token refresh requests in the Backnd Function service.  
Our server team is investigating the root cause, and we will provide updates as they become available..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 16 Sep 2025 23:30:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmfp04lf300hwn2cevhtqboa5</link>
  <guid>https://status.thebackend.io/incident/cmfp04lf300hwn2cevhtqboa5</guid>
</item>

<item>
  <title>Checking for server failure.</title>
  <description>
    Type: Incident
    Duration: 25 minutes

    Affected Components: Inquiries, Cloud Save, Posts, Bills, Charts, GameInfo, Friends, Coupons, Events, Users, Logs, Notice, Push Notifications, Guilds, Match, Cash, Version Control, Function, Terms and Privacy, Rank, Probability, Chat
    Sep 10, 15:47:00 GMT+0 - Resolved - This incident has been resolved. Sep 10, 15:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:47:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 10 Sep 2025 15:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmfe4nr80000cnsomu0hddar3</link>
  <guid>https://status.thebackend.io/incident/cmfe4nr80000cnsomu0hddar3</guid>
</item>

<item>
  <title>Cloudflare Major Outage Causing CloudSave Service Disruption</title>
  <description>
    Type: Incident
    Duration: 35 minutes

    Affected Components: Cloud Save
    Sep 4, 05:13:00 GMT+0 - Resolved - This incident has been resolved. Sep 4, 04:58:00 GMT+0 - Investigating - Due to a major outage at Cloudflare, the Cloud Save service was temporarily unavailable.  
We have confirmed that the service was affected from **04:58 to 05:13 UTC**. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>05:13:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>04:58:00</var> GMT+0</small><br><strong>Investigating</strong> -
  Due to a major outage at Cloudflare, the Cloud Save service was temporarily unavailable.  
We have confirmed that the service was affected from **04:58 to 05:13 UTC**..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 4 Sep 2025 04:58:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmf4zvsc3004ydhf0u6xjwu3o</link>
  <guid>https://status.thebackend.io/incident/cmf4zvsc3004ydhf0u6xjwu3o</guid>
</item>

<item>
  <title>Maintenance Schedule: August 27, 2025 (Wed) 01:00 to 05:00 (UTC)</title>
  <description>
    Type: Incident
    Duration: 2 hours and 47 minutes

    Affected Components: Friends, Inquiries, Coupons, Events, Users, Logs, Notice, Push Notifications, Console, Community, Status Page, Guilds, Match, Cash, Version Control, GameInfo, Posts, Bills, Charts, Function, Probability, Chat, Terms and Privacy, Rank
    Aug 27, 03:46:51 GMT+0 - Resolved - The 2025 second-half server maintenance has been completed early. Aug 27, 01:00:16 GMT+0 - Identified - **Maintenance Schedule: August 27, 2025 (Wed) 01:00 to 05:00 (UTC)** 

Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided within the console.

\- August 27, 01:00 (UTC): All projects will enter maintenance mode.

\- August 27, 05:00 (UTC): All projects will return to their pre-maintenance status.

 \- After the maintenance is complete, you will be able to access the console normally. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>03:46:51</var> GMT+0</small><br><strong>Resolved</strong> -
  The 2025 second-half server maintenance has been completed early..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>01:00:16</var> GMT+0</small><br><strong>Identified</strong> -
  **Maintenance Schedule: August 27, 2025 (Wed) 01:00 to 05:00 (UTC)** 

Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided within the console.

\- August 27, 01:00 (UTC): All projects will enter maintenance mode.

\- August 27, 05:00 (UTC): All projects will return to their pre-maintenance status.

 \- After the maintenance is complete, you will be able to access the console normally..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 27 Aug 2025 01:00:16 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmet9q4l90037ytmxq79dr7za</link>
  <guid>https://status.thebackend.io/incident/cmet9q4l90037ytmxq79dr7za</guid>
</item>

<item>
  <title>We have identified a server failure and are responding urgently.</title>
  <description>
    Type: Incident
    Duration: 16 minutes

    Affected Components: Guilds, Match, Cash, Version Control, GameInfo, Friends, Bills, Inquiries, Coupons, Logs, Charts, Events, Users, Function, Posts, Notice, Probability, Chat, Terms and Privacy, Rank, Push Notifications
    Aug 19, 05:16:00 GMT+0 - Resolved - This incident has been resolved. Aug 19, 05:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>05:16:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 19</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 19 Aug 2025 05:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmei31nmp0002d4fkoevn5k9m</link>
  <guid>https://status.thebackend.io/incident/cmei31nmp0002d4fkoevn5k9m</guid>
</item>

<item>
  <title>Checking server connection failure</title>
  <description>
    Type: Incident
    Duration: 20 minutes

    Affected Components: Guilds, Logs, Charts, Events, Users, Function, Inquiries, Match, Cash, Version Control, GameInfo, Coupons, Posts, Friends, Bills, , Console, Notice, Probability, Chat, Terms and Privacy, Rank, Push Notifications, 
Game Server →
    Jun 6, 02:40:00 GMT+0 - Resolved - The service has been restored following an emergency response.  
We apologize for the inconvenience and appreciate your understanding. Jun 6, 02:20:07 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>02:40:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The service has been restored following an emergency response.  
We apologize for the inconvenience and appreciate your understanding..</p>
<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>02:20:07</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 6 Jun 2025 02:20:07 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cmbk6gy3e000p148ynuisilkw</link>
  <guid>https://status.thebackend.io/incident/cmbk6gy3e000p148ynuisilkw</guid>
</item>

<item>
  <title>Server Maintenance [Apr 28, 2025]</title>
  <description>
    Type: Incident
    Duration: 1 hour and 3 minutes

    Affected Components: Guilds, Logs, Charts, Events, Users, Notice, Community, Probability, Function, Console, Chat, Terms and Privacy, Rank, Push Notifications, Inquiries, Match, Cash, Version Control, GameInfo, Coupons, Posts, Friends, Bills, Status Page
    Apr 28, 02:03:00 GMT+0 - Resolved - This incident has been resolved. Apr 28, 01:00:00 GMT+0 - Identified - Hello, This is team BACKND.  
We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please find the details below, including the maintenance schedule, content, and potential impact.  
We kindly ask for your understanding as this maintenance is essential for providing a stable service.  

* **Maintenance Schedule**  
   * **April 28, 2025 (Mon) 01:00 to 04:00 (UTC)**  
         * Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided within the console.  
   * Apr 28 (Mon) 01:00 (UTC)  
         * All projects will be switched to maintenance mode.  
   * Apr 28 (Mon) 04:00 (UTC)  
         * All projects will return to their pre-maintenance status.  
         * If maintenance is completed earlier than scheduled, projects will be returned to their pre-maintenance status at that time.  
         * A notice will be posted immediately in the console announcements when maintenance is complete.
* **Maintenance Details**  
   * Database Server  
         * Infrastructure system update  
         * Optimization of the leaderboard database  
   * Chat Server  
         * Redistribute of the chat server
* **Impact of Maintenance**  
   * **During the maintenance period, there may be disruptions in server communication, and all projects will be set to maintenance mode as a precaution.**  
   * We recommend informing users within your games about this scheduled maintenance.  
   * The console will be unavailable until the maintenance is completed due to an infrastructure system update.  
   The console will provide guidance on the maintenance status.

We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).  
We will do our best to complete the maintenance as quickly and efficiently as possible.

Thank you. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 3 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>02:03:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Hello, This is team BACKND.  
We would like to inform you of a scheduled maintenance to ensure more stable server operations.  
Please find the details below, including the maintenance schedule, content, and potential impact.  
We kindly ask for your understanding as this maintenance is essential for providing a stable service.  

* **Maintenance Schedule**  
   * **April 28, 2025 (Mon) 01:00 to 04:00 (UTC)**  
         * Maintenance may be completed earlier than scheduled or may be extended. In such cases, guidance will be provided within the console.  
   * Apr 28 (Mon) 01:00 (UTC)  
         * All projects will be switched to maintenance mode.  
   * Apr 28 (Mon) 04:00 (UTC)  
         * All projects will return to their pre-maintenance status.  
         * If maintenance is completed earlier than scheduled, projects will be returned to their pre-maintenance status at that time.  
         * A notice will be posted immediately in the console announcements when maintenance is complete.
* **Maintenance Details**  
   * Database Server  
         * Infrastructure system update  
         * Optimization of the leaderboard database  
   * Chat Server  
         * Redistribute of the chat server
* **Impact of Maintenance**  
   * **During the maintenance period, there may be disruptions in server communication, and all projects will be set to maintenance mode as a precaution.**  
   * We recommend informing users within your games about this scheduled maintenance.  
   * The console will be unavailable until the maintenance is completed due to an infrastructure system update.  
   The console will provide guidance on the maintenance status.

We apologize for any inconvenience this may cause and appreciate your patience and cooperation.  
If you have any questions or need assistance, please reach out to us at [global@backnd.com](mailto:global@backnd.com).  
We will do our best to complete the maintenance as quickly and efficiently as possible.

Thank you..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 28 Apr 2025 01:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm8mwf1rr001au2l5fl7b2rrv</link>
  <guid>https://status.thebackend.io/incident/cm8mwf1rr001au2l5fl7b2rrv</guid>
</item>

<item>
  <title>CHAT Server maintenance completed</title>
  <description>
    Type: Incident
    Duration: 2 hours and 35 minutes

    Affected Components: Chat
    Feb 19, 03:35:00 GMT+0 - Resolved - This incident has been resolved. Feb 19, 01:00:00 GMT+0 - Investigating - CHAT Server maintenance has started.  
  
**Maintenance Schedule**

\- **Feb 19, 2025 (Wed) 01:00 to 03:00 (UTC)**

\- It may be terminated earlier than the scheduled time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>03:35:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  CHAT Server maintenance has started.  
  
**Maintenance Schedule**

\- **Feb 19, 2025 (Wed) 01:00 to 03:00 (UTC)**

\- It may be terminated earlier than the scheduled time..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 19 Feb 2025 01:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm7d5mghb0002g3isvloik3ln</link>
  <guid>https://status.thebackend.io/incident/cm7d5mghb0002g3isvloik3ln</guid>
</item>

<item>
  <title>Server unavailability and console unavailability have occurred, so we are checking.</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    Affected Components: Chat, Terms and Privacy, Status Page, Push Notifications, Rank, Inquiries, Match, Version Control, Cash, Guilds, GameInfo, Coupons, Logs, Charts, Posts, Users, Friends, Events, Bills, Notice, Community, Probability, Console, Function
    Jan 10, 05:01:00 GMT+0 - Resolved - It&#039;s normalized. Jan 10, 04:55:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </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>Jan <var data-var='date'> 10</var>, <var data-var='time'>05:01:00</var> GMT+0</small><br><strong>Resolved</strong> -
  It&#039;s normalized..</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>04:55:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 10 Jan 2025 04:55:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm5qalo730010fci00jjmmzq2</link>
  <guid>https://status.thebackend.io/incident/cm5qalo730010fci00jjmmzq2</guid>
</item>

<item>
  <title>Incorrect inDate information is returned for some players, resulting in duplicate rankings on the leaderboard.</title>
  <description>
    Type: Incident
    Duration: 50 minutes

    Affected Components: Rank
    Dec 26, 07:00:00 GMT+0 - Resolved - It has been normalized. Dec 26, 06:10:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Resolved</strong> -
  It has been normalized..</p>
<p><small>Dec <var data-var='date'> 26</var>, <var data-var='time'>06:10:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 26 Dec 2024 06:10:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm5ah8wvb0073wukropvvto29</link>
  <guid>https://status.thebackend.io/incident/cm5ah8wvb0073wukropvvto29</guid>
</item>

<item>
  <title>Chart server token verification error (SDK version lower than 5.7.0)</title>
  <description>
    Type: Incident
    Duration: 1 hour

    Affected Components: Charts
    Dec 20, 04:57:00 GMT+0 - Resolved - We have responded to the chart server token verification error that was found in SDK versions lower than 5.7.0.

The target projects are confirmed to be 5, and detailed information has been sent to the target customers via email.

We apologize for the inconvenience. Dec 20, 04:00:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>04:57:00</var> GMT+0</small><br><strong>Resolved</strong> -
  We have responded to the chart server token verification error that was found in SDK versions lower than 5.7.0.

The target projects are confirmed to be 5, and detailed information has been sent to the target customers via email.

We apologize for the inconvenience..</p>
<p><small>Dec <var data-var='date'> 20</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 20 Dec 2024 04:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm4wimt32003y5wvzzqhg5iwo</link>
  <guid>https://status.thebackend.io/incident/cm4wimt32003y5wvzzqhg5iwo</guid>
</item>

<item>
  <title>A server response delay occurred. [Resolution completed]</title>
  <description>
    Type: Incident
    Duration: 5 hours and 40 minutes

    Affected Components: Chat, Terms and Privacy, Status Page, Push Notifications, Rank, Inquiries, Match, Version Control, Cash, Guilds, GameInfo, Coupons, Logs, Charts, Posts, Users, Friends, Events, Bills, Notice, Community, Probability, Console, Function
    Oct 22, 13:45:00 GMT+0 - Resolved - A server response delay occurred. \[Resolution completed\] Oct 22, 12:55:00 GMT+0 - Identified - A server response delay has been reoccurred. Oct 22, 10:50:00 GMT+0 - Resolved - A server response delay occurred. \[Resolution completed\] Oct 22, 08:05:00 GMT+0 - Investigating - A server response delay occurred. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    <p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>13:45:00</var> GMT+0</small><br><strong>Resolved</strong> -
  A server response delay occurred. \[Resolution completed\].</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>12:55:00</var> GMT+0</small><br><strong>Identified</strong> -
  A server response delay has been reoccurred..</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>10:50:00</var> GMT+0</small><br><strong>Resolved</strong> -
  A server response delay occurred. \[Resolution completed\].</p>
<p><small>Oct <var data-var='date'> 22</var>, <var data-var='time'>08:05:00</var> GMT+0</small><br><strong>Investigating</strong> -
  A server response delay occurred..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 22 Oct 2024 08:05:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm2kd0rr500726nib1t6lbeai</link>
  <guid>https://status.thebackend.io/incident/cm2kd0rr500726nib1t6lbeai</guid>
</item>

  </channel>
  </rss>