User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Codat 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 → codat.io—
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 5 min ago. Last stored result reached it in 125 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 |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 112 ms | 0 |
| Mon 14 | 0 | 0.0 | 105 ms | 0 |
| Mon 16 | 0 | 0.0 | 120 ms | 0 |
| Mon 18 | 0 | 0.0 | 104 ms | 0 |
| Mon 20 | 0 | 0.0 | 119 ms | 0 |
| Mon 22 | 0 | 0.0 | 101 ms | 0 |
| Tue 01 | 0 | 0.0 | 112 ms | 0 |
| Tue 03 | 0 | 0.0 | 110 ms | 0 |
| Tue 05 | 0 | 0.0 | 122 ms | 0 |
| Tue 07 | 0 | 0.0 | 108 ms | 0 |
| Tue 09 | 0 | 0.0 | 102 ms | 0 |
| Tue 11 | 0 | 0.0 | 230 ms | 0 |
| Tue 13 | 0 | 0.0 | 108 ms | 0 |
| Tue 16 | 0 | 0.0 | 100 ms | 0 |
| Tue 18 | 0 | 0.0 | 107 ms | 0 |
| Tue 20 | 0 | 0.0 | 112 ms | 0 |
| Tue 22 | 0 | 0.0 | 118 ms | 0 |
| Wed 01 | 0 | 0.0 | 116 ms | 0 |
| Wed 03 | 0 | 0.0 | 276 ms | 0 |
| Wed 05 | 0 | 0.0 | 93 ms | 0 |
| Wed 06 | 0 | 0.0 | 120 ms | 0 |
| Wed 08 | 0 | 0.0 | 101 ms | 0 |
| Wed 11 | 0 | 0.0 | 84 ms | 0 |
| Wed 13 | 0 | 0.0 | 94 ms | 0 |
| Wed 15 | 0 | 0.0 | 119 ms | 0 |
| Wed 17 | 0 | 0.0 | 94 ms | 0 |
| Wed 19 | 0 | 0.0 | 103 ms | 0 |
| Wed 21 | 0 | 0.0 | 140 ms | 0 |
| Wed 23 | 0 | 0.0 | 107 ms | 0 |
| Thu 02 | 0 | 0.0 | 128 ms | 0 |
| Thu 04 | 0 | 0.0 | 103 ms | 0 |
| Thu 06 | 0 | 0.0 | 107 ms | 0 |
| Thu 08 | 0 | 0.0 | 110 ms | 0 |
| Thu 10 | 0 | 0.0 | 104 ms | 0 |
| Thu 12 | 0 | 0.0 | 109 ms | 0 |
| Thu 14 | 0 | 0.0 | 113 ms | 0 |
| Thu 16 | 0 | 0.0 | 127 ms | 0 |
| Thu 18 | 0 | 0.0 | 117 ms | 0 |
| Thu 20 | 0 | 0.0 | 83 ms | 0 |
| Thu 22 | 0 | 0.0 | 111 ms | 0 |
| Fri 00 | 0 | 0.0 | 108 ms | 0 |
| Fri 02 | 0 | 0.0 | 125 ms | 0 |
| Fri 04 | 0 | 0.0 | 121 ms | 0 |
| Fri 06 | 0 | 0.0 | 102 ms | 0 |
| Fri 09 | 0 | 0.0 | 127 ms | 0 |
| Fri 11 | 0 | 0.0 | 84 ms | 0 |
| Fri 13 | 0 | 0.0 | 124 ms | 0 |
| Fri 15 | 0 | 0.0 | 125 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 Codat badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Codat yet. Outages of 10 minutes or more get their own page here.
Having trouble with Codat?
One report per service every 10 minutes from this network. No account.
Follow Codat
Get an email when Codat goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Codat alerts to Slack, Discord or a webhook — free.
About Codat
We track Codat (codat.io) as part of the Money group. Codat turns on-demand client data into personalized insights that help commercial banking teams deepen relationships and grow revenue.
Codat publishes an official status page at status.codat.io; 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: 113 ms average, 83–127 ms range across 12 successful checks.
Questions
Is Codat down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Codat last down?
We have not recorded a public Codat incident since monitoring began 8 days ago.
What is Codat's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Codat respond?
113 ms on average over the last 24 hours (83–127 ms).
Does Codat have an official status page?
Yes, at https://status.codat.io.
Codat 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 Codat here at once, the problem is on Codat'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 Codat. 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.