Telegram RegisterThe public register of Telegram
Telegram profile photo for Ping交流群|通知频道

Channel

Ping交流群|通知频道

@mar_alicheckcc

On this record: Growth · Engagement · Posts · Citations · Cite this entry

432subscribers

+40 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002886541522
TypeChannel
Username@mar_alicheckcc
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/mar_alicheckcc

Growth

3924324127 August 2026 — 392 subscribers8 August 2026 — 392 subscribers8 August 2026 — 393 subscribers15 August 2026 — 415 subscribers21 August 2026 — 420 subscribers28 August 2026 — 432 subscribers7 August 202628 August 2026
6 measurements spanning 21 days, net +40. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 386–438 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 08:11432+12
21 Aug 2026, 14:17420+5
15 Aug 2026, 00:48415+22
8 Aug 2026, 09:51393+1
8 Aug 2026, 06:01392no change
7 Aug 2026, 19:16392first reading

Engagement

16 posts held, back to 10 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 16 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

5 Aug 2026, 09:14 UTC125 viewsread 8 August 2026

服务恢复了,1004vip接口临时下线,做一定的升级之后再上线

28 Jul 2026, 11:26 UTC346 viewsread 8 August 2026
Photo

今天服务器有点不稳定,起因是一个吊毛今天私信勒索我200u,还发了一段英语给我,其实我个人最开始看到这个英语的时候是十分疑惑的,比如 I can also provide you with paid typing services. I guarantee that your colleagues won't have any discomfort 这段居然要提供打字服务,估计用的是国内某个机翻导致的翻译失误,一个土生土长的英语母语使用者应该不会犯这种错误吧,然后我查了一下日志,发现访问的ip百分之99来自于河北邢台的家庭宽带,居然还是个大陆ip,如图所示,就你这种实名上网行为,我完全可以向公安部举报你让你蹲大牢,但是想着也没必要,一个连英语都需要机翻,并且还要用本地网络来打我的人,估计就是在某个吊毛那里买租了一套 DDoS 打洞工具的一个初中学历的装黑客的脚本小子,整他也不必浪费我时间,ip我已经暴露出来了,小子你自己耗子尾汁

15 Jul 2026, 07:00 UTC403 viewsread 8 August 2026
Photo

关于能量兑换的说明,因为高峰时段能量价格会上涨很多,所以我们采取了动态调价的方式,不是每一次兑换能量的时候积分都是一成不变的,根据trx价格和高峰时段租赁价格来中和计算,不过想必各位老板也只是为了图个方便,避免转错账才使用平台内部的能量购买,不会在意这些小调价😁

15 Jul 2026, 06:49 UTC396 viewsread 8 August 2026

1000 全球接口公测通过,其他接口不好测的头大家可以放进去试试

10 Jul 2026, 08:11 UTC492 viewsread 8 August 2026

今天我起床发现服务器瘫痪了,排查了半小时,发现是服务器厂商把我其他几台集群的服务器ip给拉黑了,为了服务器稳定和快速运行,我从几个厂商那里买了分别买了数十台服务器做成集群一起提供服务,可能是这些服务器之间相互访问太频繁,有一个服务器厂商今天居然屏蔽了另外几台服务器的ip,导致整体瘫痪,坑死我了,目前已经恢复正常

4 May 2026, 17:50 UTC983 viewsread 8 August 2026

代理商正好今天过了0点之后,代理商的 SSL的证书过期了,无语了,最近一天安稳日子都没得,还好今天睡觉前看了一眼服务状态,刚换了一个代理,已经正常

3 May 2026, 14:09 UTC920 viewsread 8 August 2026
Photo

今天晚上突然很卡,检查了一个小时终于找到原因了,是debian系统每个月的第一个星期天就会自动扫盘校准数据,刚才已经关了这个沙雕自动扫盘了,之前每个月的第一个星期天估计都会卡很久,只是今天我正好有空正好看到了,目前已经恢复

1 May 2026, 05:47 UTC788 viewsread 8 August 2026

这两天机房不知道啥情况,老是中午的时候就断网,我先解决一下,莫慌

30 Apr 2026, 08:04 UTC723 viewsread 8 August 2026
Photo

机房断电导致停摆了半小时,目前已经恢复···················

Showing the 12 most recent of 16 posts we hold for @mar_alicheckcc. 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.

Mentions

Named by 1 registered channel — 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.

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 28 August 2026 — this entry's latest reading, not the date you are reading this.

“Ping交流群|通知频道” (@mar_alicheckcc), 432 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/mar_alicheckcc.

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.