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 13 min ago. Last stored result reached it in 162 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 | 272 ms | 0 |
| Mon 18 | 0 | 0.0 | 258 ms | 0 |
| Mon 20 | 0 | 0.0 | 243 ms | 0 |
| Mon 22 | 0 | 0.0 | 224 ms | 0 |
| Tue 00 | 0 | 0.0 | 196 ms | 0 |
| Tue 02 | 0 | 0.0 | 409 ms | 0 |
| Tue 04 | 0 | 0.0 | 104 ms | 0 |
| Tue 06 | 0 | 0.0 | 196 ms | 0 |
| Tue 08 | 0 | 0.0 | 352 ms | 0 |
| Tue 11 | 0 | 0.0 | 79 ms | 0 |
| Tue 13 | 0 | 0.0 | 209 ms | 0 |
| Tue 15 | 0 | 0.0 | 316 ms | 0 |
| Tue 17 | 0 | 0.0 | 402 ms | 0 |
| Tue 20 | 0 | 0.0 | 340 ms | 0 |
| Tue 22 | 0 | 0.0 | 425 ms | 0 |
| Wed 00 | 0 | 0.0 | 335 ms | 0 |
| Wed 02 | 0 | 0.0 | 49 ms | 0 |
| Wed 05 | 0 | 0.0 | 145 ms | 0 |
| Wed 07 | 0 | 0.0 | 226 ms | 0 |
| Wed 09 | 0 | 0.0 | 189 ms | 0 |
| Wed 11 | 0 | 0.0 | 103 ms | 0 |
| Wed 13 | 0 | 0.0 | 235 ms | 0 |
| Wed 15 | 0 | 0.0 | 221 ms | 0 |
| Wed 18 | 0 | 0.0 | 170 ms | 0 |
| Wed 20 | 0 | 0.0 | 236 ms | 0 |
| Wed 22 | 0 | 0.0 | 326 ms | 0 |
| Thu 00 | 0 | 0.0 | 210 ms | 0 |
| Thu 02 | 0 | 0.0 | 291 ms | 0 |
| Thu 04 | 0 | 0.0 | 171 ms | 0 |
| Thu 06 | 0 | 0.0 | 252 ms | 0 |
| Thu 09 | 0 | 0.0 | 120 ms | 0 |
| Thu 11 | 0 | 0.0 | 288 ms | 0 |
| Thu 13 | 0 | 0.0 | 75 ms | 0 |
| Thu 15 | 0 | 0.0 | 216 ms | 0 |
| Thu 17 | 0 | 0.0 | 305 ms | 0 |
| Thu 19 | 0 | 0.0 | 272 ms | 0 |
| Thu 21 | 0 | 0.0 | 377 ms | 0 |
| Thu 23 | 0 | 0.0 | 317 ms | 0 |
| Fri 01 | 0 | 0.0 | 383 ms | 0 |
| Fri 03 | 0 | 0.0 | 231 ms | 0 |
| Fri 06 | 0 | 0.0 | 319 ms | 0 |
| Fri 08 | 0 | 0.0 | 113 ms | 0 |
| Fri 10 | 0 | 0.0 | 322 ms | 0 |
| Fri 11 | 0 | 0.0 | 294 ms | 0 |
| Fri 13 | 0 | 0.0 | 224 ms | 0 |
| Fri 15 | 0 | 0.0 | 203 ms | 0 |
| Fri 17 | 0 | 0.0 | 340 ms | 0 |
| Fri 19 | 0 | 0.0 | 225 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for OrbitFlare 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 OrbitFlare goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OrbitFlare alerts to Slack, Discord or a webhook — free.
We track OrbitFlare (orbitflare.com) as part of the Money group. Fast Solana RPC nodes and real-time gRPC streaming with 99.99% uptime. Enterprise Solana infrastructure for DeFi, NFTs and high-frequency trading.
OrbitFlare publishes an official status page at status.orbitflare.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: 276 ms average, 113–445 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 OrbitFlare incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
276 ms on average over the last 24 hours (113–445 ms).
Yes, at https://status.orbitflare.com.
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 OrbitFlare here at once, the problem is on OrbitFlare'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 OrbitFlare. 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.