User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
sortly.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 11 min ago. Last stored result reached it in 74 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 173 ms | 0 |
| Mon 16 | 0 | 0.0 | 311 ms | 0 |
| Mon 18 | 0 | 0.0 | 162 ms | 0 |
| Mon 20 | 0 | 0.0 | 198 ms | 0 |
| Mon 23 | 0 | 0.0 | 139 ms | 0 |
| Tue 01 | 0 | 0.0 | 251 ms | 0 |
| Tue 03 | 0 | 0.0 | 252 ms | 0 |
| Tue 05 | 0 | 0.0 | 265 ms | 0 |
| Tue 07 | 0 | 0.0 | 276 ms | 0 |
| Tue 09 | 0 | 0.0 | 223 ms | 0 |
| Tue 11 | 0 | 0.0 | 161 ms | 0 |
| Tue 13 | 0 | 0.0 | 259 ms | 0 |
| Tue 16 | 0 | 0.0 | 172 ms | 0 |
| Tue 18 | 0 | 0.0 | 97 ms | 0 |
| Tue 20 | 0 | 0.0 | 315 ms | 0 |
| Tue 23 | 0 | 0.0 | 210 ms | 0 |
| Wed 01 | 0 | 0.0 | 147 ms | 0 |
| Wed 03 | 0 | 0.0 | 152 ms | 0 |
| Wed 05 | 0 | 0.0 | 172 ms | 0 |
| Wed 07 | 0 | 0.0 | 152 ms | 0 |
| Wed 10 | 0 | 0.0 | 109 ms | 0 |
| Wed 12 | 0 | 0.0 | 141 ms | 0 |
| Wed 14 | 0 | 0.0 | 164 ms | 0 |
| Wed 16 | 0 | 0.0 | 374 ms | 0 |
| Wed 18 | 0 | 0.0 | 315 ms | 0 |
| Wed 21 | 0 | 0.0 | 245 ms | 0 |
| Wed 23 | 0 | 0.0 | 269 ms | 0 |
| Thu 01 | 0 | 0.0 | 269 ms | 0 |
| Thu 03 | 0 | 0.0 | 171 ms | 0 |
| Thu 05 | 0 | 0.0 | 311 ms | 0 |
| Thu 07 | 0 | 0.0 | 157 ms | 0 |
| Thu 09 | 0 | 0.0 | 362 ms | 0 |
| Thu 11 | 0 | 0.0 | 160 ms | 0 |
| Thu 13 | 0 | 0.0 | 283 ms | 0 |
| Thu 15 | 0 | 0.0 | 244 ms | 0 |
| Thu 17 | 0 | 0.0 | 309 ms | 0 |
| Thu 20 | 0 | 0.0 | 270 ms | 0 |
| Thu 22 | 0 | 0.0 | 202 ms | 0 |
| Fri 00 | 0 | 0.0 | 153 ms | 0 |
| Fri 02 | 0 | 0.0 | 169 ms | 0 |
| Fri 04 | 0 | 0.0 | 307 ms | 0 |
| Fri 06 | 0 | 0.0 | 409 ms | 0 |
| Fri 07 | 0 | 0.0 | 185 ms | 0 |
| Fri 09 | 0 | 0.0 | 180 ms | 0 |
| Fri 11 | 0 | 0.0 | 388 ms | 0 |
| Fri 13 | 0 | 0.0 | 168 ms | 0 |
| Fri 15 | 0 | 0.0 | 74 ms | 0 |
| Fri 17 | 0 | 0.0 | 171 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 Sortly 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 Sortly goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sortly alerts to Slack, Discord or a webhook — free.
We track Sortly (sortly.com) as part of the Cloud & developer group. Take control of your inventory with an easy system that keeps up with your people, locations, and workflows. Try Sortly free for 14 days.
Sortly publishes an official status page at status.sortly.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 230 ms average, 74–409 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 Sortly incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
230 ms on average over the last 24 hours (74–409 ms).
Yes, at https://status.sortly.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 Sortly here at once, the problem is on Sortly'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 Sortly. 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.