Cornerstone Status Page

All Systems Operational

About This Site

Welcome to Cornerstone System Status Dashboard!

This page shows the system status for the Cornerstone SaaS environments.
Downtime is when a swimlane is not accessible by 25% or more of our customers by any login method and the incident resides with Cornerstone (rather than the customer's connection). This excludes any planned maintenance , patch or release (please see calendar linked to the bottom left of this page)

The current status column is updated in near-real time to reflect any ongoing production issues.
You can Subscribe to updates via Email/SMS and Web hook by clicking the "Subscribe to updates" option just below the Cornerstone Banner.

LAX-SL4 Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
US SL4 (AWS) Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
AU SL1 (AWS) Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
JP SL1 (AWS) Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
Uptime Operational
90 days ago
100.0 % uptime
Today
UK SL1 (AWS) Operational
90 days ago
99.43 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
98.86 % uptime
Today
UK SL2 (AWS) Operational
90 days ago
99.43 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
98.86 % uptime
Today
UK SL3 (AWS) Operational
90 days ago
99.43 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
98.86 % uptime
Today
UK SL4 (AWS) Operational
90 days ago
99.42 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
98.84 % uptime
Today
CDG SL1 (AWS) Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
100.0 % uptime
Today
CDG SL4 (AWS) Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
100.0 % uptime
Today
FRA SL1 (AWS) Operational
90 days ago
100.0 % uptime
Today
Uptime Operational
90 days ago
100.0 % uptime
Today
Response Time Operational
90 days ago
100.0 % uptime
Today
US SL1 (AWS) Operational
90 days ago
99.97 % uptime
Today
Uptime Operational
90 days ago
99.94 % uptime
Today
Response Time Operational
90 days ago
100.0 % uptime
Today
US SL2 (AWS) Operational
90 days ago
99.97 % uptime
Today
Uptime Operational
90 days ago
99.94 % uptime
Today
Response Time Operational
90 days ago
100.0 % uptime
Today
US SL3 (AWS) Operational
90 days ago
99.94 % uptime
Today
Uptime Operational
90 days ago
99.94 % uptime
Today
Response Time Operational
US SL5 (AWS) Operational
90 days ago
99.94 % uptime
Today
Uptime Operational
90 days ago
99.94 % uptime
Today
Response Time Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Nov 4, 2025

No incidents reported today.

Nov 3, 2025

No incidents reported.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025
Resolved - This incident has been resolved.
Oct 30, 11:44 PDT
Monitoring - The incident has been resolved at 9:13 AM PDT.
Oct 30, 10:11 PDT
Investigating - The CSOD Technology Team observed a intermittent timeouts in the US SL5. The team is currently investigating the issue.
Start time: 06:00 am PDT.

Oct 30, 09:59 PDT
Oct 29, 2025

No incidents reported.

Oct 28, 2025
Resolved - Our observations indicate feeds are processing as expected (see below), therefore concluding this issue as Resolved.

Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

Oct 28, 06:41 PDT
Monitoring - Queues on all swimlanes are cleared.

Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

We are actively monitoring the situation and will continue to provide updates as needed.

Oct 28, 05:02 PDT
Update - Following the initial issue, subsequent feed runs failed with the error “The feed was already running.” This is due to the Edge Import system’s built-in fail-safe and recovery mechanism, which prevents new feed runs from initiating while a previous instance is still in progress. This ensures the feed will become available for processing during the next scheduled or manually triggered run.
The upcoming feed run is expected to process successfully.

Summary of Current Status
- First feed run: Stalled as a result of a known infrastructure issue, which has now been resolved.
- Second feed run: Failed with the error “The feed was already running,” in accordance with the system’s fail-safe logic.
- Third feed run: Anticipated to be successful on the next attempt.

We are actively monitoring the situation and will continue to provide updates as needed.

Oct 28, 02:26 PDT
Update - We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Oct 27, 22:32 PDT
Update - We are continuing to closely monitor activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Oct 27, 20:02 PDT
Update - Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process.
Oct 27, 17:59 PDT
Update - Our engineering team continues to monitor as the backlog clears. We'll share regular updates as things process
Oct 27, 16:08 PDT
Update - The backlog has cleared for most swimlanes. We are continuing to closely monitor progress to ensure it continues to catch up. We will share regular updates until the queues have fully cleared.
Oct 27, 14:05 PDT
Update - We are continuing to closely monitoring activity to ensure the backlog fully clears. We will share regular updates until the queues have fully cleared.
Oct 27, 11:08 PDT
Update - Our teams continue to closely monitor the ongoing loads.
Please note that new files and scheduled feed runs should process as expected.

Oct 27, 09:00 PDT
Identified - On October 26th we experienced an issue with Edge Import access, which has since been resolved.
As a result, a backlog of pending feeds accumulated, causing delays in feed processing across all swimlanes.

We are seeing feeds actively processing, and our team is proactively monitoring progress to ensure timely completion.

Status Page will be updated regularly to reflect the progress.

Oct 27, 05:52 PDT
Oct 27, 2025
Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025

No incidents reported.

Oct 22, 2025
Postmortem - Read details
Nov 2, 17:52 PST
Resolved - After an extended period of monitoring, this incident is now considered resolved. Our efforts do not stop here. Cornerstone teams continue to work closely with Spamhaus and our customers to strengthen email hygiene practices, while also enhancing our email infrastructure and application safeguards to help prevent similar incidents in the future. A detailed Root Cause Analysis (RCA) will be shared within 7 to 10 business days. For additional details, please refer to the related Known Issue article: ( https://cornerstoneondemand.my.site.com/s/articles/Known-Issue-Email-Delivery-failures-for-UK-Swimlanes ).
Oct 22, 12:41 PDT
Update - Email delivery has remained stable since October 10, with no new delivery failures related to the Spamhaus blacklisting. All emails continue to be successfully delivered, and we are maintaining close monitoring to ensure ongoing stability.
Oct 20, 21:27 PDT
Update - Our monitoring confirms that email delivery has remained fully stable since the IP configuration change on October 10th. No new delivery failures have been observed due to the Spamhaus blacklisting, and all emails are being successfully delivered.
Oct 13, 04:19 PDT
Update - Our monitoring confirms that email delivery has remained fully stable since the IP configuration change on October 10th. No new delivery failures have been observed due to the Spamhaus blacklisting, and all emails are being successfully delivered.

Everything continues to look good at this time. We are continuing to monitor the system and will provide another update within the next 24 hours as we complete the 48-hour observation window.

Oct 12, 04:04 PDT
Update - Email delivery remains stable following the IP configuration change on October 10th. No new delivery failures have been detected, and all emails continue to be successfully delivered.

We will continue to monitor the situation closely and provide an update after 24 hours.

Oct 12, 04:03 PDT
Update - Our monitoring confirms that email delivery has remained fully stable since the IP configuration change on October 10th. No new delivery failures have been observed due to Spamhaus blacklisting, and emails are being successfully delivered.

Everything continues to look good at this time. We will continue to monitor until the 48-hour window is complete. We will update you again in the next 24 hours.

Oct 11, 04:01 PDT
Monitoring - The CSOD Technology Team has successfully updated our email configuration to route traffic through an IP address in good standing. Beginning at 1200 AM Pacific Time on October 10th, UK Swimlane customers should no longer experience issues with email delivery due to Spamhaus blacklisting. All emails from Cornerstone are now expected to be delivered successfully.

We will continue to closely monitor the situation for the next 48 hours before closing this incident.

Background:
The email delivery disruption affecting UK Swimlane customers was due to our primary email IP being blacklisted by Spamhaus, starting at approximately 3:30 PM Pacific Time on October 6th. During this period, some customers may have experienced intermittent email delivery failures, depending on their organization’s IT security policies.

We appreciate your patience and will provide further updates as needed.

Oct 10, 03:57 PDT
Update - We remain in contact with Spamhaus while awaiting confirmation of the delisting. Further updates will be provided in due course.
Oct 10, 03:47 PDT
Update - We remain in contact with Spamhaus while awaiting confirmation of the delisting. Further updates will be provided in due course.
Oct 10, 01:41 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.
Oct 9, 23:11 PDT
Update - We remain in contact with Spamhaus while awaiting confirmation of the delisting. Further updates will be provided in due course.
Oct 9, 21:06 PDT
Update - We remain in contact with Spamhaus while awaiting confirmation of the delisting. Further updates will be provided in due course.
Oct 9, 19:11 PDT
Update - Communication with Spamhaus is ongoing as we await confirmation of the delisting request. We will continue to share updates on a regular basis.
Oct 9, 16:02 PDT
Update - Communication with Spamhaus is ongoing as we await confirmation of the delisting request. We will continue to share updates on a regular basis.
Oct 9, 13:31 PDT
Update - We’re actively engaging with SpamHaus and still waiting for their reply regarding our delisting request. The next update will be provided in 4 hours or sooner if any feedback from SpamHouse is available before that time.
Oct 9, 09:12 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. The next update will be provided in 4 hours or sooner if any feedback from SpamHouse is available before that time.
Oct 9, 05:03 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.
Oct 9, 02:45 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.
Oct 9, 00:01 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.
Oct 8, 21:39 PDT
Update - We’re actively engaging with SpamHaus and awaiting their reply regarding our delisting request. Regular updates will be provided until the matter is completely resolved.
Oct 8, 19:41 PDT
Update - We are in ongoing communication with SpamHaus and are currently awaiting their response to our delisting request. We’ll continue to provide regular updates until the issue is fully resolved.
Oct 8, 17:40 PDT
Update - We continue to communicate with SpamHaus and are awaiting a response to our delisting request. Regular updates will be shared until this is resolved.
Oct 8, 15:44 PDT
Update - We are in ongoing communication with Spamhaus and awaiting confirmation of our delisting request. We will continue to provide regular updates until this is resolved.
Oct 8, 13:33 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 8, 10:00 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 8, 08:03 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 8, 05:47 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 8, 02:07 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 8, 00:07 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 7, 22:01 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 7, 20:08 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 7, 18:00 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 7, 16:01 PDT
Update - We continue to work closely with Spamhaus as we await confirmation of our delisting request. We will share regular updates as new information becomes available.
Oct 7, 13:56 PDT
Update - We are still awaiting a response from Spamhaus regarding the delisting request and will provide an update as soon as we receive any information.
Oct 7, 12:00 PDT
Update - We are currently awaiting a response from Spamhaus regarding the delisting request and will provide an update as soon as we receive any information.
Oct 7, 07:55 PDT
Update - Cornerstone IPs remain listed on the Spamhaus blocklist, which means email deliveries may continue to be impacted, depending on the client’s Domain Reputation Checker policies for Spamhaus.
We are still awaiting further updates from Spamhaus regarding the delisting request.

Oct 7, 04:45 PDT
Update - We are currently awaiting a response from Spamhaus regarding the delisting request and will provide an update as soon as we receive any information.
Oct 7, 02:35 PDT
Update - We are continuing to work on the fix for this issue.
The next update will follow within 2 hours or as soon as we receive further information.

Oct 7, 00:36 PDT
Update - Email delivery success rate is improving. We will update you further in the next two hours.
Oct 6, 22:31 PDT
Identified - We have identified the cause of the issue and have implemented internal corrective measures. We are working to restore normal operations. We will update you further in the next two hours.
Oct 6, 20:39 PDT
Update - We are continuing to investigate this issue as our top priority and will provide regular updates until it is fully resolved. Thank you for your continued patience and understanding.
Oct 6, 18:35 PDT
Investigating - Cornerstone UK email sending IPs have been temporarily blacklisted by Spamhaus, a leading global email reputation authority, due to poor email hygiene detected in email activity originating from certain customer accounts.

During this time, emails may fail to deliver. This is our top priority and we are working closely with the vendor to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

Oct 6, 16:49 PDT
Oct 21, 2025

No incidents reported.