User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is FlareLane 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 → flarelane.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 1 hr ago. Last stored result reached it in 340 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 23 | 0 | 0.0 | 356 ms | 0 |
| Tue 01 | 0 | 0.0 | 307 ms | 0 |
| Tue 03 | 0 | 0.0 | 309 ms | 0 |
| Tue 05 | 0 | 0.0 | 447 ms | 0 |
| Tue 07 | 0 | 0.0 | 253 ms | 0 |
| Tue 09 | 0 | 0.0 | 396 ms | 0 |
| Tue 11 | 0 | 0.0 | 374 ms | 0 |
| Tue 14 | 0 | 0.0 | 444 ms | 0 |
| Tue 16 | 0 | 0.0 | 213 ms | 0 |
| Tue 18 | 0 | 0.0 | 343 ms | 0 |
| Tue 20 | 0 | 0.0 | 575 ms | 0 |
| Tue 23 | 0 | 0.0 | 491 ms | 0 |
| Wed 01 | 0 | 0.0 | 532 ms | 0 |
| Wed 03 | 0 | 0.0 | 481 ms | 0 |
| Wed 05 | 0 | 0.0 | 348 ms | 0 |
| Wed 08 | 0 | 0.0 | 340 ms | 0 |
| Wed 10 | 0 | 0.0 | 341 ms | 0 |
| Wed 12 | 0 | 0.0 | 271 ms | 0 |
| Wed 14 | 0 | 0.0 | 336 ms | 0 |
| Wed 16 | 0 | 0.0 | 518 ms | 0 |
| Wed 18 | 0 | 0.0 | 632 ms | 0 |
| Wed 21 | 0 | 0.0 | 415 ms | 0 |
| Wed 23 | 0 | 0.0 | 460 ms | 0 |
| Thu 01 | 0 | 0.0 | 333 ms | 0 |
| Thu 03 | 0 | 0.0 | 441 ms | 0 |
| Thu 05 | 0 | 0.0 | 426 ms | 0 |
| Thu 07 | 0 | 0.0 | 364 ms | 0 |
| Thu 09 | 0 | 0.0 | 388 ms | 0 |
| Thu 11 | 0 | 0.0 | 349 ms | 0 |
| Thu 13 | 0 | 0.0 | 414 ms | 0 |
| Thu 15 | 0 | 0.0 | 453 ms | 0 |
| Thu 17 | 0 | 0.0 | 654 ms | 0 |
| Thu 19 | 0 | 0.0 | 316 ms | 0 |
| Thu 21 | 0 | 0.0 | 672 ms | 0 |
| Fri 00 | 0 | 0.0 | 463 ms | 0 |
| Fri 02 | 0 | 0.0 | 515 ms | 0 |
| Fri 04 | 0 | 0.0 | 436 ms | 0 |
| Fri 06 | 0 | 0.0 | 633 ms | 0 |
| Fri 08 | 0 | 0.0 | 337 ms | 0 |
| Fri 10 | 0 | 0.0 | 292 ms | 0 |
| Fri 11 | 0 | 0.0 | 439 ms | 0 |
| Fri 12 | 0 | 0.0 | 413 ms | 0 |
| Fri 14 | 0 | 0.0 | 410 ms | 0 |
| Fri 16 | 0 | 0.0 | 626 ms | 0 |
| Fri 17 | 0 | 0.0 | 398 ms | 0 |
| Fri 19 | 0 | 0.0 | 408 ms | 0 |
| Fri 21 | 0 | 0.0 | 439 ms | 0 |
| Fri 23 | 0 | 0.0 | 412 ms | 0 |
Reliability
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.
Embed this status: free live FlareLane 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 FlareLane yet. Outages of 10 minutes or more get their own page here.
Having trouble with FlareLane?
One report per service every 10 minutes from this network. No account.
Follow FlareLane
Get an email when FlareLane goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send FlareLane alerts to Slack, Discord or a webhook — free.
About FlareLane
We track FlareLane (flarelane.com) as part of the Productivity group. 연간 100억 이상 메시지 발송과 2억명의 고객사 유저를 관리하는 안정적이고 신뢰성 있는 CRM 마케팅 솔루션. 플레어레인은 푸시, 문자, 알림톡, 브랜드메시지, 이메일, 인앱 메시지 등 다양한 채널을 활용하여 이상적인 고객 여정을 설계하고 유저 행동을 유도하는 신개념 마케팅 솔루션입니다.
FlareLane publishes an official status page at status.flarelane.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 425 ms average, 263–633 ms range across 16 successful checks.
Questions
Is FlareLane down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was FlareLane last down?
We have not recorded a public FlareLane incident since monitoring began 8 days ago.
What is FlareLane's uptime?
From our own checks: 100% over 8 days of checks.
How fast does FlareLane respond?
425 ms on average over the last 24 hours (263–633 ms).
Does FlareLane have an official status page?
Yes, at https://status.flarelane.com.
FlareLane 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 FlareLane here at once, the problem is on FlareLane'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 FlareLane. 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.