User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Our checks can't reach Definitive right now
Definitive is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 1 hr ago. Last stored result reached it in 33 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 52 ms | 0 |
| Mon 18 | 0 | 0.0 | 71 ms | 0 |
| Mon 20 | 0 | 0.0 | 128 ms | 0 |
| Mon 22 | 0 | 0.0 | 41 ms | 0 |
| Tue 00 | 0 | 0.0 | 27 ms | 0 |
| Tue 03 | 0 | 0.0 | 50 ms | 0 |
| Tue 05 | 0 | 0.0 | 41 ms | 0 |
| Tue 07 | 0 | 0.0 | 38 ms | 0 |
| Tue 09 | 0 | 0.0 | 39 ms | 0 |
| Tue 11 | 0 | 0.0 | 18 ms | 0 |
| Tue 13 | 0 | 0.0 | 31 ms | 0 |
| Tue 15 | 0 | 0.0 | 47 ms | 0 |
| Tue 18 | 0 | 0.0 | 36 ms | 0 |
| Tue 20 | 0 | 0.0 | 187 ms | 0 |
| Tue 22 | 0 | 0.0 | 188 ms | 0 |
| Wed 00 | 0 | 0.0 | 191 ms | 0 |
| Wed 03 | 0 | 0.0 | 34 ms | 0 |
| Wed 05 | 0 | 0.0 | 14 ms | 0 |
| Wed 07 | 0 | 0.0 | 19 ms | 0 |
| Wed 09 | 0 | 0.0 | 21 ms | 0 |
| Wed 12 | 0 | 0.0 | 25 ms | 0 |
| Wed 14 | 0 | 0.0 | 34 ms | 0 |
| Wed 16 | 0 | 0.0 | 24 ms | 0 |
| Wed 18 | 0 | 0.0 | 37 ms | 0 |
| Wed 20 | 0 | 0.0 | 19 ms | 0 |
| Wed 22 | 0 | 0.0 | 39 ms | 0 |
| Thu 01 | 0 | 0.0 | 27 ms | 0 |
| Thu 03 | 0 | 0.0 | 33 ms | 0 |
| Thu 05 | 0 | 0.0 | 163 ms | 0 |
| Thu 07 | 0 | 0.0 | 28 ms | 0 |
| Thu 09 | 0 | 0.0 | 21 ms | 0 |
| Thu 11 | 0 | 0.0 | 44 ms | 0 |
| Thu 13 | 0 | 0.0 | 39 ms | 0 |
| Thu 15 | 0 | 0.0 | 34 ms | 0 |
| Thu 17 | 0 | 0.0 | 44 ms | 0 |
| Thu 19 | 0 | 0.0 | 25 ms | 0 |
| Thu 21 | 0 | 0.0 | 225 ms | 0 |
| Thu 23 | 0 | 0.0 | 18 ms | 0 |
| Fri 01 | 0 | 0.0 | 173 ms | 0 |
| Fri 03 | 0 | 0.0 | 36 ms | 0 |
| Fri 05 | 0 | 0.0 | 38 ms | 0 |
| Fri 08 | 0 | 0.0 | 15 ms | 0 |
| Fri 10 | 0 | 0.0 | 20 ms | 0 |
| Fri 12 | 0 | 0.0 | 20 ms | 0 |
| Fri 13 | 0 | 0.0 | 15 ms | 0 |
| Fri 15 | 0 | 0.0 | 20 ms | 0 |
| Fri 17 | 0 | 0.0 | 56 ms | 0 |
| Fri 18 | 0 | 0.0 | 33 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Definitive 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 Definitive goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Definitive alerts to Slack, Discord or a webhook — free.
We track Definitive (definitive.fi) as part of the Money group. Definitive is a trading platform built for traders who want the best pricing, fastest trading, and advanced orders in one professional-grade mobile app and web terminal.
Definitive publishes an official status page at status.definitive.fi; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 51 ms average, 11–225 ms range across 14 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public Definitive incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
51 ms on average over the last 24 hours (11–225 ms).
Yes, at https://status.definitive.fi.
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 Definitive here at once, the problem is on Definitive'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 Definitive. 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.