Channel
@cloudflare2tg
On this record: Growth · Engagement · Posts · Citations · Cite this entry
889subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002435446970 |
|---|---|
| Type | Channel |
| Username | @cloudflare2tg |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/cloudflare2tg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 05:51 | 889 | no change |
| 9 Aug 2026, 03:02 | 889 | first reading |
20 posts held, back to 8 August 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (8 August 2026 – 9 August 2026) |
| Views total | 332 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 03:02 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.
CloudFlare Optimized IPs: IPv4: 104.21.229.137 104.17.92.173 104.17.177.130 104.18.79.20 104.18.96.247 198.41.208.252 198.41.209.41 198.41.208.63 198.41.208.227 198.41.208.229 198.41.208.252 198.41.209.41 198.41.208.63 198.41.208.227 198.41.208.229 IPv6: 2606:4700:9a9e:7532:93f6:af45:d25d:9d94 2606:4700:99e6:7d3d:e058:caa8:ec48:43f6 2606:4700:99e6:5860:170f:5cd8:44cb:dba6 2606:4700:8d7e:e8c1:24fe:19c3:a6e:b2cb 2606…
CloudFlare Optimized IPs: IPv4: 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.87 198.41.208.229 104.16.253.190 104.17.28.21 104.19.255.216 104.16.107.116 104.18.242.95 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.87 198.41.208.229 IPv6: 2606:4700:964b:b57b:506c:c7d2:64cd:21c3 2606:4700:4:24d0:e353:2fc0:b668:6720 2606:4700:4:b6d8:ae10:3c72:2a60:8821 2606:4700:90d3:c66e:5b21:ce05:59f1:9baf 2606:470…
CloudFlare Optimized IPs: IPv4: 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.87 198.41.208.229 104.18.4.86 104.16.253.190 104.18.143.86 104.17.28.21 104.19.255.216 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.87 198.41.208.229 IPv6: 2606:4700:9a9b:7af0:f78b:a1e3:e5c3:9c4f 2606:4700:90d2:1620:9fe5:9f56:ad64:5b71 2606:4700:90d2:95d:d6a7:d21b:2601:1ad1 2606:4700:4402:2770:ac63:2651:990e:3884 2606:4…
CloudFlare Optimized IPs: IPv4: 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.229 198.41.208.87 104.18.4.86 104.16.103.28 104.18.184.149 104.18.143.86 104.19.255.216 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.229 198.41.208.87 IPv6: 2606:4700:9640:73d0:b42e:c31f:f15a:609d 2606:4700:3027:8d9d:9acb:4063:f150:3062 2606:4700:8cae:d349:54b7:7db7:bd85:9a74 2606:4700:3027:42db:5f8d:e63:aa6e:b209 2606:…
CloudFlare Optimized IPs: IPv4: 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.229 198.41.208.87 104.18.4.86 104.16.103.28 104.18.184.149 104.18.8.85 104.18.143.86 198.41.208.252 198.41.208.186 198.41.209.41 198.41.208.229 198.41.208.87 IPv6: 2606:4700:4406:aac9:a07e:690f:d72f:7384 2606:4700:99e7:80b6:15dc:c737:41ab:2279 2606:4700:91bf:6878:8698:970c:c8d2:df81 2606:4700:91bf:4a1f:a775:7435:b5ed:513a 2606:47…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.18 198.41.209.35 198.41.208.119 198.41.208.87 104.18.17.166 104.19.3.54 104.18.184.149 104.18.8.85 104.19.249.171 162.159.160.215 198.41.208.18 198.41.209.35 198.41.208.119 198.41.208.87 IPv6: 2606:4700:9645:e0af:4a81:d2da:885d:c3ce 2606:4700:99e5:19a9:273e:642b:dcb4:22c2 2606:4700:83bd:e5e5:6120:4f3f:4585:fb52 2606:4700:99e5:3d91:e224:d900:e45e:7376 2606:4…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.35 198.41.208.18 198.41.208.119 198.41.209.35 104.18.17.166 104.19.3.54 104.18.184.149 104.18.8.85 104.19.249.171 162.159.160.215 198.41.208.35 198.41.208.18 198.41.208.119 198.41.209.35 IPv6: 2606:4700:8396:9851:7f5d:1d01:2be:10e7 2606:4700:8396:3698:ebc4:f231:ea2f:596f 2606:4700:9769:59dd:ceab:59d3:d725:64a8 2606:4700:2d:21b3:1ed5:45e7:27e9:7d39 2606:4700…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 104.18.17.166 104.19.3.54 104.19.64.204 104.18.8.85 104.19.249.171 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 IPv6: 2606:4700:91bb:696f:4a90:a5f2:58b2:a1b4 2606:4700:8ca4:8b04:d994:d6bf:7edf:ba2f 2606:4700:8ca4:c125:578:1e84:2209:54c2 2606:4700:8ca2:2f60:af48:7bf9:cb5c:e33 2606:4700…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 104.18.17.166 104.19.3.54 104.18.126.217 104.19.64.204 104.19.249.171 IPv6: 2606:4700:99e8:58a6:e1c3:b2f1:4779:a1c1 2606:4700:b:c071:c72f:c6ce:f659:96 2606:4700:b:8844:4a14:a5d5:6a4:1fd2 2606:4700:99e8:8014:e60e:d5bd:a45:4ba2 2606:4700:3035…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 162.159.160.215 198.41.208.35 198.41.208.18 198.41.209.35 198.41.208.119 104.18.126.217 104.17.56.126 104.17.237.51 104.18.102.124 104.17.193.99 IPv6: 2606:4700:8ca6:9e56:455b:cfc6:81d7:ab3a 2606:4700:83ba:bb5a:6999:3a03:179d:4383 2606:4700:83ba:554c:aed3:d70f:47e3:3d1f 2606:4700:91b9:59c2:df6a:b9bd:4b4c:c2ca 26…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 198.41.208.35 162.159.160.60 198.41.209.35 198.41.208.119 104.18.126.217 104.17.237.51 104.17.56.126 104.18.102.124 104.17.193.99 162.159.160.215 198.41.208.35 162.159.160.60 198.41.209.35 198.41.208.119 IPv6: 2606:4700:3030:b512:84ff:19d7:df97:bcc8 2606:4700:13f:5d9b:33b9:9ea:e969:b133 2606:4700:9a69:e4c0:95e3:e92d:9de9:a2a5 2606:4700:a:9de7:20fd:6c4f:3fd3:807d 2606:…
CloudFlare Optimized IPs: IPv4: 162.159.160.215 162.159.160.60 198.41.208.35 198.41.208.245 162.159.250.121 104.17.56.126 104.18.170.118 104.21.229.15 104.17.193.99 104.17.152.170 162.159.160.215 162.159.160.60 198.41.208.35 198.41.208.245 162.159.250.121 IPv6: 2606:4700:6:8f7b:87a5:9712:b674:2ad 2606:4700:1c:f01:53ff:56a0:5118:7c05 2606:4700:9ae6:10c4:8f98:87:401:ffd7 2606:4700:2c:cce9:407f:138c:396c:81ec 2606:470…
Showing the 12 most recent of 20 posts we hold for @cloudflare2tg. 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,086,887 of 1,160,990entries 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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“CF2TG | آیپی تمیز کلادفلیر” (@cloudflare2tg), 889 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cloudflare2tg.
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.