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 50 min ago. Last stored result reached it in 461 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 23 | 0 | 0.0 | 622 ms | 0 |
| Wed 01 | 0 | 0.0 | 503 ms | 0 |
| Wed 03 | 0 | 0.0 | 575 ms | 0 |
| Wed 06 | 0 | 0.0 | 655 ms | 0 |
| Wed 08 | 0 | 0.0 | 647 ms | 0 |
| Wed 10 | 0 | 0.0 | 366 ms | 0 |
| Wed 12 | 0 | 0.0 | 490 ms | 0 |
| Wed 14 | 0 | 0.0 | 546 ms | 0 |
| Wed 16 | 0 | 0.0 | 443 ms | 0 |
| Wed 19 | 0 | 0.0 | 484 ms | 0 |
| Wed 21 | 0 | 0.0 | 501 ms | 0 |
| Wed 23 | 0 | 0.0 | 491 ms | 0 |
| Thu 01 | 0 | 0.0 | 466 ms | 0 |
| Thu 03 | 0 | 0.0 | 510 ms | 0 |
| Thu 05 | 0 | 0.0 | 558 ms | 0 |
| Thu 07 | 0 | 0.0 | 519 ms | 0 |
| Thu 10 | 0 | 0.0 | 419 ms | 0 |
| Thu 12 | 0 | 0.0 | 413 ms | 0 |
| Thu 14 | 0 | 0.0 | 21 ms | 0 |
| Thu 16 | 0 | 0.0 | 389 ms | 0 |
| Thu 18 | 0 | 0.0 | 554 ms | 0 |
| Thu 20 | 0 | 0.0 | 529 ms | 0 |
| Thu 22 | 0 | 0.0 | 558 ms | 0 |
| Fri 00 | 0 | 0.0 | 515 ms | 0 |
| Fri 02 | 0 | 0.0 | 500 ms | 0 |
| Fri 04 | 0 | 0.0 | 540 ms | 0 |
| Fri 06 | 0 | 0.0 | 394 ms | 0 |
| Fri 08 | 0 | 0.0 | 447 ms | 0 |
| Fri 10 | 0 | 0.0 | 481 ms | 0 |
| Fri 12 | 0 | 0.0 | 472 ms | 0 |
| Fri 14 | 0 | 0.0 | 506 ms | 0 |
| Fri 16 | 0 | 0.0 | 526 ms | 0 |
| Fri 18 | 0 | 0.0 | 496 ms | 0 |
| Fri 20 | 0 | 0.0 | 625 ms | 0 |
| Fri 22 | 0 | 0.0 | 461 ms | 0 |
| Sat 00 | 0 | 0.0 | 503 ms | 0 |
| Sat 01 | 0 | 0.0 | 504 ms | 0 |
| Sat 03 | 0 | 0.0 | 517 ms | 0 |
| Sat 05 | 0 | 0.0 | 570 ms | 0 |
| Sat 07 | 0 | 0.0 | 263 ms | 0 |
| Sat 09 | 0 | 0.0 | 424 ms | 0 |
| Sat 11 | 0 | 0.0 | 396 ms | 0 |
| Sat 14 | 0 | 0.0 | 484 ms | 0 |
| Sat 15 | 0 | 0.0 | 612 ms | 0 |
| Sat 17 | 0 | 0.0 | 442 ms | 0 |
| Sat 20 | 0 | 0.0 | 470 ms | 0 |
| Sat 22 | 0 | 0.0 | 356 ms | 0 |
| Sun 00 | 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 10 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 confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 451 ms average, 263–612 ms range across 13 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 10 days ago.
From our own checks: 100% over 10 days of checks.
451 ms on average over the last 24 hours (263–612 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.