IP Address Migration Plan – SkyPro Hong Kong Following a notice from our upstream network provider, the current IP address range used in the SkyPro Hong Kong region will be fully replaced. To ensure a smooth transition for your services, we have outlined the following IP address migration plan: From now until August 26, 2026 (inclusive): If you are ready to proceed with the migration, please submit a ticket to requ…

Channel
SkyStroll Announcements
@SkyStroll
On this record: Growth · Engagement · Posts · Citations · Cite this entry
90subscribers
+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 | -1002420402789 |
|---|---|
| Type | Channel |
| Username | @SkyStroll |
| 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 | 7 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 7 times, most recently 7 October 2026 |
| On Telegram | t.me/SkyStroll |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 03:45 | 90 | +1 |
| 9 Aug 2026, 15:17 | 89 | no change |
| 7 Aug 2026, 15:16 | 89 | first reading |
Engagement
20 posts held, back to 4 August 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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Maintenance has been completed, and all customer instances have been restarted. The Service Downtime Compensation is now available for claim. If you have any question, feel free to submit a ticket.
Emergency Maintenance - SkyLite / SkyPro Product Line The Linux community and major security agencies have disclosed a critical high-risk vulnerability (CVE-2026-53359) in the Linux kernel KVM/x86 virtualization module. To ensure the security of your business environment and data, we have initiated emergency maintenance. This maintenance involves upgrading the kernel patches on the underlying compute nodes affected…
IP Address Change Completed – SkyLite Tokyo The IP address change for the SkyLite Tokyo region has been fully completed. This update only involves IPv4 addresses; IPv6 addresses remain unchanged. Please log in to the console to view the new IP address of your instance. If your instance is no longer accessible using the previous IP address, you can try the following methods: - Restart the instance in the console, s…
IP Address Migration Plan – SkyLite Tokyo Following a notice from our upstream network provider, the current IP address range used in the SkyLite Tokyo region will be fully replaced. To ensure a smooth transition for your services, we have outlined the following IP address migration plan: From now until July 5, 2026 (inclusive): If you are ready to proceed with the migration, please submit a support ticket to reque…
Network Outage Notice - Tokyo Region Dear customers, Due to an unexpected equipment failure at our upstream network provider, all services in the Tokyo region experienced a temporary network outage, which has now been fully restored. The affected product lines and scope are as follows (UTC time): SkyPro Tokyo: 2026-06-14 15:52 ~ 2026-06-14 17:36, affected for approximately 1 hour 44 minutes SkyLite Tokyo: 2026-06-…
Notice Regarding Adjustments to Wallet Balance Withdrawal Fees The withdrawal fee for wallet balances has been reduced from the previous 10% (minimum $5) to a minimum of $2. For the currently supported withdrawal methods, withdrawal fees are not calculated as a percentage of the amount; instead, the fee amount is set based solely on actual costs. Actual fees are subject to the amount displayed at the time of the w…
SkyPro TYO Alpha have been restocked. Purchase link: https://skystroll.net/store/skypro-tyo?product=38 If you encounter high latency, low peak speeds (<100Mbps), or abnormal packet loss when accessing mainland China, please submit a ticket to contact us. We will evaluate whether optimization adjustments are possible. When submitting a ticket, please be sure to specify the exact IP address where the issue occurred a…
The SkyPro TYO Alpha product is currently sold out. We are keeping in touch with our suppliers to request additional IP addresses. We have resolved the issue of missing routes related to China Telecom in certain regions. We have also optimized and adjusted abnormal connection speeds in regions such as Guangdong, Henan, and Jiangxi province. If you still experiencing issues, please submit a support ticket to contact …
SkyStroll Product Update We're thrilled to announce that our highly anticipated SkyPro series has officially landed in the Asia 2 (Tokyo) region! Building on the SkyPro series' core focus on China-optimized connectivity, our new Tokyo location delivers an uncompromising network experience. With up to 10 Gbps global peak bandwidth and premium routing specifically tailored for mainland China, SkyPro guarantees low-la…
This incident has been resolved. The Service Downtime Compensation will be available in a few days. If you have any question, feel free to submit a ticket.
Service Outage Notice - Tokyo Region Network Issue Dear Customers, At approximately 11:15 (UTC), due to an unexpected equipment failure at our upstream network provider, the SkyLite Tokyo region and SkyRack Tokyo region were affected. Some servers may be unreachable, unstable, or experiencing increased latency. We have confirmed that other regions and services are not affected. We are in close communication with …
Showing the 12 most recent of 20 posts we hold for @SkyStroll. 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.
Mentions
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“SkyStroll Announcements” (@SkyStroll), 90 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/SkyStroll.
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.