Pagely Outage History

Started Oct 21, 2026, 02:14 PM UTC· resolved Oct 21, 2026, 06:51 PM UTC

1. investigating Oct 21, 2026, 02:14 PM UTC

   You may we aware of the recent critical PHP vulnerabilities (https://www.php.net/archive/2026.php#2026-10-21-5) that have a patch in progress from the PHP team. Pagely is well aware of this matter and will be applying the patched PHP versions to customer servers once it is available. No actions are needed from our customers on this PHP upgrade. Further updates will be posted shortly.

2. investigating Oct 21, 2026, 02:21 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 21, 2026, 02:34 PM UTC

   Overnight, we deployed some mitigations, and we're building updated PHP containers with the full fixes now.

4. resolved Oct 21, 2026, 06:51 PM UTC

   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.

Read the full incident report →

Started Sep 04, 2026, 05:00 PM UTC· resolved Sep 04, 2026, 05:00 PM UTC

1. resolved Sep 04, 2026, 05:07 PM UTC

   Call quality issues that impacted our care representatives have been resolved. Thank you for your patience.

Read the full incident report →

Started Aug 17, 2026, 09:22 PM UTC· resolved Aug 18, 2026, 12:16 AM UTC

1. investigating Aug 17, 2026, 09:22 PM UTC

   We're currently investigating reports of issues logging in to the Pagely Atomic control panel.

2. investigating Aug 17, 2026, 11:22 PM UTC

   We're still investigating the login issues affecting the Atomic control panel. We will have another update shortly.

3. monitoring Aug 17, 2026, 11:58 PM UTC

   We've implemented a fix and logins to the Atomic control panel are now working normally. Customers should be able to sign in as expected; if you continue to experience trouble, please clear your browser cache or try again shortly. We'll continue to monitor to ensure the issue is fully resolved. Thank you for your patience while we worked through this.

4. resolved Aug 18, 2026, 12:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 17, 2026, 12:18 PM UTC· resolved Jun 17, 2026, 12:47 PM UTC

1. identified Jun 17, 2026, 12:18 PM UTC

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

2. monitoring Jun 17, 2026, 12:21 PM UTC

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

3. resolved Jun 17, 2026, 12:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2026, 11:56 AM UTC· resolved Jun 10, 2026, 01:06 PM UTC

1. investigating Jun 10, 2026, 11:56 AM UTC

   We are currently investigating this issue.

2. monitoring Jun 10, 2026, 12:34 PM UTC

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

3. resolved Jun 10, 2026, 01:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 04, 2026, 01:11 PM UTC· resolved Jun 04, 2026, 05:11 PM UTC

1. investigating Jun 04, 2026, 01:11 PM UTC

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

2. investigating Jun 04, 2026, 02:18 PM UTC

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

3. identified Jun 04, 2026, 02:38 PM UTC

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

4. monitoring Jun 04, 2026, 02:44 PM UTC

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

5. resolved Jun 04, 2026, 05:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 13, 2026, 10:56 PM UTC· resolved May 14, 2026, 01:24 AM UTC

1. investigating May 13, 2026, 10:56 PM UTC

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

2. investigating May 14, 2026, 12:59 AM UTC

   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. resolved May 14, 2026, 01:24 AM UTC

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

Read the full incident report →

Started May 08, 2026, 08:26 PM UTC· resolved May 08, 2026, 09:34 PM UTC

1. investigating May 08, 2026, 08:26 PM UTC

   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. resolved May 08, 2026, 09:34 PM UTC

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

Read the full incident report →

Started May 08, 2026, 01:26 AM UTC· resolved May 08, 2026, 07:50 AM UTC

1. investigating May 08, 2026, 01:26 AM UTC

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

2. investigating May 08, 2026, 01:51 AM UTC

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

3. investigating May 08, 2026, 02:52 AM UTC

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

4. investigating May 08, 2026, 04:56 AM UTC

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

5. monitoring May 08, 2026, 07:34 AM UTC

   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. resolved May 08, 2026, 07:50 AM UTC

   This incident is now resolved.

Read the full incident report →

Started May 08, 2026, 12:05 AM UTC· resolved May 08, 2026, 07:50 AM UTC

1. investigating May 08, 2026, 12:05 AM UTC

   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. identified May 08, 2026, 12:41 AM UTC

   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. identified May 08, 2026, 01:01 AM UTC

   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. identified May 08, 2026, 03:00 AM UTC

   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. identified May 08, 2026, 06:19 AM UTC

   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. monitoring May 08, 2026, 07:38 AM UTC

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

7. resolved May 08, 2026, 07:50 AM UTC

   This incident is now resolved.

Read the full incident report →

Started Apr 30, 2026, 01:28 PM UTC· resolved Apr 30, 2026, 04:35 PM UTC

1. investigating Apr 30, 2026, 01:28 PM UTC

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

2. identified Apr 30, 2026, 01:58 PM UTC

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

3. identified Apr 30, 2026, 02:07 PM UTC

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

4. monitoring Apr 30, 2026, 02:35 PM UTC

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

5. monitoring Apr 30, 2026, 03:54 PM UTC

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

6. resolved Apr 30, 2026, 04:35 PM UTC

   Atomic is operating normally and this issue is now resolved.

Read the full incident report →

Started Apr 24, 2026, 05:16 PM UTC· resolved Apr 24, 2026, 09:41 PM UTC

1. investigating Apr 24, 2026, 05:16 PM UTC

   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. identified Apr 24, 2026, 06:32 PM UTC

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

3. monitoring Apr 24, 2026, 07:54 PM UTC

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

4. monitoring Apr 24, 2026, 09:08 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Apr 24, 2026, 09:41 PM UTC

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

Read the full incident report →

Started Feb 10, 2026, 04:03 AM UTC· resolved Feb 10, 2026, 03:54 PM UTC

1. investigating Feb 10, 2026, 04:03 AM UTC

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

2. resolved Feb 10, 2026, 03:54 PM UTC

   New account signup issues are now resolved.

Read the full incident report →

Started Dec 04, 2025, 10:54 PM UTC· resolved Dec 04, 2025, 11:38 PM UTC

1. investigating Dec 04, 2025, 10:54 PM UTC

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

2. resolved Dec 04, 2025, 11:38 PM UTC

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

Read the full incident report →

Started Dec 02, 2025, 06:37 PM UTC· resolved Dec 02, 2025, 08:53 PM UTC

1. investigating Dec 02, 2025, 06:37 PM UTC

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

2. monitoring Dec 02, 2025, 07:06 PM UTC

   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. resolved Dec 02, 2025, 08:53 PM UTC

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

Read the full incident report →

Started Oct 20, 2025, 10:08 AM UTC· resolved Oct 20, 2025, 10:16 PM UTC

1. monitoring Oct 20, 2025, 10:08 AM UTC

   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. monitoring Oct 20, 2025, 11:25 AM UTC

   We are continuing to monitor for any further issues.

3. monitoring Oct 20, 2025, 03:24 PM UTC

   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.

4. monitoring Oct 20, 2025, 08:26 PM UTC

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

5. monitoring Oct 20, 2025, 10:14 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Oct 20, 2025, 10:16 PM UTC

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

Read the full incident report →

Started Oct 15, 2025, 03:50 PM UTC· resolved Oct 16, 2025, 12:44 AM UTC

1. investigating Oct 15, 2025, 03:50 PM UTC

   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. identified Oct 15, 2025, 04:35 PM UTC

   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. identified Oct 15, 2025, 05:46 PM UTC

   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. identified Oct 15, 2025, 07:32 PM UTC

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

5. identified Oct 15, 2025, 09:48 PM UTC

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

6. resolved Oct 16, 2025, 12:44 AM UTC

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

Read the full incident report →

Started Jul 09, 2025, 07:14 PM UTC· resolved Jul 09, 2025, 08:30 PM UTC

1. investigating Jul 09, 2025, 07:14 PM UTC

   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. investigating Jul 09, 2025, 07:17 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 09, 2025, 07:23 PM UTC

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

4. resolved Jul 09, 2025, 08:30 PM UTC

   Authentication issues have been resolved.

Read the full incident report →

Started Jun 27, 2025, 06:35 AM UTC· resolved Jun 27, 2025, 08:12 AM UTC

1. investigating Jun 27, 2025, 06:35 AM UTC

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

2. monitoring Jun 27, 2025, 06:44 AM UTC

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

3. investigating Jun 27, 2025, 07:09 AM UTC

   We are currently investigating this issue.

4. resolved Jun 27, 2025, 08:12 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 07, 2025, 01:27 PM UTC· resolved May 07, 2025, 04:24 PM UTC

1. investigating May 07, 2025, 01:27 PM UTC

   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. investigating May 07, 2025, 01:56 PM UTC

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

3. identified May 07, 2025, 03:19 PM UTC

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

4. monitoring May 07, 2025, 04:03 PM UTC

   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. resolved May 07, 2025, 04:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 31, 2025, 05:58 PM UTC· resolved Mar 31, 2025, 08:20 PM UTC

1. investigating Mar 31, 2025, 05:58 PM UTC

   We are currently investigating issues with the Atomic API and will have additional updates shortly.

2. investigating Mar 31, 2025, 06:04 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 31, 2025, 06:17 PM UTC

   We have identified an issue with an endpoint related to a gateway configuration change made earlier today. We expect the fix to be rolled out shortly.

4. identified Mar 31, 2025, 07:23 PM UTC

   Additional changes are being deployed to the gateway and we expect a resolution to this issue shortly.

5. monitoring Mar 31, 2025, 08:04 PM UTC

   We have reverted the changes and our API at this time is working as intended. We will continue to monitor this issue before marking this incident as resolved.

6. resolved Mar 31, 2025, 08:20 PM UTC

   As we mentioned in our last update we reverted changes to our gateway which affected the Atomic API. We have not seen any further issues and will mark this incident as resolved.

Read the full incident report →

Started Mar 24, 2025, 03:28 PM UTC· resolved Mar 24, 2025, 04:31 PM UTC

1. investigating Mar 24, 2025, 03:28 PM UTC

   We are currently investigating an issue with PressCDN purges returning API failures. We will provide additional details shortly.

2. monitoring Mar 24, 2025, 04:05 PM UTC

   Our team has identified the root of the issue. A fix has been implemented and PressCDN purges should now complete successfully. We are continuing monitoring for any further issues.

3. resolved Mar 24, 2025, 04:31 PM UTC

   This incident is now resolved. PressCDN purges should now complete successfully. Our team identified issues resulting from the earlier Atomic Control Panel Maintenance and we have taken the appropriate corrective action to restore functionality to API calls.

Read the full incident report →

Started Mar 21, 2025, 09:35 PM UTC· resolved Mar 21, 2025, 10:44 PM UTC

1. investigating Mar 21, 2025, 09:35 PM UTC

   Unfortunately the app provisioning issue persists after an initial fix. This is a new incident to track further progress on the issue.

2. monitoring Mar 21, 2025, 10:18 PM UTC

   Our team has identified the root of the issue. We have tested new provisioning and each app provision has been successful.

3. resolved Mar 21, 2025, 10:44 PM UTC

   This incident has been resolved. Our team identified a newly provisioned internal server that was collecting new app provision information which was not intended. We have corrected the issue and app provisioning is now directed to the proper internal server.

Read the full incident report →

Started Dec 31, 2024, 01:07 AM UTC· resolved Dec 31, 2024, 05:01 AM UTC

1. investigating Dec 31, 2024, 01:07 AM UTC

   We were alerted to an issue with the shared database vps-virginia-aurora-20 and are currently investigating the issues at this time.

2. identified Dec 31, 2024, 01:53 AM UTC

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

3. identified Dec 31, 2024, 02:52 AM UTC

   Our team is continuing to work with AWS to implement a fix at this time.

4. identified Dec 31, 2024, 03:57 AM UTC

   Our engineering team is actively working with AWS regarding issues with the database vps-virginia-aurora-20.

5. monitoring Dec 31, 2024, 04:46 AM UTC

   Our engineering team has restored vps-virginia-aurora-20 to a new database environment and sites are now able to connect to this new environment properly. We are still monitoring this new environment and site availability has been restored.

6. resolved Dec 31, 2024, 05:01 AM UTC

   The new database environment is working as expected and no further action is needed at this time. This incident has been resolved.

Read the full incident report →

Started Dec 18, 2024, 07:19 PM UTC· resolved Dec 18, 2024, 07:54 PM UTC

1. investigating Dec 18, 2024, 07:19 PM UTC

   We are currently investigating availability issues with our shared instances web128 and web129. We will provide further updates as we continue investigation into this incident.

2. monitoring Dec 18, 2024, 07:42 PM UTC

   Our team has resolved the issue with high load on web128 and web129. We will continue to monitor these instances and provide another update shortly.

3. resolved Dec 18, 2024, 07:54 PM UTC

   This incident has been resolved.

Read the full incident report →