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 255 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 428 ms | 0 |
| Tue 02 | 0 | 0.0 | 208 ms | 0 |
| Tue 04 | 0 | 0.0 | 234 ms | 0 |
| Tue 07 | 0 | 0.0 | 203 ms | 0 |
| Tue 09 | 0 | 0.0 | 290 ms | 0 |
| Tue 11 | 0 | 0.0 | 301 ms | 0 |
| Tue 13 | 0 | 0.0 | 168 ms | 0 |
| Tue 15 | 0 | 0.0 | 441 ms | 0 |
| Tue 17 | 0 | 0.0 | 139 ms | 0 |
| Tue 20 | 0 | 0.0 | 302 ms | 0 |
| Tue 22 | 0 | 0.0 | 159 ms | 0 |
| Wed 00 | 0 | 0.0 | 390 ms | 0 |
| Wed 02 | 0 | 0.0 | 342 ms | 0 |
| Wed 05 | 0 | 0.0 | 290 ms | 0 |
| Wed 07 | 0 | 0.0 | 231 ms | 0 |
| Wed 09 | 0 | 0.0 | 347 ms | 0 |
| Wed 12 | 0 | 0.0 | 171 ms | 0 |
| Wed 14 | 0 | 0.0 | 283 ms | 0 |
| Wed 16 | 0 | 0.0 | 348 ms | 0 |
| Wed 18 | 0 | 0.0 | 445 ms | 0 |
| Wed 20 | 0 | 0.0 | 234 ms | 0 |
| Wed 22 | 0 | 0.0 | 210 ms | 0 |
| Thu 00 | 0 | 0.0 | 258 ms | 0 |
| Thu 03 | 0 | 0.0 | 408 ms | 0 |
| Thu 05 | 0 | 0.0 | 174 ms | 0 |
| Thu 07 | 0 | 0.0 | 270 ms | 0 |
| Thu 09 | 0 | 0.0 | 174 ms | 0 |
| Thu 11 | 0 | 0.0 | 180 ms | 0 |
| Thu 13 | 0 | 0.0 | 107 ms | 0 |
| Thu 15 | 0 | 0.0 | 167 ms | 0 |
| Thu 17 | 0 | 0.0 | 1156 ms | 0 |
| Thu 19 | 0 | 0.0 | 230 ms | 0 |
| Thu 21 | 0 | 0.0 | 278 ms | 0 |
| Thu 23 | 0 | 0.0 | 280 ms | 0 |
| Fri 01 | 0 | 0.0 | 224 ms | 0 |
| Fri 03 | 0 | 0.0 | 257 ms | 0 |
| Fri 06 | 0 | 0.0 | 264 ms | 0 |
| Fri 08 | 0 | 0.0 | 373 ms | 0 |
| Fri 10 | 0 | 0.0 | 184 ms | 0 |
| Fri 12 | 0 | 0.0 | 189 ms | 0 |
| Fri 14 | 0 | 0.0 | 197 ms | 0 |
| Fri 16 | 0 | 0.0 | 464 ms | 0 |
| Fri 17 | 0 | 0.0 | 331 ms | 0 |
| Fri 19 | 0 | 0.0 | 262 ms | 0 |
| Fri 21 | 0 | 0.0 | 233 ms | 0 |
| Fri 23 | 0 | 0.0 | 71 ms | 0 |
| Sat 01 | 0 | 0.0 | 321 ms | 0 |
| Sat 03 | 0 | 0.0 | 255 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tazapay 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 Tazapay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tazapay alerts to Slack, Discord or a webhook — free.
Tazapay is listed in our Money category and checked at tazapay.com. Simplify global payments with Tazapay’s all-in-one payment infrastructure, including cross-border collections, payouts to 100+ countries, virtual accounts in 40+ currencies, and stablecoin payments.
Tazapay publishes an official status page at status.tazapay.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 266 ms average, 71–486 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 Tazapay incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
266 ms on average over the last 24 hours (71–486 ms).
Yes, at https://status.tazapay.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 Tazapay here at once, the problem is on Tazapay'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 Tazapay. 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.