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 55 min ago. Last stored result reached it in 185 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 188 ms | 0 |
| Mon 20 | 0 | 0.0 | 193 ms | 0 |
| Mon 22 | 0 | 0.0 | 308 ms | 0 |
| Tue 00 | 0 | 0.0 | 145 ms | 0 |
| Tue 02 | 0 | 0.0 | 567 ms | 0 |
| Tue 04 | 0 | 0.0 | 163 ms | 0 |
| Tue 07 | 0 | 0.0 | 185 ms | 0 |
| Tue 09 | 0 | 0.0 | 189 ms | 0 |
| Tue 11 | 0 | 0.0 | 173 ms | 0 |
| Tue 13 | 0 | 0.0 | 561 ms | 0 |
| Tue 15 | 0 | 0.0 | 176 ms | 0 |
| Tue 17 | 0 | 0.0 | 404 ms | 0 |
| Tue 20 | 0 | 0.0 | 168 ms | 0 |
| Tue 22 | 0 | 0.0 | 187 ms | 0 |
| Wed 00 | 0 | 0.0 | 168 ms | 0 |
| Wed 02 | 0 | 0.0 | 192 ms | 0 |
| Wed 05 | 0 | 0.0 | 2215 ms | 0 |
| Wed 07 | 0 | 0.0 | 256 ms | 0 |
| Wed 09 | 0 | 0.0 | 210 ms | 0 |
| Wed 11 | 0 | 0.0 | 192 ms | 0 |
| Wed 14 | 0 | 0.0 | 188 ms | 0 |
| Wed 16 | 0 | 0.0 | 191 ms | 0 |
| Wed 18 | 0 | 0.0 | 201 ms | 0 |
| Wed 20 | 0 | 0.0 | 199 ms | 0 |
| Wed 22 | 0 | 0.0 | 185 ms | 0 |
| Thu 00 | 0 | 0.0 | 159 ms | 0 |
| Thu 03 | 0 | 0.0 | 484 ms | 0 |
| Thu 05 | 0 | 0.0 | 220 ms | 0 |
| Thu 07 | 0 | 0.0 | 179 ms | 0 |
| Thu 09 | 0 | 0.0 | 151 ms | 0 |
| Thu 11 | 0 | 0.0 | 184 ms | 0 |
| Thu 13 | 0 | 0.0 | 210 ms | 0 |
| Thu 15 | 0 | 0.0 | 580 ms | 0 |
| Thu 17 | 0 | 0.0 | 197 ms | 0 |
| Thu 19 | 0 | 0.0 | 193 ms | 0 |
| Thu 21 | 0 | 0.0 | 174 ms | 0 |
| Thu 23 | 0 | 0.0 | 170 ms | 0 |
| Fri 01 | 0 | 0.0 | 182 ms | 0 |
| Fri 03 | 0 | 0.0 | 242 ms | 0 |
| Fri 05 | 0 | 0.0 | 141 ms | 0 |
| Fri 08 | 0 | 0.0 | 190 ms | 0 |
| Fri 09 | 0 | 0.0 | 580 ms | 0 |
| Fri 11 | 0 | 0.0 | 156 ms | 0 |
| Fri 13 | 0 | 0.0 | 188 ms | 0 |
| Fri 15 | 0 | 0.0 | 177 ms | 0 |
| Fri 17 | 0 | 0.0 | 203 ms | 0 |
| Fri 18 | 0 | 0.0 | 139 ms | 0 |
| Fri 19 | 0 | 0.0 | 185 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 SEON 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 SEON goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SEON alerts to Slack, Discord or a webhook — free.
We track SEON (seon.io) as part of the Money group. SEON's fraud prevention platform unifies real-time detection and AML in one place. Built on 1,100+ first-party signals, with 14 days implementation average.
SEON publishes an official status page at status.seon.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: 210 ms average, 139–580 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 SEON incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
210 ms on average over the last 24 hours (139–580 ms).
Yes, at https://status.seon.io.
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 SEON here at once, the problem is on SEON'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 SEON. 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.