User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is StackHawk down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → stackhawk.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 47 min ago. Last stored result reached it in 69 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 01 | 0 | 0.0 | 91 ms | 0 |
| Mon 03 | 0 | 0.0 | 31 ms | 0 |
| Mon 05 | 0 | 0.0 | 82 ms | 0 |
| Mon 07 | 0 | 0.0 | 52 ms | 0 |
| Mon 10 | 0 | 0.0 | 94 ms | 0 |
| Mon 12 | 0 | 0.0 | 53 ms | 0 |
| Mon 14 | 0 | 0.0 | 68 ms | 0 |
| Mon 16 | 0 | 0.0 | 108 ms | 0 |
| Mon 18 | 0 | 0.0 | 103 ms | 0 |
| Mon 20 | 0 | 0.0 | 142 ms | 0 |
| Mon 22 | 0 | 0.0 | 206 ms | 0 |
| Tue 00 | 0 | 0.0 | 52 ms | 0 |
| Tue 02 | 0 | 0.0 | 99 ms | 0 |
| Tue 04 | 0 | 0.0 | 56 ms | 0 |
| Tue 07 | 0 | 0.0 | 68 ms | 0 |
| Tue 09 | 0 | 0.0 | 55 ms | 0 |
| Tue 11 | 0 | 0.0 | 54 ms | 0 |
| Tue 13 | 0 | 0.0 | 81 ms | 0 |
| Tue 15 | 0 | 0.0 | 208 ms | 0 |
| Tue 18 | 0 | 0.0 | 109 ms | 0 |
| Tue 20 | 0 | 0.0 | 120 ms | 0 |
| Tue 22 | 0 | 0.0 | 150 ms | 0 |
| Wed 00 | 0 | 0.0 | 62 ms | 0 |
| Wed 03 | 0 | 0.0 | 51 ms | 0 |
| Wed 05 | 0 | 0.0 | 63 ms | 0 |
| Wed 07 | 0 | 0.0 | 72 ms | 0 |
| Wed 09 | 0 | 0.0 | 37 ms | 0 |
| Wed 12 | 0 | 0.0 | 55 ms | 0 |
| Wed 14 | 0 | 0.0 | 55 ms | 0 |
| Wed 16 | 0 | 0.0 | 111 ms | 0 |
| Wed 18 | 0 | 0.0 | 128 ms | 0 |
| Wed 20 | 0 | 0.0 | 80 ms | 0 |
| Wed 22 | 0 | 0.0 | 89 ms | 0 |
| Wed 23 | 0 | 0.0 | 93 ms | 0 |
| Thu 01 | 0 | 0.0 | 92 ms | 0 |
| Thu 03 | 0 | 0.0 | 104 ms | 0 |
| Thu 06 | 0 | 0.0 | 59 ms | 0 |
| Thu 08 | 0 | 0.0 | 44 ms | 0 |
| Thu 10 | 0 | 0.0 | 36 ms | 0 |
| Thu 12 | 0 | 0.0 | 77 ms | 0 |
| Thu 14 | 0 | 0.0 | 89 ms | 0 |
| Thu 16 | 0 | 0.0 | 101 ms | 0 |
| Thu 18 | 0 | 0.0 | 50 ms | 0 |
| Thu 20 | 0 | 0.0 | 100 ms | 0 |
| Thu 22 | 0 | 0.0 | 64 ms | 0 |
| Fri 00 | 0 | 0.0 | 79 ms | 0 |
| Fri 02 | 0 | 0.0 | 102 ms | 0 |
| Fri 04 | 0 | 0.0 | 69 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live StackHawk badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for StackHawk yet. Outages of 10 minutes or more get their own page here.
Having trouble with StackHawk?
One report per service every 10 minutes from this network. No account.
Follow StackHawk
Get an email when StackHawk goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send StackHawk alerts to Slack, Discord or a webhook — free.
About StackHawk
We track StackHawk (stackhawk.com) as part of the AI group. Secure AI-generated code before it ships. StackHawk enables coding agents to find, fix, and verify exploitable vulnerabilities automatically.
StackHawk publishes an official status page at status.stackhawk.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 73 ms average, 36–102 ms range across 12 successful checks.
Questions
Is StackHawk down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was StackHawk last down?
We have not recorded a public StackHawk incident since monitoring began 7 days ago.
What is StackHawk's uptime?
From our own checks: 100% over 7 days of checks.
How fast does StackHawk respond?
73 ms on average over the last 24 hours (36–102 ms).
Does StackHawk have an official status page?
Yes, at https://status.stackhawk.com.
StackHawk not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report StackHawk here at once, the problem is on StackHawk's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with StackHawk. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.