No reviews yet. Be the first to share your experience!
Latest Posts
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
China Telecom LAX-SHA CN2 GIA partial circuits failure.
( All CN2 LAX customers are impacted. )
11,200
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
TYO Pro:
- NCP S3 submarine fiber cut again. Impact CTGnet backbone.
- Higher latency (bypass HKG.)
- No ETR.
LAX Pro:
- CN2 backbone local fiber cut in LA Downtown.
- Packet loss and congestion happening.
- ETR 14:00 UTC.
Please note:
DMIT does not own those fiber and we do not have control on China Telecom’s backbone.
All the fiber cuts above only impact the China Telecom network.
DMIT backbone is normal so far.
We will keep watch on it and chase for update from China Telecom.
12,500
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
HKG Pro:
We are currently adjusting internet routing. Some ISPs have excessively long routing convergence times, leading to detours and blackouts. Thank you for your patience.
9,930
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
LAX EB:
We’ve notice the jitter issue during the peak hours. DMIT is working with upstream and CUG to resolve this matter. It should be resolved sooner.
TYO Pro:
We’ve switched major upstream (GSL) of TYO Pro to Cloudflare.
There is one prefixe has issue on CTGnet routing. We’ve already reported it to CTGnet.
5,730
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
📷 Photo
Current Outage Notification:
1. CTGnet Tokyo <> Shanghai CN2 GIA's NCP submarine cable remains disrupted and has not yet been restored.
2. GSL Tokyo <> Hong Kong submarine cable is completely out of service.
3. GSL Taipei <> Tokyo submarine cable is partially out of service.
4. GSL Hong Kong <> Taipei submarine cable is partially out of service.
5. GSL LUMEN Hong Kong is offline (or GSL Hong Kong intranet failure), causing CMI's DDoS scrubbing routes to be rerouted via the United States.
22,300
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
DMIT NOC and the management team have gained a thorough understanding of the current network situation. For security reasons, DMIT will temporarily refrain from sharing further details here.
DMIT is currently actively addressing the situation.
7,350
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
We have lost one of our redundant connections to China Unicom's Los Angeles router. Due to overload, we have temporarily removed the route from AS9929 to AS4134 on Eyeball routing.
This will be restored once China Unicom completes repairs.
6,850
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
We have lost one of our redundant connections to China Unicom's Los Angeles router. Due to overload, we have temporarily removed the route from AS9929 to AS4134 on Eyeball routing. This will be restored once China Unicom completes repairs.
7,960
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
LAX. EB:
Observed China Unicom AS10099-9929 latency and packet loss increases.
We've reached vendors about this matter.
DMIT both circuits with China Unicom are both in good conditions.
Based on the following observation, we thought that it could be cable fault in Unicom's network. It leads to China Unicom AS10099-9929 loss capacity, which leads to U. S. -> China direction congested.
• LAX. Pro has not been impacted;
• LAX. Pro shares inbound with LAX. EB ( China Unicom -> DMIT directions. )
• All China Unicom customers in Los Angeles are impacted.
13,700
0
0
/var/log/DMIT-NOC.log
May 19, 2026, 05:53 PM
CTGnet reply due to NCP cable fault. The traffic between Tokyo and Shanghai is now bypassing Hong Kong.
10,600
0
0
/var/log/DMIT-NOC.log
May 4, 2026, 07:56 PM
📢 DMIT Payment System Upgrade & Security Enhancements
To provide a safer and more convenient payment experience, DMIT has officially implemented a new PCI-compliant Stripe payment gateway.
🛡️ Why the change? (PCI Security Standards) To meet strict security requirements:
1. All payment info must be processed via a PCI DSS compliant gateway.
2. No sensitive card data is stored locally.
3. Transmission and storage must be fully encrypted.
Our new Stripe integration meets all these standards. All credit card and alternative payment inputs are now handled directly within Stripe's secure environment.
✨ What’s New?
- Enhanced Data Protection: Higher security standards for your peace of mind.
- New Payment Methods: We now support Apple Pay, Google Pay, and Cash App, alongside traditional credit cards.
⚠️ Important Notice Regarding Saved Cards As part of this transition to a secure architecture, we have removed all previously stored payment methods from Stripe and card basic info from WHMCS (we never stored sensitive card data). Please note that the old card management page is no longer available.
💳 How to Add Your New Payment Method
Method 1: During Checkout Select "Credit Card & Others" at checkout. You can add a new card or use one of the newly supported digital wallets. All info will be securely saved via the new gateway.
Method 2: Via Client Area You can add or update cards anytime via the new management interface:
Log in to your account.
- Go to "Billing".
- Select the "Manage Credit Card" tab.
🔗 Direct Link: https://www.dmit.io/index.php?m=stripe_next_cards
Thank you for your understanding and cooperation as we work to provide a more secure service experience.
4,330
/var/log/DMIT-NOC.log
May 4, 2026, 07:56 PM
📢 DMIT Payment System Upgrade & Security Enhancements To provide a safer and more convenient payment experience, DMIT has officially implemented a new PCI-compliant Stripe payment gateway. 🛡️ Why the change? (PCI Security Standards) To meet strict security…
5,080
0
0
/var/log/DMIT-NOC.log
May 4, 2026, 07:56 PM
HKG router config emergency maintenance in next hour.
May have short time detour, or blackout.
Done
6,360
0
0
/var/log/DMIT-NOC.log
Apr 18, 2026, 03:15 PM
DMIT observed multi-vector DDoS attack since yesterday towards to all our prefixes, including HKG, TYO and LAX.
You might experience some packet loss in sudden before the DDoS mitigation take effect.
From detection, detour to mitigation start, it might takes up to 1.5s.
We are applying a network changes to fast up the mitigation reponse time.
Internet Packet loss:
DMIT uses GSL as one of IP Transit (Not major) in Los Angeles.
But we heard there are some over Tbps attack towards to other GSL client today which made other GSL client (like DMIT) also impacted.
DMIT will keep monitoring and trying our best to serve your business.
4,580
0
0
/var/log/DMIT-NOC.log
Apr 9, 2026, 09:48 PM
Update:
LAX:
IPv4 sessions are restored.
Remaining issue:
- Both interface is not well configured due to CTG internal mistake.
- The BGP session is mis configured due to the multi-party miscommunication. DMIT <> CTG <> CT-Group.
HKG:
The new type of DDoS is on-going. The filter is working as expected.
Mitigation facility repairing work is on track.
The report will be ready once everything is fully resolved.
As so far, the serivce is still within SLA.
4,710
0
0
/var/log/DMIT-NOC.log
Apr 9, 2026, 09:48 PM
DMIT Network Incident Report: LAX & HKG
This is the last update until there is another major event needs to be updated.
Here is the combined technical postmortem regarding the recent network instability.
🇺🇸 LAX CN2 GIA Incident
Current Status: All immediate mitigations applied. Final correction from CTG is pending due to the China-wide "Network Freeze" (ending Dec 15).
1. Root Cause: Prefix Limit Exceeded
The Mismatch: DMIT ordered a 1k prefix-limit, but the provider (CTG) left it at the default 300. This parameter is non-testable after service delivery, so we trusted the configuration.
The Trigger: Two clients increased route announcements + multiple DDoS RTBH routes pushed the count over 300.
The Result: AS4809 (CN2) immediately idled the BGP session upon exceeding the limit.
2. Why did failover result in packet loss?
Design: The redundant session (CoreSite) remained UP as designed (filtering DDoS routes to save prefix space).
The Critical Failure: Provider LACP Misconfiguration. CTG configured our link aggregation as a single interface capacity, ignoring our multiple physical 10G connections.
Impact: When traffic shifted to CoreSite, it exceeded the logical 10G cap, causing severe congestion and packet loss despite physical capacity being available.
3. Why the long recovery?
Administration: Due to the "Network Freeze," router CLI access is suspended.
Approval: CTA/CTG required emergency access approval from the Group level. Since it was after-hours in China, getting this authorization took significant time.
================
🇭🇰 HKG Incident
Current Status: 99.9% of traffic is successfully filtered. Active monitoring in place. 10Mpps ongoing.
1. Root Cause: "Carpet Bombing"
Attack Type: A massive Carpet Bombing attack targeted 3 specific subnets.
Vectors: Mixed volume of TCP-SYN, TCP-ACK (Zero/Empty), SYN-ACK, TCP Null, FIN, RST.
2. Why did mitigation fail initially?
The Leak: A combination of misconfigured detour rules and a hardware fault caused traffic to bypass local scrubbers. Malicious traffic entered directly via the backbone (LAX IP Transit).
The "Red Herring": We initially focused on refining rules, not realizing the mitigation equipment itself had a hardware/software fault. This misled our diagnosis and delayed the fix.
3. Resource Contention The concurrent critical failure in LAX required non-stop coordination, splitting our engineering resources and inevitably slowing down the HKG diagnosis.
🛡️ Future Prevention & Commitment
Stricter Auditing: We will implement an extra layer to manually review every text field on vendor orders to ensure delivered configurations (like Prefix Limits and LACP speeds) match our requirements perfectly.
The Reality: DDoS vectors evolve rapidly. While we cannot guarantee zero incidents, DMIT commits to using every resource to maintain stability and protect your business at reasonable costs.
================
Reimbursement: All services no matter location and network profile will have traffic reset on today, and everything an extra chance for free to reset the traffic before May 2026. (Deliver in the future by the website feature.)
