已结束

Channel
SaltyFish.IO
@SaltyFishIO
On this record: Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
3,785subscribers
+32 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 | -1001241643464 |
|---|---|
| Type | Channel |
| Username | @SaltyFishIO |
| 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 | 28 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/SaltyFishIO |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 18:09 | 3,785 | +7 |
| 25 Aug 2026, 22:16 | 3,778 | +4 |
| 22 Aug 2026, 18:08 | 3,774 | +4 |
| 19 Aug 2026, 18:22 | 3,770 | +2 |
| 16 Aug 2026, 14:55 | 3,768 | +4 |
| 12 Aug 2026, 13:27 | 3,764 | +7 |
| 9 Aug 2026, 15:17 | 3,757 | +4 |
| 6 Aug 2026, 20:30 | 3,753 | no change |
| 6 Aug 2026, 20:29 | 3,753 | first reading |
Engagement
20 posts held, back to 22 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
维护通知 我们计划于 2026/07/14 21:00 (UTC+8) 对 AMS 区域机柜设备进行维护,届时实例将会离线,预计维护时长1.5小时。
我们已完成对故障宿主机的磁盘替换工作,对于受影响客户,将会收到来自我们的邮件,邮件内包含了受影响实例清单。 在控制面板中进行重装系统后即可恢复使用。
补偿已下发。
尊敬的用户: 我们很遗憾地通知您,近期我们位于德国法兰克福区域的一台宿主机发生了硬件故障,导致存储在其上的数据丢失。对于由此给您带来的影响,我们深表歉意。 德国法兰克福区域其中一台宿主机所使用的Intel P4510 SSD 为早期采购,出厂即存在固件缺陷(同代SSD相关文章供参考) ,导致故障并停止工作。 受影响硬盘上保存的数据无法被恢复。 我们的存储采用 RAID10 镜像阵列。该阵列由多个镜像子组(主盘+备盘)组成,同一份数据会在子组内的主盘和备盘上各保存一份,具备较高的冗余保护能力。 正常情况下,即使某块硬盘损坏,也可通过同一子组内的另一块硬盘恢复数据。 但本次故障中,发生故障的多块 P4510 硬盘恰好位于同一镜像子组内(即主盘与备盘同时失效),导致该子组的主、备数据副本同时丢失,超出了冗余机制的保护范围,因此数据未能恢复。 我们已第一时间排查所有P4510型号SSD,并对现有相同型号硬盘完成紧急固件升级,从根…
我们的IPv4地址储量已接近耗尽,为了避免因特殊原因,导致大量IP地址在更换后短时间内再次被阻断,我们目前已暂停受理更换IP地址请求,预计 6月6日 后恢复受理请求。
Dear customers, 为了服务的可持续性以及服务质量保证,经过对成本的综合评估,我们已对产品新购价格进行调整。 存量实例续费价格不会产生变化
AMS区域硬件设备故障,正在联系数据中心检查 Update 2026/05/06 11:38 (CEST): 数据中心已安排远程手检查硬件,远程手需要按顺序响应工单请求,这将需要一些时间 Update 2026/05/06 12:26 (CEST): 已恢复,正在拉起所有实例
2026/04/01 3:04 (UTC+8) Update: FRA.E2 迁移已完成,请各位客户检查数据完整性,原始镜像将保留至2026/4/10。 部分客户使用了自行安装的操作系统/部署的第三方软件,导致网络不可达,请通过VNC自行尝试修复,若遇疑难,欢迎通过工单联系我们提供技术支持。
Dear Customers, 由于消费级 AMD Ryzen 硬件可靠性问题,Frankfurt Elite Network VPS 产品 位于 e2 边缘机房的实例 需迁移至核心机房的 AMD EPYC 宿主机集群 硬件规格保持不变,网络端口限速将免费升级为 e1 同等。 您可提交工单申请提前迁移,需在工单内告知数据是否需要保留。 携带数据迁移为按顺序进行,当迁移开始时,实例离线约 30 分钟 - 1 小时,在这之前您的实例将保持在线状态 迁移完毕后请登入实例验证数据完整性。如发现数据异常,请在迁移完成后24小时内提交工单联系我们。 超过截止日期后,我们将统一执行保留数据迁移,截止日期:2026年3月31日 对此造成的不便,我们深感抱歉。感谢您的配合。
Dear customers, 我们的支援团队春节休假时间为2026年 2 月 15 日至2月 23 日。在此期间,我们的服务将有所调整。 技术部门:我们的技术支援团队将继续为您提供服务,工单处理时间将延长至48小时内回复。 财务部门:推介提现请求将在假期期间暂停,假期结束后将恢复正常,退款相关请求将在假期期间继续受理。
计划维护通知 我们计划于 2025/12/12 15:00 (UTC+8) 对 财务面板 / Looking Glass 进行例行维护,届时财务面板 / Looking Glass 会处于不可用状态,实例运行不会受到任何影响。 预计结束时间: 2025/12/12 16:00 (UTC+8) 已完成
Showing the 12 most recent of 20 posts we hold for @SaltyFishIO. 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.
Citation-graph rank
Citation-graph rank — 841,464 of 1,626,935entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
@ShadowrocketNews · 46,419
Telegram ranks this channel #16 of 60 here — alongside 59 others — read 27 August 2026
@vps_xhq · 49,158
Telegram ranks this channel #19 of 57 here — alongside 56 others — read 26 August 2026
@github_2dust · 90,905
Telegram ranks this channel #68 of 71 here — alongside 70 others — read 17 August 2026
This channel appears in 3 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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“SaltyFish.IO” (@SaltyFishIO), 3,785 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/SaltyFishIO.
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.