bTeam Developer - Notice history

100% - uptime

Developer Portal - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.59%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025
100% - uptime

Image.Random - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.59%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

bTeam's WebAnalysics - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

bSearch - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.59%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025
100% - uptime
100% - uptime

MyForum SSO - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

MyForum Feed RSS - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

Dev SDK on MyForum (deprecated) - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

MyForum Web - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

bTeam Meet Now - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025
100% - uptime

Home Center for IoT devices - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.59%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

Lockscreen Note Backend - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 99.59%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025
100% - uptime

App - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%
Oct 2025
Nov 2025
Dec 2025

Internal Git Programming Space (GitHub.com) - Operational

Notice history

Dec 2025

No notices reported this month

Nov 2025

System Incident – Cloudflare Outage Impacting bTeam's Service
  • Update
    Update

    The issue has been resolved. This incident is now marked as Done.

  • Resolved
    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.

  • Update
    Update

    🙏 Thank You for Your Patience

    We will continue to track Cloudflare’s updates and confirm full restoration as soon as all systems are stable.

  • Update
    Update

    Cloudflare has restored functionality for their dashboard services.

  • Update
    Update

    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.

  • Monitoring
    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.

  • Update
    Update

    Users may have experienced:

    • Failed logins

    • Slow or failed API requests

    • Temporary connectivity errors

  • Identified
    Identified

    They are continuing to investigate this issue.

  • Investigating
    Investigating
    We are currently investigating this incident.
Cannot login to My TTKT
  • Postmortem
    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

  • Update
    Update

    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

  • Resolved
    Resolved
    This incident has been resolved.
  • Update
    Update

    Issues fixed. Detailed technical report will be published soon. We are continuing to investigate this incident.

  • Update
    Update

    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.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. Hopefully the rollback will get the system working again.

  • Identified
    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.

  • Investigating
    Investigating
    We are currently investigating this incident.

Oct 2025 to Dec 2025

Next