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 13 min ago. Last stored result reached it in 175 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 172 ms | 0 |
| Mon 16 | 0 | 0.0 | 199 ms | 0 |
| Mon 18 | 0 | 0.0 | 21 ms | 0 |
| Mon 20 | 0 | 0.0 | 105 ms | 0 |
| Mon 22 | 0 | 0.0 | 163 ms | 0 |
| Tue 00 | 0 | 0.0 | 85 ms | 0 |
| Tue 02 | 0 | 0.0 | 126 ms | 0 |
| Tue 04 | 0 | 0.0 | 181 ms | 0 |
| Tue 06 | 0 | 0.0 | 139 ms | 0 |
| Tue 09 | 0 | 0.0 | 95 ms | 0 |
| Tue 11 | 0 | 0.0 | 173 ms | 0 |
| Tue 13 | 0 | 0.0 | 171 ms | 0 |
| Tue 15 | 0 | 0.0 | 100 ms | 0 |
| Tue 17 | 0 | 0.0 | 172 ms | 0 |
| Tue 20 | 0 | 0.0 | 184 ms | 0 |
| Tue 22 | 0 | 0.0 | 1483 ms | 0 |
| Wed 00 | 0 | 0.0 | 158 ms | 0 |
| Wed 02 | 0 | 0.0 | 113 ms | 0 |
| Wed 05 | 0 | 0.0 | 106 ms | 0 |
| Wed 07 | 0 | 0.0 | 248 ms | 0 |
| Wed 09 | 0 | 0.0 | 173 ms | 0 |
| Wed 11 | 0 | 0.0 | 382 ms | 0 |
| Wed 14 | 0 | 0.0 | 175 ms | 0 |
| Wed 16 | 0 | 0.0 | 222 ms | 0 |
| Wed 18 | 0 | 0.0 | 163 ms | 0 |
| Wed 20 | 0 | 0.0 | 147 ms | 0 |
| Wed 22 | 0 | 0.0 | 165 ms | 0 |
| Thu 00 | 0 | 0.0 | 228 ms | 0 |
| Thu 03 | 0 | 0.0 | 228 ms | 0 |
| Thu 05 | 0 | 0.0 | 226 ms | 0 |
| Thu 07 | 0 | 0.0 | 123 ms | 0 |
| Thu 09 | 0 | 0.0 | 91 ms | 0 |
| Thu 11 | 0 | 0.0 | 113 ms | 0 |
| Thu 13 | 0 | 0.0 | 202 ms | 0 |
| Thu 15 | 0 | 0.0 | 82 ms | 0 |
| Thu 17 | 0 | 0.0 | 90 ms | 0 |
| Thu 19 | 0 | 0.0 | 170 ms | 0 |
| Thu 21 | 0 | 0.0 | 208 ms | 0 |
| Thu 23 | 0 | 0.0 | 105 ms | 0 |
| Fri 01 | 0 | 0.0 | 203 ms | 0 |
| Fri 03 | 0 | 0.0 | 85 ms | 0 |
| Fri 05 | 0 | 0.0 | 158 ms | 0 |
| Fri 07 | 0 | 0.0 | 167 ms | 0 |
| Fri 09 | 0 | 0.0 | 99 ms | 0 |
| Fri 11 | 0 | 0.0 | 84 ms | 0 |
| Fri 14 | 0 | 0.0 | 167 ms | 0 |
| Fri 16 | 0 | 0.0 | 217 ms | 0 |
| Fri 18 | 0 | 0.0 | 175 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 Procurify 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 Procurify goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Procurify alerts to Slack, Discord or a webhook — free.
We track Procurify (procurify.com) as part of the Money group. See what your company is spending before the money moves. Procurement software that runs intake, approvals, POs and payment on one agentic platform.
Procurify publishes an official status page at status.procurify.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 150 ms average, 69–217 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 Procurify incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
150 ms on average over the last 24 hours (69–217 ms).
Yes, at https://status.procurify.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 Procurify here at once, the problem is on Procurify'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 Procurify. 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.