User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
jinxxy.com · 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 16 min ago. Last stored result reached it in 90 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 105 ms | 0 |
| Tue 14 | 0 | 0.0 | 418 ms | 0 |
| Tue 16 | 0 | 0.0 | 138 ms | 0 |
| Tue 18 | 0 | 0.0 | 166 ms | 0 |
| Tue 21 | 0 | 0.0 | 139 ms | 0 |
| Tue 23 | 0 | 0.0 | 195 ms | 0 |
| Wed 01 | 0 | 0.0 | 154 ms | 0 |
| Wed 03 | 0 | 0.0 | 313 ms | 0 |
| Wed 06 | 0 | 0.0 | 87 ms | 0 |
| Wed 08 | 0 | 0.0 | 131 ms | 0 |
| Wed 10 | 0 | 0.0 | 101 ms | 0 |
| Wed 12 | 0 | 0.0 | 173 ms | 0 |
| Wed 14 | 0 | 0.0 | 173 ms | 0 |
| Wed 16 | 0 | 0.0 | 135 ms | 0 |
| Wed 19 | 0 | 0.0 | 92 ms | 0 |
| Wed 21 | 0 | 0.0 | 582 ms | 0 |
| Wed 23 | 0 | 0.0 | 210 ms | 0 |
| Thu 01 | 0 | 0.0 | 172 ms | 0 |
| Thu 03 | 0 | 0.0 | 129 ms | 0 |
| Thu 05 | 0 | 0.0 | 171 ms | 0 |
| Thu 07 | 0 | 0.0 | 91 ms | 0 |
| Thu 09 | 0 | 0.0 | 146 ms | 0 |
| Thu 11 | 0 | 0.0 | 169 ms | 0 |
| Thu 13 | 0 | 0.0 | 89 ms | 0 |
| Thu 16 | 0 | 0.0 | 135 ms | 0 |
| Thu 18 | 0 | 0.0 | 123 ms | 0 |
| Thu 20 | 0 | 0.0 | 107 ms | 0 |
| Thu 22 | 0 | 0.0 | 373 ms | 0 |
| Fri 00 | 0 | 0.0 | 577 ms | 0 |
| Fri 02 | 0 | 0.0 | 173 ms | 0 |
| Fri 04 | 0 | 0.0 | 377 ms | 0 |
| Fri 06 | 0 | 0.0 | 354 ms | 0 |
| Fri 08 | 0 | 0.0 | 122 ms | 0 |
| Fri 10 | 0 | 0.0 | 121 ms | 0 |
| Fri 12 | 0 | 0.0 | 157 ms | 0 |
| Fri 14 | 0 | 0.0 | 194 ms | 0 |
| Fri 16 | 0 | 0.0 | 170 ms | 0 |
| Fri 18 | 0 | 0.0 | 142 ms | 0 |
| Fri 20 | 0 | 0.0 | 203 ms | 0 |
| Fri 22 | 0 | 0.0 | 220 ms | 0 |
| Sat 00 | 0 | 0.0 | 98 ms | 0 |
| Sat 02 | 0 | 0.0 | 104 ms | 0 |
| Sat 04 | 0 | 0.0 | 104 ms | 0 |
| Sat 06 | 0 | 0.0 | 133 ms | 0 |
| Sat 08 | 0 | 0.0 | 131 ms | 0 |
| Sat 10 | 0 | 0.0 | 73 ms | 0 |
| Sat 13 | 0 | 0.0 | 114 ms | 0 |
| Sat 15 | 0 | 0.0 | 126 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Jinxxy 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 Jinxxy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Jinxxy alerts to Slack, Discord or a webhook — free.
Jinxxy is listed in our Cloud & developer category and checked at jinxxy.com. Discover avatars, digital assets, and tools for VRChat, VTubing, and more. Jinxxy empowers creators and fuels the future of virtual marketplaces.
Jinxxy publishes an official status page at status.jinxxy.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 133 ms average, 73–220 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Jinxxy incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
133 ms on average over the last 24 hours (73–220 ms).
Yes, at https://status.jinxxy.com.
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 Jinxxy here at once, the problem is on Jinxxy'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 Jinxxy. 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.