Historial de interrupciones de Pagely

1. 22 de octubre de 2026 a las 9:49 UTCinvestigating

   Pagely Development team is aware of and investigating sporadic errors related to the Atomic dashboard such as this "Hubo un problema con una llamada de API... por favor, consulte a un desarrollador a "Request ID ...". Debe recargar la aplicación" Se proporcionará información actualizada sobre esta cuestión lo antes posible.

2. 22 de octubre de 2026 a las 11:44 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 22 de octubre de 2026 a las 14:03 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de octubre de 2026 a las 14:14 UTCinvestigating

   Usted puede ser consciente de las vulnerabilidades de PHP críticas recientes (https://www.php.net/archive/2026.php#2026-10-21-5) que tienen un parche en progreso del equipo de desarrollo de PHP. Pagely es muy consciente de este asunto y estará aplicando las versiones de PHP parcheadas a los servidores de clientes una vez que esté disponible. No se necesitan acciones de nuestros clientes en esta actualización de PHP. Pronto se publicarán más actualizaciones.

2. 21 de octubre de 2026 a las 14:21 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 21 de octubre de 2026 a las 14:34 UTCinvestigating

   Durante la noche, desplegamos algunas atenuaciones, y estamos construyendo contenedores PHP actualizados con las soluciones completas ahora.

4. 21 de octubre de 2026 a las 18:51 UTCresolved

   Pagely has completed the deployment of PHP security updates across customer servers to address the recently disclosed critical remote code execution vulnerabilities. No further action is required from customers regarding this update. This advisory is now resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de agosto de 2026 a las 21:22 UTCinvestigating

   Actualmente estamos investigando informes de problemas que se registran en el panel de control Pagely Atomic.

2. 17 de agosto de 2026 a las 23:22 UTCinvestigating

   Todavía estamos investigando los problemas de inicio de sesión que afectan al panel de control atómico. Tendremos otra actualización en breve.

3. 17 de agosto de 2026 a las 23:58 UTCmonitoring

   Hemos implementado una solución y los logins al panel de control atómico están trabajando normalmente. Los clientes deben poder iniciar sesión como se espera; si continúa experimentando problemas, por favor, despeje el caché de su navegador o inténtelo de nuevo en breve. Seguiremos monitoreando para asegurar que el problema se resuelva completamente. Gracias por su paciencia mientras trabajamos a través de esto.

4. 18 de agosto de 2026 a las 0:16 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de junio de 2026 a las 12:18 UTCidentified

   Users may experience errors when clearing cache. We have identified the issue and are working to resolve it.

2. 17 de junio de 2026 a las 12:21 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 17 de junio de 2026 a las 12:47 UTCresolved

   This incident has been resolved.

1. 10 de junio de 2026 a las 11:56 UTCinvestigating

   We are currently investigating this issue.

2. 10 de junio de 2026 a las 12:34 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10 de junio de 2026 a las 13:06 UTCresolved

   This incident has been resolved.

1. 4 de junio de 2026 a las 13:11 UTCinvestigating

   We are currently investigating reports of issues with Atomic that may impact control actions in the dashboard including authentication

2. 4 de junio de 2026 a las 14:18 UTCinvestigating

   Our team is continuing to investigate the root cause and work towards service restoration.

3. 4 de junio de 2026 a las 14:38 UTCidentified

   The issue has been identified and a fix is being implemented.

4. 4 de junio de 2026 a las 14:44 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 4 de junio de 2026 a las 17:11 UTCresolved

   This incident has been resolved.

1. 13 de mayo de 2026 a las 22:56 UTCinvestigating

   We’re investigating problems with Let’s Encrypt certificate issuance.

2. 14 de mayo de 2026 a las 0:59 UTCinvestigating

   We are continuing to investigate the issue with Let’s Encrypt certificate creation and the issue currently is intermittent. We will provide further updates shortly.

3. 14 de mayo de 2026 a las 1:24 UTCresolved

   New Let’s Encrypt certificates are issuing properly and this issue is now resolved.

1. 8 de mayo de 2026 a las 20:26 UTCinvestigating

   We’re investigating reports of problems issuing Let’s Encrypt certificates. This appears tied to Let’s Encrypt pausing issuance while they investigate; we’re monitoring their status page and will update as we learn more. Status page can be found via the following link for Let's Encrypt: https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3

2. 8 de mayo de 2026 a las 21:34 UTCresolved

   Let's Encrypt have corrected the issues on their side, and customers can again request LE certificates through Atomic.

1. 8 de mayo de 2026 a las 1:26 UTCinvestigating

   We are currently investigating issues with Atomic logins. We will provide more information shortly.

2. 8 de mayo de 2026 a las 1:51 UTCinvestigating

   This issue would also affect cron task execution and we are investigating this as well.

3. 8 de mayo de 2026 a las 2:52 UTCinvestigating

   We’re continuing to troubleshoot Atomic and will share additional details as they become available.

4. 8 de mayo de 2026 a las 4:56 UTCinvestigating

   Atomic remains unavailable while we continue investigation and remediation; we’ll share additional details as they become available.

5. 8 de mayo de 2026 a las 7:34 UTCmonitoring

   We identified and resolved the networking issue, and Atomic access has been restored. Scheduled cron jobs are also running normally again. We will resolve this incident if our monitoring continues to look normal.

6. 8 de mayo de 2026 a las 7:50 UTCresolved

   This incident is now resolved.

1. 8 de mayo de 2026 a las 0:05 UTCinvestigating

   We are investigating an issue affecting a subset of EC2 instances in AWS US East (Virginia). Those instances are temporarily unreachable while we determine root cause.

2. 8 de mayo de 2026 a las 0:41 UTCidentified

   We have identified the affected EC2 instances in AWS. Reboots have been started on all of them while we continue to confirm recovery. Additional updates will be provided shortly.

3. 8 de mayo de 2026 a las 1:01 UTCidentified

   A few hosts still show EBS volume issues that prevent a full restart; we are actively fixing those and continuing investigation alongside the broader recovery work.

4. 8 de mayo de 2026 a las 3:00 UTCidentified

   A small number of instances still have an EBS-related issue we’re actively investigating, and all other instances, those not affected by this problem, have been back to normal for some time now.

5. 8 de mayo de 2026 a las 6:19 UTCidentified

   We’ve restored several EBS volumes and brought associated EC2 instances back online; work is still in progress on the remaining instances, and we’ll share another update shortly.

6. 8 de mayo de 2026 a las 7:38 UTCmonitoring

   All affected instances are now restored and we continue to monitor for any issues.

7. 8 de mayo de 2026 a las 7:50 UTCresolved

   This incident is now resolved.

1. 30 de abril de 2026 a las 13:28 UTCinvestigating

   Our Operations and Development team are currently investigating an issue with login failures to Atomic

2. 30 de abril de 2026 a las 13:58 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 30 de abril de 2026 a las 14:07 UTCidentified

   We are continuing to work on a fix for this issue.

4. 30 de abril de 2026 a las 14:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 30 de abril de 2026 a las 15:54 UTCmonitoring

   Additional fixes are being applied to address issues affecting parts of the Atomic interface

6. 30 de abril de 2026 a las 16:35 UTCresolved

   Atomic is operating normally and this issue is now resolved.

1. 24 de abril de 2026 a las 17:16 UTCinvestigating

   We are currently investigating issues with new account provisioning. Our technical teams have been alerted and are actively working to determine the cause and implement a resolution.

2. 24 de abril de 2026 a las 18:32 UTCidentified

   The issue has been identified with provisioning and the team is applying a fix.

3. 24 de abril de 2026 a las 19:54 UTCmonitoring

   Fix has been applied and we are waiting for our queue processing to normalize. Will provide additional updates shortly.

4. 24 de abril de 2026 a las 21:08 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 de abril de 2026 a las 21:41 UTCresolved

   Provisioning flow is operating normally and this issue is now resolved.

1. 10 de febrero de 2026 a las 4:03 UTCinvestigating

   Our team is aware of an issue that is impacting new account and new plan registrations in Atomic. We are actively investigating.

2. 10 de febrero de 2026 a las 15:54 UTCresolved

   New account signup issues are now resolved.

1. 4 de diciembre de 2025 a las 22:54 UTCinvestigating

   We are currently investigating an issue with our payment processor preventing payments and affecting new sign-ups.

2. 4 de diciembre de 2025 a las 23:38 UTCresolved

   Our payment processor addressed the issue with failed transactions and this issue is now resolved.

1. 2 de diciembre de 2025 a las 18:37 UTCinvestigating

   We are investigating an issue impacting a subset of our shared-hosting customers. Details will be added as they become available.

2. 2 de diciembre de 2025 a las 19:06 UTCmonitoring

   Our engineering team identified a surge of requests to certain web nodes on our shared hosting infrastructure. We have mitigated some of the requests and continue to monitor the issue. At the moment, all web nodes are operating normally and we expect to resolve this incident shortly.

3. 2 de diciembre de 2025 a las 20:53 UTCresolved

   We have not seen any further issues with our shared hosting environment and this incident is now resolved.

1. 25 de noviembre de 2025 a las 15:56 UTCinvestigating

   We are currently investigating an issue with our payment processor preventing payments and affecting new sign-ups.

2. 25 de noviembre de 2025 a las 18:26 UTCinvestigating

   We are in contact with our payment processor and will provide further updates shortly.

3. 25 de noviembre de 2025 a las 22:10 UTCinvestigating

   We continue to work with our payment processor on a resolution and will post further updates when we have more information.

4. 26 de noviembre de 2025 a las 1:36 UTCresolved

   The issue with the payment processor has been fixed and this issue is now resolved.

1. 20 de octubre de 2025 a las 10:08 UTCmonitoring

   We are currently experiencing degraded performance across some of our services due to an ongoing outage affecting the AWS US-East (Virginia) region. Our engineering team is actively monitoring the situation and working to mitigate the impact. We will provide updates as more information becomes available.

2. 20 de octubre de 2025 a las 15:24 UTCmonitoring

   We are continuing to monitor this issue. AWS still is reporting intermittent issues, but we are not aware of any impact to Pagely customers at this time.

3. 20 de octubre de 2025 a las 20:26 UTCmonitoring

   Pagely is continuing to monitor, but at this time we believe there are no outstanding issues.

4. 20 de octubre de 2025 a las 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20 de octubre de 2025 a las 22:16 UTCresolved

   This incident is now resolved as we have not seen any further issues related to this incident.

1. 15 de octubre de 2025 a las 15:50 UTCinvestigating

   We are currently investigating reports of delays in account provisioning for new users. Our technical teams have been alerted and are actively working to determine the cause and implement a resolution.

2. 15 de octubre de 2025 a las 16:35 UTCidentified

   We have identified the potential root cause of the account provisioning delays. Our team is implementing a fix to restore normal provisioning operations. We will update as soon as all systems are functioning as expected.

3. 15 de octubre de 2025 a las 17:46 UTCidentified

   A fix has been released to address the delays in account provisioning and we are continuing to work on resolving this issue. Further updates will be provided shortly.

4. 15 de octubre de 2025 a las 19:32 UTCidentified

   Additional fixes are still being worked on and we will continue to provide updates until this issue is resolved.

5. 15 de octubre de 2025 a las 21:48 UTCidentified

   We have found additional endpoints that need to be fixed and we continue to make progress to a resolution.

6. 16 de octubre de 2025 a las 0:44 UTCresolved

   This incident has been resolved. Account provisioning services are now operating normally. Our team has confirmed that new account creation is functioning as expected.

1. 9 de julio de 2025 a las 19:14 UTCinvestigating

   We are currently having issues with authentication. This impacts users logging into Atomic, performing certain config changes, and executing CI/CD workflows. We are actively investigating.

2. 9 de julio de 2025 a las 19:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 de julio de 2025 a las 19:23 UTCmonitoring

   We have implemented a fix for this issue, and are continuing to monitor.

4. 9 de julio de 2025 a las 20:30 UTCresolved

   Authentication issues have been resolved.

1. 27 de junio de 2025 a las 6:35 UTCinvestigating

   An issue has been identified preventing the Atomic interface from communicating with other systems, including apps dashboard. We are currently investigating.

2. 27 de junio de 2025 a las 6:44 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 de junio de 2025 a las 7:09 UTCinvestigating

   We are currently investigating this issue.

4. 27 de junio de 2025 a las 8:12 UTCresolved

   This incident has been resolved.