История сбоев Pagely

1. 17 августа 2026 г. в 21:22 UTCinvestigating

   В настоящее время мы расследуем сообщения о проблемах, входящих в панель управления Pagely Atomic.

2. 17 августа 2026 г. в 23:22 UTCinvestigating

   Мы все еще расследуем проблемы входа в систему, влияющие на панель управления Атомной. Скоро у нас будет еще одно обновление.

3. 17 августа 2026 г. в 23:58 UTCmonitoring

   Мы внедрили исправление, и вход в панель управления Атомной теперь работает нормально. Клиенты должны иметь возможность войти, как и ожидалось; если вы продолжаете испытывать проблемы, пожалуйста, очистите кэш браузера или попробуйте снова в ближайшее время. Мы продолжим следить за тем, чтобы проблема была полностью решена. Спасибо за ваше терпение, пока мы работали над этим.

4. 18 августа 2026 г. в 00:16 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 17 июня 2026 г. в 12:18 UTCidentified

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

2. 17 июня 2026 г. в 12:21 UTCmonitoring

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

3. 17 июня 2026 г. в 12:47 UTCresolved

   This incident has been resolved.

1. 10 июня 2026 г. в 11:56 UTCinvestigating

   We are currently investigating this issue.

2. 10 июня 2026 г. в 12:34 UTCmonitoring

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

3. 10 июня 2026 г. в 13:06 UTCresolved

   This incident has been resolved.

1. 4 июня 2026 г. в 13:11 UTCinvestigating

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

2. 4 июня 2026 г. в 14:18 UTCinvestigating

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

3. 4 июня 2026 г. в 14:38 UTCidentified

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

4. 4 июня 2026 г. в 14:44 UTCmonitoring

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

5. 4 июня 2026 г. в 17:11 UTCresolved

   This incident has been resolved.

1. 13 мая 2026 г. в 22:56 UTCinvestigating

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

2. 14 мая 2026 г. в 00: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 мая 2026 г. в 01:24 UTCresolved

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

1. 8 мая 2026 г. в 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 мая 2026 г. в 21:34 UTCresolved

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

1. 8 мая 2026 г. в 01:26 UTCinvestigating

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

2. 8 мая 2026 г. в 01:51 UTCinvestigating

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

3. 8 мая 2026 г. в 02:52 UTCinvestigating

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

4. 8 мая 2026 г. в 04:56 UTCinvestigating

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

5. 8 мая 2026 г. в 07: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 мая 2026 г. в 07:50 UTCresolved

   This incident is now resolved.

1. 8 мая 2026 г. в 00: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 мая 2026 г. в 00: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 мая 2026 г. в 01: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 мая 2026 г. в 03: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 мая 2026 г. в 06: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 мая 2026 г. в 07:38 UTCmonitoring

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

7. 8 мая 2026 г. в 07:50 UTCresolved

   This incident is now resolved.

1. 30 апреля 2026 г. в 13:28 UTCinvestigating

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

2. 30 апреля 2026 г. в 13:58 UTCidentified

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

3. 30 апреля 2026 г. в 14:07 UTCidentified

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

4. 30 апреля 2026 г. в 14:35 UTCmonitoring

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

5. 30 апреля 2026 г. в 15:54 UTCmonitoring

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

6. 30 апреля 2026 г. в 16:35 UTCresolved

   Atomic is operating normally and this issue is now resolved.

1. 24 апреля 2026 г. в 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 апреля 2026 г. в 18:32 UTCidentified

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

3. 24 апреля 2026 г. в 19:54 UTCmonitoring

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

4. 24 апреля 2026 г. в 21:08 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 24 апреля 2026 г. в 21:41 UTCresolved

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

1. 10 февраля 2026 г. в 04: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 февраля 2026 г. в 15:54 UTCresolved

   New account signup issues are now resolved.

1. 4 декабря 2025 г. в 22:54 UTCinvestigating

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

2. 4 декабря 2025 г. в 23:38 UTCresolved

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

1. 2 декабря 2025 г. в 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 декабря 2025 г. в 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 декабря 2025 г. в 20:53 UTCresolved

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

1. 25 ноября 2025 г. в 15:56 UTCinvestigating

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

2. 25 ноября 2025 г. в 18:26 UTCinvestigating

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

3. 25 ноября 2025 г. в 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 ноября 2025 г. в 01:36 UTCresolved

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

1. 20 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 20:26 UTCmonitoring

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

4. 20 октября 2025 г. в 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 20 октября 2025 г. в 22:16 UTCresolved

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

1. 15 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 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 октября 2025 г. в 19:32 UTCidentified

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

5. 15 октября 2025 г. в 21:48 UTCidentified

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

6. 16 октября 2025 г. в 00: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 июля 2025 г. в 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 июля 2025 г. в 19:17 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 июля 2025 г. в 19:23 UTCmonitoring

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

4. 9 июля 2025 г. в 20:30 UTCresolved

   Authentication issues have been resolved.

1. 27 июня 2025 г. в 06: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 июня 2025 г. в 06:44 UTCmonitoring

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

3. 27 июня 2025 г. в 07:09 UTCinvestigating

   We are currently investigating this issue.

4. 27 июня 2025 г. в 08:12 UTCresolved

   This incident has been resolved.

1. 25 июня 2025 г. в 04:17 UTCinvestigating

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

2. 25 июня 2025 г. в 04:41 UTCmonitoring

   A fix has been implemented, chats and tickets have tested successfully, and we are monitoring to confirm the issue is resolved.

3. 25 июня 2025 г. в 05:30 UTCresolved

   Since the implemented fix, no further issues have been identified, issue is considered resolved.

1. 7 мая 2025 г. в 13:27 UTCinvestigating

   We are currently investigating an issue in the Atomic control panel where domains are unable to be promoted to an App's Primary Domain. We will provide additional details shortly.

2. 7 мая 2025 г. в 13:56 UTCinvestigating

   We are continuing to investigate this issue. This issue may also impact adding/removing domains from an App in Atomic.

3. 7 мая 2025 г. в 15:19 UTCidentified

   The root cause has been identified and a fix is being deployed.

4. 7 мая 2025 г. в 16:03 UTCmonitoring

   A fix has been deployed and promoting/adding/and deleting domains should now be functioning as intended. We are continuing monitoring for any further issues.

5. 7 мая 2025 г. в 16:24 UTCresolved

   This incident has been resolved.