Cornerstone Status Page

Jul 13, 2026

Our Engineering team has identified the root cause of the issue and has successfully implemented a fix. Internal and External Career Sites are now functioning as intended, and job requisitions are once again visible to candidates. We will continue to closely monitor the environment to ensure ongoing stability and prevent any recurrence. Thank you for your patience and understanding.

Jul 8, 2026 · resolved Jul 10

After careful review and monitoring, we’ve determined this does not meet the definition of a Severity2: emails are firing as expected, and Mailspike’s blacklisting is having only a minor effect on email delivery for customers in the impacted IP—primarily those who rely on Mailspike for inbound email filtering. As a result, the incident is being closed on the Status page, and any further communications will be handled as a Severity3 via the existing Known Issue article: https://cornerstoneondemand.my.site.com/s/articles/Known-Issue-CSX-UK-Email-IP-blacklisted-by-Mailspike CSOD technical teams will continue working closely with Mailspike to address the underlying concerns.

Jul 7, 2026 · resolved Jul 7

All queues have been caught up and after a period of monitoring we are considering this issue Resolved.

Jun 29, 2026 · resolved Jun 29

**Incident Summary:** On June 28th, 2026, at 11:24 AM PT, users in the UK Production environment experienced intermittent service degradation impacting session management functionality. The issue resulted in reduced service availability and intermittent failures while accessing affected applications. **Impact:** Users experienced intermittent service disruption and degraded application responsiveness due to instability within the session management service. Some requests were impacted during the incident window, resulting in temporary failures across affected portal functionalities. **Root Cause Analysis \(RCA\):** The issue was related to transient service instability following infrastructure changes, which impacted the availability and responsiveness of the session management service. During recovery, service initialization delays affected the ability to restore full processing capacity within the expected timeframe, resulting in intermittent service impact. **Resolution:** As an immediate mitigation, service traffic handling was adjusted to allow the affected components to stabilize and recover successfully. Once service capacity was restored and stability was confirmed, normal traffic processing resumed and application performance returned to expected levels. **Preventive Actions:** The following measures have been implemented to reduce the likelihood of recurrence: * Service startup and recovery behavior are being reviewed to improve restoration time during availability events. * Additional monitoring and validation checks are being enhanced to improve visibility into service health and recovery patterns.

Jun 22, 2026 · resolved Jun 22

**Incident Summary:** On 22nd June 2026, users in the EU region experienced intermittent service degradation caused by DNS resolution failures. Our LXP applications were unable to reliably resolve internal service names, resulting in connectivity issues and increased response times. A subset of customers experienced HTTP 504 Gateway Timeout errors during the incident window. **Impact:** A subset of EU customers experienced service degradation, including increased latency and 504 Gateway Timeout responses. Internal application communication was intermittently disrupted due to failed DNS lookups. Customer transactions and requests dependent on affected services were delayed or unsuccessful until DNS functionality was restored. **Root Cause:** The issue was caused by resource saturation and degraded performance of DNS within the EU cluster. As DNS response times increased, application pods experienced delays and failures when resolving internal and external hostnames. This impacted service-to-service communication and request processing across the environment. **Corrective Actions:** As an immediate mitigation, additional resources were allocated to the DNS pods to handle the sudden spike in DNS traffic and restore service stability **Preventive Actions:** The team is re-evaluating DNS configuration and scaling parameters, reviewing DNS traffic patterns, and adjusting resource allocations based on updated capacity planning.

Is Cornerstone down right now?

No — Cornerstone is up. All systems operational as of Jul 13, 11:47 PM UTC.

What is Cornerstone's current status?

Cornerstone: All Systems Operational. Alert24 checks Cornerstone's status page continuously and can notify you the moment it changes.

How do I get alerted when Cornerstone goes down?

Alert24 monitors Cornerstone and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.