Kudelski Security logo

Is Kudelski Security Down?

SaaSLive status, outages, and incident history

No. Kudelski Security is up right now.

Every monitored Kudelski Security system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment Kudelski Security breaks

Kudelski Security is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Kudelski Security status page
How we know: the official Kudelski Security status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Kudelski Security Status Summary

As of 22:14 UTC on 9 November 2026, Kudelski Security is operational. PulsAPI checked Kudelski Security's official status page and found 8 of 8 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.85% uptime for Kudelski Security, counting degraded performance as up. The latest incident, "EMEA - Ingestion degradation", was on Nov 4, 2026 and lasted 1h 39m.

Cite as: PulsAPI, “Kudelski Security status”, checked 9 November 2026, 22:14 UTC. https://www.pulsapi.com/services/kudelski-security

Kudelski Security Component Status

The main Kudelski Security systems on this page. All 8 are operational right now.

8operational
CFC Phone System
Operational
Client Portal
Operational
Client Portal API
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking MDR ONE, MDR One Resolute, Monthly Reporting, Security Alert / Event Ingestion Pipeline / Managed System Access, Vulnerability Scanning.

See all of them free

Component statuses may change independently during partial outages.

Recent Kudelski Security Outages & Incidents

Incident history from the official Kudelski Security status page, including resolution updates.

EMEA - Ingestion degradationResolved Nov 4, 2026 · 1h 39mResolved

The incident has been resolved and services are back to normal. We thank you for your patience and understanding. --- [2026-11-04T02:07:44.833Z] (monitoring) The fix has been deployed in production. This fixed the issue. Our ingestion is back and all services are back to normal. We will monitor the situation for couple of minutes before closing the incident. --- [2026-11-04T01:19:47.509Z] (identified) We are still working on the resolution of the incident. We have implemented an internal work-around that allows us to monitor events in a degradated way. We will continue monitoring the service while we push to full resolution of the incident. Please be assured our teams are actively working on this incident and we will provide a resolution as soon as possible. --- [2026-11-04T00:50:07.629Z] (identified) The cause of the incident has been identified and we are actively working on the resolution. According to the information available right now, we estimate the service should be fully back and functional within 1h. No events will be lost during the incident. --- [2026-11-04T00:42:56.961Z] (investigating) We are experiencing a service degradation on our events ingestion. We are currently investigating the incident and will update this page in the next 1 hour. Please trust all our teams are actively working to a swift resolution of the degradation.

Microsoft Sentinel API failures and delays in East US, East US 2, and West US regionsResolved Nov 3, 2026 · 7h 40mResolved

The incident has been resolved and services are back to normal. We thank you for your patience and understanding. --- [2026-11-03T14:21:30.588Z] (monitoring) It seems that the issue has been fixed by Microsoft. We started to have again API access to Sentinel instance. We will monitor the situation to confirm a full resolution. --- [2026-11-03T13:49:54.461Z] (identified) Impacted regions has been update from Microsoft : Southeast Asia, East US, West US 2, West US 3, Canada Central, North Central US, Jio India West, Central US, Japan West, Australia Southeast, Qatar Central, Central India, East Asia, UAE Central, Canada East, West US, South Africa North, East US 2, Australia Central, Japan East, Korea South, Brazil South, West Central US, South Central US, Australia East, UAE North, Korea Central The CFC continue to manually monitoring incidents in Sentinel console as API access is still not fixed by Microsoft and has extend this monitoring to the newly published list of impacted regions. Last status from Microsoft : We detected this issue through our automated service monitoring after identifying a significant increase in unsuccessful requests. Our investigation remains focused on a backend dependency that is not consistently starting and processing requests as expected, resulting in request failures and intermittent errors. We have applied several mitigation actions, including reverting a recent change, redeploying the affected components, and correcting supporting configuration; however, full recovery has not yet been confirmed. We are still validating the cause of the incident while working on mitigation workstreams to restore full service, including comparing diagnostic data from functioning and affected components and evaluating additional recovery actions. --- [2026-11-03T09:09:41.770Z] (identified) Microsoft is still working on the issue, we will continue to monitor update from their side. As a temporary solution, the CFC will start to monitor MS Sentinel incidents directly inside the MS Sentinel console for impacted clients. This will allow to perform the monitoring in a best effort mode while MS fix this incident. --- [2026-11-03T07:51:13.969Z] (identified) Microsoft is currently experiencing Sentinel API failures and delays in East US, East US 2, and West US regions. Microsoft EMEA customers are not impacted by this issue. More information can be found here : https://app.azure.com/h/7H5N-XK8/d09a5a We are currently following the incident and will update this page in the next 1 hour.

Microsoft Sentinel Delays Across Multiple RegionsResolved Oct 29, 2026 · 19h 15mResolved

Dear Customer, We would like to inform you that the Microsoft Sentinel service issue affecting multiple Azure regions has now been resolved. Affected Service: Microsoft Sentinel Regions: Multiple Azure regions worldwide Impact: A subset of customers may have experienced delays in incident ingestion, processing, and incident status updates within Microsoft Sentinel. Start Time: 28 October 2026, 09:52 UTC Resolution Time: 28 October 2026, 18:10 UTC Current Status: Microsoft identified a significant increase in processing demand that exceeded available backend resources, resulting in processing backlogs and increased latency. Microsoft implemented mitigation measures to reduce processing pressure and prioritize the recovery of accumulated backlogs. Service performance returned to expected levels at 18:10 UTC on 28 October 2026, and customer impact was confirmed as mitigated. Next Steps: Microsoft will conduct an internal retrospective and publish a Post-Incident Review (PIR) to impacted customers, generally within 14 days. Thank you for your patience and understanding throughout this matter. North America: 1-866-929-3528 EMEA: +41 58 317 77 77 Kind regards, The Cyber Fusion Center --- [2026-10-29T13:50:50.799Z] (identified) Dear Customer, We would like to inform you about an ongoing issue affecting the Microsoft Sentinel service across multiple regions. Affected Service: Microsoft Sentinel Regions: Multiple Azure regions worldwide Impact: A subset of customers may experience delays in incident ingestion, processing, and incident status updates within Microsoft Sentinel. Start Time: 28 October 2026, 09:52 UTC Current Status: Microsoft has identified increased processing demand exceeding available resources in part of its infrastructure, resulting in processing backlogs and increased latency. Service performance initially improved following mitigation measures; however, a slight increase in backlog and processing delays has since been observed. Microsoft is implementing additional mitigation measures to increase processing throughput and reduce the volume of data requiring processing, while continuing to monitor service health. Next Update: Microsoft will provide the next update within 6 hours, or sooner if significant developments occur. Thank you for your patience and understanding throughout this matter. North America: 1-866-929-3528 EMEA: +41 58 317 77 77 Kind regards, The Cyber Fusion Center

Kudelski Security Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Kudelski Security incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 6 days with incidentsNov 9

Going further back: Kudelski Security uptime by month and every recorded Kudelski Security outage.

Live Kudelski Security Outage Reports

Problems reported by engineers using Kudelski Security. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Kudelski Security problems reported yet.

Something wrong with Kudelski Security on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Kudelski Security

Kudelski Security exposes 8 monitored components on its status page at status.kudelskisecurity.com — Client Portal, Client Portal API and Monthly Reporting among them. Follow Kudelski Security downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Kudelski Security uptime at 99.85%. Response times, incident history, and SLA tracking for Kudelski Security are available on the PulsAPI dashboard.

Kudelski Security Status FAQ

Is Kudelski Security down right now?

The verdict at the top of this page comes from the latest poll of the official Kudelski Security status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Kudelski Security is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Kudelski Security recovers.

How do I check Kudelski Security uptime history?

PulsAPI tracks Kudelski Security uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.85%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Kudelski Security changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Kudelski Security outages?

PulsAPI reads the official Kudelski Security status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Kudelski Security components?

Yes. PulsAPI monitors 8 individual Kudelski Security components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Kudelski Security goes down?

Yes. Create a free account and subscribe to Kudelski Security: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Kudelski Security to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Kudelski Security problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Kudelski Security?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Kudelski Security plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Kudelski Security with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services