User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Flare 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 → flare.io—
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 24 min ago. Last stored result reached it in 113 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 18 | 0 | 0.0 | 245 ms | 0 |
| Mon 20 | 0 | 0.0 | 65 ms | 0 |
| Mon 22 | 0 | 0.0 | 98 ms | 0 |
| Tue 00 | 0 | 0.0 | 103 ms | 0 |
| Tue 02 | 0 | 0.0 | 157 ms | 0 |
| Tue 04 | 0 | 0.0 | 88 ms | 0 |
| Tue 06 | 0 | 0.0 | 89 ms | 0 |
| Tue 09 | 0 | 0.0 | 213 ms | 0 |
| Tue 11 | 0 | 0.0 | 100 ms | 0 |
| Tue 13 | 0 | 0.0 | 65 ms | 0 |
| Tue 15 | 0 | 0.0 | 81 ms | 0 |
| Tue 17 | 0 | 0.0 | 101 ms | 0 |
| Tue 20 | 0 | 0.0 | 66 ms | 0 |
| Tue 22 | 0 | 0.0 | 156 ms | 0 |
| Wed 00 | 0 | 0.0 | 74 ms | 0 |
| Wed 02 | 0 | 0.0 | 108 ms | 0 |
| Wed 05 | 0 | 0.0 | 146 ms | 0 |
| Wed 07 | 0 | 0.0 | 120 ms | 0 |
| Wed 09 | 0 | 0.0 | 55 ms | 0 |
| Wed 11 | 0 | 0.0 | 57 ms | 0 |
| Wed 13 | 0 | 0.0 | 67 ms | 0 |
| Wed 15 | 0 | 0.0 | 69 ms | 0 |
| Wed 18 | 0 | 0.0 | 134 ms | 0 |
| Wed 20 | 0 | 0.0 | 301 ms | 0 |
| Wed 22 | 0 | 0.0 | 295 ms | 0 |
| Thu 00 | 0 | 0.0 | 85 ms | 0 |
| Thu 02 | 0 | 0.0 | 76 ms | 0 |
| Thu 04 | 0 | 0.0 | 204 ms | 0 |
| Thu 06 | 0 | 0.0 | 192 ms | 0 |
| Thu 08 | 0 | 0.0 | 70 ms | 0 |
| Thu 10 | 0 | 0.0 | 41 ms | 0 |
| Thu 13 | 0 | 0.0 | 112 ms | 0 |
| Thu 15 | 0 | 0.0 | 112 ms | 0 |
| Thu 17 | 0 | 0.0 | 100 ms | 0 |
| Thu 19 | 0 | 0.0 | 127 ms | 0 |
| Thu 21 | 0 | 0.0 | 49 ms | 0 |
| Thu 22 | 0 | 0.0 | 91 ms | 0 |
| Fri 00 | 0 | 0.0 | 108 ms | 0 |
| Fri 02 | 0 | 0.0 | 138 ms | 0 |
| Fri 04 | 0 | 0.0 | 223 ms | 0 |
| Fri 06 | 0 | 0.0 | 196 ms | 0 |
| Fri 08 | 0 | 0.0 | 142 ms | 0 |
| Fri 10 | 0 | 0.0 | 62 ms | 0 |
| Fri 11 | 0 | 0.0 | 241 ms | 0 |
| Fri 13 | 0 | 0.0 | 42 ms | 0 |
| Fri 15 | 0 | 0.0 | 49 ms | 0 |
| Fri 17 | 0 | 0.0 | 102 ms | 0 |
| Fri 18 | 0 | 0.0 | 113 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 Flare 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 Flare yet. Outages of 10 minutes or more get their own page here.
Having trouble with Flare?
One report per service every 10 minutes from this network. No account.
Follow Flare
Get an email when Flare goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Flare alerts to Slack, Discord or a webhook — free.
About Flare
We track Flare (flare.io) as part of the Productivity group. Flare equips your team to shut down cybercrime before it escalates. Detect, prioritize, and remediate external cyber threats with Identity-first threat intelligence.
Flare publishes an official status page at status.flare.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 119 ms average, 42–241 ms range across 15 successful checks.
Questions
Is Flare down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Flare last down?
We have not recorded a public Flare incident since monitoring began 7 days ago.
What is Flare's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Flare respond?
119 ms on average over the last 24 hours (42–241 ms).
Does Flare have an official status page?
Yes, at https://status.flare.io.
Flare 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Flare here at once, the problem is on Flare'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 Flare. 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.