Is Cornerstone down?

Last checked 6m ago
Current status
Cornerstone is up

No incidents right now.

Official status page: https://status.csod.com · Polled every 5 minutes · 28 components tracked

Real-time Cornerstone status, recent outages, and incident history — pulled directly from Cornerstone's official status page at https://status.csod.com every 5 minutes. Pingoru tracks 28 Cornerstone services and has captured 23 incidents in the last 90 days (98.16% uptime). Get email, Slack, Discord, or webhook alerts the moment Cornerstone reports a new incident — free for 5 monitors, no credit card.

Users who monitor Cornerstone also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers
Cornerstone uptime 98.16% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Resolved
    Started Apr 27, 2026, 11:21 AM UTC · Resolved Apr 27, 2026, 11:21 AM UTC
    1 update · show timeline
    • resolved · Apr 27, 2026, 01:11 PM UTC

      CSOD Technology Team observed a service disruption on the CDG SL1 beginning at 4:21 AM PT, with service restored at 4:31 AM PT. During this time, some clients may have experienced intermittent timeouts. The issue has been resolved and the environment is stable.

    Latest: CSOD Technology Team observed a service disruption on the CDG SL1 beginning at 4:21 AM PT, with service restored at 4:31 AM PT. During this time, some clients may have experienced …

  2. Resolved
    Started Apr 23, 2026, 05:41 PM UTC · Resolved Apr 23, 2026, 09:00 AM UTC
    1 update · show timeline
    • resolved · Apr 23, 2026, 05:41 PM UTC

      CSOD Technology Team observed a service disruption on the US SL4 swimlane beginning at 4:55 AM PT, with service restored at 6:16 AM PT. During this time, some clients may have experienced intermittent timeouts. The issue has been resolved and the environment is stable.

    Latest: CSOD Technology Team observed a service disruption on the US SL4 swimlane beginning at 4:55 AM PT, with service restored at 6:16 AM PT. During this time, some clients may have expe…

  3. Resolved 9d 19h
    Started Apr 14, 2026, 01:57 PM UTC · Resolved Apr 24, 2026, 09:36 AM UTC
    UptimeUptimeUptimeUptimeResponse TimeResponse TimeResponse TimeResponse Time
    10 updates · show timeline
    • investigating · Apr 14, 2026, 01:57 PM UTC

      US swimlanes are currently experiencing functional issues, including difficulties accessing reports. Clients with portals in this swimlane may encounter delays or disruptions while performing certain tasks. This issue was first reported yesterday (https://status.csod.com/incidents/m2s13ms05fdp) and has resurfaced, with reports not functioning as intended. This remains our top priority, and our teams are actively working toward a resolution. We appreciate your patience and recommend checking back periodically for updates as they become available.

    • monitoring · Apr 14, 2026, 02:40 PM UTC

      Our Engineering teams have identified the issue and implemented a fix to resolve it. We will continue to closely monitor the system to ensure stability. Any further updates will be communicated via the Known Issue article and Statuspage. We appreciate your understanding and patience.

    • investigating · Apr 16, 2026, 01:05 PM UTC

      Our Engineering team has proactively identified that the issue has resurfaced through backend monitoring systems and is currently investigating it with priority. Further updates will be shared through the Known Issue article and Statuspage. Thank you for your patience and understanding.

    • monitoring · Apr 16, 2026, 02:51 PM UTC

      A fix has been implemented and we are monitoring the results.

    • investigating · Apr 17, 2026, 01:03 PM UTC

      Engineering Team has confirmed the recurrence of the issue today as well. We will keep you posted on any significant updates regarding this concern. Sincerely apologize for the inconvenience caused.

    • investigating · Apr 17, 2026, 03:58 PM UTC

      We are continuing to investigate this issue. We will keep you posted on any significant updates. We apologize for the inconvenience caused.

    • monitoring · Apr 17, 2026, 04:31 PM UTC

      A fix has been implemented and we are monitoring the results.

    • monitoring · Apr 21, 2026, 08:57 PM UTC

      No issues were observed with Reporting 2.0 today. We will continue to closely monitor the system throughout the week to ensure ongoing stability. Any further updates will be communicated via the Known Issue article and Statuspage. We appreciate your patience and understanding.

    • resolved · Apr 24, 2026, 09:36 AM UTC

      After a week of monitoring with no further recurrences observed, we are considering this issue resolved. Thank you for your patience and understanding!

    • postmortem · Apr 28, 2026, 05:15 PM UTC

      **Incident Summary:** Starting April 13th, 2026, intermittent errors were observed in reporting functionality across US Production swimlanes \(SL1, SL2, SL3, and SL5\). **Root Cause Analysis \(RCA\):** The issue was caused by the auto-scaling mechanism. Newly provisioned nodes were not fully ready to handle reporting requests, leading to processing delays and request timeouts. **Corrective Action:** Auto-scaling \(scale-out\) has been temporarily paused. The system is currently operating on a fixed, increased server capacity without scale-in or scale-out to ensure stability. **Preventive Actions:** * Capacity has been proactively increased to handle expected load without relying on auto-scaling. * Additional nodes are being utilized with auto-scaling disabled to maintain consistent performance. * Engineering teams are working on enhancements to improve node readiness and ensure seamless scaling in the future.

    Latest: **Incident Summary:** Starting April 13th, 2026, intermittent errors were observed in reporting functionality across US Production swimlanes \(SL1, SL2, SL3, and SL5\). **Root Caus…

See the full Cornerstone outage history

18 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 5 incidents
  • Latency/intermittent timeouts observed on CDG SL1 Production Environment Resolved
    Started Apr 27, 2026, 11:21 AM UTC · Resolved Apr 27, 2026, 11:21 AM UTC ·
  • Intermittent Timeouts on US SL4 Resolved
    Started Apr 23, 2026, 05:41 PM UTC · Resolved Apr 23, 2026, 09:00 AM UTC ·
  • Resurfaced: Unable to access reports in Reporting 2.0 (US Swimlanes Production Environment) Resolved
    Started Apr 14, 2026, 01:57 PM UTC · Resolved Apr 24, 2026, 09:36 AM UTC · 9d 19h
  • Unable to access reports in Reporting 2.0 (US Swimlanes Production Environment) Resolved
    Started Apr 13, 2026, 02:34 PM UTC · Resolved Apr 13, 2026, 06:40 PM UTC · 4h 6m
  • Intermittent Errors on Manage Candidates Page - US Swimlanes Resolved
    Started Mar 30, 2026, 07:38 PM UTC · Resolved Mar 30, 2026, 11:18 PM UTC · 3h 39m

See Cornerstone in your Pingoru dashboard

Monitor Cornerstone alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Cornerstone to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Cornerstone incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Cornerstone or see every provider at once.

Maintenance calendar

Scheduled Cornerstone maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Cornerstone status change, one inbox

Pingoru watches Cornerstone's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Cornerstone reports on 28 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Cornerstone alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Cornerstone maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Cornerstone services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Cornerstone from the same account, with per-user notification preferences for any monitor.

Get notified on Cornerstone status changes

Pingoru watches Cornerstone's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Cornerstone free

Monitor Cornerstone along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Cornerstone and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Cornerstone uptime & incident history

See 90 days of Cornerstone uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Cornerstone uptime history

Frequently asked questions

What is Cornerstone's uptime?
Over the last 90 days, Cornerstone reported 98.16% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.csod.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Cornerstone's uptime history rolling forward in real time.
Has Cornerstone had outages in 2026?
Yes — Cornerstone has had 21 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Cornerstone outage?
The most recent Cornerstone incident was "Latency/intermittent timeouts observed on CDG SL1 Production Environment", which started on April 27, 2026 and was resolved on April 27, 2026. Pingoru captured this directly from https://status.csod.com. See the full incident card above for affected components and the update timeline.
How often does Cornerstone have outages?
Based on the last 90 days, Cornerstone averages 7.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Cornerstone's status page?
Cornerstone's official status page is https://status.csod.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Cornerstone down right now?
Cornerstone is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Cornerstone reports a change. Current status is based on 28 tracked services.
How does Pingoru know if Cornerstone is down?
We read https://status.csod.com directly, using Cornerstone's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Cornerstone has an outage?
Create a free Pingoru account and add Cornerstone as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Cornerstone's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Cornerstone incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Cornerstone issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Cornerstone status?
We use Cornerstone's own status page at https://status.csod.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Cornerstone components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Cornerstone's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Cornerstone free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →