A New Chapter for BeeProxies: Moving Forward Together To our valued community, We are reaching out to share an important update regarding the future of BeeProxies. Recently, our primary infrastructure provider unexpectedly ceased operations. While this has caused a temporary disruption to our current services, we are using this challenge as a catalyst to accelerate our vision for the future. The Game Plan For the p…

Channel
BeeProxies Announcements
@beeproxies
On this record: Growth · Engagement · Posts · Citations · Cite this entry
575subscribers
-1 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 | -1001657153512 |
|---|---|
| Type | Channel |
| Username | @beeproxies |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/beeproxies |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 22:00 | 575 | -1 |
| 7 Aug 2026, 11:02 | 576 | first reading |
Engagement
20 posts held, back to 20 May 2024 — 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 20 posts for this entry, the most recent from 7 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🐝 BeeProxies Update & Announcement Dear BeeProxies Community, 📢 Important Updates: We are fully aware of the recent downtimes and want to sincerely apologize for the disruption. Our team has been working around the clock to improve stability and prevent future issues. ✨ What's New: 🔧 New Experimental Node We've launched a new endpoint: swarm.beeproxies.com:1337 This experimental node is designed for improved rel…
🔔 All ongoing issues are resolved. Discount code: 10OFF
⚠️ We are aware of the issue, we are working on solution.
🚨 SPECIAL THANK YOU OFFER 🚨 Dear valued customers! 💙 We sincerely apologize for the brief service interruptions on June 26th and today. While these were minimal, we know how important reliable service is to you! 🛡 As our way of saying THANK YOU for your patience and loyalty, we're excited to offer: 🎉 15% OFF ALL PROXIES 🎉 ✨ Valid for ALL customers ⏰ Limited time offer Use Code: SUMMER05 Ready to upgrade your pr…
Scheduled Maintenance Notice Date: Friday, June 26, 2025 Estimated Start Time: 1:00 PM (Central EU)~ Expected Duration: 30 minutes to 12 hours~ Affected Services We have scheduled essential maintenance that will temporarily impact: - Primary bot functionality - Several private API endpoints Service Continuity Good news: Our proxy services will remain fully operational throughout the maintenance window. If you requ…
🌸 Women’s Day Special – Exclusive Discount! 🌸 Strong connections, just like strong women! 💪 ✨ Celebrate Women’s Day with 10% OFF on all BeeProxies plans. 🛒 Use code WMNPWR at checkout. 📅 Hurry! Offer expires 3/9 - 00:00. 🔗 Grab your deal now: https://t.me/buybee_bot
The technical issue affecting order placements has now been resolved. You can proceed with your orders as usual. We sincerely apologize for any inconvenience this may have caused and truly appreciate your patience and understanding. Thank you for your understanding! The BeeProxies Team 🖤💛
We are currently experiencing a temporary issue with our backend system, which may affect your ability to place orders at this time. Our team is actively working to resolve this as quickly as possible. We sincerely apologize for any inconvenience this may cause and appreciate your patience. Once the issue is resolved, we will notify you immediately. Thank you for your understanding!
🎉 Happy New Year, BeeProxies Family! 🐝✨ We’re buzzing with gratitude as we welcome another amazing year with you! Thank you for your trust and support—it means the world to us. 🌎💛 ✨ Important Update for the Holidays ✨ Our team will be operating at a slower pace over the next few days due to the holiday season and some internal adjustments. Here's what to keep in mind: 💳 Deposits: Please double-check the exact amou…
🎉 Announcing the Winners of our Spooky Month Giveaway! 🎉 Thank you to everyone who took part in our Spooky Month Discount event! 🕸 We had an incredible response, and we're thrilled to announce the lucky winners who will each receive 50GB of proxy data on us! 👻 🎃 Congratulations to our Winners! (Telegram ID's)🎃 5****433 1****776 5****732 4****625 5****6588 Feel free to contact us @beeproxies_support to claim your …
🎃 Halloween Promo Ending Soon! 🎃 Today’s the final day of our spooky Halloween promotion! 🧛♂️ Don’t miss your chance to get in on the giveaway! All orders placed from the initial announcement until midnight will automatically qualify for a chance to win. 💀👻 Hurry and take advantage of our Halloween discount before it disappears! Don’t let this treat turn into a trick! 🕛 Offer ends at midnight – don’t miss out! 🕛
Showing the 12 most recent of 20 posts we hold for @beeproxies. 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 — 550,139 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.
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.
Mentions
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“BeeProxies Announcements” (@beeproxies), 575 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/beeproxies.
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.