Channel
@cloudnativeuz
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
58subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003535027317 |
|---|---|
| Type | Channel |
| Username | @cloudnativeuz |
| Created | Between 1 December 2025 and 27 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cloudnativeuz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 06:31 | 58 | no change |
| 8 Aug 2026, 06:02 | 58 | first reading |
15 posts held, back to 27 December 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 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 15 posts for this entry, the most recent from 10 May 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
53 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 41.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 22 | 41.5% | |
| 🔥 | 17 | 32.1% | |
| ❤ | 12 | 22.6% | |
| ❤🔥 | 2 | 3.77% |
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 11 of the 15 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 53reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 27 December 2025 to 10 May 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.
Community is built by people, but it also needs the right infrastructure to help people discover, join, and stay connected. CNCF Community Groups have moved to the new Open Community Groups platform: https://ocgroups.dev/ And this is already a large ecosystem: 272 groups, 88,328 members, 5,993 events, and 140,739 attendees are now represented on the new CNCF community platform. For me, this is more than just a pl…
❤4🔥1
🔥 DevOpsDays Tashkent 2026 — Agenda is live! 📅 May 15 | 📍 INHA University, 9 Ziyolilar St, Tashkent 16 talks, 4 workshops, 18 speakers — one packed day: 🎙 Panel: AI in Production — what actually works and what breaks DevOps ☸️ Kubernetes, SRE, Gateway API, Dynamic Resource Allocation 🔭 Observability, Traffic Management, mobile CI/CD ☁️ On-prem S3, Cozystack, Managed Kubernetes, CNCF 🤖 AI Agents in DevOps, GPU infr…
👍5🔥3❤🔥2
🚀 Tekton joins the CNCF Incubation: a new milestone for Cloud-Native CI/CD! It’s official — Tekton has moved from the CD Foundation to the CNCF as an Incubating project. This is a massive step forward for the ecosystem, solidifying Tekton’s position as the standard for Kubernetes-native pipelines. 👉 https://www.cncf.io/blog/2026/03/24/tekton-becomes-a-cncf-incubating-project/ Why is this a big deal? 🔹 Kubernetes…
🔥3❤1👍1
🎤 DevOpsDays Toshkent 2026 — Spiker qabuli davom etmoqda! Hali ham o'z tajribangizni ulashishni xohlaysizmi? Spiker arizalarini qabul qilishda davom etmoqdamiz va siz ham sahna egasi bo'lishingiz mumkin! 🔥 Agar siz: — Kubernetes, Cloud yoki GitOps bilan real loyihada ishlagan bo'lsangiz — AI workloadlarini production muhitiga joriy etgan bo'lsangiz — SRE, DevSecOps yoki MLOps bo'yicha amaliy tajribangiz bo'lsa — Mu…
🔥1
🔥 DevOpsDays Toshkent 2026 - Chiptalar sotuvga chiqdi! 🔥 O'zbekistondagi yagona xalqaro DevOps konferensiyasi qaytmoqda! Bu — muhandislar, arxitektorlar va IT sohasidagi yetakchilarning noyob uchrashuvidir. Unda avtomatlashtirish, sun'iy intellekt va zamonaviy infrastruktura uyg'unlashadi. 🎟 Erta band qiluvchilar uchun maxsus narx — 65 000 so'm! 🚀 1-apreldan boshlab narx 130 000 so'mgacha ko'tariladi, shuning uchun…
👍3
🚀 CNCF: Kubernetes has become the de facto “operating system” for AI According to the CNCF Annual Cloud Native Survey: • 82% of container users now run Kubernetes in production (up from 66% in 2023) • 98% of organizations have adopted cloud-native approaches • 66% of companies hosting genAI models use Kubernetes for some or all of their inference workloads If you’re building an AI/ML platform, Kubernetes is no long…
👍4
☁️ AWS User Group Tashkent x Cloud Native Uzbekistan Meetup Kubernetes & Cloud-Native Engineering (EN) ⚠️ Due to circumstances beyond his control, Aleksandr Stepchenko will unfortunately not be able to take part in this meetup. Instead, Emil Garipov will join the agenda with an updated talk. Building with Kubernetes? Starting your cloud-native journey? This joint meetup is for you — practical insights + real commun…
🔥4❤3
☁️ AWS User Group Tashkent x Cloud Native Uzbekistan Meetup Kubernetes & Container Security (EN) Building with Kubernetes? Starting your cloud-native journey? This joint meetup is for you — practical insights + real community in Uzbekistan with Cloud Native Uzbekistan (CNCF Community Group). 🎤 Talks 🚀 The Future of Kubernetes — Daz Akbarov (AWS) & Vadym Voitiuk (AWS) What’s next in K8s: new capabilities, emerging p…
❤4🔥2👍1
📚 Want to stay sharp with Kubernetes in 2026? Start here. CNCF has just published a curated list of the Top 28 Kubernetes Resources for 2026 — and this one is genuinely useful, not just another random collection of links. 👉 https://www.cncf.io/blog/2026/01/19/top-28-kubernetes-resources-for-2026-learn-and-stay-up-to-date/ What you’ll find inside: Official CNCF resources Documentation that actually matters in rea…
👍3🔥3
Channel photo updated
A quick thought for anyone exploring Cloud Native If you’re getting into Kubernetes or Cloud Native, at some point you probably had this feeling: “There are way too many tools. Where do I even start?” You’re not alone. Everyone hits this moment. At some point I found this link, and it honestly helped me calm down and zoom out instead of panicking 🔗 https://landscape.cncf.io/ This isn’t something you’re supposed to…
👍2
🚀 DevOpsDays Toshkent 2026 - Taymer boshlandi! Sanoat ekspertlari bilim almashish, tajriba o‘rtoqlashish va DevOps kelajagini o‘rganish uchun to‘planadigan global DevOpsDays konferensiyasining ishtirokchisiga aylaning. 🎤 DevOps hamjamiyati bilan baham ko‘rishga arziydigan g‘oyalaringiz bormi? Bugun spiker sifatida ariza topshiring va boshqalarga ilhom bering! 📍 Lokatsiya: Toshkent, O‘zbekiston 📌 DevOpsDays Toshke…
Showing the 12 most recent of 15 posts we hold for @cloudnativeuz. 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 — 1,037,539 of 1,176,251entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Cloud Native Uzbekistan” (@cloudnativeuz), 58 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/cloudnativeuz.
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.