en
Feedback
AperNet

AperNet

Open in Telegram
1 106
Subscribers
No data24 hours
-17 days
-830 days
Posts Archive
AperNet
1 106
🎄

AperNet
1 106
[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/

AperNet
1 106
We have finished the maintenance.

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
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

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
[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

AperNet
1 106
[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.

AperNet
1 106
[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.

AperNet
1 106
Gift
x8

Prizes of the draw

8 Telegram Premium subscriptions for 12 months

Completion date

AperNet
1 106
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

AperNet
1 106
photo content

AperNet
1 106
Maintenance completed. Some routing issues will be fixed in a few hours.

AperNet
1 106
An error occurred during the software update, our engineer is on the way to the datacenter.

AperNet
1 106
[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.