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 142 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 101 ms | 0 |
| Mon 16 | 0 | 0.0 | 235 ms | 0 |
| Mon 18 | 0 | 0.0 | 115 ms | 0 |
| Mon 20 | 0 | 0.0 | 185 ms | 0 |
| Mon 22 | 0 | 0.0 | 324 ms | 0 |
| Tue 00 | 0 | 0.0 | 209 ms | 0 |
| Tue 02 | 0 | 0.0 | 334 ms | 0 |
| Tue 04 | 0 | 0.0 | 118 ms | 0 |
| Tue 07 | 0 | 0.0 | 221 ms | 0 |
| Tue 09 | 0 | 0.0 | 79 ms | 0 |
| Tue 11 | 0 | 0.0 | 143 ms | 0 |
| Tue 13 | 0 | 0.0 | 164 ms | 0 |
| Tue 15 | 0 | 0.0 | 195 ms | 0 |
| Tue 18 | 0 | 0.0 | 107 ms | 0 |
| Tue 20 | 0 | 0.0 | 264 ms | 0 |
| Tue 22 | 0 | 0.0 | 233 ms | 0 |
| Wed 00 | 0 | 0.0 | 446 ms | 0 |
| Wed 03 | 0 | 0.0 | 195 ms | 0 |
| Wed 05 | 0 | 0.0 | 168 ms | 0 |
| Wed 07 | 0 | 0.0 | 136 ms | 0 |
| Wed 09 | 0 | 0.0 | 100 ms | 0 |
| Wed 12 | 0 | 0.0 | 172 ms | 0 |
| Wed 14 | 0 | 0.0 | 136 ms | 0 |
| Wed 16 | 0 | 0.0 | 158 ms | 0 |
| Wed 18 | 0 | 0.0 | 159 ms | 0 |
| Wed 20 | 0 | 0.0 | 180 ms | 0 |
| Wed 22 | 0 | 0.0 | 120 ms | 0 |
| Thu 01 | 0 | 0.0 | 187 ms | 0 |
| Thu 03 | 0 | 0.0 | 84 ms | 0 |
| Thu 05 | 0 | 0.0 | 226 ms | 0 |
| Thu 07 | 0 | 0.0 | 113 ms | 0 |
| Thu 09 | 0 | 0.0 | 112 ms | 0 |
| Thu 11 | 0 | 0.0 | 224 ms | 0 |
| Thu 13 | 0 | 0.0 | 192 ms | 0 |
| Thu 15 | 0 | 0.0 | 316 ms | 0 |
| Thu 17 | 0 | 0.0 | 220 ms | 0 |
| Thu 19 | 0 | 0.0 | 106 ms | 0 |
| Thu 21 | 0 | 0.0 | 129 ms | 0 |
| Thu 23 | 0 | 0.0 | 315 ms | 0 |
| Fri 01 | 0 | 0.0 | 143 ms | 0 |
| Fri 03 | 0 | 0.0 | 201 ms | 0 |
| Fri 05 | 0 | 0.0 | 118 ms | 0 |
| Fri 07 | 0 | 0.0 | 237 ms | 0 |
| Fri 08 | 0 | 0.0 | 116 ms | 0 |
| Fri 10 | 0 | 0.0 | 196 ms | 0 |
| Fri 12 | 0 | 0.0 | 107 ms | 0 |
| Fri 14 | 0 | 0.0 | 124 ms | 0 |
| Fri 16 | 0 | 0.0 | 142 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 Upflow 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 Upflow goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Upflow alerts to Slack, Discord or a webhook — free.
Upflow, at upflow.io, is one of the Cloud & developer services we monitor. Accounts receivable software that gets you paid with agents you can trust. Uncover insights, run your AR playbook, and turn invoices into matched cash.
Upflow publishes an official status page at status.upflow.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 160 ms average, 71–315 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Upflow incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
160 ms on average over the last 24 hours (71–315 ms).
Yes, at https://status.upflow.io.
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 Upflow here at once, the problem is on Upflow'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 Upflow. 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.