Is Centrify down?

Last checked 7m ago
Current status
Centrify is up

No incidents right now.

Get alerts when Centrify breaks →

Free · no credit card

Official status page: https://uptime.centrify.com · Polled every 5 minutes · 41 components tracked

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

Users who monitor Centrify 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
Centrify uptime 98.77% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Privileged Access Service / Cloud Suite Pod34 increased latency and unresponsiveness
    Resolved 1d 7h
    Started Apr 26, 2026, 06:21 AM UTC · Resolved Apr 27, 2026, 02:14 PM UTC
    Privileged Access Service / Cloud Suite
    3 updates · show timeline
    • investigating · Apr 26, 2026, 06:21 AM UTC

      We are investigating reports of degraded performance affecting Privileged Access Service / Cloud Suite Pod34. Some users may experience slower than normal response times. Users may encounter slow page loads, increased latency, or timeouts. Our team is actively investigating.

    • monitoring · Apr 26, 2026, 02:09 PM UTC

      We wanted to provide you with an update on the incident affecting the service(s) listed below. We have implemented a mitigation and are monitoring the situation. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

    • resolved · Apr 27, 2026, 02:14 PM UTC

      We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. Our team has implemented a fix, and all systems are now operating normally. We apologize for any inconvenience this incident may have caused, and we appreciate your understanding and support. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

    Latest: We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. Our team has implemented a fix, and all systems are now operating normally. W…

  2. Privileged Access Service / Cloud Suite Pod34 increased latency and unresponsiveness
    Resolved 30m
    Started Apr 26, 2026, 05:19 AM UTC · Resolved Apr 26, 2026, 05:49 AM UTC
    Privileged Access Service / Cloud Suite
    2 updates · show timeline
    • investigating · Apr 26, 2026, 05:19 AM UTC

      We are investigating reports of degraded performance affecting Privileged Access Service / Cloud Suite Pod34. Some users may experience slower than normal response times. Users may encounter slow page loads, increased latency, or timeouts. Our team is actively investigating.

    • resolved · Apr 26, 2026, 05:49 AM UTC

      We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. The load causing the issue has resolved. We apologize for any inconvenience this incident may have caused, and we appreciate your understanding and support. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

    Latest: We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. The load causing the issue has resolved. We apologize for any inconvenience t…

  3. Privileged Access Service / Cloud Suite: HTTP 401 on Custom Authorization Profiles in Cloud Suite 26.1
    Resolved 15h 25m
    Started Apr 25, 2026, 09:25 PM UTC · Resolved Apr 26, 2026, 12:51 PM UTC
    Privileged Access Service / Cloud SuitePrivileged Access Service / Cloud SuitePrivileged Access Service / Cloud SuitePrivileged Access Service / Cloud SuitePrivileged Access Service / Cloud SuitePrivileged Access Service / Cloud SuitePrivileged Access Service / Cloud Suite
    2 updates · show timeline
    • identified · Apr 25, 2026, 09:25 PM UTC

      We have identified an issue in the recently rolled out Cloud Suite 26.1 release where custom authorization profiles containing wildcard or regex characters (e.g., "*") may return HTTP 401 errors. Built-in authorization profiles are not affected. A workaround is available. Please refer to the following knowledge base article for details: https://support.delinea.com/s/article/1777148833588 A fix is actively in progress, and is expected to be available shortly. We will post an update as events warrant. We apologize for any inconvenience this may cause.

    • resolved · Apr 26, 2026, 12:51 PM UTC

      We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. Our team has implemented a fix, and all systems are now operating normally. We apologize for any inconvenience this incident may have caused, and we appreciate your understanding and support. For any questions or concerns, please reach out to our support team at https://support.delinea.com.

    Latest: We’re pleased to inform you that the incident affecting the service(s) listed below has been resolved. Our team has implemented a fix, and all systems are now operating normally. W…

  4. Secret Server Cloud: US - Intermittent Application errors
    Resolved 1d 2h
    Started Apr 24, 2026, 05:58 PM UTC · Resolved Apr 25, 2026, 08:56 PM UTC
    Secret Server Cloud
    4 updates · show timeline
    • identified · Apr 24, 2026, 05:58 PM UTC

      We have identified the cause of the current issues impacting Secret Server Cloud in the US region. An ongoing cloud provider incident is affecting an availability zone hosting workloads in our US East region. Customers may encounter HTTP 500 errors when accessing the Secret Server UI, with messages similar to the following: "Http failure response for https://.secretservercloud.com/... : 500 OK" To restore service, we are failing over traffic to our secondary region. Customers may experience brief connectivity errors during the failover. We will continue to provide updates as the failover progresses. We apologize for the disruption and thank you for your patience.

    • monitoring · Apr 24, 2026, 07:06 PM UTC

      After further investigation, we determined that a failover to our secondary region was not required. We have moved the affected resources to a different availability zone within the primary region and are observing improvement in service health. Application errors are no longer being reported. We will continue to monitor the environment closely and post a further update once the incident is fully resolved. We apologize for the disruption and thank you for your patience.

    • monitoring · Apr 24, 2026, 11:06 PM UTC

      We are continuing to monitor for any further issues. We are not seeing any Application errors since 15:31PM Eastern.

    • resolved · Apr 25, 2026, 08:56 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Centrify outage history

5 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
  • Privileged Access Service / Cloud Suite Pod34 increased latency and unresponsiveness Resolved
    Started Apr 26, 2026, 06:21 AM UTC · Resolved Apr 27, 2026, 02:14 PM UTC · 1d 7h
  • Privileged Access Service / Cloud Suite Pod34 increased latency and unresponsiveness Resolved
    Started Apr 26, 2026, 05:19 AM UTC · Resolved Apr 26, 2026, 05:49 AM UTC · 30m
  • Privileged Access Service / Cloud Suite: HTTP 401 on Custom Authorization Profiles in Cloud Suite 26.1 Resolved
    Started Apr 25, 2026, 09:25 PM UTC · Resolved Apr 26, 2026, 12:51 PM UTC · 15h 25m
  • Secret Server Cloud: US - Intermittent Application errors Resolved
    Started Apr 24, 2026, 05:58 PM UTC · Resolved Apr 25, 2026, 08:56 PM UTC · 1d 2h
  • Platform: Global - SAML/Federation Authentication Failures Resolved
    Started Apr 10, 2026, 04:11 AM UTC · Resolved Apr 03, 2026, 10:00 PM UTC · —

See Centrify in your Pingoru dashboard

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

Every status page, one dashboard

Add Centrify 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 Centrify 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 Centrify or see every provider at once.

Maintenance calendar

Scheduled Centrify 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 Centrify status change, one inbox

Pingoru watches Centrify'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

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

Email + Slack + Discord + Teams

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

Maintenance, not surprises

Upcoming Centrify 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 Centrify services without silencing the monitor entirely.

Invite your team

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

Get notified on Centrify status changes

Pingoru watches Centrify'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 Centrify free

Monitor Centrify along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Centrify 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 Centrify uptime & incident history

See 90 days of Centrify 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 Centrify uptime history

Frequently asked questions

What is Centrify's uptime?
Over the last 90 days, Centrify reported 98.77% uptime on its official status page. That figure is calculated from the public incident timeline at https://uptime.centrify.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Centrify's uptime history rolling forward in real time.
Has Centrify had outages in 2026?
Yes — Centrify has had 15 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 Centrify outage?
The most recent Centrify incident was "Emergency Delinea Privileged Access Service / Cloud Suite 26.1 Cloud Maintenance on Pod34 and Pod52", which started on April 26, 2026 and was resolved on April 26, 2026. Pingoru captured this directly from https://uptime.centrify.com. See the full incident card above for affected components and the update timeline.
How often does Centrify have outages?
Based on the last 90 days, Centrify averages 5.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 Centrify's status page?
Centrify's official status page is https://uptime.centrify.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 Centrify down right now?
Centrify is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Centrify reports a change. Current status is based on 41 tracked services.
How does Pingoru know if Centrify is down?
We read https://uptime.centrify.com directly, using Centrify'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 Centrify has an outage?
Create a free Pingoru account and add Centrify as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Centrify's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Centrify 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 Centrify 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 Centrify status?
We use Centrify's own status page at https://uptime.centrify.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 Centrify components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Centrify'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 Centrify free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →