For Owner of LAX.Pro Opt IP and LAX.Pro:
DMIT intends to give the whole Pro series the best experience. We should no longer be limited to providing looks attractive "Bi-Di CN2" to customers who have demand for China routing.
Our mission is to offer a practical product. So, the Optimized premium routing will be merged in to premium routing. The premium routing will have best China connection.
The route from DMIT to China will remain in CN2 GIA.
DMIT will only perform the optimize on the route from China to DMIT, just like the Optimized Routing.
The jitter and packet loss of CN2 for most users comes from the circuit below:
AS4134 Backbone Nanjing > AS4809 Nanjing (All eastern China CT Users, except Shanghai): It has limited capacity and high delay on attack response.
AS4837 Backbone > AS4809 Backbone (All China Unicom Users): Limited Capacity and AS4837 have no RTBH BGP community which means the attack is unable to be stopped by CT.
The changes on the package:
The route Opt IP will become the same as the normal Premium routing.
The Opt IP will be renamed to extra IP.
These changes will proceed in October 2021.
Please do not hesitate to contact with us any questions.
DMIT intends to give the whole Pro series the best experience. We should no longer be limited to providing looks attractive "Bi-Di CN2" to customers who have demand for China routing.
Our mission is to offer a practical product. So, the Optimized premium routing will be merged in to premium routing. The premium routing will have best China connection.
The route from DMIT to China will remain in CN2 GIA.
DMIT will only perform the optimize on the route from China to DMIT, just like the Optimized Routing.
The jitter and packet loss of CN2 for most users comes from the circuit below:
AS4134 Backbone Nanjing > AS4809 Nanjing (All eastern China CT Users, except Shanghai): It has limited capacity and high delay on attack response.
AS4837 Backbone > AS4809 Backbone (All China Unicom Users): Limited Capacity and AS4837 have no RTBH BGP community which means the attack is unable to be stopped by CT.
The changes on the package:
The route Opt IP will become the same as the normal Premium routing.
The Opt IP will be renamed to extra IP.
These changes will proceed in October 2021.
Please do not hesitate to contact with us any questions.
TOS Update:
https://www.dmit.io/pages/tos
3. ACCOUNT MANAGEMENT
3.8 DMIT system will try to identify the natural person/legal person during the account registration. These accounts will share the same limitations, such as refund, IP replacement, promotions policy, and affiliate program if we are sure that your account is registered by the same natural person/legal person who already has had an account or accounts in DMIT.
https://www.dmit.io/pages/tos
3. ACCOUNT MANAGEMENT
3.8 DMIT system will try to identify the natural person/legal person during the account registration. These accounts will share the same limitations, such as refund, IP replacement, promotions policy, and affiliate program if we are sure that your account is registered by the same natural person/legal person who already has had an account or accounts in DMIT.
tail -f /var/log/DMIT.log
TOS Update: https://www.dmit.io/pages/tos 3. ACCOUNT MANAGEMENT 3.8 DMIT system will try to identify the natural person/legal person during the account registration. These accounts will share the same limitations, such as refund, IP replacement, promotions…
Minor changes.
alternative speaking:
The below scenario will be limited:
1. using the new account(s) to place orders and use your own aff link.
2. be banned after abuse usage, then creating a new account.
3. using multiple account(s) against the once per account promotion policy.
4. using multiple account(s) against the refund policy.
alternative speaking:
The below scenario will be limited:
1. using the new account(s) to place orders and use your own aff link.
2. be banned after abuse usage, then creating a new account.
3. using multiple account(s) against the once per account promotion policy.
4. using multiple account(s) against the refund policy.
Maintenance notice
Location: LAX
Status: Planing
Description:
1. Upgrade Core Router system to avoid knew secure issues.
2. Backbone Connection with HKG and TYO
3. Perform network configuration standardized for future functions.
Impact:
1. Unstable network connection;
2. DMIT.io might be affected at the same time.
3. Some premium IP Transit routes cannot be restored immediately.
Date: between Septt 11 ~ Sept. 13, 2021.
Time: 2PM ~ 10PM Eastern.
Duration: up to 8hrs.
Location: LAX
Status: Planing
Description:
1. Upgrade Core Router system to avoid knew secure issues.
2. Backbone Connection with HKG and TYO
3. Perform network configuration standardized for future functions.
Impact:
1. Unstable network connection;
2. DMIT.io might be affected at the same time.
3. Some premium IP Transit routes cannot be restored immediately.
Date: between Septt 11 ~ Sept. 13, 2021.
Time: 2PM ~ 10PM Eastern.
Duration: up to 8hrs.
tail -f /var/log/DMIT.log pinned «Maintenance notice Location: LAX Status: Planing Description: 1. Upgrade Core Router system to avoid knew secure issues. 2. Backbone Connection with HKG and TYO 3. Perform network configuration standardized for future functions. Impact: 1. Unstable network…»
tail -f /var/log/DMIT.log
Maintenance notice Location: LAX Status: Planing Description: 1. Upgrade Core Router system to avoid knew secure issues. 2. Backbone Connection with HKG and TYO 3. Perform network configuration standardized for future functions. Impact: 1. Unstable network…
Step 3 has been completed.
Step 2 is in progress.
Step 1 will be performed soon once we received the firmware from Jtac.
Step 2 is in progress.
Step 1 will be performed soon once we received the firmware from Jtac.
tail -f /var/log/DMIT.log
Routing Engine upgrade in progrss.
It takes time to upgrade both routing-engine and cooperate with the on-site engineers.
tail -f /var/log/DMIT.log
It takes time to upgrade both routing-engine and cooperate with the on-site engineers.
The backup Routing Engine is back to work.
The network is in recovering. Premium routing takes 40mins to recover.
This is a hard limit by the ISP AS4809
We are waiting for the on-site engineer to upgrade the master Routing Engine (The network is running on the backup engine now. This will not impact the network)
The network is in recovering. Premium routing takes 40mins to recover.
This is a hard limit by the ISP AS4809
We are waiting for the on-site engineer to upgrade the master Routing Engine (The network is running on the backup engine now. This will not impact the network)
tail -f /var/log/DMIT.log
The backup Routing Engine is back to work. The network is in recovering. Premium routing takes 40mins to recover. This is a hard limit by the ISP AS4809 We are waiting for the on-site engineer to upgrade the master Routing Engine (The network is running…
The network should back to work now include Premium Transit AS4809.
After inspection, the earthquake in Japan only slightly affected DMIT's data center in Equinix TY: a management node got circuit failed.
All computing and network nodes are running as expected.
Due to the particularity of the Tokyo data center, we still recommend that you schedule regular backups in this data center.
Stay safe.
All computing and network nodes are running as expected.
Due to the particularity of the Tokyo data center, we still recommend that you schedule regular backups in this data center.
Stay safe.
The Issue on the Los Angles is noticed, please wait for our NOC's investigation.
tail -f /var/log/DMIT.log
The Issue on the Los Angles is noticed, please wait for our NOC's investigation.
Solved. DDoS Mitigation Cluster has routing loop issues. Huge DDoS used up the entire bandwidth capacity of the core router. The router tried to reset all interfaces on the PFE to "solve" this issue.
To save FIB, the DDoS Cluster has no full FIB, it shares with other tables.
We'll keep looking into this to avoid any potential problems
The DDoS is not that huge on Internet, due to the looping, it was enlarged by "TTL-times".
If the source is Windows which has 128 TTL then it will be 128 times.
To save FIB, the DDoS Cluster has no full FIB, it shares with other tables.
We'll keep looking into this to avoid any potential problems
The DDoS is not that huge on Internet, due to the looping, it was enlarged by "TTL-times".
If the source is Windows which has 128 TTL then it will be 128 times.