CrowdStrike outages and problems
User reports, last 24 hours
31 reports in total, counted in 15-minute windows
No problem reports came in for CrowdStrike in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 31 reports. The last spike in reports was 266 h ago and lasted 22 min. These are user reports from the US, where most people report CrowdStrike problems.
Around the world right now: normal in 4 other countries. By country
- NormalClose to the usual level24 h · 31 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 31 user reports came in for CrowdStrike. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 4 reports, about 24 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
CrowdStrike in November 2026
- Problem reports in November
- 192
- Outage spikes
- 0
- Periods of elevated reports
- 0
Monthly report for November 2026
People who report a problem with CrowdStrike to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Login
- App
- Connecting to VPN
CrowdStrike reports around the world
In the last 24 hours, 45 problem reports about CrowdStrike came in from 3 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 0 | 37 |
| Germany | Normal | 0 | 5 |
| The Netherlands | Normal | 0 | 3 |
| The UK | Normal | 0 | 0 |
| Spain | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. Map outlines: Natural Earth.
CrowdStrike problem spikes, last 30 days
Since 27 October, CrowdStrike had 1 outage spike and 1 period of elevated reports. The longest lasted 22 min, on 30 October.
- Mon 12 Oct: no data
- Tue 13 Oct: no data
- Wed 14 Oct: no data
- Thu 15 Oct: no data
- Fri 16 Oct: no data
- Sat 17 Oct: no data
- Sun 18 Oct: no data
- Mon 19 Oct: no data
- Tue 20 Oct: no data
- Wed 21 Oct: no data
- Thu 22 Oct: no data
- Fri 23 Oct: no data
- Sat 24 Oct: no data
- Sun 25 Oct: no data
- Mon 26 Oct: no data
- Tue 27 Oct: 2 reports
- Wed 28 Oct: 72 reports (elevated reports that day)
- Thu 29 Oct: 12 reports
- Fri 30 Oct: 23 reports (outage spike that day)
- Sat 31 Oct: 3 reports
- Sun 1 Nov: 0 reports
- Mon 2 Nov: 53 reports
- Tue 3 Nov: 39 reports
- Wed 4 Nov: 13 reports
- Thu 5 Nov: 11 reports
- Fri 6 Nov: 11 reports
- Sat 7 Nov: 1 report
- Sun 8 Nov: 20 reports
- Mon 9 Nov: 32 reports
- Tue 10 Nov: 12 reports
-
Outage
Fri 30 Oct, 17:31–17:53Lasted 22 min12peak reports
-
Elevated reports
Wed 28 Oct, 15:20–15:41Lasted 21 min11peak reports
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- The US222
- Germany6
- The UK5
- Spain3
- The Netherlands3
Country history starts on 29 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 27 October 2026. Monthly reports for all services
How to fix CrowdStrike not working
CrowdStrike is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach crowdstrike.com over your own connection, right now. Nothing is sent to us or stored.
Check the Falcon service
Open Services.msc and find CrowdStrike Falcon Sensor Service. The Status column shows Running or Stopped; if it is stopped, note the exact message before you change anything.
Restart the sensor
Right-click the service and choose Start or Restart. If that fails, open Command Prompt as administrator, run `sc query CSFalconService`, then run `net start CSFalconService` when the query shows it is stopped.
Test a different network
Turn off any VPN under Windows Settings > Network & internet > VPN, turn off the proxy under Network & internet > Proxy, then join a different Wi-Fi network. The sensor needs outbound HTTPS access to the Falcon cloud; a captive portal or strict firewall can block that path while other apps still load. That check is quick.
Ask your admin to check the host
Send your IT admin the device name and the Falcon sensor version. Ask them to open the host record in the Falcon console and review Sensor status and Last seen; a stale record points to a connectivity problem.
While CrowdStrike is down: what to use instead
- Windows Security Open the built-in Windows Security app if you need a local malware scan while the endpoint agent is not responding.
- Microsoft Defender for Endpoint Use it if your organisation already has Defender licensed and you need another console to check device health and alerts.
- SentinelOne Fall back to it if your team already runs SentinelOne on some machines and can cover affected endpoints from that console.
- Palo Alto Networks Cortex XDR Use it where Cortex XDR is already deployed, so you can review endpoint alerts and isolate a host from that console.
Problems at the same time as CrowdStrike
Since 27 October, all 2 of CrowdStrike's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Archive of Our Own2 times
- Starbucks2 times
- Character.AI2 times
- RBC Royal Bank of Canada2 times
- Google2 times
- ADP2 times
How many of CrowdStrike's spikes overlapped one of theirs.
During the latest spike
CrowdStrike: Fri 30 Oct, 17:31 to 17:53
- Archive of Our Own, outage,29 Oct 07:55 to 1 Nov 10:32
- McDonald's App, outage,11:35 to 21:55
- Capital One, outage,12:43 to 31 Oct 06:42
- Starbucks, outage,12:54 to 23:39
- FedEx, outage,13:34 to 21:10
- Frontier, outage,13:57 to 31 Oct 00:22
- Paddy Power, outage,14:14 to 20:36
- Character.AI, outage,14:42 to 17:36
21 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report CrowdStrike problems
The busiest hour for reports about CrowdStrike is 17:00 to 18:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 0.28 reports on an average day
- 01:00 to 02:00: 0.19 reports on an average day
- 02:00 to 03:00: 0.22 reports on an average day
- 03:00 to 04:00: 0.21 reports on an average day
- 04:00 to 05:00: 0.06 reports on an average day
- 05:00 to 06:00: 0.06 reports on an average day
- 06:00 to 07:00: 0.06 reports on an average day
- 07:00 to 08:00: 0.03 reports on an average day
- 08:00 to 09:00: 0.09 reports on an average day
- 09:00 to 10:00: 0.17 reports on an average day
- 10:00 to 11:00: 0.01 reports on an average day
- 11:00 to 12:00: 0.03 reports on an average day
- 12:00 to 13:00: 0.16 reports on an average day
- 13:00 to 14:00: 0.21 reports on an average day
- 14:00 to 15:00: 0.53 reports on an average day
- 15:00 to 16:00: 0.87 reports on an average day
- 16:00 to 17:00: 0.85 reports on an average day
- 17:00 to 18:00: 1 report on an average day
- 18:00 to 19:00: 0.68 reports on an average day
- 19:00 to 20:00: 0.61 reports on an average day
- 20:00 to 21:00: 0.51 reports on an average day
- 21:00 to 22:00: 0.73 reports on an average day
- 22:00 to 23:00: 0.36 reports on an average day
- 23:00 to 00:00: 0.47 reports on an average day
By day of the week
- Monday: 16 reports on an average Monday
- Tuesday: 9 reports on an average Tuesday
- Wednesday: 20 reports on an average Wednesday
- Thursday: 5.6 reports on an average Thursday
- Friday: 5.8 reports on an average Friday
- Saturday: 0.8 reports on an average Saturday
- Sunday: 3.9 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 34 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when CrowdStrike goes down
CrowdStrike is a cloud security platform for endpoint protection and threat detection, and security teams and managed service providers rely on it to watch devices and respond to alerts. An outage interrupts console access and Falcon sensor check-ins that keep endpoint status and policy updates moving.
Falcon console sign-in can fail or stall first, and dashboards may load without fresh detections. Sensors then lose their cloud connection, so endpoints show as offline while policy changes queue instead of reaching devices. Threat hunting queries and API calls time out, leaving your team on stale data. Problems are often regional or partial, with one console function or one sensor group hit before the rest.
CrowdStrike IP address, servers and network
- IPv4 addresses
- 2.16.1.139
Show all 2
- 2.16.1.193
- IPv6 addresses
- 2a02:26f0:2780:70::215:ef11
Show all 2
- 2a02:26f0:2780:70::215:ef12
- Network
- AS20940 · Akamai International B.V., registered in the Netherlands
- Served through
- Akamai
- DNS hosted by
- its own name servers (crowdstrike.com)
- HTTPS certificate
- Issued by Let's Encrypt, valid until 18 Dec 2026 (37 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 230 ms
Checked from our server in Frankfurt, Germany, 7 days ago, for www.crowdstrike.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from www.crowdstrike.com. Fastest from Milan (19 ms), slowest from Tokyo (1,192 ms). Every location connected through Akamai International B.V. (AS20940), using 11 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 23 ms | 184.86.103.202 |
| ViennaAustria | Up · HTTP 301 | 31 ms | 104.83.4.192 |
| MilanItaly | Up · HTTP 301 | 19 ms | 173.222.106.16 |
| ParisFrance | Up · HTTP 301 | 69 ms | 96.16.248.158 |
| AmsterdamNetherlands | Up · HTTP 301 | 32 ms | 104.97.14.169 |
| MadridSpain | Up · HTTP 301 | 32 ms | 23.211.15.163 |
| WarsawPoland | Up · HTTP 301 | 42 ms | 23.47.124.140 |
| Los AngelesUSA | Up · HTTP 301 | 38 ms | 173.223.234.204 |
| São PauloBrazil | Up · HTTP 301 | 35 ms | 2.18.20.130 |
| SingaporeSingapore | Up · HTTP 301 | 149 ms | 23.50.232.251 |
| TokyoJapan | Up · HTTP 301 | 1,192 ms | 104.69.222.64 |
Checked with check-host.net from its servers in these cities 7 days ago, for www.crowdstrike.com. Time is how long each server took to load the page.
CrowdStrike FAQ
Is CrowdStrike down right now?
Why does the Falcon console show my device as offline?
Why can't I install the Falcon sensor on macOS?
Why did Windows fail to boot after a Falcon sensor update?
Why does the Falcon console sign me out or reject my SSO login?
Service updates from @CrowdStrike
No posts about problems from @CrowdStrike in the last 14 days. The latest is from .
Contact CrowdStrike support
Tip: CrowdStrike doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track CrowdStrike
The status on this page comes from user-submitted problem reports for CrowdStrike, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for CrowdStrike, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. CrowdStrike doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.