AperNet
Open in Telegram
https://hosting.apernet.io https://new.apernet.io
Show moreThe country is not specifiedTechnologies & Applications36 748
1 106
Subscribers
No data24 hours
-17 days
-830 days
Data loading in progress...
Similar Channels
Tags Cloud
No data
Any problems? Please refresh the page or contact our support manager.
Incoming and Outgoing Mentions
---
---
---
---
---
---
Attracting Subscribers
March '25
March '25
+2
in 0 channels
February '25
+7
in 0 channels
Get PRO
January '25
+8
in 0 channels
Get PRO
December '24
+12
in 0 channels
Get PRO
November '24
+12
in 0 channels
Get PRO
October '24
+7
in 0 channels
Get PRO
September '24
+12
in 0 channels
Get PRO
August '24
+5
in 0 channels
Get PRO
July '24
+23
in 0 channels
Get PRO
June '24
+31
in 0 channels
Get PRO
May '24
+29
in 0 channels
Get PRO
April '24
+44
in 0 channels
Get PRO
March '24
+39
in 1 channels
Get PRO
February '24
+58
in 0 channels
Get PRO
January '24
+25
in 0 channels
Get PRO
December '23
+22
in 0 channels
Get PRO
November '23
+2
in 0 channels
Get PRO
October '23
+31
in 0 channels
Get PRO
September '23
+26
in 0 channels
Get PRO
August '23
+19
in 0 channels
Get PRO
July '23
+21
in 0 channels
Get PRO
June '23
+15
in 0 channels
Get PRO
May '23
+36
in 0 channels
Get PRO
April '23
+34
in 0 channels
Get PRO
March '23
+29
in 0 channels
Get PRO
February '23
+35
in 0 channels
Get PRO
January '23
+59
in 0 channels
Get PRO
December '22
+114
in 0 channels
Get PRO
November '22
+65
in 0 channels
Get PRO
October '22
+28
in 0 channels
Get PRO
September '22
+44
in 0 channels
Get PRO
August '22
+38
in 0 channels
Get PRO
July '22
+20
in 0 channels
Get PRO
June '22
+43
in 0 channels
Get PRO
May '22
+36
in 0 channels
Get PRO
April '22
+57
in 0 channels
Get PRO
March '22
+46
in 0 channels
Get PRO
February '22
+27
in 0 channels
Get PRO
January '22
+68
in 0 channels
Get PRO
December '21
+46
in 0 channels
Get PRO
November '21
+247
in 0 channels
| Date | Subscriber Growth | Mentions | Channels | |
| 24 March | +1 | |||
| 23 March | 0 | |||
| 22 March | 0 | |||
| 21 March | 0 | |||
| 20 March | 0 | |||
| 19 March | 0 | |||
| 18 March | 0 | |||
| 17 March | 0 | |||
| 16 March | 0 | |||
| 15 March | 0 | |||
| 14 March | 0 | |||
| 13 March | 0 | |||
| 12 March | 0 | |||
| 11 March | 0 | |||
| 10 March | 0 | |||
| 09 March | 0 | |||
| 08 March | 0 | |||
| 07 March | 0 | |||
| 06 March | 0 | |||
| 05 March | 0 | |||
| 04 March | 0 | |||
| 03 March | 0 | |||
| 02 March | 0 | |||
| 01 March | +1 |
Channel Posts
| 2 | [Announcement: Tokyo VPS (Basic) is Online Now]
Order our new Tokyo VPS instance: https://new.apernet.io/store/tokyo-vps-basic
Highlights:
AMD® EPYC® 7C13 Processor(s) vCPU
DDR4 2666MHz ECC RAM
NVME Storage
10 Gbps Bandwidth (Shared)
Basic Internet Routing Profile
Routed /64 IPv6 Subnet
Upstream:
PCCW / Equinix Internet Exchange Tokyo
Demo Site:
http://basic.tyo.demo.apernet.io/ | 1 108 |
| 3 | We have finished the maintenance. | 878 |
| 4 | [Maintenance: San Jose VPS]
Scheduled Window
2024-11-17 6:00 AM - 7:00 AM UTC +8
Impact
Some VPS with CPU model EPYC 7T83 will be offline for a while and rebooted. | 835 |
| 5 | [Service outage: Hong Kong]
We observed that IP forwarding on one of our core routers is not working correctly, causing a service outage.
An emergency reboot will be issued, and the service will then gradually recover.
We expect a 15-minute interruption for all HK services.
We apologize for any inconvenience you may experience during this incident. We thank you for your long-term trust and support. | 1 122 |
| 6 | [Outage: Hong Kong]
NOC observed that a junos VM that runs in one of our core routers has rebooted unexpectedly. The root cause is still under investigation.
The VM has been automatically restarted and the network is now recovering. Some more time is needed for the routing protocol to converge.
We apologize for any inconvenience you may experience during this incident. We thank you for your long-term trust and support.
Should you have any questions or concerns, please feel free to open a ticket to our support team. | 865 |
| 7 | [Scheduled Maintenance: Router Maintenance at San Jose]
Scheduled Window
2024-07-11 11:00 AM - 12:00 PM UTC +8
Impact
Please expect total black out of our San Jose site - we are performing router hardware replacement. | 1 526 |
| 8 | USER ACTION NEEDED - RCE in OpenSSH's server, on glibc-based Linux systems (CVE-2024-6387)
Oneline summary:
You need to upgrade your OpenSSH server.
What is the issue?
As disclosed in https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt, a vulnerability in OpenSSH's server has been discovered. This vulnerability allows an attacker to execute arbitrary code on the server, with the privileges of the user running the OpenSSH server.
Version Impacted:
- OpenSSH < 4.4p1 is vulnerable
- 4.4p1 <= OpenSSH < 8.5p1 is not vulnerable
- 8.5p1 <= OpenSSH < 9.8p1 is vulnerable | 1 769 |
| 9 | [Service outage: Hong Kong]
We observed that IP forwarding on one of our core routers is not working correctly, causing a service outage.
An emergency reboot will be issued, and the service will then gradually recover.
We expect a 15-minute interruption for all HK services.
We apologize for any inconvenience you may experience during this incident. We thank you for your long-term trust and support. | 1 352 |
| 10 | [Scheduled Maintenance: Hypervisor Hardware Maintenance at San Jose]
Scheduled Window
2024-06-16 05:00 AM - 06:00 AM UTC +8
Affected Products
VPS products with CPU model AMD EPYC 7T83
We are replacing a faulty SSD in our storage array - user data will not be affected.
Please expect your server to be rebooted. | 1 629 |
| 11 | [Incident: Hong Kong Light VPS]
We observed our virtualization platform that supports Light VPS was misfunctioning and the root is proven as the default configuration of corosync is too aggressive. Services are now back online.
Some of the influenced VPS was powered off during the diagnostic and some auxiliary services were also restarted.
You may need to check the status of your VPS at the user portal. If you have any issues, please don't hesitate to submit a support ticket.
We apologize for any inconvenience you may have experienced during this incident. We appreciate your long-term trust and support. | 2 468 |
| 12 | [Scheduled Maintenance: Router Topology Change at San Jose]
[What] We have determined a topology bottleneck in our network. To fix this issue, a reboot of the core router is required. The estimate down time should be less than 10 minutes. This change will improve network performance and reduce packet losses during peak hours.
[When] 2024-03-03 6:00 AM UTC +8 | 2 554 |
| 13 | [Outage: Unexpected Hypervisor Reboot at San Jose]
A bug has caused an unexpected hypervisor reboot, which impacted VPS users on a single node (CPU Model: AMD EPYC 7T83).
All impacted VMs have been rebooted. Please manually restore any service that has no persistent configuration. | 2 453 |
| 14 | [Outage: Hong Kong distribution switch reboot]
The NOC has observed a group of ethernet interfaces is flapping, causing packet-dropping issues. NOC checked and replaced the relevant cable and transceiver but the issue continued. An emergency reboot has been issued.
The network performance might be influenced, and some services might be interrupted for a short time.
We apologize for any inconvenience you may experience during this incident. We thank you for your long-term trust and support. | 2 025 |
| 15 |  Prizes of the draw: 8 Telegram Premium subscriptions for 12 months | 2 053 |
| 16 | Dear AperNet Customers,
Wishing you and your family a joyous Lunar New Year filled with prosperity and happiness. May this season bring you success, good health, and fulfilment.
Happy New Year!🎆
Management Team | 1 716 |
| 17 |  No text... | 2 189 |
| 18 | Maintenance completed. Some routing issues will be fixed in a few hours. | 1 927 |
| 19 | An error occurred during the software update, our engineer is on the way to the datacenter. | 1 889 |
| 20 | [maintenance: Hong Kong core router reboot and software update]
WHEN: 2024-01-11 05:00-06:00 AM UTC+8
WHO: All Hong Kong Service Customers
WHAT: We have identified a FIB/RIB desynchronization issue affecting our core router in Hong Kong. A software update is required to solve it. The maintenance should take approximately 40 minutes.
IMPORTANT: Services will be interrupted during the maintenance. | 1 885 |
