<?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, 28 Apr 2026 01:00:00 +0000</pubDate>
    
<item>
  <title>First Half 2026 Server Maintenance Notice - April 28 (Tue)</title>
  <description>
    Type: Maintenance
    

    Affected Components: Posts, Database, Bills, Users, Terms and Privacy, Friends, Push Notifications, Console, Inquiries, GameInfo, Guilds, Logs, Match, Cash, Charts, Chat, Probability, Notice, Cloud Save, Rank, Function, Events, Version Control, Coupons
    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>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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>Recurring Mail Identifier Processing Issue (Resolved)</title>
  <description>
    Type: Incident
    Duration: 1 day, 1 hour and 30 minutes

    Affected Components: Console
    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. 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. 
  </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>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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: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. Mar 17, 01:19:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:09:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:19:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </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, 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. 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 40 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:31:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:11:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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 7, 23:40:00 GMT+0 - Investigating - We have checked the server abnormality and are responding urgently. Oct 8, 00:50:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 8, 00:59:00 GMT+0 - Resolved - This incident has been resolved. 
  </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>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have checked the server abnormality and are responding urgently..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:59:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </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>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:18:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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:00:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 10, 15:47:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:47:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </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>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:13:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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**..&lt;/p&gt;
]]>
  </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, 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. Aug 27, 03:46:51 GMT+0 - Resolved - The 2025 second-half server maintenance has been completed early. 
  </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>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  **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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:46:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The 2025 second-half server maintenance has been completed early..&lt;/p&gt;
]]>
  </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:00:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 19, 05:16:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:16:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </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:20:07 GMT+0 - Investigating - We are currently investigating this incident. 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:20:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The service has been restored following an emergency response.  
We apologize for the inconvenience and appreciate your understanding..&lt;/p&gt;
]]>
  </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>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:03:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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, 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. Feb 19, 03:35:00 GMT+0 - Resolved - This incident has been resolved. 
  </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>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  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..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </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, 04:55:00 GMT+0 - Investigating - We are currently investigating this incident. Jan 10, 05:01:00 GMT+0 - Resolved - It&#039;s normalized. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  It&#039;s normalized..&lt;/p&gt;
]]>
  </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, 06:10:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 26, 07:00:00 GMT+0 - Resolved - It has been normalized. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:10:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  It has been normalized..&lt;/p&gt;
]]>
  </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:00:00 GMT+0 - Investigating - We are currently investigating this incident. 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:57:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  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..&lt;/p&gt;
]]>
  </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, 08:05:00 GMT+0 - Investigating - A server response delay occurred. Oct 22, 12:55:00 GMT+0 - Identified - A server response delay has been reoccurred. Oct 22, 13:45:00 GMT+0 - Resolved - A server response delay occurred. \[Resolution completed\] Oct 22, 10:50:00 GMT+0 - Resolved - A server response delay occurred. \[Resolution completed\] 
  </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>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  A server response delay occurred..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  A server response delay has been reoccurred..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  A server response delay occurred. \[Resolution completed\].&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  A server response delay occurred. \[Resolution completed\].&lt;/p&gt;
]]>
  </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>

<item>
  <title>Server maintenance completed in the second half of the year</title>
  <description>
    Type: Incident
    Duration: 2 hours and 58 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, 07:58:00 GMT+0 - Resolved - Server maintenance completed in the second half of the year Oct 22, 05:00:00 GMT+0 - Monitoring - The server Server Maintenance has started.  
  
**Maintenance Schedule** 

\- **October 22, 2024 (Tue) 05:00 to 08: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 58 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Server maintenance completed in the second half of the year.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The server Server Maintenance has started.  
  
**Maintenance Schedule** 

\- **October 22, 2024 (Tue) 05:00 to 08:00 (UTC)**

\- It may be terminated earlier than the scheduled time. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 22 Oct 2024 05:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm2jz8m98002ebr4qlhrpgeu1</link>
  <guid>https://status.thebackend.io/incident/cm2jz8m98002ebr4qlhrpgeu1</guid>
</item>

<item>
  <title>We have identified a network infrastructure problem and are responding to an emergency check.</title>
  <description>
    Type: Incident
    Duration: 35 minutes

    Affected Components: Chat, Terms and Privacy, Push Notifications, Rank, Inquiries, Match, Version Control, Cash, Guilds, GameInfo, Coupons, Logs, Charts, Posts, Users, Friends, Events, Bills, Notice, Probability, Function
    Oct 5, 15:00:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 5, 14:54:00 GMT+0 - Investigating - We are responding to an emergency confirmation by checking the network infrastructure problem. We apologize for the inconvenience caused to you. Oct 5, 15:29:00 GMT+0 - Resolved - Network infrastructure issues \[Normalization complete\] 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:54:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are responding to an emergency confirmation by checking the network infrastructure problem. We apologize for the inconvenience caused to you..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:29:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Network infrastructure issues \[Normalization complete\].&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 5 Oct 2024 14:54:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm1wc8nb8005rthjeln434xqw</link>
  <guid>https://status.thebackend.io/incident/cm1wc8nb8005rthjeln434xqw</guid>
</item>

<item>
  <title>The community has been normalized.</title>
  <description>
    Type: Incident
    Duration: 28 minutes

    Affected Components: Community
    Sep 26, 11:29:36 GMT+0 - Resolved - The community has been normalized. Sep 26, 11:02:00 GMT+0 - Investigating - We are responding by checking the phenomenon of community access unavailability.  
We apologize for the inconvenience caused to you.  
If you have any questions, please contact us through [global@backnd.com](mailto:global@backnd.com). 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:29:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The community has been normalized..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:02:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are responding by checking the phenomenon of community access unavailability.  
We apologize for the inconvenience caused to you.  
If you have any questions, please contact us through [global@backnd.com](mailto:global@backnd.com)..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Sep 2024 11:02:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm1j6pl0i004gocy9ncatq5jk</link>
  <guid>https://status.thebackend.io/incident/cm1j6pl0i004gocy9ncatq5jk</guid>
</item>

<item>
  <title>Issue of one-time leaderboard settlement abnormality</title>
  <description>
    Type: Incident
    Duration: 5 days and 22 hours

    Affected Components: Rank
    Sep 30, 07:00:00 GMT+0 - Resolved - It was normalized at 16 o&#039;clock on September 30th. Sep 24, 09:00:00 GMT+0 - Investigating - Regardless of the end schedule of the one-time leaderboard, there was a phenomenon in which settlement was made based on the end time every day. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days and 22 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  It was normalized at 16 o&#039;clock on September 30th..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Regardless of the end schedule of the one-time leaderboard, there was a phenomenon in which settlement was made based on the end time every day..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 24 Sep 2024 09:00:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm1oqhlm8000ckdlzaihce1tb</link>
  <guid>https://status.thebackend.io/incident/cm1oqhlm8000ckdlzaihce1tb</guid>
</item>

<item>
  <title>Checking console functional abnormalities</title>
  <description>
    Type: Incident
    Duration: 1 hour and 43 minutes

    Affected Components: Console
    Sep 24, 06:20:00 GMT+0 - Investigating - If you proceed with the deletion of PLAYER in the console or the immediate withdrawal, it has been found that the PLAYER information is not deleted normally, so we are checking it.  
  
Please stop using the feature until it is resolved. Sep 24, 08:03:00 GMT+0 - Resolved - Functionality has been normalized. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 43 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  If you proceed with the deletion of PLAYER in the console or the immediate withdrawal, it has been found that the PLAYER information is not deleted normally, so we are checking it.  
  
Please stop using the feature until it is resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:03:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Functionality has been normalized..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 24 Sep 2024 06:20:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/cm1g4fl39000b10wr40qglk58</link>
  <guid>https://status.thebackend.io/incident/cm1g4fl39000b10wr40qglk58</guid>
</item>

<item>
  <title>Information on some failures in game info related function requests</title>
  <description>
    Type: Incident
    Duration: 28 minutes

    Affected Components: GameInfo
    Jun 25, 05:21:00 GMT+0 - Identified - June 25th 14:21 to 14:49 (KST)

Some of the requests for the game info function were made with errors, so we responded urgently.

We apologize for the inconvenience in using it. Jun 25, 05:49:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:21:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  June 25th 14:21 to 14:49 (KST)

Some of the requests for the game info function were made with errors, so we responded urgently.

We apologize for the inconvenience in using it..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:49:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Jun 2024 05:21:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/clxu0f2mz60399bjmx93k4eb65</link>
  <guid>https://status.thebackend.io/incident/clxu0f2mz60399bjmx93k4eb65</guid>
</item>

<item>
  <title>A DNS server failure has occurred and is being verified.</title>
  <description>
    Type: Incident
    Duration: 1 hour

    Affected Components: Chat, Terms and Privacy, Push Notifications, Rank, Inquiries, Match, Version Control, Cash, Guilds, GameInfo, Coupons, Logs, Charts, Posts, Users, Friends, Events, Bills, Notice, Probability, Function
    May 9, 16:01:00 GMT+0 - Resolved - It has been normalized by completing the response process. May 9, 15:01: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>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  It has been normalized by completing the response process..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:01:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 9 May 2024 15:01:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/clvzrqdo323527baoncyj9jyim</link>
  <guid>https://status.thebackend.io/incident/clvzrqdo323527baoncyj9jyim</guid>
</item>

<item>
  <title>Notification of console login failure and BACKND [BASE] failure of some function calls</title>
  <description>
    Type: Incident
    Duration: 32 minutes

    Affected Components: Guilds, GameInfo, Charts, Posts, Console
    Feb 19, 02:17:00 GMT+0 - Resolved - This incident has been resolved. Feb 19, 01:45:00 GMT+0 - Investigating - A sudden increase in traffic requests resulted in console login unavailability and a failure to invoke some functions of BACKND \[BASE\]. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:17:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  A sudden increase in traffic requests resulted in console login unavailability and a failure to invoke some functions of BACKND \[BASE\]..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 19 Feb 2024 01:45:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/clsts2ql164058bjokg7uxiecs</link>
  <guid>https://status.thebackend.io/incident/clsts2ql164058bjokg7uxiecs</guid>
</item>

<item>
  <title>Chart/probability lookup not allowed [Recovered]</title>
  <description>
    Type: Incident
    Duration: 18 minutes

    Affected Components: Charts, Probability
    Jan 18, 08:24:00 GMT+0 - Resolved - Restoration completed at 5:24. Jan 18, 08:06:00 GMT+0 - Investigating - From 5:06 to 5:24 p.m., there was a temporary problem with the chart/probability server, which prevented normal inquiry.
I&#039;m sorry for the inconvenience in using it.
We will inform you of the details through the community notice. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:24:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Restoration completed at 5:24..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  From 5:06 to 5:24 p.m., there was a temporary problem with the chart/probability server, which prevented normal inquiry.
I&#039;m sorry for the inconvenience in using it.
We will inform you of the details through the community notice..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jan 2024 08:06:00 +0000</pubDate>
  <link>https://status.thebackend.io/incident/clriztb4z5524bhn3wm3jch4h</link>
  <guid>https://status.thebackend.io/incident/clriztb4z5524bhn3wm3jch4h</guid>
</item>

  </channel>
  </rss>