User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 31 min ago. Last stored result reached it in 446 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 00:15 | 0 | 0.0 | 515 ms | 0 |
| 02:30 | 0 | 0.0 | 500 ms | 0 |
| 04:30 | 0 | 0.0 | 540 ms | 0 |
| 06:30 | 0 | 0.0 | 394 ms | 0 |
| 08:30 | 0 | 0.0 | 447 ms | 0 |
| 10:45 | 0 | 0.0 | 481 ms | 0 |
| 12:30 | 0 | 0.0 | 472 ms | 0 |
| 14:30 | 0 | 0.0 | 506 ms | 0 |
| 16:30 | 0 | 0.0 | 526 ms | 0 |
| 18:30 | 0 | 0.0 | 496 ms | 0 |
| 20:00 | 0 | 0.0 | 613 ms | 0 |
| 20:30 | 0 | 0.0 | 637 ms | 0 |
| 22:15 | 0 | 0.0 | 461 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for SANS Institute 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 SANS Institute goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SANS Institute alerts to Slack, Discord or a webhook — free.
We track SANS Institute (sans.org) as part of the Cloud & developer group. SANS Institute is the most trusted resource for cybersecurity training, certifications and research. Offering more than 60 courses across all practice areas, SANS trains over 40,000 cybersecurity professionals annually.
SANS Institute publishes an official status page at status.sans.org; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 503 ms average, 394–637 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SANS Institute incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
503 ms on average over the last 24 hours (394–637 ms).
Yes, at https://status.sans.org.
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 SANS Institute here at once, the problem is on SANS Institute'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 SANS Institute. 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.