Channel
@aluyinfo
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
504subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002654663493 |
|---|---|
| Type | Channel |
| Username | @aluyinfo |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/aluyinfo |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 17:37 | 504 | +3 |
| 7 Sept 2026, 03:22 | 501 | -7 |
| 29 Aug 2026, 13:06 | 508 | -2 |
| 22 Aug 2026, 17:07 | 510 | +8 |
| 15 Aug 2026, 08:53 | 502 | +2 |
| 8 Aug 2026, 04:18 | 500 | no change |
| 7 Aug 2026, 17:28 | 500 | first reading |
20 posts held, back to 13 April 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 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 20 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.
182 reactions across 17 posts, in 2 distinct kinds. The most used accounts for 88.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 161 | 88.5% | |
| 🔥 | 21 | 11.5% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 18 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 182 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 April 2026 to 23 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @aluyinfo. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 13 April 2026 to 23 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Under constant high Gbit DDoS attacks for past hours. No idea when it can be fixed. No idea as to why exactly, ive not been contacted by any actors for the reason. I would be thankful for any information and will try to get everything up again. Very sorry for this whole thing, its not the way I want this business to go.
❤22
Signed bnt
Dear Customer, All Services should now be back online. All Switzerland servers had to be migrated to our Netherlands location. No IP Addresses have changed, so no action is required from your side. If you're still experiencing any issues, feel free to open a ticket with our Support Team. As compensation for the inconvenience, all affected customers have received: - 20% lifetime discount - additional week of ser…
❤14
Signed Joel
We are aware of the issues at our Swiss Location and are looking for a solution.
❤12
Signed Joel
There is currently a downtime with our management panel, as such managing your VM is not possible. This has no effect on the VMs themselves. Everything should be back normal.
❤4
Signed bnt
The Nodes are all back and VMs are booting up slowly! Sorry for the sudden downtime, wasnt really preventable at the risk of the CVE published. Rather not have even more issues for customer because of it.
Signed bnt
We will have an emergency reboot for all Nodes during the next hours. Nodes will be rebooted then all VMs started again right after.
❤4
Signed bnt
We are aware of issues with our CH3 Node. This is specific to this Node and we are unaware how it is happening. NOC has been contacted and we are awaiting response
Signed bnt
Identified as large DDoS Attack. Mitigations are in progress. Unfortunate situation.
Signed bnt
We are aware of Bulgaria being down right now and investigating!
❤6
Signed bnt
Dear Customers, We're excited to announce the expansion of our infrastructure into the Asia-Pacific region with the launch of Hong Kong for VM-Custom deployments. 🇭🇰 Deploy your Hong Kong VM now ~> [CLICK ME] Best regards, The aluy.net Team
❤21🔥3
Signed 异
Hi, guys just short announcement while I enjoy my birthday im giving 23% (since im turning 23) off using code BIRTHDAY on ALL products (yes every single item) until the 12th Check it out at https://aluy.net/pricing I love you all (im fairly low on stock for VMs so please dont kill me if its gone fast for those)
❤16🔥7
Signed bnt
NL2 and 3 will go down in about 10 minutes for approximately 20 minutes. (A little delayed) (Cancelled no downtime)
❤5
Signed bnt
Showing the 12 most recent of 20 posts we hold for @aluyinfo. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Named by 2 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Aluy” (@aluyinfo), 504 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/aluyinfo.
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.