Telegram RegisterThe public register of Telegram
Telegram profile photo for 0xHost - Announcements

Channel

0xHost - Announcements

@HostAnnouncements

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

498subscribers

-8 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-1003066333280
TypeChannel
Username@HostAnnouncements
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live25 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/HostAnnouncements

Growth

4985065027 August 2026 — 506 subscribers8 August 2026 — 506 subscribers16 August 2026 — 501 subscribers25 August 2026 — 498 subscribers7 August 202625 August 2026
4 measurements spanning 17 days, net -8. 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 497–507 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 01:36498-3
16 Aug 2026, 21:55501-5
8 Aug 2026, 04:16506no change
7 Aug 2026, 21:21506first reading

Engagement

20 posts held, back to 12 March 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 pageof 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Jul 2026, 11:27 UTC54 viewsread 8 August 2026

✅ Services restored The maintenance window is closed and everything is back online. We've completed the groundwork for our Anti-DDoS upgrade, We'll be activating it in a later step. Thanks for your patience!

30 Jul 2026, 11:03 UTC65 viewsread 8 August 2026

We're currently in a short maintenance window to upgrade our Anti-DDoS protection. This will give you stronger, more reliable service going forward. Some services may be briefly unreachable during this time. Sorry for the disruption, everything should be back up shortly. Thanks for your patience!

1 Jun 2026, 22:59 UTC170 viewsread 8 August 2026

🚀 Dedicated Server Availability We currently have a single unit available with the following configuration: AMD Ryzen 9950X 64 GB RAM 1× 2 TB SSD Price: 425 EUR/month This is a one‑time availability and will be allocated on a first‑come, first‑served basis. If you are interested in deploying this server, please contact us to proceed with the order.

1 Jun 2026, 21:53 UTC155 viewsread 8 August 2026

❗️❗️Main Domain Update We would like to inform you that 0xhost.com has been our main domain for some time now, and a redirect from 0xhost.net has already been in place over the past days. As part of this transition, 0xhost.net will be fully phased out and will become inactive soon. We strongly recommend updating any saved links, bookmarks, or integrations to use 0xhost.com directly. All services, including the clie

14 May 2026, 10:01 UTC179 viewsread 8 August 2026

✅ Update The migration is now complete, and all affected VMs are working again. Thank you for your patience while we resolved this issue.

14 May 2026, 09:00 UTC156 viewsread 8 August 2026

✅ Update The node AMD EPYC Node 01 is back online, and we will now migrate the VMs to a new node. Please do not start the VM. Thank you for your patience while we complete this migration.

13 May 2026, 19:56 UTC152 viewsread 8 August 2026

⚠️ We also want to give you an update about AMD EPYC Node 01. Since yesterday, we’ve been dealing with a node issue there. We applied a patch yesterday and initially thought the situation was stable, but the issue still seems to persist. The problem is related to a Samsung firmware bug that can prevent the NVMe from booting correctly. Tomorrow, we will install a secondary disk to keep access to the node safe, and th

13 May 2026, 19:56 UTC131 viewsread 8 August 2026

🎉 Great news! We’ve added an owned AFRINIC /22 to our available IP list. That’s a big update, and we’re excited to make it available to our customers.

12 May 2026, 22:06 UTC129 viewsread 8 August 2026

✅ Attack update Most of the attack has been mitigated. The total volume was over 6 Tbps. The target of the attack was one of our active customers, not our infrastructure directly. However, we do not rule out the possibility that the attacker may try a new pattern to cause further damage. We will continue monitoring closely and applying mitigation as needed.

12 May 2026, 20:57 UTC111 viewsread 8 August 2026

⚠️ We are currently under a large DDoS attack, and our team is actively working to mitigate it as quickly as possible. We will keep you updated. Thank you for your patience and understanding.

21 Apr 2026, 10:19 UTC164 viewsread 8 August 2026

The BGP configuration issue has been resolved. The TTL value has been corrected and services are now operating normally. Thank you for your patience.

21 Apr 2026, 09:48 UTC159 viewsread 8 August 2026

There is an issue with the BGP configuration. The TTL value is incorrect, which caused a configuration failure. We are currently fixing it. Please give us a few minutes. Apologies for the inconvenience.

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

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

“0xHost - Announcements” (@HostAnnouncements), 498 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/HostAnnouncements.

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.