Telegram RegisterThe public register of Telegram
Telegram profile photo for AirProxy

Channel

AirProxy

@airproxyinfo

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

635subscribers

+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-1001159353529
TypeChannel
Username@airproxyinfo
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 November 2026
Measurements held10
Confirmed unchanged2 times, most recently 17 November 2026
On Telegramt.me/airproxyinfo

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

6306386347 August 2026 — 634 subscribers8 August 2026 — 634 subscribers16 August 2026 — 631 subscribers24 August 2026 — 630 subscribers17 September 2026 — 636 subscribers3 October 2026 — 637 subscribers19 October 2026 — 638 subscribers25 October 2026 — 637 subscribers1 November 2026 — 633 subscribers8 November 2026 — 635 subscribers6357 August 20268 November 2026
10 measurements spanning 92 days, net +1. 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 629–639 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 00:55635+2
1 Nov 2026, 21:16633-4
25 Oct 2026, 16:27637-1
19 Oct 2026, 16:27638+1
3 Oct 2026, 07:58637+1
17 Sept 2026, 12:15636+6
24 Aug 2026, 23:37630-1
16 Aug 2026, 16:36631-3
8 Aug 2026, 02:50634no change
7 Aug 2026, 20:07634first reading

Engagement

20 posts held, back to 6 March 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 page of 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 3 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Jun 2026, 13:17 UTC328 viewsread 8 August 2026

⚠️ S3 WINDTRE PROXIES DEGRADED / OFFLINE Proxies hosted on s3.airproxy.io using WindTre as the mobile operator are currently experiencing degraded performance or may appear offline due to another outage affecting the WindTre BTS serving the area. We apologize for yet another disruption. Unfortunately, this issue is caused by a failure within WindTre's network infrastructure and is outside of AirProxy's control. ✅ …

Signed Diego

3 Jun 2026, 06:25 UTC336 viewsread 8 August 2026

⚠️ S6 WINDTRE PROXIES DEGRADED / OFFLINE Proxies hosted in s6.airproxy.io using Wind as the operator are currently experiencing degraded performance or may appear offline due to another outage on the Wind BTS serving the area. We are actively following up with the operator and will provide an update as soon as we receive feedback, which we expect within the next few hours. ✅ SOLVED

Signed Diego

28 May 2026, 07:32 UTC386 viewsread 8 August 2026

⚠️ S3 WIND PROXIES SLOW s3.airproxy.io proxies on the Wind operator are experiencing degraded performance due to another outage on the mobile cell serving the area (operator-side issue). Performance will return to normal once the operator resolves the issue, typically within 4–24 hours based on previous incidents. ✅ SOLVED

Signed Diego

25 May 2026, 13:38 UTC428 viewsread 8 August 2026

⚠️ S4 and S6 WIND PROXIES SLOW s4 and s6.airproxy.io proxies on the Wind operator are experiencing degraded performance due to an outage on the mobile cell towers serving the area (operator-side issue). We are monitoring the situation, but this is outside of our infrastructure and depends on the carrier restoring the cell. Performance is expected to return to normal once the operator resolves the issue, typically …

Signed Diego

18 May 2026, 08:24 UTC872 viewsread 8 August 2026

⚠️ S3 WIND PROXIES SLOW s3.airproxy.io proxies on the Wind operator are experiencing degraded performance due to an outage on the mobile cell serving the area (operator-side issue). We are monitoring the situation, but this is outside of our infrastructure and depends on the carrier restoring the cell. Performance is expected to return to normal once the operator resolves the issue, typically within 4–24 hours bas…

Signed Diego

4 May 2026, 12:05 UTC553 viewsread 8 August 2026

⚠️ S1 WIND PROXIES SLOW s1.airproxy.io proxies on the Wind operator are experiencing degraded performance due to an outage on the mobile cell serving the area (operator-side issue). We are monitoring the situation, but this is outside of our infrastructure and depends on the carrier restoring the cell. Performance is expected to return to normal once the operator resolves the issue, typically within 4–24 hours bas…

Signed Diego

19 Jan 2026, 15:31 UTC843 viewsread 8 August 2026

❕SCHEDULED MAINTENANCE ON S6 PROXIES tl;dr s6.airproxy.io proxies will be offline for ~1 hour on Wednesday 21st at 09:30 UTC due to a server room relocation. No action required. Proxies will come back online automatically with improved performance. What’s happening The s6 server room will be relocated to a new location a few kilometers away, which connects to a different and more performing set of cell towers. This…

Signed Diego

13 Jan 2026, 12:56 UTC744 viewsread 8 August 2026

⚠️ S6 PROXIES DOWN s6.airproxy.io proxies are currently down due to a power outage in the area that lead to the discharge of the UPS batteries. We are heading to the location to power up the diesel generator. Proxies are expected to come up in 45 minutes. ✅ SOLVED

Signed Diego

25 Nov 2025, 12:20 UTC879 viewsread 8 August 2026

⚠️ S3 PROXIES DOWN s3.airproxy.io proxies are currently down due to a power outage in the area that lead to the discharge of the UPS batteries. We are heading to the location to power up the diesel generator. Proxies are expected to come up in 20 minutes. ✅ SOLVED

Signed Diego

24 Sept 2025, 07:49 UTC≈1,300 viewsread 8 August 2026

⚠️ S6 PROXIES DOWN s6.airproxy.io proxies are currently down due to a power outage in the area that lead to the discharge of the UPS batteries. We are heading to the location to power up the diesel generator. Proxies are expected to come up in 30-40 minutes. ✅ SOLVED

Signed Diego

21 Aug 2025, 10:33 UTC≈1,190 viewsread 8 August 2026

⚠️ OPERATORS ISSUE IN S1 & S6 We are seeing Wind, Iliad and Vodafone experiencing connectivity problems in the S1 and S6 areas, likely due to the storm currently ongoing. We see them going up and down during this time. We expect the issue to be solved shortly (within minutes or about an hour). ✅ SOLVED

Signed Diego

30 Jul 2025, 08:43 UTC≈1,220 viewsread 8 August 2026

⚠️ We are seeing s3 offline. Staff is on the way to check/fix. EDIT: solved ✅

Signed Diego

Showing the 12 most recent of 20 posts we hold for @airproxyinfo. 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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“AirProxy” (@airproxyinfo), 635 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/airproxyinfo.

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.