Check 15Five system status

Use the 15Five public status page to check whether a platform issue is affecting your account. When complete, you will have identified whether an active incident, degraded service, or maintenance window explains the behavior you are experiencing.

Before You Begin

  • You do not need a 15Five account to access the status page.

Steps

  1. Go to https://status.15five.com/.
  2. Review the status for each monitored service area:

Core Services - HRIS & SCIM Integrations - API - Login / SSO - Core Application - Billing

Notifications - Email - Push - Website - Slack

Maintenance - Whether 15Five is down for a scheduled maintenance window

  1. Interpret the status indicator next to each service:

- Operational — the service is functioning normally - Degraded Performance — the service is running with reduced speed or reliability - Partial Outage — some users are affected - Major Outage — the service is unavailable - Under Maintenance — the service is intentionally offline for scheduled work

If Something Goes Wrong

Issue Check Fix
Status page does not load Check your internet connection Open the page from a different network or browser
Status shows Operational but 15Five is still misbehaving Confirm the issue affects the specific service you are using Contact the 15Five Support Team — provide the affected feature, a description of the behavior, and when it started
Status shows an active incident but no resolution time is listed Check the Incident History section at the bottom of the status page Subscribe to status updates using the Subscribe button on the page to receive notifications when the incident is resolved
You received an error message not explained by any listed status The issue may be account-specific rather than platform-wide Contact the 15Five Support Team and include any error message text

Not Covered Here

This article does not cover resolving specific product errors. See for login problems, or Contact the 15Five Support Team to report an issue directly.

Related Articles

Was this article helpful?

Sorry to hear that. Tell us what was missing →