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 30 min ago. Last stored result reached it in 343 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 493 ms | 0 |
| Tue 02 | 0 | 0.0 | 280 ms | 0 |
| Tue 04 | 0 | 0.0 | 340 ms | 0 |
| Tue 06 | 0 | 0.0 | 395 ms | 0 |
| Tue 08 | 0 | 0.0 | 277 ms | 0 |
| Tue 10 | 0 | 0.0 | 389 ms | 0 |
| Tue 13 | 0 | 0.0 | 395 ms | 0 |
| Tue 15 | 0 | 0.0 | 322 ms | 0 |
| Tue 17 | 0 | 0.0 | 332 ms | 0 |
| Tue 19 | 0 | 0.0 | 357 ms | 0 |
| Tue 22 | 0 | 0.0 | 267 ms | 0 |
| Wed 00 | 0 | 0.0 | 371 ms | 0 |
| Wed 02 | 0 | 0.0 | 370 ms | 0 |
| Wed 04 | 0 | 0.0 | 323 ms | 0 |
| Wed 06 | 0 | 0.0 | 287 ms | 0 |
| Wed 09 | 0 | 0.0 | 315 ms | 0 |
| Wed 11 | 0 | 0.0 | 339 ms | 0 |
| Wed 13 | 0 | 0.0 | 354 ms | 0 |
| Wed 15 | 0 | 0.0 | 355 ms | 0 |
| Wed 17 | 0 | 0.0 | 445 ms | 0 |
| Wed 20 | 0 | 0.0 | 396 ms | 0 |
| Wed 22 | 0 | 0.0 | 308 ms | 0 |
| Thu 00 | 0 | 0.0 | 282 ms | 0 |
| Thu 02 | 0 | 0.0 | 328 ms | 0 |
| Thu 04 | 0 | 0.0 | 333 ms | 0 |
| Thu 06 | 0 | 0.0 | 356 ms | 0 |
| Thu 08 | 0 | 0.0 | 351 ms | 0 |
| Thu 10 | 0 | 0.0 | 293 ms | 0 |
| Thu 12 | 0 | 0.0 | 287 ms | 0 |
| Thu 14 | 0 | 0.0 | 371 ms | 0 |
| Thu 16 | 0 | 0.0 | 380 ms | 0 |
| Thu 19 | 0 | 0.0 | 402 ms | 0 |
| Thu 21 | 0 | 0.0 | 420 ms | 0 |
| Thu 23 | 0 | 0.0 | 252 ms | 0 |
| Fri 01 | 0 | 0.0 | 376 ms | 0 |
| Fri 02 | 0 | 0.0 | 315 ms | 0 |
| Fri 04 | 0 | 0.0 | 286 ms | 0 |
| Fri 06 | 0 | 0.0 | 300 ms | 0 |
| Fri 08 | 0 | 0.0 | 233 ms | 0 |
| Fri 10 | 0 | 0.0 | 300 ms | 0 |
| Fri 11 | 0 | 0.0 | 216 ms | 0 |
| Fri 13 | 0 | 0.0 | 277 ms | 0 |
| Fri 15 | 0 | 0.0 | 415 ms | 0 |
| Fri 17 | 0 | 0.0 | 300 ms | 0 |
| Fri 18 | 0 | 0.0 | 390 ms | 0 |
| Fri 19 | 0 | 0.0 | 278 ms | 0 |
| Fri 21 | 0 | 0.0 | 311 ms | 0 |
| Fri 22 | 0 | 0.0 | 343 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 Extensiv 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 Extensiv goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Extensiv alerts to Slack, Discord or a webhook — free.
Extensiv is listed in our Money category and checked at extensiv.com. Serve every client: big and bulky, serialized inventory, wholesale or ecommerce. 3PL WMS with EDI, integrations, and flexible, accurate billing. See a demo.
Extensiv publishes an official status page at status.extensiv.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 301 ms average, 216–415 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Extensiv incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
301 ms on average over the last 24 hours (216–415 ms).
Yes, at https://status.extensiv.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 Extensiv here at once, the problem is on Extensiv'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 Extensiv. 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.