5 Aug 2026, 08:54 UTC≈5,990 viewsread 12 August 2026
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.
Channel
/var/log/DMIT-NOC.log
@DMIT_INC
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,448subscribers
+458 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001356752668 |
|---|---|
| Type | Channel |
| Username | @DMIT_INC |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/DMIT_INC |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 81% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 00:19 | 6,448 | +22 |
| 19 Sept 2026, 12:56 | 6,426 | +14 |
| 15 Sept 2026, 07:59 | 6,412 | +8 |
| 11 Sept 2026, 11:18 | 6,404 | +21 |
| 6 Sept 2026, 15:57 | 6,383 | +90 |
| 2 Sept 2026, 02:45 | 6,293 | +60 |
| 30 Aug 2026, 02:04 | 6,233 | +99 |
| 26 Aug 2026, 15:37 | 6,134 | +18 |
| 23 Aug 2026, 12:23 | 6,116 | +26 |
| 19 Aug 2026, 12:47 | 6,090 | +39 |
| 16 Aug 2026, 16:14 | 6,051 | +24 |
| 12 Aug 2026, 18:25 | 6,027 | +13 |
| 10 Aug 2026, 03:32 | 6,014 | +21 |
| 6 Aug 2026, 21:33 | 5,993 | +3 |
| 6 Aug 2026, 07:17 | 5,990 | first reading |
Engagement
20 posts held, back to 12 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
29 Jul 2026, 11:15 UTC≈4,200 viewsread 12 August 2026
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…
22 Jul 2026, 09:54 UTC≈5,010 viewsread 12 August 2026
DMIT has switched all traffic to non faulty China Telecom PoP. The network should be stable. We will revert back to redundancy PoP connectivity once CT resolved the issue.
22 Jul 2026, 09:46 UTC≈9,880 viewsread 12 August 2026
Incident notice Location: Los Angeles Data Center Network Profile: Premium DMIT has identify there is some issue on China Telecom CN2 backbone caused on going packet loss on LAX.Pro We've reached out China Telecom about this matter.
16 Jul 2026, 10:43 UTC≈6,010 viewsread 12 August 2026
Maintenance Notice Region: Los Angeles Data Center Scope: AN4/AN5 hypervisor Impact: Approximately 5 minutes (maximum 30 minutes); Only one hypervisor each time. Dates: July 16, 2026 – July 31, 2026 (UTC) Reason: New data center facility has been delivered; The existing data center has design defects on power infrastructure; migrating of all existing infrastructure to a higher-standard data center.
16 Jul 2026, 07:28 UTCviews —
/var/log/DMIT-NOC.log pinned «https://telegra.ph/DMIT-ToS-Change-Summary-07-16»
16 Jul 2026, 07:27 UTC≈7,600 viewsread 12 August 2026
https://telegra.ph/DMIT-ToS-Change-Summary-07-16
12 Jul 2026, 07:08 UTC≈5,540 viewsread 12 August 2026
Maintenance has been completed. All switches have the most updated JunOS firmware installed. So far it's stable and running well. We will keep monitor it.
12 Jul 2026, 06:03 UTC≈5,850 viewsread 12 August 2026
It will be done soon. There are multiple switches in-line needs to do the same upgrade.
12 Jul 2026, 05:15 UTC≈4,730 viewsread 12 August 2026
Normally, performing maintenance on one switch would not affect the other. However, this JunOS firmware version contains a critical bug: protocol renegotiation triggers a protocol restart or even a kernel reboot. When we were updating one of the switches, the other one rebooted unexpectedly. That bring network down for 3 mins. This is the issue we are attempting to resolve with this update.
12 Jul 2026, 05:05 UTC≈4,690 viewsread 12 August 2026
Emergency Maintenance Location: LAX New Location Details: Fixing a switch firmware error Impact: LAX.AS3
8 Jul 2026, 09:58 UTC≈4,980 viewsread 12 August 2026
A free, unconditional self-service IPv4 address change opportunity has been issued. This free opportunity can be used before September 1, 2026, and applies to all product services created before July 1, 2026. It is limited to one use per service, with no additional restrictive conditions and no manual review required. Please note that once an IP address is changed, it cannot be reverted. Furthermore, DMIT does not g…
Showing the 12 most recent of 20 posts we hold for @DMIT_INC. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
NodeSeek官方频道
@nodeseekc · 36,870
Telegram ranks this channel #52 of 52 here — alongside 51 others — read 2 September 2026
@nodeseekc · 36,870
Telegram ranks this channel #52 of 52 here — alongside 51 others — read 2 September 2026
Project X Channel
@projectXtls · 29,942
Telegram ranks this channel #53 of 58 here — alongside 57 others — read 8 September 2026
@projectXtls · 29,942
Telegram ranks this channel #53 of 58 here — alongside 57 others — read 8 September 2026
VPS信号旗播报
@vps_xhq · 49,725
Telegram ranks this channel #56 of 57 here — alongside 56 others — read 26 August 2026
@vps_xhq · 49,725
Telegram ranks this channel #56 of 57 here — alongside 56 others — read 26 August 2026
Shadowrocket News
@ShadowrocketNews · 46,826
Telegram ranks this channel #60 of 60 here — alongside 59 others — read 27 August 2026
@ShadowrocketNews · 46,826
Telegram ranks this channel #60 of 60 here — alongside 59 others — read 27 August 2026
Github_2dust
@github_2dust · 91,529
Telegram ranks this channel #66 of 71 here — alongside 70 others — read 17 August 2026
@github_2dust · 91,529
Telegram ranks this channel #66 of 71 here — alongside 70 others — read 17 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 29 September 2026 — this entry's latest reading, not the date you are reading this.
“/var/log/DMIT-NOC.log” (@DMIT_INC), 6,448 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/DMIT_INC.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.