User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
fileforce.jp · Cloud & developer
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 99 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:45 | 0 | 0.0 | 325 ms | 0 |
| 10:00 | 0 | 0.0 | 346 ms | 0 |
| 12:00 | 0 | 0.0 | 115 ms | 0 |
| 14:00 | 0 | 0.0 | 80 ms | 0 |
| 16:00 | 0 | 0.0 | 544 ms | 0 |
| 18:15 | 0 | 0.0 | 216 ms | 0 |
| 20:15 | 0 | 0.0 | 101 ms | 0 |
| 22:15 | 0 | 0.0 | 243 ms | 0 |
| 00:15 | 0 | 0.0 | 212 ms | 0 |
| 02:15 | 0 | 0.0 | 319 ms | 0 |
| 04:30 | 0 | 0.0 | 99 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 Fileforce 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 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.
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: 223 ms average, 28–544 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 Fileforce incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
223 ms on average over the last 24 hours (28–544 ms).
Yes, at https://status.fileforce.jp.
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.