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 23 min ago. Last stored result reached it in 1769 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 863 ms | 0 |
| Tue 09 | 0 | 0.0 | 1456 ms | 0 |
| Tue 11 | 0 | 0.0 | 1394 ms | 0 |
| Tue 13 | 0 | 0.0 | 1448 ms | 0 |
| Tue 16 | 0 | 0.0 | 1291 ms | 0 |
| Tue 18 | 0 | 0.0 | 1063 ms | 0 |
| Tue 20 | 0 | 0.0 | 900 ms | 0 |
| Tue 22 | 0 | 0.0 | 1324 ms | 0 |
| Wed 01 | 0 | 0.0 | 882 ms | 0 |
| Wed 03 | 0 | 0.0 | 1310 ms | 0 |
| Wed 05 | 0 | 0.0 | 1214 ms | 0 |
| Wed 07 | 0 | 0.0 | 1481 ms | 0 |
| Wed 10 | 0 | 0.0 | 1193 ms | 0 |
| Wed 12 | 0 | 0.0 | 2764 ms | 0 |
| Wed 14 | 0 | 0.0 | 1783 ms | 0 |
| Wed 16 | 0 | 0.0 | 1664 ms | 0 |
| Wed 18 | 0 | 0.0 | 1318 ms | 0 |
| Wed 20 | 0 | 0.0 | 1558 ms | 0 |
| Wed 23 | 0 | 0.0 | 1215 ms | 0 |
| Thu 01 | 0 | 0.0 | 1321 ms | 0 |
| Thu 03 | 0 | 0.0 | 2571 ms | 0 |
| Thu 05 | 0 | 0.0 | 1544 ms | 0 |
| Thu 07 | 0 | 0.0 | 2505 ms | 0 |
| Thu 09 | 0 | 0.0 | 1694 ms | 0 |
| Thu 11 | 0 | 0.0 | 2043 ms | 0 |
| Thu 13 | 0 | 0.0 | 2130 ms | 0 |
| Thu 15 | 0 | 0.0 | 1492 ms | 0 |
| Thu 17 | 0 | 0.0 | 1224 ms | 0 |
| Thu 19 | 0 | 0.0 | 1582 ms | 0 |
| Thu 21 | 0 | 0.0 | 1448 ms | 0 |
| Thu 23 | 0 | 0.0 | 1254 ms | 0 |
| Fri 01 | 0 | 0.0 | 1271 ms | 0 |
| Fri 04 | 0 | 0.0 | 1237 ms | 0 |
| Fri 06 | 0 | 0.0 | 838 ms | 0 |
| Fri 08 | 0 | 0.0 | 1222 ms | 0 |
| Fri 10 | 0 | 0.0 | 2016 ms | 0 |
| Fri 11 | 0 | 0.0 | — | 1 |
| Fri 12 | 0 | 0.0 | 2178 ms | 0 |
| Fri 14 | 0 | 0.0 | 1647 ms | 0 |
| Fri 16 | 0 | 0.0 | 2223 ms | 0 |
| Fri 18 | 0 | 0.0 | 1555 ms | 0 |
| Fri 20 | 0 | 0.0 | 1652 ms | 0 |
| Fri 22 | 0 | 0.0 | 1663 ms | 0 |
| Sat 00 | 0 | 0.0 | 1714 ms | 0 |
| Sat 02 | 0 | 0.0 | 1792 ms | 0 |
| Sat 04 | 0 | 0.0 | 1873 ms | 0 |
| Sat 06 | 0 | 0.0 | 1769 ms | 0 |
| Sat 08 | 0 | 0.0 | 1692 ms | 0 |
98.82% 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 Financial Edge 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 Financial Edge goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Financial Edge alerts to Slack, Discord or a webhook — free.
We track Financial Edge (fe.training) as part of the Money group. Financial Edge is Wall Street's leading finance training provider. Experience the same world-class learning online, from financial modeling to valuation.
Financial Edge publishes an official status page at status.fe.training; 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: 98.82% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1836 ms average, 1555–2223 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Financial Edge incident since monitoring began 8 days ago.
From our own checks: 98.82% over 8 days of checks.
1836 ms on average over the last 24 hours (1555–2223 ms).
Yes, at https://status.fe.training.
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 Financial Edge here at once, the problem is on Financial Edge'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 Financial Edge. 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.