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 1 hr ago. Last stored result reached it in 195 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 481 ms | 0 |
| Tue 05 | 0 | 0.0 | 502 ms | 0 |
| Tue 08 | 0 | 0.0 | 518 ms | 0 |
| Tue 10 | 0 | 0.0 | 537 ms | 0 |
| Tue 12 | 0 | 0.0 | 277 ms | 0 |
| Tue 14 | 0 | 0.0 | 532 ms | 0 |
| Tue 16 | 0 | 0.0 | 422 ms | 0 |
| Tue 19 | 0 | 0.0 | 540 ms | 0 |
| Tue 21 | 0 | 0.0 | 268 ms | 0 |
| Tue 23 | 0 | 0.0 | 508 ms | 0 |
| Wed 01 | 0 | 0.0 | 551 ms | 0 |
| Wed 04 | 0 | 0.0 | 469 ms | 0 |
| Wed 06 | 0 | 0.0 | 344 ms | 0 |
| Wed 08 | 0 | 0.0 | 156 ms | 0 |
| Wed 10 | 0 | 0.0 | 210 ms | 0 |
| Wed 13 | 0 | 0.0 | 220 ms | 0 |
| Wed 15 | 0 | 0.0 | 227 ms | 0 |
| Wed 17 | 0 | 0.0 | 428 ms | 0 |
| Wed 19 | 0 | 0.0 | 382 ms | 0 |
| Wed 21 | 0 | 0.0 | 272 ms | 0 |
| Wed 23 | 0 | 0.0 | 437 ms | 0 |
| Thu 02 | 0 | 0.0 | 237 ms | 0 |
| Thu 04 | 0 | 0.0 | 153 ms | 0 |
| Thu 06 | 0 | 0.0 | 142 ms | 0 |
| Thu 08 | 0 | 0.0 | 292 ms | 0 |
| Thu 10 | 0 | 0.0 | 422 ms | 0 |
| Thu 12 | 0 | 0.0 | 464 ms | 0 |
| Thu 14 | 0 | 0.0 | 530 ms | 0 |
| Thu 16 | 0 | 0.0 | 202 ms | 0 |
| Thu 18 | 0 | 0.0 | 393 ms | 0 |
| Thu 20 | 0 | 0.0 | 421 ms | 0 |
| Thu 22 | 0 | 0.0 | 205 ms | 0 |
| Fri 00 | 0 | 0.0 | 291 ms | 0 |
| Fri 02 | 0 | 0.0 | 188 ms | 0 |
| Fri 04 | 0 | 0.0 | 692 ms | 0 |
| Fri 06 | 0 | 0.0 | 541 ms | 0 |
| Fri 08 | 0 | 0.0 | 416 ms | 0 |
| Fri 10 | 0 | 0.0 | 262 ms | 0 |
| Fri 11 | 0 | 0.0 | 424 ms | 0 |
| Fri 13 | 0 | 0.0 | 525 ms | 0 |
| Fri 15 | 0 | 0.0 | 234 ms | 0 |
| Fri 17 | 0 | 0.0 | 575 ms | 0 |
| Fri 19 | 0 | 0.0 | 301 ms | 0 |
| Fri 21 | 0 | 0.0 | 583 ms | 0 |
| Fri 23 | 0 | 0.0 | 224 ms | 0 |
| Sat 00 | 0 | 0.0 | 414 ms | 0 |
| Sat 02 | 0 | 0.0 | 589 ms | 0 |
| Sat 04 | 0 | 0.0 | 195 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Yorkn 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 Yorkn goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Yorkn alerts to Slack, Discord or a webhook — free.
We track Yorkn (yorkn.com) as part of the Cloud & developer group. Yorkn Inc. is a promotional products supplier serving distributors across Canada and the USA since 2012 — 20,000+ custom branded items with USD & CAD pricing, freight, duties and a one-colour imprint included.
Yorkn publishes an official status page at status.yorkn.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 397 ms average, 131–589 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 Yorkn incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
397 ms on average over the last 24 hours (131–589 ms).
Yes, at https://status.yorkn.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 Yorkn here at once, the problem is on Yorkn'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 Yorkn. 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.