Pagely Outage History
Uptime record, past incidents, and downtime history for Pagely.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 91.7% | 12 | 1 |
| April 2026 | 86.7% | 30 | 4 |
| March 2026 | 75% | 4 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 46 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
SSL Creation Issues with Let's Encrypt Certificates
Started: May 8, 8:26 PM
investigating
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
May 8, 8:26 PM
Atomic Login Issues
Started: May 8, 1:26 AM
monitoring
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.
May 8, 7:34 AM
investigating
Atomic remains unavailable while we continue investigation and remediation; we’ll share additional details as they become available.
May 8, 4:56 AM
investigating
We’re continuing to troubleshoot Atomic and will share additional details as they become available.
May 8, 2:52 AM
investigating
This issue would also affect cron task execution and we are investigating this as well.
May 8, 1:51 AM
investigating
We are currently investigating issues with Atomic logins. We will provide more information shortly.
May 8, 1:26 AM
Subset of EC2 instances in AWS Virginia Experiencing Issues
Started: May 8, 12:05 AM
monitoring
All affected instances are now restored and we continue to monitor for any issues.
May 8, 7:38 AM
identified
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.
May 8, 6:19 AM
identified
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.
May 8, 3:00 AM
identified
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.
May 8, 1:01 AM
identified
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.
May 8, 12:41 AM
investigating
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.
May 8, 12:05 AM
April 2026
Pagely Atomic login failure
Started: Apr 30, 1:28 PM
monitoring
Additional fixes are being applied to address issues affecting parts of the Atomic interface
Apr 30, 3:54 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 30, 2:35 PM
identified
We are continuing to work on a fix for this issue.
Apr 30, 2:07 PM
identified
The issue has been identified and a fix is being implemented.
Apr 30, 1:58 PM
investigating
Our Operations and Development team are currently investigating an issue with login failures to Atomic
Apr 30, 1:28 PM
New Account Provisioning Issues
Started: Apr 24, 5:16 PM
monitoring
We are continuing to monitor for any further issues.
Apr 24, 9:08 PM
monitoring
Fix has been applied and we are waiting for our queue processing to normalize. Will provide additional updates shortly.
Apr 24, 7:54 PM
identified
The issue has been identified with provisioning and the team is applying a fix.
Apr 24, 6:32 PM
investigating
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.
Apr 24, 5:16 PM