Is CISA Known Exploited Vulnerabilities API down?
Current status, daily uptime history and troubleshooting for the CISA Known Exploited Vulnerabilities API (Security).
No, CISA Known Exploited Vulnerabilities is up
CISA Known Exploited Vulnerabilities answered our last daily check (Oct 24, 2026, 12:25 UTC) in 675 ms with HTTP 200.
Checking CISA Known Exploited Vulnerabilities now…
Sending a request from our server.
CISA Known Exploited Vulnerabilities API uptime history
- Uptime
- 2 checks so far
- Last check
- Oct 24, 2026, 12:25 UTC
- Response
- 675 ms · HTTP 200
- Last up
- Now
We check CISA Known Exploited Vulnerabilities's listed URL (https://rapidapi.com/crisp-point-studio-crisp-point-studio-default/api/live-cisa-cybersecurity-vulnerabilities-kev) once a day. History started when CISA Known Exploited Vulnerabilities was first checked, so new entries show fewer than 30 days.
CISA Known Exploited Vulnerabilities API not working for you?
- CISA Known Exploited Vulnerabilities needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
- A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
- If calls fail only in the browser with a CORS error, CISA Known Exploited Vulnerabilities may not allow cross-origin requests. Call it from your server instead.
- If it works from one network but not another, check firewalls, VPNs and regional blocks.
- Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.
Security APIs up at their last check
- 1
Presend API
Online · 399 msSecurity and developer utility API -- malware, vulnerability, and domain checks, no signup.
- No API key needed
- Fast: 399 ms response
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 2
IPGuardian API
Online · 940 msCheck IP addresses against 140+ public threat intelligence blocklists.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 3
IPLogs API
Online · 762 msFree VPN, proxy, Tor and datacenter IP detection. 13 sources, active probing.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 4
OSV API
Online · 608 msOpen source vulnerability database and distributed triage infrastructure.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS - 5
Passwordinator API
Online · 730 msGenerate random passwords of varying complexities.
- No API key needed
- Callable from the browser (CORS)
- HTTPS
No authHTTPSCORS
Compare all CISA Known Exploited Vulnerabilities alternatives · APIs down right now
CISA Known Exploited Vulnerabilities API status FAQ
Is CISA Known Exploited Vulnerabilities API down right now?
CISA Known Exploited Vulnerabilities answered our last daily check (Oct 24, 2026, 12:25 UTC) in 675 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether CISA Known Exploited Vulnerabilities is responding at this moment.
How do you check whether CISA Known Exploited Vulnerabilities API is up?
Once a day our checker requests CISA Known Exploited Vulnerabilities's listed URL (https://rapidapi.com/crisp-point-studio-crisp-point-studio-default/api/live-cisa-cybersecurity-vulnerabilities-kev) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.
What can I use if CISA Known Exploited Vulnerabilities API is down?
Free Security APIs that were up at their last check include Presend, IPGuardian, IPLogs. See the full list of CISA Known Exploited Vulnerabilities alternatives for a comparison.
Why does CISA Known Exploited Vulnerabilities API work for others but not for me?
CISA Known Exploited Vulnerabilities needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, CISA Known Exploited Vulnerabilities may not allow cross-origin requests. Call it from your server instead.