User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 280 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 242 ms | 0 |
| Mon 18 | 0 | 0.0 | 189 ms | 0 |
| Mon 20 | 0 | 0.0 | 84 ms | 0 |
| Mon 22 | 0 | 0.0 | 126 ms | 0 |
| Tue 00 | 0 | 0.0 | 302 ms | 0 |
| Tue 02 | 0 | 0.0 | 212 ms | 0 |
| Tue 04 | 0 | 0.0 | 177 ms | 0 |
| Tue 07 | 0 | 0.0 | 169 ms | 0 |
| Tue 09 | 0 | 0.0 | 207 ms | 0 |
| Tue 11 | 0 | 0.0 | 184 ms | 0 |
| Tue 13 | 0 | 0.0 | 225 ms | 0 |
| Tue 15 | 0 | 0.0 | 288 ms | 0 |
| Tue 18 | 0 | 0.0 | 254 ms | 0 |
| Tue 20 | 0 | 0.0 | 105 ms | 0 |
| Tue 22 | 0 | 0.0 | 135 ms | 0 |
| Wed 00 | 0 | 0.0 | 261 ms | 0 |
| Wed 03 | 0 | 0.0 | 212 ms | 0 |
| Wed 05 | 0 | 0.0 | 452 ms | 0 |
| Wed 07 | 0 | 0.0 | 73 ms | 0 |
| Wed 09 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 155 ms | 0 |
| Wed 14 | 0 | 0.0 | 108 ms | 0 |
| Wed 16 | 0 | 0.0 | 290 ms | 0 |
| Wed 18 | 0 | 0.0 | 266 ms | 0 |
| Wed 20 | 0 | 0.0 | 176 ms | 0 |
| Wed 22 | 0 | 0.0 | 229 ms | 0 |
| Thu 01 | 0 | 0.0 | 234 ms | 0 |
| Thu 03 | 0 | 0.0 | 161 ms | 0 |
| Thu 05 | 0 | 0.0 | 287 ms | 0 |
| Thu 07 | 0 | 0.0 | 273 ms | 0 |
| Thu 09 | 0 | 0.0 | 104 ms | 0 |
| Thu 11 | 0 | 0.0 | 136 ms | 0 |
| Thu 13 | 0 | 0.0 | 111 ms | 0 |
| Thu 15 | 0 | 0.0 | 133 ms | 0 |
| Thu 17 | 0 | 0.0 | 450 ms | 0 |
| Thu 19 | 0 | 0.0 | 336 ms | 0 |
| Thu 21 | 0 | 0.0 | 343 ms | 0 |
| Thu 23 | 0 | 0.0 | 269 ms | 0 |
| Fri 01 | 0 | 0.0 | 186 ms | 0 |
| Fri 03 | 0 | 0.0 | 301 ms | 0 |
| Fri 06 | 0 | 0.0 | 187 ms | 0 |
| Fri 08 | 0 | 0.0 | 155 ms | 0 |
| Fri 10 | 0 | 0.0 | 58 ms | 0 |
| Fri 11 | 0 | 0.0 | 87 ms | 0 |
| Fri 13 | 0 | 0.0 | 128 ms | 0 |
| Fri 15 | 0 | 0.0 | 191 ms | 0 |
| Fri 17 | 0 | 0.0 | 163 ms | 0 |
| Fri 18 | 0 | 0.0 | 280 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Uphance 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 Uphance goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Uphance alerts to Slack, Discord or a webhook — free.
Uphance is listed in our Money category and checked at uphance.com. Apparel management software for wholesale and DTC brands with warehouse or 3PL complexity: PLM, production, inventory, orders, and accounting in one system.
Uphance publishes an official status page at status.uphance.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 185 ms average, 57–343 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Uphance incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
185 ms on average over the last 24 hours (57–343 ms).
Yes, at https://status.uphance.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Uphance here at once, the problem is on Uphance'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 Uphance. 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.