AperNet
Ir al canal en Telegram
https://hosting.apernet.io https://new.apernet.io
Mostrar másEl país no está especificadoTecnologías y Aplicaciones36 748
1 106
Suscriptores
Sin datos24 horas
-17 días
-830 días
Carga de datos en curso...
Canales Similares
Nube de Etiquetas
Sin datos
¿Algún problema? Por favor, actualice la página o contacte a nuestro gerente de soporte.
Menciones Entrantes y Salientes
---
---
---
---
---
---
Atraer Suscriptores
marzo '25
marzo '25
+2
en 0 canales
febrero '25
+7
en 0 canales
Get PRO
enero '25
+8
en 0 canales
Get PRO
diciembre '24
+12
en 0 canales
Get PRO
noviembre '24
+12
en 0 canales
Get PRO
octubre '24
+7
en 0 canales
Get PRO
septiembre '24
+12
en 0 canales
Get PRO
agosto '24
+5
en 0 canales
Get PRO
julio '24
+23
en 0 canales
Get PRO
junio '24
+31
en 0 canales
Get PRO
mayo '24
+29
en 0 canales
Get PRO
abril '24
+44
en 0 canales
Get PRO
marzo '24
+39
en 1 canales
Get PRO
febrero '24
+58
en 0 canales
Get PRO
enero '24
+25
en 0 canales
Get PRO
diciembre '23
+22
en 0 canales
Get PRO
noviembre '23
+2
en 0 canales
Get PRO
octubre '23
+31
en 0 canales
Get PRO
septiembre '23
+26
en 0 canales
Get PRO
agosto '23
+19
en 0 canales
Get PRO
julio '23
+21
en 0 canales
Get PRO
junio '23
+15
en 0 canales
Get PRO
mayo '23
+36
en 0 canales
Get PRO
abril '23
+34
en 0 canales
Get PRO
marzo '23
+29
en 0 canales
Get PRO
febrero '23
+35
en 0 canales
Get PRO
enero '23
+59
en 0 canales
Get PRO
diciembre '22
+114
en 0 canales
Get PRO
noviembre '22
+65
en 0 canales
Get PRO
octubre '22
+28
en 0 canales
Get PRO
septiembre '22
+44
en 0 canales
Get PRO
agosto '22
+38
en 0 canales
Get PRO
julio '22
+20
en 0 canales
Get PRO
junio '22
+43
en 0 canales
Get PRO
mayo '22
+36
en 0 canales
Get PRO
abril '22
+57
en 0 canales
Get PRO
marzo '22
+46
en 0 canales
Get PRO
febrero '22
+27
en 0 canales
Get PRO
enero '22
+68
en 0 canales
Get PRO
diciembre '21
+46
en 0 canales
Get PRO
noviembre '21
+247
en 0 canales
| Fecha | Crecimiento de Suscriptores | Menciones | Canales | |
| 24 marzo | +1 | |||
| 23 marzo | 0 | |||
| 22 marzo | 0 | |||
| 21 marzo | 0 | |||
| 20 marzo | 0 | |||
| 19 marzo | 0 | |||
| 18 marzo | 0 | |||
| 17 marzo | 0 | |||
| 16 marzo | 0 | |||
| 15 marzo | 0 | |||
| 14 marzo | 0 | |||
| 13 marzo | 0 | |||
| 12 marzo | 0 | |||
| 11 marzo | 0 | |||
| 10 marzo | 0 | |||
| 09 marzo | 0 | |||
| 08 marzo | 0 | |||
| 07 marzo | 0 | |||
| 06 marzo | 0 | |||
| 05 marzo | 0 | |||
| 04 marzo | 0 | |||
| 03 marzo | 0 | |||
| 02 marzo | 0 | |||
| 01 marzo | +1 |
Publicaciones del Canal
| 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 | Premios del sorteo: 8 suscripciones Premium de Telegram por 12 meses | 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 | Sin texto... | 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 |
