Pearl Education is a software-as-a-service platform, so keeping the Products available and performing well is core to how districts, state education agencies, and program operators rely on us. This page explains where to check live service status and how availability commitments are made in our agreements.

Service Status Page

Pearl publishes a public service status page:

• Status page: https://status.poweredbypearl.com/ (hosted on Statuspage; resolves to pearl.statuspage.io)

The status page is the fastest way to see whether the Products are operating normally, whether an incident is in progress, and whether maintenance is scheduled. It displays a rolling 90-day uptime history and a log of past incidents.

Subscribing to Updates

We recommend that district and SEA technical contacts subscribe to status notifications so they are alerted automatically when an incident is opened, updated, or resolved. The hosted Statuspage page supports subscriptions (such as email and RSS).

How Availability Commitments Work

It is important to distinguish this informational status page from a contractual uptime commitment:

• Support is always included. Pearl provides standard technical Support with the Platform Services through its help center and support channels (MSA §1.15).
• Service levels live in the SLA. A specific availability/uptime commitment applies only when a Service Level Agreement (SLA) is included by reference in, or attached to, an Order Form. Where an SLA is included, Pearl will meet the service levels stated there, and the SLA’s service-credit remedies are the customer’s exclusive remedies for availability failures (MSA §2.2). If your Order Form does not include an SLA, this status page reflects operational status but does not itself create an uptime guarantee.

Customers who need a defined uptime commitment should request that an SLA be referenced on their Order Form during contracting.

Maintenance and Beta Features

• Updates. Pearl may update the Platform Services from time to time, provided no update materially reduces the core functionality purchased for the then-current Service Period (MSA §2.4).
• Beta/evaluation features. Features identified as beta or evaluation are provided as-is, may be modified or withdrawn at any time, and are excluded from any SLA. Pearl will not require use of beta features for any production workflow (MSA §2.5).

Related Pages

For how we recover from disruptions, back up data, and maintain redundancy, see Business Continuity and Disaster Recovery. For how we notify customers about security incidents, see the Security pages.