User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Modern Treasury down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → moderntreasury.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 481 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 505 ms | 0 |
| Tue 11 | 0 | 0.0 | 567 ms | 0 |
| Tue 13 | 0 | 0.0 | 447 ms | 0 |
| Tue 15 | 0 | 0.0 | 525 ms | 0 |
| Tue 17 | 0 | 0.0 | 593 ms | 0 |
| Tue 20 | 0 | 0.0 | 337 ms | 0 |
| Tue 22 | 0 | 0.0 | 371 ms | 0 |
| Wed 00 | 0 | 0.0 | 468 ms | 0 |
| Wed 02 | 0 | 0.0 | 460 ms | 0 |
| Wed 05 | 0 | 0.0 | 427 ms | 0 |
| Wed 07 | 0 | 0.0 | 547 ms | 0 |
| Wed 09 | 0 | 0.0 | 577 ms | 0 |
| Wed 11 | 0 | 0.0 | 513 ms | 0 |
| Wed 13 | 0 | 0.0 | 612 ms | 0 |
| Wed 15 | 0 | 0.0 | 521 ms | 0 |
| Wed 18 | 0 | 0.0 | 464 ms | 0 |
| Wed 20 | 0 | 0.0 | 481 ms | 0 |
| Wed 22 | 0 | 0.0 | 501 ms | 0 |
| Thu 00 | 0 | 0.0 | 403 ms | 0 |
| Thu 02 | 0 | 0.0 | 557 ms | 0 |
| Thu 04 | 0 | 0.0 | 388 ms | 0 |
| Thu 06 | 0 | 0.0 | 662 ms | 0 |
| Thu 08 | 0 | 0.0 | 576 ms | 0 |
| Thu 10 | 0 | 0.0 | 588 ms | 0 |
| Thu 13 | 0 | 0.0 | 436 ms | 0 |
| Thu 15 | 0 | 0.0 | 541 ms | 0 |
| Thu 17 | 0 | 0.0 | 565 ms | 0 |
| Thu 18 | 0 | 0.0 | 375 ms | 0 |
| Thu 20 | 0 | 0.0 | 648 ms | 0 |
| Thu 22 | 0 | 0.0 | 374 ms | 0 |
| Fri 00 | 0 | 0.0 | 508 ms | 0 |
| Fri 02 | 0 | 0.0 | 310 ms | 0 |
| Fri 04 | 0 | 0.0 | 525 ms | 0 |
| Fri 06 | 0 | 0.0 | 580 ms | 0 |
| Fri 08 | 0 | 0.0 | 407 ms | 0 |
| Fri 10 | 0 | 0.0 | 577 ms | 0 |
| Fri 11 | 0 | 0.0 | 472 ms | 0 |
| Fri 12 | 0 | 0.0 | 620 ms | 0 |
| Fri 14 | 0 | 0.0 | 519 ms | 0 |
| Fri 16 | 0 | 0.0 | 575 ms | 0 |
| Fri 18 | 0 | 0.0 | 980 ms | 0 |
| Fri 20 | 0 | 0.0 | 501 ms | 0 |
| Fri 22 | 0 | 0.0 | 457 ms | 0 |
| Sat 00 | 0 | 0.0 | 467 ms | 0 |
| Sat 02 | 0 | 0.0 | 429 ms | 0 |
| Sat 04 | 0 | 0.0 | 911 ms | 0 |
| Sat 06 | 0 | 0.0 | 509 ms | 0 |
| Sat 08 | 0 | 0.0 | 481 ms | 0 |
Reliability
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.
Embed this status: free live Modern Treasury badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Database Maintenance
We are planning for a scheduled maintenance during that time.
Announced by Modern Treasury · sourceDatabase Maintenance
We are planning for a scheduled maintenance during that time.
Announced by Modern Treasury · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Modern Treasury yet. Outages of 10 minutes or more get their own page here.
Having trouble with Modern Treasury?
One report per service every 10 minutes from this network. No account.
Follow Modern Treasury
Get an email when Modern Treasury goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Modern Treasury alerts to Slack, Discord or a webhook — free.
About Modern Treasury
We track Modern Treasury (moderntreasury.com) as part of the Money group. A payment service provider (PSP) for fiat and stablecoin. Launch in days with one API, sub-accounts, and built-in compliance across ACH, RTP, FedNow, and wire.
Modern Treasury publishes an official status page at status.moderntreasury.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: 573 ms average, 429–980 ms range across 14 successful checks.
Questions
Is Modern Treasury down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Modern Treasury last down?
We have not recorded a public Modern Treasury incident since monitoring began 8 days ago.
What is Modern Treasury's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Modern Treasury respond?
573 ms on average over the last 24 hours (429–980 ms).
Does Modern Treasury have an official status page?
Yes, at https://status.moderntreasury.com.
Modern Treasury not working for me but the status is fine. What now?
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 Modern Treasury here at once, the problem is on Modern Treasury'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 Modern Treasury. 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.