User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
fileforce.jp · Cloud & developer
Is Fileforce 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 → fileforce.jp—
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 35 min ago. Last stored result reached it in 418 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 14 | 0 | 0.0 | 251 ms | 0 |
| Mon 16 | 0 | 0.0 | 106 ms | 0 |
| Mon 18 | 0 | 0.0 | 184 ms | 0 |
| Mon 21 | 0 | 0.0 | 67 ms | 0 |
| Mon 23 | 0 | 0.0 | 178 ms | 0 |
| Tue 01 | 0 | 0.0 | 370 ms | 0 |
| Tue 03 | 0 | 0.0 | 354 ms | 0 |
| Tue 05 | 0 | 0.0 | 204 ms | 0 |
| Tue 07 | 0 | 0.0 | 301 ms | 0 |
| Tue 09 | 0 | 0.0 | 325 ms | 0 |
| Tue 11 | 0 | 0.0 | 226 ms | 0 |
| Tue 14 | 0 | 0.0 | 66 ms | 0 |
| Tue 16 | 0 | 0.0 | 100 ms | 0 |
| Tue 18 | 0 | 0.0 | 321 ms | 0 |
| Tue 20 | 0 | 0.0 | 132 ms | 0 |
| Tue 23 | 0 | 0.0 | 326 ms | 0 |
| Wed 01 | 0 | 0.0 | 77 ms | 0 |
| Wed 03 | 0 | 0.0 | 491 ms | 0 |
| Wed 05 | 0 | 0.0 | 440 ms | 0 |
| Wed 07 | 0 | 0.0 | 321 ms | 0 |
| Wed 08 | 0 | 0.0 | 335 ms | 0 |
| Wed 10 | 0 | 0.0 | 337 ms | 0 |
| Wed 12 | 0 | 0.0 | 513 ms | 0 |
| Wed 15 | 0 | 0.0 | 245 ms | 0 |
| Wed 17 | 0 | 0.0 | 289 ms | 0 |
| Wed 19 | 0 | 0.0 | 607 ms | 0 |
| Wed 21 | 0 | 0.0 | 238 ms | 0 |
| Wed 23 | 0 | 0.0 | 295 ms | 0 |
| Thu 01 | 0 | 0.0 | 339 ms | 0 |
| Thu 03 | 0 | 0.0 | 451 ms | 0 |
| Thu 05 | 0 | 0.0 | 321 ms | 0 |
| Thu 07 | 0 | 0.0 | 325 ms | 0 |
| Thu 10 | 0 | 0.0 | 346 ms | 0 |
| Thu 12 | 0 | 0.0 | 115 ms | 0 |
| Thu 14 | 0 | 0.0 | 80 ms | 0 |
| Thu 16 | 0 | 0.0 | 544 ms | 0 |
| Thu 18 | 0 | 0.0 | 216 ms | 0 |
| Thu 20 | 0 | 0.0 | 101 ms | 0 |
| Thu 22 | 0 | 0.0 | 243 ms | 0 |
| Fri 00 | 0 | 0.0 | 212 ms | 0 |
| Fri 02 | 0 | 0.0 | 319 ms | 0 |
| Fri 04 | 0 | 0.0 | 99 ms | 0 |
| Fri 06 | 0 | 0.0 | 329 ms | 0 |
| Fri 08 | 0 | 0.0 | 155 ms | 0 |
| Fri 10 | 0 | 0.0 | 346 ms | 0 |
| Fri 12 | 0 | 0.0 | 71 ms | 0 |
| Fri 14 | 0 | 0.0 | 79 ms | 0 |
| Fri 16 | 0 | 0.0 | 418 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 Fileforce 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 Fileforce yet. Outages of 10 minutes or more get their own page here.
Having trouble with Fileforce?
One report per service every 10 minutes from this network. No account.
Follow Fileforce
Get an email when Fileforce goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fileforce alerts to Slack, Discord or a webhook — free.
About Fileforce
Fileforce, at fileforce.jp, is one of the Cloud & developer services we monitor. Fileforceは、従来のファイルサーバー運用をそのまま継承できる純国産クラウドファイルサーバー（クラウドストレージ）です。エクスプローラー操作で利用でき、既存のアクセス権限設計を維持したまま高水準のデータセキュリティを実現します。ファイルサーバーDXを推進する機能も豊富に備え、ユーザー数無制限のためコストパフォーマンスにも優れています。
Fileforce publishes an official status page at status.fileforce.jp; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 221 ms average, 8–418 ms range across 14 successful checks.
Questions
Is Fileforce down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Fileforce last down?
We have not recorded a public Fileforce incident since monitoring began 7 days ago.
What is Fileforce's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Fileforce respond?
221 ms on average over the last 24 hours (8–418 ms).
Does Fileforce have an official status page?
Yes, at https://status.fileforce.jp.
Fileforce 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Fileforce here at once, the problem is on Fileforce'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 Fileforce. 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.