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 2 hr ago. Last stored result reached it in 213 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 257 ms | 0 |
| Mon 14 | 0 | 0.0 | 187 ms | 0 |
| Mon 16 | 0 | 0.0 | 214 ms | 0 |
| Mon 18 | 0 | 0.0 | 279 ms | 0 |
| Mon 20 | 0 | 0.0 | 256 ms | 0 |
| Mon 22 | 0 | 0.0 | 188 ms | 0 |
| Tue 00 | 0 | 0.0 | 215 ms | 0 |
| Tue 02 | 0 | 0.0 | 190 ms | 0 |
| Tue 04 | 0 | 0.0 | 163 ms | 0 |
| Tue 07 | 0 | 0.0 | 388 ms | 0 |
| Tue 09 | 0 | 0.0 | 296 ms | 0 |
| Tue 11 | 0 | 0.0 | 306 ms | 0 |
| Tue 13 | 0 | 0.0 | 251 ms | 0 |
| Tue 15 | 0 | 0.0 | 214 ms | 0 |
| Tue 17 | 0 | 0.0 | 189 ms | 0 |
| Tue 18 | 0 | 0.0 | 397 ms | 0 |
| Tue 20 | 0 | 0.0 | 299 ms | 0 |
| Tue 23 | 0 | 0.0 | 252 ms | 0 |
| Wed 01 | 0 | 0.0 | 204 ms | 0 |
| Wed 03 | 0 | 0.0 | 166 ms | 0 |
| Wed 05 | 0 | 0.0 | 244 ms | 0 |
| Wed 07 | 0 | 0.0 | 238 ms | 0 |
| Wed 10 | 0 | 0.0 | 277 ms | 0 |
| Wed 12 | 0 | 0.0 | 243 ms | 0 |
| Wed 14 | 0 | 0.0 | 204 ms | 0 |
| Wed 16 | 0 | 0.0 | 281 ms | 0 |
| Wed 18 | 0 | 0.0 | 255 ms | 0 |
| Wed 21 | 0 | 0.0 | 305 ms | 0 |
| Wed 23 | 0 | 0.0 | 270 ms | 0 |
| Thu 01 | 0 | 0.0 | 274 ms | 0 |
| Thu 03 | 0 | 0.0 | 234 ms | 0 |
| Thu 05 | 0 | 0.0 | 255 ms | 0 |
| Thu 07 | 0 | 0.0 | 272 ms | 0 |
| Thu 09 | 0 | 0.0 | 235 ms | 0 |
| Thu 11 | 0 | 0.0 | 210 ms | 0 |
| Thu 13 | 0 | 0.0 | 231 ms | 0 |
| Thu 15 | 0 | 0.0 | 232 ms | 0 |
| Thu 17 | 0 | 0.0 | 405 ms | 0 |
| Thu 19 | 0 | 0.0 | 170 ms | 0 |
| Thu 21 | 0 | 0.0 | 222 ms | 0 |
| Fri 00 | 0 | 0.0 | 159 ms | 0 |
| Fri 02 | 0 | 0.0 | 236 ms | 0 |
| Fri 04 | 0 | 0.0 | 235 ms | 0 |
| Fri 06 | 0 | 0.0 | 330 ms | 0 |
| Fri 08 | 0 | 0.0 | 297 ms | 0 |
| Fri 10 | 0 | 0.0 | 155 ms | 0 |
| Fri 11 | 0 | 0.0 | 160 ms | 0 |
| Fri 13 | 0 | 0.0 | 213 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 Flashbots 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 Flashbots goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Flashbots alerts to Slack, Discord or a webhook — free.
We track Flashbots (flashbots.net) as part of the Money group. A research and development organization mitigating the negative externalities posed by MEV.
Flashbots publishes an official status page at status.flashbots.net; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 235 ms average, 155–405 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Flashbots incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
235 ms on average over the last 24 hours (155–405 ms).
Yes, at https://status.flashbots.net.
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 Flashbots here at once, the problem is on Flashbots'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 Flashbots. 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.