bTeam Developer Status - Incident history https://bteam-developer.instatus.com bTeam Developer Fri, 5 Jun 2026 10:00:00 +0000 โ€œCookies not Enabledโ€ Messaging blocking website access Type: Incident Duration: 1 day, 5 hours and 24 minutes Affected Components: bTeam Meet Now, App, MyForum SSO, Dev SDK on MyForum (deprecated), MyForum Web Jun 6, 12:25:44 GMT+0 - Identified - We are continuing to work on a fix for this incident. Jun 6, 12:26:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 6, 03:29:15 GMT+0 - Investigating - We are currently investigating this incident. Jun 6, 03:30:28 GMT+0 - Investigating - The network administration team is aware of the issue. Please note that this team is located in Europe where it is currently outside normal working hours. Therefore, it may take slightly longer before a resolution is reached. Thank you for your patience! Jun 6, 03:47:41 GMT+0 - Investigating - We checked Network (Fetch/XHR) They were pretty normal. ## Additional diagnostic information We can confirm this issue is affecting multiple domains hosted on the iFastNet network, including: 1. myforum.mydiscussion.net ## Observed behavior: ๐Ÿ‘‰ Visiting the website loads normally at first. ๐Ÿ‘‰ The browser is automatically redirected through: * /?i=1 * /?i=2 * /?i=3 ๐Ÿ‘‰ After the third redirect, the site is redirected to: * https://sv101.ifastnet.com/cookies.html The โ€œCookies are not enabledโ€ page appears even though cookies are enabled. ## Diagnostics performed: * Tested on multiple browsers. * Tested in Incognito/Private mode. * Disabled browser extensions. * Cleared cookies/cache. * Issue affects all hosted subdomains, not a single website. * Network tab shows normal page loads followed by the automatic ?i=1 โ†’ ?i=2 โ†’ ?i=3 verification sequence and then a redirect to cookies.html. ## Conclusion: The issue appears to occur within the iFastNet browser verification or cookie validation system rather than the hosted website itself, since multiple independent domains and subdomains are affected in the same way. Jun 5, 10:00:00 GMT+0 - Investigating - ### _This issue is caused by our web hosting provider and is affecting our service._ # \[OUTAGE\] โ€œCookies not Enabledโ€ messaging appears incorrectly - 5 June 2026 **IMPACT**: Attempting to access some websites returns the system โ€œCookies are not enabledโ€ message, even when cookies are enabled. **AFFECTED**: Some browsers when accessing a domain on the proxy PHP hosting network. **STATUS**: Investigating - The network administration team is aware of the issue. **NEXT UPDATE**: This post will be updating with further developments. > ### We will continue to update you with the latest information on the issue. _I sincerely apologize if this incident has affected you._ Jun 6, 15:23:44 GMT+0 - Resolved - ## _From iFastNet's team:_ Hey all, Back with another update. This issue was not caused by a bug in the system (Yay to no โ€œship it on Friday and leaveโ€!) but rather a DDoS attack with some weird effects. The attack has subsided as I write this message, so sites should begin working again (Although if the attacker continues their actions it could happen again). To answer the question of does the team work weekends - yes. I believe they operate with limited numbers, but there are staff on site to address issues. If your site is not working and displays the cookie message as described by so many here, please do the following: * Clear your cache and cookies * Load your site in a new tab/window If it still does not work, please post your URL below this post. **Thank you for your patience with this issue!** Jun 6, 15:25:23 GMT+0 - Postmortem - # Postmortem: Incorrect "Cookies Not Enabled" Messaging Blocking Website Access **Incident Date:** June 5โ€“6, 2026 **Severity:** Major Outage **Status:** Resolved ## Summary Between June 5, 2026, at 5:00 PM and June 6, 2026, at 7:26 PM, users attempting to access websites hosted on the MyForum platform experienced widespread access failures. Affected visitors were incorrectly presented with a "Cookies are not enabled" message despite having cookies enabled in their browsers. The issue impacted MyForum, MyForum SSO, MyForum Web, the deprecated Dev SDK, and several related services. During the incident, many websites became inaccessible, preventing users from accessing forums and associated web applications. The incident was traced to an external DDoS attack affecting our hosting provider's network infrastructure and browser verification systems. No customer data was compromised. ## Impact ### Customer Impact * Visitors were unable to access affected websites. * Users were redirected through a browser verification sequence before ultimately reaching an erroneous "Cookies are not enabled" page. * Login and authentication flows relying on MyForum SSO were disrupted. * Community forums and hosted applications experienced extended downtime. ### Services Affected * MyForum * MyForum SSO * MyForum Web * Dev SDK on MyForum (deprecated) * Related services utilizing the affected hosting infrastructure ### Duration * Major service disruption: June 5, 2026, 5:00 PM โ€“ June 6, 2026, 7:26 PM * Full resolution confirmed: June 6, 2026, 10:23 PM ## Timeline ### June 5, 2026 **5:00 PM** * Reports begin arriving that websites are displaying a "Cookies are not enabled" message. * Investigation initiated. * Initial assessment identifies issue originating from hosting provider infrastructure. ### June 6, 2026 **10:29 AM** * Incident officially escalated for active investigation. **10:30 AM** * Network administration team engaged. * Communication issued regarding extended response times due to after-hours staffing. **10:47 AM** * Additional diagnostics completed. * Confirmed issue affects multiple domains across the hosting network. * Browser redirects observed through verification endpoints (`?i=1`, `?i=2`, `?i=3`) before redirecting users to a cookie error page. * Testing confirmed issue occurs across multiple browsers, private browsing sessions, and independent websites. **7:25 PM** * Engineering identifies corrective action and begins deployment. **7:26 PM** * Fix implemented. * Services begin recovering. * Monitoring phase initiated. **10:23 PM** * Hosting provider confirms the underlying DDoS attack has subsided. * Incident resolved. * Services operating normally. ## Root Cause The incident was caused by a DDoS attack targeting infrastructure operated by our web hosting provider. The attack interfered with the provider's browser verification and cookie validation mechanisms. As a result, legitimate users were incorrectly classified as failing browser validation checks and were redirected to a generic "Cookies are not enabled" page. Because the issue occurred within the provider's network protection systems rather than within MyForum applications themselves, multiple independent domains and services were affected simultaneously. ## Resolution The hosting provider implemented mitigations to address the attack and restore normal verification behavior. Once the mitigation was deployed, websites began serving content normally and authentication systems resumed operation. Users who continued to experience issues after service restoration were advised to: 1. Clear browser cache and cookies. 2. Open the website in a new browser tab or window. 3. Report affected URLs if problems persisted. ## What Went Well * The issue was quickly identified as external to customer websites. * Cross-domain diagnostics helped isolate the problem to provider infrastructure. * Regular status updates were communicated throughout the incident. * Service functionality returned immediately following mitigation deployment. ## What Could Be Improved * Earlier visibility into provider-side verification failures. * Faster escalation paths for after-hours infrastructure incidents. * Improved monitoring for abnormal browser verification redirects. * More detailed customer-facing diagnostics during the investigation phase. ## Preventive Actions To reduce the likelihood and impact of similar incidents in the future, we will: * Implement additional monitoring for unexpected redirect patterns and verification failures. * Improve alerting around authentication and browser validation anomalies. * Review escalation procedures with infrastructure providers. * Evaluate additional redundancy and mitigation options for externally hosted services. * Enhance incident communication templates for provider-related outages. ## Closing We understand that this outage disrupted access to community forums and hosted services, and we sincerely apologize for the inconvenience. We appreciate the patience of our users while our team and hosting provider worked to identify and resolve the issue. We will continue to review this incident and implement improvements to strengthen reliability and incident response processes going forward. Type: Incident

Duration: 1 day, 5 hours and 24 minutes

Affected Components: , , , ,

<p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>12:25:44</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>12:26:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>03:29:15</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>03:30:28</var> GMT+0</small><br><strong>Investigating</strong> - The network administration team is aware of the issue. Please note that this team is located in Europe where it is currently outside normal working hours. Therefore, it may take slightly longer before a resolution is reached. Thank you for your patience!.</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>03:47:41</var> GMT+0</small><br><strong>Investigating</strong> - We checked Network (Fetch/XHR) They were pretty normal. ## Additional diagnostic information We can confirm this issue is affecting multiple domains hosted on the iFastNet network, including: 1. myforum.mydiscussion.net ## Observed behavior: ๐Ÿ‘‰ Visiting the website loads normally at first. ๐Ÿ‘‰ The browser is automatically redirected through: * /?i=1 * /?i=2 * /?i=3 ๐Ÿ‘‰ After the third redirect, the site is redirected to: * https://sv101.ifastnet.com/cookies.html The โ€œCookies are not enabledโ€ page appears even though cookies are enabled. ## Diagnostics performed: * Tested on multiple browsers. * Tested in Incognito/Private mode. * Disabled browser extensions. * Cleared cookies/cache. * Issue affects all hosted subdomains, not a single website. * Network tab shows normal page loads followed by the automatic ?i=1 โ†’ ?i=2 โ†’ ?i=3 verification sequence and then a redirect to cookies.html. ## Conclusion: The issue appears to occur within the iFastNet browser verification or cookie validation system rather than the hosted website itself, since multiple independent domains and subdomains are affected in the same way..</p> <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Investigating</strong> - ### _This issue is caused by our web hosting provider and is affecting our service._ # \[OUTAGE\] โ€œCookies not Enabledโ€ messaging appears incorrectly - 5 June 2026 **IMPACT**: Attempting to access some websites returns the system โ€œCookies are not enabledโ€ message, even when cookies are enabled. **AFFECTED**: Some browsers when accessing a domain on the proxy PHP hosting network. **STATUS**: Investigating - The network administration team is aware of the issue. **NEXT UPDATE**: This post will be updating with further developments. > ### We will continue to update you with the latest information on the issue. _I sincerely apologize if this incident has affected you._.</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>15:23:44</var> GMT+0</small><br><strong>Resolved</strong> - ## _From iFastNet's team:_ Hey all, Back with another update. This issue was not caused by a bug in the system (Yay to no โ€œship it on Friday and leaveโ€!) but rather a DDoS attack with some weird effects. The attack has subsided as I write this message, so sites should begin working again (Although if the attacker continues their actions it could happen again). To answer the question of does the team work weekends - yes. I believe they operate with limited numbers, but there are staff on site to address issues. If your site is not working and displays the cookie message as described by so many here, please do the following: * Clear your cache and cookies * Load your site in a new tab/window If it still does not work, please post your URL below this post. **Thank you for your patience with this issue!**.</p> <p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>15:25:23</var> GMT+0</small><br><strong>Postmortem</strong> - # Postmortem: Incorrect "Cookies Not Enabled" Messaging Blocking Website Access **Incident Date:** June 5โ€“6, 2026 **Severity:** Major Outage **Status:** Resolved ## Summary Between June 5, 2026, at 5:00 PM and June 6, 2026, at 7:26 PM, users attempting to access websites hosted on the MyForum platform experienced widespread access failures. Affected visitors were incorrectly presented with a "Cookies are not enabled" message despite having cookies enabled in their browsers. The issue impacted MyForum, MyForum SSO, MyForum Web, the deprecated Dev SDK, and several related services. During the incident, many websites became inaccessible, preventing users from accessing forums and associated web applications. The incident was traced to an external DDoS attack affecting our hosting provider's network infrastructure and browser verification systems. No customer data was compromised. ## Impact ### Customer Impact * Visitors were unable to access affected websites. * Users were redirected through a browser verification sequence before ultimately reaching an erroneous "Cookies are not enabled" page. * Login and authentication flows relying on MyForum SSO were disrupted. * Community forums and hosted applications experienced extended downtime. ### Services Affected * MyForum * MyForum SSO * MyForum Web * Dev SDK on MyForum (deprecated) * Related services utilizing the affected hosting infrastructure ### Duration * Major service disruption: June 5, 2026, 5:00 PM โ€“ June 6, 2026, 7:26 PM * Full resolution confirmed: June 6, 2026, 10:23 PM ## Timeline ### June 5, 2026 **5:00 PM** * Reports begin arriving that websites are displaying a "Cookies are not enabled" message. * Investigation initiated. * Initial assessment identifies issue originating from hosting provider infrastructure. ### June 6, 2026 **10:29 AM** * Incident officially escalated for active investigation. **10:30 AM** * Network administration team engaged. * Communication issued regarding extended response times due to after-hours staffing. **10:47 AM** * Additional diagnostics completed. * Confirmed issue affects multiple domains across the hosting network. * Browser redirects observed through verification endpoints (`?i=1`, `?i=2`, `?i=3`) before redirecting users to a cookie error page. * Testing confirmed issue occurs across multiple browsers, private browsing sessions, and independent websites. **7:25 PM** * Engineering identifies corrective action and begins deployment. **7:26 PM** * Fix implemented. * Services begin recovering. * Monitoring phase initiated. **10:23 PM** * Hosting provider confirms the underlying DDoS attack has subsided. * Incident resolved. * Services operating normally. ## Root Cause The incident was caused by a DDoS attack targeting infrastructure operated by our web hosting provider. The attack interfered with the provider's browser verification and cookie validation mechanisms. As a result, legitimate users were incorrectly classified as failing browser validation checks and were redirected to a generic "Cookies are not enabled" page. Because the issue occurred within the provider's network protection systems rather than within MyForum applications themselves, multiple independent domains and services were affected simultaneously. ## Resolution The hosting provider implemented mitigations to address the attack and restore normal verification behavior. Once the mitigation was deployed, websites began serving content normally and authentication systems resumed operation. Users who continued to experience issues after service restoration were advised to: 1. Clear browser cache and cookies. 2. Open the website in a new browser tab or window. 3. Report affected URLs if problems persisted. ## What Went Well * The issue was quickly identified as external to customer websites. * Cross-domain diagnostics helped isolate the problem to provider infrastructure. * Regular status updates were communicated throughout the incident. * Service functionality returned immediately following mitigation deployment. ## What Could Be Improved * Earlier visibility into provider-side verification failures. * Faster escalation paths for after-hours infrastructure incidents. * Improved monitoring for abnormal browser verification redirects. * More detailed customer-facing diagnostics during the investigation phase. ## Preventive Actions To reduce the likelihood and impact of similar incidents in the future, we will: * Implement additional monitoring for unexpected redirect patterns and verification failures. * Improve alerting around authentication and browser validation anomalies. * Review escalation procedures with infrastructure providers. * Evaluate additional redundancy and mitigation options for externally hosted services. * Enhance incident communication templates for provider-related outages. ## Closing We understand that this outage disrupted access to community forums and hosted services, and we sincerely apologize for the inconvenience. We appreciate the patience of our users while our team and hosting provider worked to identify and resolve the issue. We will continue to review this incident and implement improvements to strengthen reliability and incident response processes going forward..</p> ]]> Fri, 5 Jun 2026 10:00:00 +0000 https://bteam-developer.instatus.com/incident/cmq1s8vl500iophlx8vhud64t https://bteam-developer.instatus.com/incident/cmq1s8vl500iophlx8vhud64t System Incident โ€“ Cloudflare Outage Impacting bTeam's Service Type: Incident Duration: 2 hours and 58 minutes Affected Components: Image.Random, Developer Portal, Lockscreen Note Backend, bSearch, , , Home Center for IoT devices, MyForum โ†’ My TTKT โ†’ Nov 18, 11:52:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 18, 14:23:40 GMT+0 - Identified - They are continuing to investigate this issue. Nov 18, 14:23:41 GMT+0 - Identified - Users may have experienced: * Failed logins * Slow or failed API requests * Temporary connectivity errors Nov 18, 14:46:23 GMT+0 - Monitoring - Cloudflare has identified the root cause and is rolling out a fix. Some login sessions in MyForum SSO may still be affected during this period. Nov 18, 14:46:47 GMT+0 - Monitoring - Cloudflare has reported partial recovery for Access and WARP. bTeam's services are gradually stabilizing, but some users may still see intermittent connection errors or slow loading. **Our team is monitoring closely and will provide updates as recovery continues.** Nov 18, 14:47:59 GMT+0 - Monitoring - Cloudflare has restored functionality for their dashboard services. Nov 18, 14:48:42 GMT+0 - Monitoring - ### ๐Ÿ™ **Thank You for Your Patience** We will continue to track Cloudflareโ€™s updates and confirm full restoration as soon as all systems are stable. Nov 18, 14:50:17 GMT+0 - Resolved - Cloudflare has implemented a fix and reports that the incident is now resolved. Our services are stabilizing. We are monitoring to ensure everything is fully back to normal. Nov 18, 14:50:55 GMT+0 - Resolved - The issue has been resolved. This incident is now marked as _Done_. Type: Incident

Duration: 2 hours and 58 minutes

Affected Components: , , , , , ,

<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>11:52:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:23:40</var> GMT+0</small><br><strong>Identified</strong> - They are continuing to investigate this issue..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:23:41</var> GMT+0</small><br><strong>Identified</strong> - Users may have experienced: * Failed logins * Slow or failed API requests * Temporary connectivity errors.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:46:23</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare has identified the root cause and is rolling out a fix. Some login sessions in MyForum SSO may still be affected during this period..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:46:47</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare has reported partial recovery for Access and WARP. bTeam's services are gradually stabilizing, but some users may still see intermittent connection errors or slow loading. **Our team is monitoring closely and will provide updates as recovery continues.**.</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:47:59</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare has restored functionality for their dashboard services..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:48:42</var> GMT+0</small><br><strong>Monitoring</strong> - ### ๐Ÿ™ **Thank You for Your Patience** We will continue to track Cloudflareโ€™s updates and confirm full restoration as soon as all systems are stable..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:50:17</var> GMT+0</small><br><strong>Resolved</strong> - Cloudflare has implemented a fix and reports that the incident is now resolved. Our services are stabilizing. We are monitoring to ensure everything is fully back to normal..</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:50:55</var> GMT+0</small><br><strong>Resolved</strong> - The issue has been resolved. This incident is now marked as _Done_..</p> ]]> Tue, 18 Nov 2025 11:52:00 +0000 https://bteam-developer.instatus.com/incident/cmi4mwdl5000k8f7uqa5vav5q https://bteam-developer.instatus.com/incident/cmi4mwdl5000k8f7uqa5vav5q Cannot login to My TTKT Type: Incident Duration: 18 hours and 34 minutes Affected Components: , My TTKT โ†’ Nov 16, 04:51:30 GMT+0 - Resolved - # **Postmortem: My TTKT Service Outage** **Date of Incident:** _Nov 11, 2025_ **Duration:** 1 hour 43 minutes **Service Impacted:** My TTKT **Timezone:** **All times in UTC** --- ## **1\. Summary** My TTKT experienced a global outage beginning on November 11, 2025, caused by a compromised latest update that contained a backdoor. An attacker was able to use this backdoor to upload a malicious shell and encrypt core middleware source files, causing the service to become unavailable. Despite the breach, user data remained safe, as all data is stored on the separate MyForum service, which follows stricter update verification processes under bTeam Developer rules. The incident was fully resolved on **November 12, 2025**, at **5:09 AM** after restoring the last stable configuration and removing all malicious artifacts. --- ## **2\. Impact** * **Global outage:** All users worldwide are unable to access My TTKT via website, app, and custom API * **Duration:** 1 hour 43 minutes * **Data integrity:** No loss or corruption. MyForum hosting protects all stored user content and personal information. * **Ops impact:** Required rollback to stable version and removal of malicious files --- ## **3\. Root Cause** A release deployed by the VDJGO! team bypassed rigorous security and code-review procedures. This version contained a backdoor that allowed an attacker to: * Gain unauthorized access to the middleware server * Upload a malicious shell * Encrypt core source files, disabling system functionality The insufficient review process allowed the compromised version to be deployed into production. --- ## **4\. Timeline (UTC)** **10:36 AM โ€” Investigating** Service issues detected; the team begins an investigation. **12:41 PM โ€” Identified** Problems traced to the latest update. Rollback initialized. **12:43 PM โ€” Monitoring** Rollback completed; system behavior being observed. **12:44 PM โ€” Update** Fix deployed. Some users (mostly in ideographic-language regions) still report data issues. **12:45 PM โ€” Update** Primary issues resolved; technical report preparation begins. **5:09 AM (Next Day) โ€” Resolved** Incident fully resolved. System restored and validated. **Total outage duration:** 1 hour 43 minutes. --- ## **5\. Recovery Actions Taken** * Restored the system to the latest verified stable configuration * Rolled back the compromised update * Cleared caches and removed the attacker-uploaded shell * Verified full server integrity * Confirmed that MyForum-hosted data was unaffected, personal user data and secret variable is okay --- ## **6\. Preventive & Long-Term Action Items** ### **Immediate** * Enforce strict code audit and security scanning before any deployment * Strengthen mandatory review steps for VDJGO! updates ### **Near-Term** * Implement robust CI/CD validations: * Automated SAST * Dependency vulnerability checks * Backdoor/signature scanning ### **Long-Term** * Harden firewall rules and access controls * Deploy intrusion detection and anomaly monitoring * Introduce stricter deployment approval separation * Provide ongoing security training for engineering teams Nov 16, 04:51:41 GMT+0 - Postmortem - # **Postmortem: My TTKT Service Outage** **Date of Incident:** _Nov 11, 2025_ **Duration:** 1 hour 43 minutes **Service Impacted:** My TTKT **Timezone:** **All times in UTC** --- ## **1\. Summary** My TTKT experienced a global outage beginning on November 11, 2025, caused by a compromised latest update that contained a backdoor. An attacker was able to use this backdoor to upload a malicious shell and encrypt core middleware source files, causing the service to become unavailable. Despite the breach, user data remained safe, as all data is stored on the separate MyForum service, which follows stricter update verification processes under bTeam Developer rules. The incident was fully resolved on **November 12, 2025**, at **5:09 AM** after restoring the last stable configuration and removing all malicious artifacts. --- ## **2\. Impact** * **Global outage:** All users worldwide are unable to access My TTKT via website, app, and custom API * **Duration:** 1 hour 43 minutes * **Data integrity:** No loss or corruption. MyForum hosting protects all stored user content and personal information. * **Ops impact:** Required rollback to stable version and removal of malicious files --- ## **3\. Root Cause** A release deployed by the VDJGO! team bypassed rigorous security and code-review procedures. This version contained a backdoor that allowed an attacker to: * Gain unauthorized access to the middleware server * Upload a malicious shell * Encrypt core source files, disabling system functionality The insufficient review process allowed the compromised version to be deployed into production. --- ## **4\. Timeline (UTC)** **10:36 AM โ€” Investigating** Service issues detected; the team begins an investigation. **12:41 PM โ€” Identified** Problems traced to the latest update. Rollback initialized. **12:43 PM โ€” Monitoring** Rollback completed; system behavior being observed. **12:44 PM โ€” Update** Fix deployed. Some users (mostly in ideographic-language regions) still report data issues. **12:45 PM โ€” Update** Primary issues resolved; technical report preparation begins. **5:09 AM (Next Day) โ€” Resolved** Incident fully resolved. System restored and validated. **Total outage duration:** 1 hour 43 minutes. --- ## **5\. Recovery Actions Taken** * Restored the system to the latest verified stable configuration * Rolled back the compromised update * Cleared caches and removed the attacker-uploaded shell * Verified full server integrity * Confirmed that MyForum-hosted data was unaffected, personal user data and secret variable is okay --- ## **6\. Preventive & Long-Term Action Items** ### **Immediate** * Enforce strict code audit and security scanning before any deployment * Strengthen mandatory review steps for VDJGO! updates ### **Near-Term** * Implement robust CI/CD validations: * Automated SAST * Dependency vulnerability checks * Backdoor/signature scanning ### **Long-Term** * Harden firewall rules and access controls * Deploy intrusion detection and anomaly monitoring * Introduce stricter deployment approval separation * Provide ongoing security training for engineering teams Nov 11, 10:36:10 GMT+0 - Investigating - We are currently investigating this incident. Nov 11, 12:41:20 GMT+0 - Identified - We are continuing to work on a fix for this incident. Some issues occurred when we upgraded to the latest update. Rollback is in progress. Nov 11, 12:43:37 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Hopefully the rollback will get the system working again. Nov 11, 12:44:46 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Some users are reporting issues with their data, mainly in countries that use ideographic languages. Nov 11, 12:45:51 GMT+0 - Monitoring - Issues fixed. Detailed technical report will be published soon. We are continuing to investigate this incident. Nov 12, 05:09:45 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 18 hours and 34 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>04:51:30</var> GMT+0</small><br><strong>Resolved</strong> - # **Postmortem: My TTKT Service Outage** **Date of Incident:** _Nov 11, 2025_ **Duration:** 1 hour 43 minutes **Service Impacted:** My TTKT **Timezone:** **All times in UTC** --- ## **1\. Summary** My TTKT experienced a global outage beginning on November 11, 2025, caused by a compromised latest update that contained a backdoor. An attacker was able to use this backdoor to upload a malicious shell and encrypt core middleware source files, causing the service to become unavailable. Despite the breach, user data remained safe, as all data is stored on the separate MyForum service, which follows stricter update verification processes under bTeam Developer rules. The incident was fully resolved on **November 12, 2025**, at **5:09 AM** after restoring the last stable configuration and removing all malicious artifacts. --- ## **2\. Impact** * **Global outage:** All users worldwide are unable to access My TTKT via website, app, and custom API * **Duration:** 1 hour 43 minutes * **Data integrity:** No loss or corruption. MyForum hosting protects all stored user content and personal information. * **Ops impact:** Required rollback to stable version and removal of malicious files --- ## **3\. Root Cause** A release deployed by the VDJGO! team bypassed rigorous security and code-review procedures. This version contained a backdoor that allowed an attacker to: * Gain unauthorized access to the middleware server * Upload a malicious shell * Encrypt core source files, disabling system functionality The insufficient review process allowed the compromised version to be deployed into production. --- ## **4\. Timeline (UTC)** **10:36 AM โ€” Investigating** Service issues detected; the team begins an investigation. **12:41 PM โ€” Identified** Problems traced to the latest update. Rollback initialized. **12:43 PM โ€” Monitoring** Rollback completed; system behavior being observed. **12:44 PM โ€” Update** Fix deployed. Some users (mostly in ideographic-language regions) still report data issues. **12:45 PM โ€” Update** Primary issues resolved; technical report preparation begins. **5:09 AM (Next Day) โ€” Resolved** Incident fully resolved. System restored and validated. **Total outage duration:** 1 hour 43 minutes. --- ## **5\. Recovery Actions Taken** * Restored the system to the latest verified stable configuration * Rolled back the compromised update * Cleared caches and removed the attacker-uploaded shell * Verified full server integrity * Confirmed that MyForum-hosted data was unaffected, personal user data and secret variable is okay --- ## **6\. Preventive & Long-Term Action Items** ### **Immediate** * Enforce strict code audit and security scanning before any deployment * Strengthen mandatory review steps for VDJGO! updates ### **Near-Term** * Implement robust CI/CD validations: * Automated SAST * Dependency vulnerability checks * Backdoor/signature scanning ### **Long-Term** * Harden firewall rules and access controls * Deploy intrusion detection and anomaly monitoring * Introduce stricter deployment approval separation * Provide ongoing security training for engineering teams.</p> <p><small>Nov <var data-var='date'> 16</var>, <var data-var='time'>04:51:41</var> GMT+0</small><br><strong>Postmortem</strong> - # **Postmortem: My TTKT Service Outage** **Date of Incident:** _Nov 11, 2025_ **Duration:** 1 hour 43 minutes **Service Impacted:** My TTKT **Timezone:** **All times in UTC** --- ## **1\. Summary** My TTKT experienced a global outage beginning on November 11, 2025, caused by a compromised latest update that contained a backdoor. An attacker was able to use this backdoor to upload a malicious shell and encrypt core middleware source files, causing the service to become unavailable. Despite the breach, user data remained safe, as all data is stored on the separate MyForum service, which follows stricter update verification processes under bTeam Developer rules. The incident was fully resolved on **November 12, 2025**, at **5:09 AM** after restoring the last stable configuration and removing all malicious artifacts. --- ## **2\. Impact** * **Global outage:** All users worldwide are unable to access My TTKT via website, app, and custom API * **Duration:** 1 hour 43 minutes * **Data integrity:** No loss or corruption. MyForum hosting protects all stored user content and personal information. * **Ops impact:** Required rollback to stable version and removal of malicious files --- ## **3\. Root Cause** A release deployed by the VDJGO! team bypassed rigorous security and code-review procedures. This version contained a backdoor that allowed an attacker to: * Gain unauthorized access to the middleware server * Upload a malicious shell * Encrypt core source files, disabling system functionality The insufficient review process allowed the compromised version to be deployed into production. --- ## **4\. Timeline (UTC)** **10:36 AM โ€” Investigating** Service issues detected; the team begins an investigation. **12:41 PM โ€” Identified** Problems traced to the latest update. Rollback initialized. **12:43 PM โ€” Monitoring** Rollback completed; system behavior being observed. **12:44 PM โ€” Update** Fix deployed. Some users (mostly in ideographic-language regions) still report data issues. **12:45 PM โ€” Update** Primary issues resolved; technical report preparation begins. **5:09 AM (Next Day) โ€” Resolved** Incident fully resolved. System restored and validated. **Total outage duration:** 1 hour 43 minutes. --- ## **5\. Recovery Actions Taken** * Restored the system to the latest verified stable configuration * Rolled back the compromised update * Cleared caches and removed the attacker-uploaded shell * Verified full server integrity * Confirmed that MyForum-hosted data was unaffected, personal user data and secret variable is okay --- ## **6\. Preventive & Long-Term Action Items** ### **Immediate** * Enforce strict code audit and security scanning before any deployment * Strengthen mandatory review steps for VDJGO! updates ### **Near-Term** * Implement robust CI/CD validations: * Automated SAST * Dependency vulnerability checks * Backdoor/signature scanning ### **Long-Term** * Harden firewall rules and access controls * Deploy intrusion detection and anomaly monitoring * Introduce stricter deployment approval separation * Provide ongoing security training for engineering teams.</p> <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>10:36:10</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>12:41:20</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Some issues occurred when we upgraded to the latest update. Rollback is in progress..</p> <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>12:43:37</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Hopefully the rollback will get the system working again..</p> <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>12:44:46</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Some users are reporting issues with their data, mainly in countries that use ideographic languages..</p> <p><small>Nov <var data-var='date'> 11</var>, <var data-var='time'>12:45:51</var> GMT+0</small><br><strong>Monitoring</strong> - Issues fixed. Detailed technical report will be published soon. We are continuing to investigate this incident. .</p> <p><small>Nov <var data-var='date'> 12</var>, <var data-var='time'>05:09:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 11 Nov 2025 10:36:10 +0000 https://bteam-developer.instatus.com/incident/cmhufrefy04ecus5hw4l375dl https://bteam-developer.instatus.com/incident/cmhufrefy04ecus5hw4l375dl We are planning for a scheduled maintenance during that time. Type: Maintenance Duration: 1 hour Affected Components: , MyForum โ†’ Oct 20, 02:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Oct 20, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 20, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Mon, 20 Oct 2025 02:00:00 +0000 https://bteam-developer.instatus.com/maintenance/cmgx4optx00ab9dxtokgjks6c https://bteam-developer.instatus.com/maintenance/cmgx4optx00ab9dxtokgjks6c MyForum under construction Type: Incident Duration: 30 minutes Sep 29, 15:49:01 GMT+0 - Resolved - This incident has been resolved. Sep 29, 15:19:21 GMT+0 - Investigating - We're updating some MyForum features! Type: Incident

Duration: 30 minutes

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>15:49:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>15:19:21</var> GMT+0</small><br><strong>Investigating</strong> - We're updating some MyForum features!.</p> ]]> Fri, 29 Sep 2023 15:19:21 +0000 https://bteam-developer.instatus.com/incident/cln4r1r3e378517bhonppgz8y0n https://bteam-developer.instatus.com/incident/cln4r1r3e378517bhonppgz8y0n MyForum under construction Type: Incident Duration: 44 minutes Affected Components: , MyForum โ†’ Jul 15, 13:24:59 GMT+0 - Investigating - Important notice: MyForum will be closed from 07/14/2023 at 13:30 UTC to update the new interface and new feature Jul 15, 14:09:28 GMT+0 - Resolved - ![](https://i.imgur.com/Kz2XDue.jpg) ![](https://i.imgur.com/mx2tRfK.jpg) ![](https://i.imgur.com/SG9r5gu.jpg) We're back, now you can post your weekend trip photos and share them with your friends or simply chat with your parents Type: Incident

Duration: 44 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>13:24:59</var> GMT+0</small><br><strong>Investigating</strong> - Important notice: MyForum will be closed from 07/14/2023 at 13:30 UTC to update the new interface and new feature.</p> <p><small>Jul <var data-var='date'> 15</var>, <var data-var='time'>14:09:28</var> GMT+0</small><br><strong>Resolved</strong> - ![](https://i.imgur.com/Kz2XDue.jpg) ![](https://i.imgur.com/mx2tRfK.jpg) ![](https://i.imgur.com/SG9r5gu.jpg) We're back, now you can post your weekend trip photos and share them with your friends or simply chat with your parents.</p> ]]> Sat, 15 Jul 2023 13:24:59 +0000 https://bteam-developer.instatus.com/incident/clk41ii6t210058bioanc0k6g1i https://bteam-developer.instatus.com/incident/clk41ii6t210058bioanc0k6g1i MyForum has an urgent problem Type: Incident Duration: 1 day, 19 hours and 32 minutes Affected Components: bTeam's WebAnalysics, Developer Portal, Lockscreen Note Backend, , , , Image.Random, bSearch, Home Center for IoT devices, , bTeam CDN โ†’ MyForum โ†’ bTeam Website โ†’ My TTKT โ†’ May 6, 09:58:32 GMT+0 - Investigating - We are currently investigating this incident. May 6, 10:11:29 GMT+0 - Investigating - We are currently investigating this incident. Don't worry, your data is safe! The server is currently having a configuration error, we will update it continuously. May 8, 05:30:23 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 8, 05:30:55 GMT+0 - Resolved - This incident has been resolved. May 8, 05:31:11 GMT+0 - Resolved - This incident has been resolved. May 8, 05:27:53 GMT+0 - Identified - We are continuing to work on a fix for this incident. May 8, 05:33:19 GMT+0 - Resolved - This incident has been resolved. All bTeam's services have been working stably. We did a full server error check on every service and everything is fine! May 8, 05:29:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. May 8, 05:31:56 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 19 hours and 32 minutes

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

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>09:58:32</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>10:11:29</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Don't worry, your data is safe! The server is currently having a configuration error, we will update it continuously..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:30:23</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:30:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:31:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:27:53</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:33:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. All bTeam's services have been working stably. We did a full server error check on every service and everything is fine! .</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:29:14</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>05:31:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 6 May 2023 09:58:32 +0000 https://bteam-developer.instatus.com/incident/clhbtbdhi161897h6njd1nk6bs2 https://bteam-developer.instatus.com/incident/clhbtbdhi161897h6njd1nk6bs2 MyForum is getting DDoS Type: Incident Duration: 8 minutes Affected Components: bSearch, , , Image.Random, bTeam's WebAnalysics, Home Center for IoT devices, Developer Portal, , Lockscreen Note Backend, Internal Git Programming Space (GitHub.com) , , MyForum โ†’ bTeam Website โ†’ My TTKT โ†’ bTeam CDN โ†’ Dec 2, 13:56:46 GMT+0 - Investigating - **MyForum is getting DDoS** We are currently investigating this incident. The accident has caused our server to go down. We are working to bring this service back ASAP! Your data is always safe! Dec 2, 13:58:21 GMT+0 - Identified - **MyForum is getting DDoS** We are continuing to work on a fix for this incident. The accident has caused our server to go down. We are working to bring this service back ASAP! Your data is always safe! We'll update our status here. Dec 2, 13:59:36 GMT+0 - Identified - ### OUR WEBSITE STATUS **We just encountered a massive DDOS attack** This site is currently not available. Please try again later. The attack has resulted in a decrease in server performance, we will notify you if there are any changes! In addition, other services such as MyForum Facts, ShortMedia and LIVE on MyForum are also not accessible. We need to investigate the damage. Your data is always safe! **Robots are maintaining this page! Please return here later!** We're sorry for the inconvenience, but this is necessary to ensure the stability of the system and the safety of your information. Dec 2, 14:03:57 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Dec 2, 14:04:45 GMT+0 - Resolved - ### We just resolved the issue! We're so glad to tell you that #MyForum is UP!!! Now you can share your status, chat with your friend, and more with our mobile app and website! Dec 2, 14:15:00 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 8 minutes

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

<p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>13:56:46</var> GMT+0</small><br><strong>Investigating</strong> - **MyForum is getting DDoS** We are currently investigating this incident. The accident has caused our server to go down. We are working to bring this service back ASAP! Your data is always safe!.</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>13:58:21</var> GMT+0</small><br><strong>Identified</strong> - **MyForum is getting DDoS** We are continuing to work on a fix for this incident. The accident has caused our server to go down. We are working to bring this service back ASAP! Your data is always safe! We'll update our status here..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>13:59:36</var> GMT+0</small><br><strong>Identified</strong> - ### OUR WEBSITE STATUS **We just encountered a massive DDOS attack** This site is currently not available. Please try again later. The attack has resulted in a decrease in server performance, we will notify you if there are any changes! In addition, other services such as MyForum Facts, ShortMedia and LIVE on MyForum are also not accessible. We need to investigate the damage. Your data is always safe! **Robots are maintaining this page! Please return here later!** We're sorry for the inconvenience, but this is necessary to ensure the stability of the system and the safety of your information..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>14:03:57</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>14:04:45</var> GMT+0</small><br><strong>Resolved</strong> - ### We just resolved the issue! We're so glad to tell you that #MyForum is UP!!! Now you can share your status, chat with your friend, and more with our mobile app and website!.</p> <p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Fri, 2 Dec 2022 13:56:46 +0000 https://bteam-developer.instatus.com/incident/clb6kkoxx144253itoe7oyc3lj5 https://bteam-developer.instatus.com/incident/clb6kkoxx144253itoe7oyc3lj5 Some users in South America and West Asia cannot access Type: Incident Duration: 1 day, 23 hours and 25 minutes Affected Components: , MyForum โ†’ Jul 31, 05:03:51 GMT+0 - Investigating - We are currently investigating this incident. Jul 31, 05:05:10 GMT+0 - Identified - We found an issue with the Shift8 CDN that resulted in data sync errors. We are continuing to work on a fix for this incident. Jul 31, 05:08:35 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. We found an issue with the Shift8 CDN that resulted in data sync errors Warning: Some post data from users in South America and West Asia may be lost, trying to recover user data ๐Ÿ‘ Connection: The connection is stable again, you can now post pictures of your weekend getaway ๐Ÿ˜Š ๐Ÿ—บ or your new homemade chocolate cake! ๐Ÿ˜ Jul 31, 05:10:35 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. We found an issue with the Shift8 CDN that resulted in data sync errors IMPORTANT: This fix maybe take more times! We're fixing it to return your posts as soon as possible! ๐Ÿค Warning: Some post data from users in South America and West Asia may be lost, trying to recover user data ๐Ÿ‘ Connection: The connection is stable again, you can now post pictures of your weekend getaway ๐Ÿ˜Š ๐Ÿ—บ or your new homemade chocolate cake! ๐Ÿ˜ Aug 2, 04:28:29 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 1 day, 23 hours and 25 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:03:51</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:05:10</var> GMT+0</small><br><strong>Identified</strong> - We found an issue with the Shift8 CDN that resulted in data sync errors. We are continuing to work on a fix for this incident..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:08:35</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result. We found an issue with the Shift8 CDN that resulted in data sync errors Warning: Some post data from users in South America and West Asia may be lost, trying to recover user data ๐Ÿ‘ Connection: The connection is stable again, you can now post pictures of your weekend getaway ๐Ÿ˜Š ๐Ÿ—บ or your new homemade chocolate cake! ๐Ÿ˜.</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:10:35</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result. We found an issue with the Shift8 CDN that resulted in data sync errors IMPORTANT: This fix maybe take more times! We're fixing it to return your posts as soon as possible! ๐Ÿค Warning: Some post data from users in South America and West Asia may be lost, trying to recover user data ๐Ÿ‘ Connection: The connection is stable again, you can now post pictures of your weekend getaway ๐Ÿ˜Š ๐Ÿ—บ or your new homemade chocolate cake! ๐Ÿ˜.</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>04:28:29</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Sun, 31 Jul 2022 05:03:51 +0000 https://bteam-developer.instatus.com/incident/cl68uxoyt2267vvmxqreogm6b https://bteam-developer.instatus.com/incident/cl68uxoyt2267vvmxqreogm6b Migrating to MyForum Type: Incident Duration: 1 day, 23 hours and 27 minutes Jul 31, 05:02:36 GMT+0 - Identified - Please prepare everything to migrate to MyForum, you just need to go to the app or website, our server will guide you through the steps of data migration through the new service. You'll still be using the old apps until the end of August 2022, and the apps will redirect themselves to new, easier-to-use software! Jul 31, 05:12:00 GMT+0 - Identified - Please prepare everything to migrate to MyForum, you just need to go to the app or website, our server will guide you through the steps of data migration through the new service. You'll still be using the old apps until the end of August 2022, and the apps will redirect themselves to new, easier-to-use software! WE'RE TERMINATING ChatRoom and DoCommunication now! Aug 2, 04:29:10 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 1 day, 23 hours and 27 minutes

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:02:36</var> GMT+0</small><br><strong>Identified</strong> - Please prepare everything to migrate to MyForum, you just need to go to the app or website, our server will guide you through the steps of data migration through the new service. You'll still be using the old apps until the end of August 2022, and the apps will redirect themselves to new, easier-to-use software!.</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>05:12:00</var> GMT+0</small><br><strong>Identified</strong> - Please prepare everything to migrate to MyForum, you just need to go to the app or website, our server will guide you through the steps of data migration through the new service. You'll still be using the old apps until the end of August 2022, and the apps will redirect themselves to new, easier-to-use software! WE'RE TERMINATING ChatRoom and DoCommunication now!.</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>04:29:10</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Sun, 31 Jul 2022 05:02:36 +0000 https://bteam-developer.instatus.com/incident/cl68uw3an2461w8mxrj5633el https://bteam-developer.instatus.com/incident/cl68uw3an2461w8mxrj5633el Update for iKnowledge Type: Incident Duration: 3 hours and 1 minute Affected Components: bSearch, , Image.Random, , bTeam's WebAnalysics, Home Center for IoT devices, Developer Portal, Lockscreen Note Backend, , bTeam Website โ†’ bTeam CDN โ†’ My TTKT โ†’ Apr 8, 10:32:00 GMT+0 - Resolved - We just resolved the issue! Apr 8, 13:32:33 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 3 hours and 1 minute

Affected Components: , , , , , , , ,

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>10:32:00</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>13:32:33</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Fri, 8 Apr 2022 13:32:33 +0000 https://bteam-developer.instatus.com/incident/cl1qh012u643723ftncv7hu98dy https://bteam-developer.instatus.com/incident/cl1qh012u643723ftncv7hu98dy bVOD: Massive DDOS attack disrupts the system Type: Incident Duration: 1 day Affected Components: bSearch, , Image.Random, , bTeam's WebAnalysics, Home Center for IoT devices, Developer Portal, Lockscreen Note Backend, , bTeam Website โ†’ bTeam CDN โ†’ My TTKT โ†’ Apr 6, 13:34:00 GMT+0 - Identified - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers" Apr 7, 13:34:00 GMT+0 - Resolved - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers" Apr 4, 13:34:00 GMT+0 - Monitoring - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers" Apr 5, 13:34:00 GMT+0 - Resolved - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers" Type: Incident

Duration: 1 day

Affected Components: , , , , , , , ,

<p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>13:34:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers".</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:34:00</var> GMT+0</small><br><strong>Resolved</strong> - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers".</p> <p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>13:34:00</var> GMT+0</small><br><strong>Monitoring</strong> - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers".</p> <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>13:34:00</var> GMT+0</small><br><strong>Resolved</strong> - We are currently investigating this incident. **Massive DDOS attack disrupts the system** Traffic is mainly from Russia and China, we are continuing to create "DDOS barriers".</p> ]]> Mon, 4 Apr 2022 13:34:00 +0000 https://bteam-developer.instatus.com/incident/cl1qh4ovh649439ftncf4xi8bin https://bteam-developer.instatus.com/incident/cl1qh4ovh649439ftncf4xi8bin Maintain Video Embed API application on a schedule Type: Incident Duration: 14 days and 9 hours Feb 12, 03:46:20 GMT+0 - Identified - We are continuing to work on a fix for this incident. `bVOD` Feb 26, 12:45:58 GMT+0 - Resolved - We just resolved the issue! Feb 12, 05:46:00 GMT+0 - Monitoring - We implemented a fix and currently monitoring the result. Type: Incident

Duration: 14 days and 9 hours

<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>03:46:20</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. `bVOD`.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>12:45:58</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>05:46:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and currently monitoring the result..</p> ]]> Sat, 12 Feb 2022 03:46:20 +0000 https://bteam-developer.instatus.com/incident/ckzjaso86498197e2ocg38rkfpv https://bteam-developer.instatus.com/incident/ckzjaso86498197e2ocg38rkfpv Update Services for Mobile App does not work correctly in US-West, Canada, and Australia Type: Incident Duration: 14 days, 9 hours and 5 minutes Feb 12, 03:41:04 GMT+0 - Investigating - We are currently investigating this incident. We had found an error in `System Config` file storage in the External Memory (SD Card) that can cause the app not to update correctly! Feel free if you are using a Samsung phone and update it via Galaxy App Store. We also published it on Amazon for another device as soon as possible! Feb 12, 04:41:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 26, 12:46:17 GMT+0 - Resolved - We just resolved the issue! Type: Incident

Duration: 14 days, 9 hours and 5 minutes

<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>03:41:04</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. We had found an error in `System Config` file storage in the External Memory (SD Card) that can cause the app not to update correctly! Feel free if you are using a Samsung phone and update it via Galaxy App Store. We also published it on Amazon for another device as soon as possible!.</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>04:41:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>12:46:17</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> ]]> Sat, 12 Feb 2022 03:41:04 +0000 https://bteam-developer.instatus.com/incident/ckzjalwxw493708e2ocrzx642jp https://bteam-developer.instatus.com/incident/ckzjalwxw493708e2ocrzx642jp Maintain DoCommunication application on a schedule Type: Incident Duration: 5 days, 10 hours and 51 minutes Affected Components: bSearch, , Image.Random, , bTeam's WebAnalysics, Home Center for IoT devices, Developer Portal, Lockscreen Note Backend, bTeam Website โ†’ bTeam CDN โ†’ Feb 6, 02:46:23 GMT+0 - Investigating - **Maintain DoCommunication application on a schedule (Company App)** Feb 11, 13:36:57 GMT+0 - Resolved - We just resolved the issue! Feb 6, 02:48:42 GMT+0 - Identified - We are continuing to work on a fix for this incident. Maintain DoCommunication application on a schedule Feb 6, 02:47:14 GMT+0 - Identified - Maintain DoCommunication application on a schedule Feb 6, 02:48:01 GMT+0 - Identified - Maintain DoCommunication application on a schedule Type: Incident

Duration: 5 days, 10 hours and 51 minutes

Affected Components: , , , , , , ,

<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:46:23</var> GMT+0</small><br><strong>Investigating</strong> - **Maintain DoCommunication application on a schedule (Company App)** .</p> <p><small>Feb <var data-var='date'> 11</var>, <var data-var='time'>13:36:57</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:48:42</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Maintain DoCommunication application on a schedule.</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:47:14</var> GMT+0</small><br><strong>Identified</strong> - Maintain DoCommunication application on a schedule.</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:48:01</var> GMT+0</small><br><strong>Identified</strong> - Maintain DoCommunication application on a schedule.</p> ]]> Sun, 6 Feb 2022 02:46:23 +0000 https://bteam-developer.instatus.com/incident/ckzao050621087ean4g3ed3pcc https://bteam-developer.instatus.com/incident/ckzao050621087ean4g3ed3pcc Time Sync (NTP Server) is currently down Type: Incident Duration: 2 minutes Feb 5, 14:55:15 GMT+0 - Resolved - We just resolved the issue! Feb 5, 14:53:03 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 2 minutes

<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>14:55:15</var> GMT+0</small><br><strong>Resolved</strong> - We just resolved the issue!.</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>14:53:03</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Sat, 5 Feb 2022 14:53:03 +0000 https://bteam-developer.instatus.com/incident/ckz9yiqk466679cynb2ydaxbih https://bteam-developer.instatus.com/incident/ckz9yiqk466679cynb2ydaxbih