TGViewer
Channel Public Channel
/var/log/DMIT-NOC.log

/var/log/DMIT-NOC.log

@dmit_inc

Subscribers
6.45K
Photos
191
Videos
0
Links
124
Recent Posts 18 shown
Post #1281 2.25K
/var/log/DMIT-NOC.log 🟢 CN2 GIA access point degradation in CoreSite LA2 Minor · Resolved · 2026-09-18 16:36 UTC Resolved 2026-09-18 16:36 UTC China Telecom stated the issue at their CoreSite LA location has been resolved. DMIT has reloaded the routes received from China Telecom…
🟢 CN2 GIA access point degradation in CoreSite LA2
Minor · Resolved · 2026-09-18 16:36 UTC

China Telecom stated the issue at their CoreSite LA location has been resolved. DMIT has reloaded the routes received from China Telecom CoreSite LA.
Post #1280 2.56K
🟢 CN2 GIA access point degradation in CoreSite LA2
Minor · Resolved · 2026-09-18 16:36 UTC

Resolved 2026-09-18 16:36 UTC
China Telecom stated the issue at their CoreSite LA location has been resolved. DMIT has reloaded the routes received from China Telecom CoreSite LA.

Monitoring 2026-09-18 09:05 UTC
DMIT has detected packet loss on the CN2 GIA access point in CoreSite LA2. Traffic has been rerouted to the DRT CN2 GIA access point. Network performance for all products is currently unaffected.
Post #1277 12.3K
/var/log/DMIT-NOC.log Los Angeles Major issue: Widespread underlying fiber-optic cable failures affecting Cogent and Zayo have led to reduced network stability in the Los Angeles area. Due to nested leasing arrangements within US Tier-1 backbones, the impact has extended to GTT…
DMIT has isolated the issue, except AS174 and AS3257 single home network.

Nevertheless, Cogent's Los Angeles metropolitan area network is experiencing a severe outage, with some parts of the network unable to access the Internet at all.

Screenshot shows the reachability of DMIT's Cogent interface and the location of failure.

Since this issue has been isolated, traffic was divert to NTT, GSL, Arelion and GTT. DMIT will stop update the network status of Cogent.
Both inbount and outbount routes from Cogent are removed 8hrs ago, since it's unusable.
Post #1275 10.8K
Los Angeles Major issue:

Widespread underlying fiber-optic cable failures affecting Cogent and Zayo have led to reduced network stability in the Los Angeles area.
Due to nested leasing arrangements within US Tier-1 backbones, the impact has extended to GTT and Arelion.
Packet loss has been observed on routes from Los Angeles toward the East (including Europe); the DMIT NOC has temporarily removed some of the most severely affected routes.

Some AS174 and AS3257 single home networks are not able to be migrated for network reachablity reason.

https://tranzact.zayo.com/#!/networkStatus

https://ecogent.cogentco.com/network-status
Post #1274 3.62K
/var/log/DMIT-NOC.log Update from CUG NOC: Territory backbone fiber cut leads to major capacity loss. There are 144 of 288 fibers waiting to be repaired. The repair is in progress. ETR: unknowns. *DMIT Notes: This fiber is between the cable landing station and L3 devices.…
CUG Report the fiber has been reconnected. Please check the network status.
DMIT will revert diversion of China Unicom inbound for LAX.Pro soon.
Post #1273 7.33K
/var/log/DMIT-NOC.log LAX.Pro: China Unicom's inbound routing has been temporarily rerouted via the GTT network. Latency and packet loss issues have currently returned to normal levels. We will switch the routing back to the original path once AS9929 returns to normal operation.…
Update from CUG NOC:

Territory backbone fiber cut leads to major capacity loss.

There are 144 of 288 fibers waiting to be repaired.

The repair is in progress.

ETR: unknowns.

*DMIT Notes: This fiber is between the cable landing station and L3 devices. It is highly possible that it is not owned by CUA. The repair process and updates should come from the local fiber vendor.
Post #1272 4.18K
/var/log/DMIT-NOC.log LAX.EB: AS9929 backbone issue. High packet loss was observed LAX.Pro: Due to the AS9929 issue, the inbound was also impacted. The overall quality reduced.
LAX.Pro:

China Unicom's inbound routing has been temporarily rerouted via the GTT network.
Latency and packet loss issues have currently returned to normal levels.

We will switch the routing back to the original path once AS9929 returns to normal operation.

Although the AS3257-AS4837 route has a bandwidth of only 200 Gbps and cannot guarantee zero packet loss like AS9929 premium routes during normal time, it currently represents a "better" choice, given that AS9929 is causing packet loss rates exceeding 30% on the China Unicom (CU) network.
Post #1271 4.26K
LAX.EB:
AS9929 backbone issue.
High packet loss was observed

LAX.Pro:
Due to the AS9929 issue, the inbound was also impacted. The overall quality reduced.
Post #1270 9.16K
Post #1269 5.45K
/var/log/DMIT-NOC.log DMIT proactive security detected that 2% of tenants were deploying potentially risky applications in the DMIT LAX data center. These tenants' applications sent significant large traffic to China several hours ago. - DMIT detected abnormal traffic within…
All impacted services have been stopped.
Post #1268 13K
DMIT proactive security detected that 2% of tenants were deploying potentially risky applications in the DMIT LAX data center. These tenants' applications sent significant large traffic to China several hours ago.

- DMIT detected abnormal traffic within the network 12 hours ago but took no action due to complexity.
- However, this potential risk factor was officially exploited 8 hours ago.
- DMIT will officially notify affected customers within 12 hours and require them to resolve the issue within 24 hours to avoid service interruption for a long time and abuse penalties.
- The relevant users will receive an email soon, and the VM will be immediately shut down to avoid the transfer being used up. (DMIT will not recover this transfer quota since it was due to the client's unsafe application.)

This vulnerable application cannot directly generate such a large amount of traffic, even though it is open to the internet. Exploiting this type of vulnerability requires real data and requests; it does not possess amplification characteristics.

DMIT initially speculates that attackers in restricted areas are exploiting this TCP 443 application design flaw on a large scale to make super-large-scale real and accepted requests to OpenAI.

Further details will be officially provided after the issue is resolved.
Post #1267 5.32K
DMIT has observed that some customers' applications running pose serious security risks and are being exploited on a large scale. This has already impacted DMIT's network security.
Investigation and mitigation in progress.
Post #1266 11.8K
/var/log/DMIT-NOC.log DMIT LAX.EB: Increase packet loss and latency observed. AS10099-9929 backbone issue. DMIT LAX.Pro CN2 Backbone DRT circuit has minor jitter. We've report it to CN2 NOC.
AS9929 LAX is utilizing some capacity at SJC.

Weeks ago, there was a failure of a DWDM line card on the CUA network, which resulted in a loss of capacity for LAX-SJC.

CUG informed us that this issue has been resolved and is expected to be fully operational at this time.
Post #1265 11.5K
/var/log/DMIT-NOC.log LAX Pro: DMIT observed CN2 backbone issue. We’ve minimized the packet loss by switching all traffic to one of the CN2 core. The packet loss has dropped from 30% to 4%. DMIT NOC also reached the CT NOC about this matter.
CN2 core CoreSite LA1: Datacenter cooling system water leak, which lead to capacity issue on CN2 backbone on LA1 site.

CN2 core Digital Realty LAX10: Backbone cable fault.

Both faults happening together made CN2 backbone has significant capacity issue.

DMIT keeps monitoring about this issue.
Post #1264 5.87K
LAX Pro:

DMIT observed CN2 backbone issue.
We’ve minimized the packet loss by switching all traffic to one of the CN2 core.
The packet loss has dropped from 30% to 4%.

DMIT NOC also reached the CT NOC about this matter.
Post #1263 16.9K
DMIT LAX.EB:

Increase packet loss and latency observed.
AS10099-9929 backbone issue.

DMIT LAX.Pro

CN2 Backbone DRT circuit has minor jitter. We've report it to CN2 NOC.
Post #1262 8.02K
Dear Valued Customers,

Due to rising global IP leasing costs, DMIT has transitioned to purchasing and independently managing our own IP addresses to ensure long-term stability and absorb cost pressures.

We understand some users may need to retain their existing Cogent IPs (IPs starting with 154). You may keep these IPs; however, due to external cost increases, a surcharge of $1 USD/month per IPv4 will be applied to products retaining 154-prefix IPs starting December 1, 2026. This fee will be automatically added to your invoice and can be canceled at any time if you no longer need the IP.

How to avoid this fee:
You can switch to our new, self-owned IP addresses at any time. This replacement is completely free. Simply log in to your Control Panel, go to the Network tab, and manually request an IP change (select the "Discontinued Cogent IP" rule).

**If your service does not use any IP addresses starting with 154, you are completely unaffected by this change.*

Thank you for your continued support and trust in DMIT. Please contact our support team if you have any questions.
-—
Additional Notes:
1. The IP surcharge only applies to renewal invoices generated after December 1, 2026. Existing invoices and base renewal prices remain unchanged.
2. You can temporarily avoid the fee by completing your renewal before your next renewal invoice is generated.
3. You can permanently avoid the fee by changing your IP before your next renewal invoice is generated.
4. No changes or fees will apply to your current active billing cycle.
5. For further details, please refer to ToS Clause "15. Price Change".
Older posts →

About this channel

How can I read @dmit_inc without a Telegram account?
TGViewer shows the public web preview Telegram publishes for /var/log/DMIT-NOC.log: recent posts, photos, videos and the subscriber count, with no app, login or account.
How many subscribers does /var/log/DMIT-NOC.log have?
/var/log/DMIT-NOC.log (@dmit_inc) has 6.45K subscribers on Telegram, refreshed roughly every 30 minutes.
Does /var/log/DMIT-NOC.log know I viewed it here?
No. Public channel previews carry no viewer identity, and TGViewer has no accounts or tracking of what you look up.
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →