User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
hacomono.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 55 min ago. Last stored result reached it in 443 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 14 | 0 | 0.0 | 73 ms | 0 |
| Tue 16 | 0 | 0.0 | 135 ms | 0 |
| Tue 18 | 0 | 0.0 | 75 ms | 0 |
| Tue 20 | 0 | 0.0 | 96 ms | 0 |
| Tue 23 | 0 | 0.0 | 88 ms | 0 |
| Wed 01 | 0 | 0.0 | 348 ms | 0 |
| Wed 03 | 0 | 0.0 | 130 ms | 0 |
| Wed 05 | 0 | 0.0 | 112 ms | 0 |
| Wed 08 | 0 | 0.0 | 101 ms | 0 |
| Wed 10 | 0 | 0.0 | 99 ms | 0 |
| Wed 12 | 0 | 0.0 | 70 ms | 0 |
| Wed 14 | 0 | 0.0 | 88 ms | 0 |
| Wed 16 | 0 | 0.0 | 116 ms | 0 |
| Wed 18 | 0 | 0.0 | 243 ms | 0 |
| Wed 21 | 0 | 0.0 | 148 ms | 0 |
| Wed 23 | 0 | 0.0 | 99 ms | 0 |
| Thu 01 | 0 | 0.0 | 2434 ms | 0 |
| Thu 03 | 0 | 0.0 | 76 ms | 0 |
| Thu 06 | 0 | 0.0 | 2028 ms | 0 |
| Thu 08 | 0 | 0.0 | 234 ms | 0 |
| Thu 10 | 0 | 0.0 | 197 ms | 0 |
| Thu 12 | 0 | 0.0 | 99 ms | 0 |
| Thu 14 | 0 | 0.0 | 187 ms | 0 |
| Thu 16 | 0 | 0.0 | 119 ms | 0 |
| Thu 18 | 0 | 0.0 | 152 ms | 0 |
| Thu 20 | 0 | 0.0 | 60 ms | 0 |
| Thu 22 | 0 | 0.0 | 164 ms | 0 |
| Fri 00 | 0 | 0.0 | 130 ms | 0 |
| Fri 02 | 0 | 0.0 | 186 ms | 0 |
| Fri 04 | 0 | 0.0 | 74 ms | 0 |
| Fri 06 | 0 | 0.0 | 75 ms | 0 |
| Fri 08 | 0 | 0.0 | 87 ms | 0 |
| Fri 11 | 0 | 0.0 | 78 ms | 0 |
| Fri 13 | 0 | 0.0 | 124 ms | 0 |
| Fri 15 | 0 | 0.0 | 206 ms | 0 |
| Fri 17 | 0 | 0.0 | 105 ms | 0 |
| Fri 19 | 0 | 0.0 | 60 ms | 0 |
| Fri 21 | 0 | 0.0 | 69 ms | 0 |
| Fri 23 | 0 | 0.0 | 75 ms | 0 |
| Sat 01 | 0 | 0.0 | 72 ms | 0 |
| Sat 03 | 0 | 0.0 | 81 ms | 0 |
| Sat 05 | 0 | 0.0 | 75 ms | 0 |
| Sat 07 | 0 | 0.0 | 189 ms | 0 |
| Sat 08 | 0 | 0.0 | 71 ms | 0 |
| Sat 10 | 0 | 0.0 | 97 ms | 0 |
| Sat 13 | 0 | 0.0 | 60 ms | 0 |
| Sat 15 | 0 | 0.0 | 333 ms | 0 |
| Sat 18 | 0 | 0.0 | 443 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for hacomono 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 hacomono goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
hacomono is listed in our Cloud & developer category and checked at hacomono.jp. hacomonoは、会員管理・予約・決済・データ分析など店舗の基幹業務を網羅するオールインワンマネジメントシステムです。業務効率化、理想の店舗運営を実現します。
hacomono publishes an official status page at status.hacomono.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 130 ms average, 59–443 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public hacomono incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
130 ms on average over the last 24 hours (59–443 ms).
Yes, at https://status.hacomono.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 hacomono here at once, the problem is on hacomono'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 hacomono. 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.