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 2 hr ago. Last stored result reached it in 2237 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 06 | 0 | 0.0 | 2053 ms | 0 |
| Tue 08 | 0 | 0.0 | 2017 ms | 0 |
| Tue 10 | 0 | 0.0 | 2814 ms | 0 |
| Tue 12 | 0 | 0.0 | 4537 ms | 0 |
| Tue 13 | 0 | 0.0 | 1921 ms | 0 |
| Tue 15 | 0 | 0.0 | 2340 ms | 0 |
| Tue 17 | 0 | 0.0 | 1743 ms | 0 |
| Tue 19 | 0 | 0.0 | 2363 ms | 0 |
| Tue 22 | 0 | 0.0 | 2267 ms | 0 |
| Wed 00 | 0 | 0.0 | 2894 ms | 0 |
| Wed 02 | 0 | 0.0 | 2500 ms | 0 |
| Wed 04 | 0 | 0.0 | 2682 ms | 0 |
| Wed 06 | 0 | 0.0 | 3868 ms | 0 |
| Wed 09 | 0 | 0.0 | 2625 ms | 0 |
| Wed 11 | 0 | 0.0 | 3711 ms | 0 |
| Wed 13 | 0 | 0.0 | 2813 ms | 0 |
| Wed 15 | 0 | 0.0 | 2903 ms | 0 |
| Wed 17 | 0 | 0.0 | 3544 ms | 0 |
| Wed 20 | 0 | 0.0 | 2322 ms | 0 |
| Wed 22 | 0 | 0.0 | 3046 ms | 0 |
| Thu 00 | 0 | 0.0 | 2421 ms | 0 |
| Thu 02 | 0 | 0.0 | 1909 ms | 0 |
| Thu 04 | 0 | 0.0 | 2466 ms | 0 |
| Thu 06 | 0 | 0.0 | 2478 ms | 0 |
| Thu 08 | 0 | 0.0 | 2871 ms | 0 |
| Thu 10 | 0 | 0.0 | 2650 ms | 0 |
| Thu 12 | 0 | 0.0 | 2590 ms | 0 |
| Thu 14 | 0 | 0.0 | 2796 ms | 0 |
| Thu 15 | 0 | 0.0 | 2086 ms | 0 |
| Thu 17 | 0 | 0.0 | 2603 ms | 0 |
| Thu 19 | 0 | 0.0 | 2948 ms | 0 |
| Thu 21 | 0 | 0.0 | 3711 ms | 0 |
| Thu 23 | 0 | 0.0 | 2517 ms | 0 |
| Fri 01 | 0 | 0.0 | 2526 ms | 0 |
| Fri 03 | 0 | 0.0 | 3290 ms | 0 |
| Fri 05 | 0 | 0.0 | 2435 ms | 0 |
| Fri 07 | 0 | 0.0 | 3404 ms | 0 |
| Fri 09 | 0 | 0.0 | 2813 ms | 0 |
| Fri 10 | 0 | 0.0 | 2591 ms | 0 |
| Fri 12 | 0 | 0.0 | 2982 ms | 0 |
| Fri 14 | 0 | 0.0 | 2502 ms | 0 |
| Fri 16 | 0 | 0.0 | 2397 ms | 0 |
| Fri 18 | 0 | 0.0 | 2591 ms | 0 |
| Fri 20 | 0 | 0.0 | 1839 ms | 0 |
| Fri 22 | 0 | 0.0 | 3005 ms | 0 |
| Fri 23 | 0 | 0.0 | 2464 ms | 0 |
| Sat 01 | 0 | 0.0 | 3641 ms | 0 |
| Sat 03 | 0 | 0.0 | 2237 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 SAMK 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 SAMK goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SAMK alerts to Slack, Discord or a webhook — free.
SAMK is listed in our Cloud & developer category and checked at samk.fi. Olemme monialainen ja kansainvälinen korkeakoulu. Länsirannikolla olemme merkittävä osaajien tekijä, kehittäjä, kansainvälistäjä ja yrittäjyyden edistäjä.
SAMK publishes an official status page at status.samk.fi; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 2681 ms average, 1839–3641 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 SAMK incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
2681 ms on average over the last 24 hours (1839–3641 ms).
Yes, at https://status.samk.fi.
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 SAMK here at once, the problem is on SAMK'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 SAMK. 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.