Company Logo

Is there an Pagely outage?

Pagely status: Systems Active

Last checked: a minute ago

Get notified about any outages, downtime or incidents for Pagely and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Pagely outages and incidents

Outage and incident data over the last 30 days for Pagely.

There have been 0 outages or incidents for Pagely in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Pagely

Outlogger tracks the status of these components for Xero:

API Active
Atomic Control Panel Active
Automation Active
CI/CD Integrations Active
Live Chat Active
PressDNS Active
Shared Hosting Infrastructure Active
Site Backup Downloads Active
Slack Support Channels Active
Support System Active
VPS Hosting Infrastructure Active
Component Status
API Active
Atomic Control Panel Active
Automation Active
CI/CD Integrations Active
Live Chat Active
PressDNS Active
Shared Hosting Infrastructure Active
Site Backup Downloads Active
Slack Support Channels Active
Support System Active
VPS Hosting Infrastructure Active

Latest Pagely outages and incidents.

View the latest incidents for Pagely and check for official updates:

Updates:

  • Time: Nov. 4, 2022, 5:36 a.m.
    Status: Resolved
    Update: Impacted hosts have had fixes applied to resolve this issue.
  • Time: Nov. 4, 2022, 2:37 a.m.
    Status: Monitoring
    Update: A fix has been implemented and is being deployed to all affected hosts. We will continue to monitor the situation.
  • Time: Nov. 4, 2022, 12:55 a.m.
    Status: Identified
    Update: We have identified an issue involving higher than normal server CPU usage and response times for customers using New Relic, and we are currently implementing a fix. We will post additional updates here as we have more information.

Updates:

  • Time: Nov. 4, 2022, 5:36 a.m.
    Status: Resolved
    Update: Impacted hosts have had fixes applied to resolve this issue.
  • Time: Nov. 4, 2022, 2:37 a.m.
    Status: Monitoring
    Update: A fix has been implemented and is being deployed to all affected hosts. We will continue to monitor the situation.
  • Time: Nov. 4, 2022, 12:55 a.m.
    Status: Identified
    Update: We have identified an issue involving higher than normal server CPU usage and response times for customers using New Relic, and we are currently implementing a fix. We will post additional updates here as we have more information.

Updates:

  • Time: July 28, 2022, 7:32 p.m.
    Status: Resolved
    Update: As of 12:15 PM MST, the issues and errors around tickets and chats from our provider have been resolved.
  • Time: July 28, 2022, 6:52 p.m.
    Status: Identified
    Update: Latest update: July 28, 2022 11:36 AM: We are beginning to see some improvement in the error rates affecting the US-East region. Our team is monitoring and we will post another update in the next 30 minutes.
  • Time: July 28, 2022, 6:52 p.m.
    Status: Identified
    Update: Latest update: July 28, 2022 11:36 AM: We are beginning to see some improvement in the error rates affecting the US-East region. Our team is monitoring and we will post another update in the next 30 minutes.
  • Time: July 28, 2022, 6:29 p.m.
    Status: Identified
    Update: Update from provider: July 28, 2022 11:00 AM: Our team continues to investigate elevated error rates and access issues in the US-East region. We will post another update within the next 30 minutes.
  • Time: July 28, 2022, 6:29 p.m.
    Status: Identified
    Update: Update from provider: July 28, 2022 11:00 AM: Our team continues to investigate elevated error rates and access issues in the US-East region. We will post another update within the next 30 minutes.
  • Time: July 28, 2022, 5:44 p.m.
    Status: Identified
    Update: Latest updates from the provider: We have confirmed access issues and high error rates in the US-East region. Further updates to come shortly.
  • Time: July 28, 2022, 5:44 p.m.
    Status: Identified
    Update: Latest updates from the provider: We have confirmed access issues and high error rates in the US-East region. Further updates to come shortly.
  • Time: July 28, 2022, 5:31 p.m.
    Status: Investigating
    Update: We're currently investigating an issue with our Live Chat and Ticketing system in which the systems are intermittently available with our platform provider and working on a resolution in order to bring them fully back online.

Updates:

  • Time: July 28, 2022, 8:24 p.m.
    Status: Resolved
    Update: After further monitoring, no further issues appear to be happening within the us-east-2 Ohio region. Everything has been resolved at this time.
  • Time: July 28, 2022, 7:18 p.m.
    Status: Monitoring
    Update: We've gone ahead and confirmed that all servers appear to be operational from within the us-east-2 Ohio region at this time. We will continue to monitor the region to ensure no other issues remain.
  • Time: July 28, 2022, 6:47 p.m.
    Status: Identified
    Update: At this time, most of the AWS issues that appeared to be the root cause of the issues has been cleared. We are still continuing to work on servers within the region that may still be unavailable to ensure they recover fully.
  • Time: July 28, 2022, 6:31 p.m.
    Status: Identified
    Update: Latest update from AWS: Instance Impairments 11:25 AM PDT We continue to make progress in recovering the remaining EC2 instances and EBS volumes affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. The vast majority of EC2 instances are now healthy, but we continue to work on recovering the remaining EBS volumes affected by the issue. EC2 API error rates and latencies have returned to normal levels. Elastic Load Balancing remains weighted away from the affected Availability Zone. Error rates and latencies for Lambda function invocations have now returned to normal levels. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 30 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 6:31 p.m.
    Status: Identified
    Update: Latest update from AWS: 11:25 AM PDT We continue to make progress in recovering the remaining EC2 instances and EBS volumes affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. The vast majority of EC2 instances are now healthy, but we continue to work on recovering the remaining EBS volumes affected by the issue. EC2 API error rates and latencies have returned to normal levels. Elastic Load Balancing remains weighted away from the affected Availability Zone. Error rates and latencies for Lambda function invocations have now returned to normal levels. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 30 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 6:08 p.m.
    Status: Identified
    Update: Further update from AWS: 10:49 AM PDT We continue to see recovery of EC2 instances that were affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. At this stage, the vast majority of affected EC2 instances and EBS volumes have returned to a healthy state and we continue to work on the remaining EC2 instances and EBS volumes. Elastic Load Balancing has shifted traffic away from the affected Availability Zone. Single-AZ RDS databases were also affected and will recover as the underlying EC2 instance recovers. Multi-AZ RDS databases would have mitigated impact by failing away from the affected Availability Zone. While the vast majority of Lambda functions continue operating normally, some functions are experiencing invocation failures and latencies, but we expect this to improve over the next 30 minutes. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 45 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 5:31 p.m.
    Status: Identified
    Update: Our team is working on failover options while AWS works to resolve this issue. Latest update from AWS: Instance Impairments 10:25 AM PDT We can confirm that some instances within a single Availability Zone (USE2-AZ1) in the US-EAST-2 Region have experienced a loss of power. The loss of power is affecting part of a single data center within the affected Availability Zone. Power has been restored to the affected facility and at this stage the majority of the affected EC2 instances have recovered. We expect to recover the vast majority of EC2 instances within the next hour. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 5:12 p.m.
    Status: Investigating
    Update: We're currently investigating an issue with the AWS us-east-2 (Ohio) region causing an outage for servers within that region.

Updates:

  • Time: July 28, 2022, 8:24 p.m.
    Status: Resolved
    Update: After further monitoring, no further issues appear to be happening within the us-east-2 Ohio region. Everything has been resolved at this time.
  • Time: July 28, 2022, 7:18 p.m.
    Status: Monitoring
    Update: We've gone ahead and confirmed that all servers appear to be operational from within the us-east-2 Ohio region at this time. We will continue to monitor the region to ensure no other issues remain.
  • Time: July 28, 2022, 6:47 p.m.
    Status: Identified
    Update: At this time, most of the AWS issues that appeared to be the root cause of the issues has been cleared. We are still continuing to work on servers within the region that may still be unavailable to ensure they recover fully.
  • Time: July 28, 2022, 6:31 p.m.
    Status: Identified
    Update: Latest update from AWS: Instance Impairments 11:25 AM PDT We continue to make progress in recovering the remaining EC2 instances and EBS volumes affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. The vast majority of EC2 instances are now healthy, but we continue to work on recovering the remaining EBS volumes affected by the issue. EC2 API error rates and latencies have returned to normal levels. Elastic Load Balancing remains weighted away from the affected Availability Zone. Error rates and latencies for Lambda function invocations have now returned to normal levels. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 30 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 6:31 p.m.
    Status: Identified
    Update: Latest update from AWS: 11:25 AM PDT We continue to make progress in recovering the remaining EC2 instances and EBS volumes affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. The vast majority of EC2 instances are now healthy, but we continue to work on recovering the remaining EBS volumes affected by the issue. EC2 API error rates and latencies have returned to normal levels. Elastic Load Balancing remains weighted away from the affected Availability Zone. Error rates and latencies for Lambda function invocations have now returned to normal levels. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 30 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 6:08 p.m.
    Status: Identified
    Update: Further update from AWS: 10:49 AM PDT We continue to see recovery of EC2 instances that were affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. At this stage, the vast majority of affected EC2 instances and EBS volumes have returned to a healthy state and we continue to work on the remaining EC2 instances and EBS volumes. Elastic Load Balancing has shifted traffic away from the affected Availability Zone. Single-AZ RDS databases were also affected and will recover as the underlying EC2 instance recovers. Multi-AZ RDS databases would have mitigated impact by failing away from the affected Availability Zone. While the vast majority of Lambda functions continue operating normally, some functions are experiencing invocation failures and latencies, but we expect this to improve over the next 30 minutes. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 45 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 5:31 p.m.
    Status: Identified
    Update: Our team is working on failover options while AWS works to resolve this issue. Latest update from AWS: Instance Impairments 10:25 AM PDT We can confirm that some instances within a single Availability Zone (USE2-AZ1) in the US-EAST-2 Region have experienced a loss of power. The loss of power is affecting part of a single data center within the affected Availability Zone. Power has been restored to the affected facility and at this stage the majority of the affected EC2 instances have recovered. We expect to recover the vast majority of EC2 instances within the next hour. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.
  • Time: July 28, 2022, 5:12 p.m.
    Status: Investigating
    Update: We're currently investigating an issue with the AWS us-east-2 (Ohio) region causing an outage for servers within that region.

Check the status of similar companies and alternatives to Pagely

Avalara
Avalara

Systems Active

Crisis Text Line
Crisis Text Line

Issues Detected

Jamf
Jamf

Systems Active

Mulesoft
Mulesoft

Systems Active

Meltwater
Meltwater

Systems Active

HashiCorp
HashiCorp

Systems Active

Datto
Datto

Issues Detected

Vox Media
Vox Media

Systems Active

Cradlepoint
Cradlepoint

Systems Active

Liferay
Liferay

Systems Active

Zapier
Zapier

Systems Active

Workato US
Workato US

Systems Active

Frequently Asked Questions - Pagely

Is there a Pagely outage?
The current status of Pagely is: Systems Active
Where can I find the official status page of Pagely?
The official status page for Pagely is here
How can I get notified if Pagely is down or experiencing an outage?
To get notified of any status changes to Pagely, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Pagely every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Pagely do?
A Managed WordPress platform was created in the mid-2000s to simplify and make WordPress more accessible. It now serves high-quality solutions to clients.