51 Pagely incidents · 2022年2月 — official updates, affected components, duration and resolution details.
我们正在调查关于 向Pagely原子控制小组报告的问题.
我们还在调查 影响原子控制板的登录问题 我们很快就会有另一个更新.
我们已经执行了一个固定 登录原子控制板 现在正常工作。 客户应该能够按预期报名;如果继续遇到麻烦,请清除您的浏览器缓存或很快再次尝试. 我们将继续监督,确保问题得到全面解决. 谢谢你的耐心 在我们工作期间.
这一事件已经得到解决.
自动翻译自官方事件更新。
Users may experience errors when clearing cache. We have identified the issue and are working to resolve it.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports of issues with Atomic that may impact control actions in the dashboard including authentication
Our team is continuing to investigate the root cause and work towards service restoration.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We’re investigating problems with Let’s Encrypt certificate issuance.
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.
New Let’s Encrypt certificates are issuing properly and this issue is now resolved.
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
Let's Encrypt have corrected the issues on their side, and customers can again request LE certificates through Atomic.
We are currently investigating issues with Atomic logins. We will provide more information shortly.
This issue would also affect cron task execution and we are investigating this as well.
We’re continuing to troubleshoot Atomic and will share additional details as they become available.
Atomic remains unavailable while we continue investigation and remediation; we’ll share additional details as they become available.
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.
This incident is now resolved.
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.
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.
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.
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.
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.
All affected instances are now restored and we continue to monitor for any issues.
This incident is now resolved.
Our Operations and Development team are currently investigating an issue with login failures to Atomic
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
Additional fixes are being applied to address issues affecting parts of the Atomic interface
Atomic is operating normally and this issue is now resolved.
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.
The issue has been identified with provisioning and the team is applying a fix.
Fix has been applied and we are waiting for our queue processing to normalize. Will provide additional updates shortly.
We are continuing to monitor for any further issues.
Provisioning flow is operating normally and this issue is now resolved.
Our team is aware of an issue that is impacting new account and new plan registrations in Atomic. We are actively investigating.
New account signup issues are now resolved.
We are currently investigating an issue with our payment processor preventing payments and affecting new sign-ups.
Our payment processor addressed the issue with failed transactions and this issue is now resolved.
We are investigating an issue impacting a subset of our shared-hosting customers. Details will be added as they become available.
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.
We have not seen any further issues with our shared hosting environment and this incident is now resolved.
We are currently investigating an issue with our payment processor preventing payments and affecting new sign-ups.
We are in contact with our payment processor and will provide further updates shortly.
We continue to work with our payment processor on a resolution and will post further updates when we have more information.
The issue with the payment processor has been fixed and this issue is now resolved.
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.
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.
Pagely is continuing to monitor, but at this time we believe there are no outstanding issues.
We are continuing to monitor for any further issues.
This incident is now resolved as we have not seen any further issues related to this incident.
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.
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.
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.
Additional fixes are still being worked on and we will continue to provide updates until this issue is resolved.
We have found additional endpoints that need to be fixed and we continue to make progress to a resolution.
This incident has been resolved. Account provisioning services are now operating normally. Our team has confirmed that new account creation is functioning as expected.
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.
We are continuing to investigate this issue.
We have implemented a fix for this issue, and are continuing to monitor.
Authentication issues have been resolved.
An issue has been identified preventing the Atomic interface from communicating with other systems, including apps dashboard. We are currently investigating.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
This incident has been resolved.
An issue has been identified preventing the Atomic interface from communicating with other systems, including support. We are currently investigating.
A fix has been implemented, chats and tickets have tested successfully, and we are monitoring to confirm the issue is resolved.
Since the implemented fix, no further issues have been identified, issue is considered resolved.
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.
We are continuing to investigate this issue. This issue may also impact adding/removing domains from an App in Atomic.
The root cause has been identified and a fix is being deployed.
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.
This incident has been resolved.