User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
netwitness.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 76 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 12 | 0 | 0.0 | 235 ms | 0 |
| Wed 15 | 0 | 0.0 | 140 ms | 0 |
| Wed 17 | 0 | 0.0 | 146 ms | 0 |
| Wed 19 | 0 | 0.0 | 123 ms | 0 |
| Wed 21 | 0 | 0.0 | 271 ms | 0 |
| Wed 23 | 0 | 0.0 | 186 ms | 0 |
| Thu 01 | 0 | 0.0 | 200 ms | 0 |
| Thu 03 | 0 | 0.0 | 152 ms | 0 |
| Thu 05 | 0 | 0.0 | 179 ms | 0 |
| Thu 08 | 0 | 0.0 | 167 ms | 0 |
| Thu 10 | 0 | 0.0 | 239 ms | 0 |
| Thu 12 | 0 | 0.0 | 174 ms | 0 |
| Thu 14 | 0 | 0.0 | 187 ms | 0 |
| Thu 16 | 0 | 0.0 | 117 ms | 0 |
| Thu 18 | 0 | 0.0 | 87 ms | 0 |
| Thu 20 | 0 | 0.0 | 197 ms | 0 |
| Thu 22 | 0 | 0.0 | 226 ms | 0 |
| Fri 00 | 0 | 0.0 | 149 ms | 0 |
| Fri 02 | 0 | 0.0 | 191 ms | 0 |
| Fri 04 | 0 | 0.0 | 85 ms | 0 |
| Fri 06 | 0 | 0.0 | 101 ms | 0 |
| Fri 08 | 0 | 0.0 | 284 ms | 0 |
| Fri 09 | 0 | 0.0 | 118 ms | 0 |
| Fri 10 | 0 | 0.0 | 88 ms | 0 |
| Fri 11 | 0 | 0.0 | 169 ms | 0 |
| Fri 13 | 0 | 0.0 | 168 ms | 0 |
| Fri 14 | 0 | 0.0 | 174 ms | 0 |
| Fri 16 | 0 | 0.0 | 200 ms | 0 |
| Fri 17 | 0 | 0.0 | 200 ms | 0 |
| Fri 19 | 0 | 0.0 | 198 ms | 0 |
| Fri 20 | 0 | 0.0 | 139 ms | 0 |
| Fri 22 | 0 | 0.0 | 87 ms | 0 |
| Fri 23 | 0 | 0.0 | 211 ms | 0 |
| Sat 01 | 0 | 0.0 | 115 ms | 0 |
| Sat 03 | 0 | 0.0 | 129 ms | 0 |
| Sat 05 | 0 | 0.0 | 116 ms | 0 |
| Sat 06 | 0 | 0.0 | 177 ms | 0 |
| Sat 07 | 0 | 0.0 | 45 ms | 0 |
| Sat 09 | 0 | 0.0 | 46 ms | 0 |
| Sat 12 | 0 | 0.0 | 64 ms | 0 |
| Sat 14 | 0 | 0.0 | 77 ms | 0 |
| Sat 17 | 0 | 0.0 | 138 ms | 0 |
| Sat 19 | 0 | 0.0 | 141 ms | 0 |
| Sat 21 | 0 | 0.0 | 173 ms | 0 |
| Sat 23 | 0 | 0.0 | 122 ms | 0 |
| Sun 02 | 0 | 0.0 | 128 ms | 0 |
| Sun 04 | 0 | 0.0 | 212 ms | 0 |
| Sun 07 | 0 | 0.0 | 73 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Netwitness yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Netwitness goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Netwitness, at netwitness.com, is one of the Cloud & developer services we monitor. Netwitness delivers unified threat detection and response across network, endpoint, and cloud. Protect your enterprise with intelligent, real-time security.
Netwitness publishes an official status page at status.netwitness.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 115 ms average, 46–212 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Netwitness incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
115 ms on average over the last 24 hours (46–212 ms).
Yes, at https://status.netwitness.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Netwitness here at once, the problem is on Netwitness'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 Netwitness. 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.