Telegram RegisterThe public register of Telegram
Telegram profile photo for OpenBLD.net

Channel

OpenBLD.net

@openbld

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

241subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001979410496
TypeChannel
Username@openbld
Created15 October 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/openbld

Growth

2392412406 August 2026 — 239 subscribers7 August 2026 — 239 subscribers13 August 2026 — 241 subscribers6 August 202613 August 2026
3 measurements spanning 8 days, net +2. 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 239–241 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 23:48241+2
7 Aug 2026, 02:33239no change
6 Aug 2026, 04:23239first reading

Engagement

20 posts held, back to 5 November 2025the 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.

ERR · 30 days
31.7%
avg views ÷ 241 subscribers
Avg views / post
76.5
2 posts measured
Reaction rate
13.7%
reactions ÷ views · ER floor
Posts in window
2
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (5 November 20256 August 2026)
Views total153
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 02:33 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

238 reactions across 19 posts, in 23 distinct kinds. The most used accounts for 40.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥9740.8%
👍3313.9%
197.98%
104.20%
🏆93.78%
👏93.78%
😎93.78%
😱83.36%
💯72.94%
🤝62.52%
🫡52.10%
🙏41.68%
🎉31.26%
🥰31.26%
20.84%
👎20.84%
😈20.84%
😡20.84%
😢20.84%
🤬20.84%
3 further kinds41.68%

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 19 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 238reactions 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 5 November 2025 to 6 August 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.

Recent posts

6 Aug 2026, 07:32 UTC46 views9 reactionsread 7 August 2026
Photo

🇰🇿 OpenBLD on Onehost.kz VPS NVMe SSD in Kazakhstan Under the hood: IPv6, AMD EPYC™, DDR4, NVMe SSD storage, and a high-speed network. A strong candidate for passing OpenBLD’s stress test. Last year, Onehost.kz supported the OpenBLD project by providing a VPS server in Almaty. Since then, the infrastructure has demonstrated stable 99.99% uptime, with no noticeable overselling or system freezes. The server in Almat

🔥62🏆1

Signed Yevgeniy G.

30 Jul 2026, 09:18 UTC107 views12 reactionsread 7 August 2026
Photo

➕ zBLD Plus for Enterprise: DNS Big Data The solution is available for On-Premise deployments and is designed for organizations that require detailed DNS analytics, full control over their data, and event storage within their own infrastructure. Centralized DNS event collection with ClickHouse and VictoriaLogs integration. * centralized collection of DNS events from all zBLD instances; * streaming data delivery to

🔥101👏1

Signed Yevgeniy G.

9 Jul 2026, 09:21 UTC164 views13 reactionsread 7 August 2026
Photo

⚔️ OpenBLD.net: Algorithm (zBLD) vs. Algorithm (DGA) Malware and botnets use DGA (Domain Generation Algorithm) - algorithms that generate hundreds of "trash" domains per second to communicate with C2 servers. An attack example from real OpenBLD logs: • 96bccebb2f7e...wu7y6z[.]com • 60r...60pg0131[.]cc • and billions of similar ones... What's the harm? Aside from the obvious malicious intent, this chaotic spam cl

🔥6👍4🥰3

Signed Yevgeniy G.

29 Jun 2026, 10:02 UTC184 views12 reactionsread 7 August 2026
Photo

🚀 OpenBLD.net - Independent DNS Resolution We’ve become used to relying on DNS from Google, Cloudflare, and other large public DNS providers. They are fast, convenient, and easy to use. But in the age of AI, large-scale data aggregation, and user profiling, convenience should not come at the cost of privacy. OpenBLD takes a different path. We are building an independent DNS ecosystem designed to reduce dependency

🔥84

Signed Yevgeniy G.

4 Jun 2026, 10:07 UTC220 views15 reactionsread 7 August 2026
Photo

🚀 OpenBLD.net в Сан-Франциско! Благодаря 3HCLOUD.kz в OpenBLD появился новый сервер, в Сан-Франциско. 3HCLOUD за годы показал: • Стабильная работа сервисов • Очень адекватные цены • Несколько локаций по всему миру, включая Казахстан 🇰🇿 • Встроенный Firewall и дополнительные инструменты защиты • Быстрая и качественная сеть За годы развития OpenBLD через проект прошло немало облачных провайдеров - Не все выдерживаю

🔥7👏53

Signed Yevgeniy Goncharov

28 May 2026, 04:26 UTC234 views4 reactionsread 7 August 2026
Photo

OpenBLD.net: 🤝 ClouDNS.net — quality proven over time ClouDNS has been part of the OpenBLD.net infrastructure for many years. It’s one of those rare cases where a service consistently proves its quality over time: • Global network (Anycast + GeoDNS) • Failover and fallback mechanisms • Monitoring and health checks • Stability and SLA • Cost-effective OpenBLD.net builds a secure DNS infrastructure. ClouDNS → stable

🤝4

Signed Yevgeniy Goncharov

20 May 2026, 07:21 UTC≈3,350 views9 reactionsread 7 August 2026
Photo

⚡ DNS is not just about domains. It is about Trust. Recent supply chain incidents are a strong reminder that modern attacks often start through tools and workflows developers already trust: • npm packages and dependency updates • compromised maintainer accounts • VSCode extensions • GitHub Actions workflows • fake installers and update mechanisms Several recent cases highlight this trend: • Axios compromised on n

💯7😱2

Signed Yevgeniy Goncharov

25 Apr 2026, 05:43 UTC253 views8 reactionsread 7 August 2026

⚠️ Notice: The Astana server will be maintenance for several days in the coming days. This should not affect overall service availability. If you will have any connectivity issues, contact me please. ✅ up: The server was upgraded and returned back to OpenBLD.net ecosystem.

👍6🫡2

Signed Yevgeniy Goncharov

22 Apr 2026, 11:47 UTC273 views10 reactionsread 7 August 2026
Photo

😎 OpenBLD.net - Dedup DNS Events Yo! The privacy march continues! 🚀 Anonymized IPs are cool, but now they’re deduplicated too! OpenBLD is rolling out an event deduplication mechanism. Anonymization + Deduplication — what could be better? Sure, I might be shooting myself in the leg when it comes to incident analysis, but you never know until you try! An efficient system should be lean and clean, and for a public s

🔥72👨‍💻1

Signed Yevgeniy Goncharov

16 Apr 2026, 06:33 UTC266 views16 reactionsread 7 August 2026
Photo

🥷 OpenBLD.net — IP Anonymization OpenBLD is implementing an IP anonymization mode. Address data will be masked in logs and metrics—if any, and if they're not needed in their raw form. DNS reveals more than you think. Your behavior is your life, it's your daily pattern. Typical request path: Request > Domain > Time > Location Your pattern, if you want a digital stamp) OpenBLD now features IP anonymization in logs

😎7🔥432

Signed Yevgeniy Goncharov

19 Mar 2026, 06:21 UTC312 views13 reactionsread 7 August 2026
Photo

🤝 UptimeRobot.com supports OpenBLD.net This is one of those cases when a service truly becomes part of your infrastructure. Honestly, for me, it’s a clear choice. Why • 50 free monitors • 20+ integrations • Real-time alerts (web, mobile, Telegram, and more) • Public status pages • A new interface — clean, fast, and convenient • Most importantly — a responsive and friendly UptimeRobot team OpenBLD uptime status

6👍4🤝2😢1

Signed Yevgeniy Goncharov

Showing the 12 most recent of 20 posts we hold for @openbld. 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 — 374,631 of 1,481,306entries 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.

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.

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

“OpenBLD.net” (@openbld), 241 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/openbld.

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.