User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Forward 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 → getfwd.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 19 min ago. Last stored result reached it in 198 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 13 | 0 | 0.0 | 233 ms | 0 |
| Mon 15 | 0 | 0.0 | 330 ms | 0 |
| Mon 18 | 0 | 0.0 | 299 ms | 0 |
| Mon 20 | 0 | 0.0 | 159 ms | 0 |
| Mon 22 | 0 | 0.0 | 334 ms | 0 |
| Tue 00 | 0 | 0.0 | 168 ms | 0 |
| Tue 02 | 0 | 0.0 | 276 ms | 0 |
| Tue 04 | 0 | 0.0 | 365 ms | 0 |
| Tue 06 | 0 | 0.0 | 97 ms | 0 |
| Tue 08 | 0 | 0.0 | 97 ms | 0 |
| Tue 10 | 0 | 0.0 | 236 ms | 0 |
| Tue 13 | 0 | 0.0 | 132 ms | 0 |
| Tue 15 | 0 | 0.0 | 271 ms | 0 |
| Tue 17 | 0 | 0.0 | 112 ms | 0 |
| Tue 19 | 0 | 0.0 | 297 ms | 0 |
| Tue 22 | 0 | 0.0 | 211 ms | 0 |
| Wed 00 | 0 | 0.0 | 296 ms | 0 |
| Wed 02 | 0 | 0.0 | 176 ms | 0 |
| Wed 04 | 0 | 0.0 | 241 ms | 0 |
| Wed 06 | 0 | 0.0 | 272 ms | 0 |
| Wed 09 | 0 | 0.0 | 209 ms | 0 |
| Wed 11 | 0 | 0.0 | 266 ms | 0 |
| Wed 13 | 0 | 0.0 | 150 ms | 0 |
| Wed 15 | 0 | 0.0 | 151 ms | 0 |
| Wed 17 | 0 | 0.0 | 268 ms | 0 |
| Wed 20 | 0 | 0.0 | 105 ms | 0 |
| Wed 22 | 0 | 0.0 | 391 ms | 0 |
| Thu 00 | 0 | 0.0 | 166 ms | 0 |
| Thu 02 | 0 | 0.0 | 194 ms | 0 |
| Thu 04 | 0 | 0.0 | 284 ms | 0 |
| Thu 06 | 0 | 0.0 | 222 ms | 0 |
| Thu 08 | 0 | 0.0 | 179 ms | 0 |
| Thu 10 | 0 | 0.0 | 276 ms | 0 |
| Thu 12 | 0 | 0.0 | 179 ms | 0 |
| Thu 14 | 0 | 0.0 | 295 ms | 0 |
| Thu 16 | 0 | 0.0 | 233 ms | 0 |
| Thu 19 | 0 | 0.0 | 314 ms | 0 |
| Thu 21 | 0 | 0.0 | 208 ms | 0 |
| Thu 23 | 0 | 0.0 | 189 ms | 0 |
| Fri 00 | 0 | 0.0 | 450 ms | 0 |
| Fri 02 | 0 | 0.0 | 194 ms | 0 |
| Fri 05 | 0 | 0.0 | 314 ms | 0 |
| Fri 07 | 0 | 0.0 | 339 ms | 0 |
| Fri 09 | 0 | 0.0 | 259 ms | 0 |
| Fri 10 | 0 | 0.0 | 55 ms | 0 |
| Fri 12 | 0 | 0.0 | 168 ms | 0 |
| Fri 14 | 0 | 0.0 | 251 ms | 0 |
| Fri 16 | 0 | 0.0 | 198 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Forward 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 Forward yet. Outages of 10 minutes or more get their own page here.
Having trouble with Forward?
One report per service every 10 minutes from this network. No account.
Follow Forward
Get an email when Forward goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Forward alerts to Slack, Discord or a webhook — free.
About Forward
We track Forward (getfwd.com) as part of the Money group. Embedded payments built by software founders, for software builders
Forward publishes an official status page at status.getfwd.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 245 ms average, 55–450 ms range across 15 successful checks.
Questions
Is Forward down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Forward last down?
We have not recorded a public Forward incident since monitoring began 7 days ago.
What is Forward's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Forward respond?
245 ms on average over the last 24 hours (55–450 ms).
Does Forward have an official status page?
Yes, at https://status.getfwd.com.
Forward 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 Forward here at once, the problem is on Forward'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 Forward. 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.