User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
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 42 min ago. Last stored result reached it in 202 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 212 ms | 0 |
| Mon 17 | 0 | 0.0 | 224 ms | 0 |
| Mon 19 | 0 | 0.0 | 305 ms | 0 |
| Mon 21 | 0 | 0.0 | 290 ms | 0 |
| Mon 23 | 0 | 0.0 | 160 ms | 0 |
| Tue 01 | 0 | 0.0 | 376 ms | 0 |
| Tue 03 | 0 | 0.0 | 179 ms | 0 |
| Tue 06 | 0 | 0.0 | 283 ms | 0 |
| Tue 08 | 0 | 0.0 | 239 ms | 0 |
| Tue 10 | 0 | 0.0 | 195 ms | 0 |
| Tue 12 | 0 | 0.0 | 311 ms | 0 |
| Tue 14 | 0 | 0.0 | 353 ms | 0 |
| Tue 16 | 0 | 0.0 | 230 ms | 0 |
| Tue 19 | 0 | 0.0 | 343 ms | 0 |
| Tue 21 | 0 | 0.0 | 240 ms | 0 |
| Tue 23 | 0 | 0.0 | 262 ms | 0 |
| Wed 01 | 0 | 0.0 | 355 ms | 0 |
| Wed 04 | 0 | 0.0 | 210 ms | 0 |
| Wed 06 | 0 | 0.0 | 334 ms | 0 |
| Wed 08 | 0 | 0.0 | 182 ms | 0 |
| Wed 10 | 0 | 0.0 | 404 ms | 0 |
| Wed 13 | 0 | 0.0 | 267 ms | 0 |
| Wed 15 | 0 | 0.0 | 371 ms | 0 |
| Wed 17 | 0 | 0.0 | 355 ms | 0 |
| Wed 19 | 0 | 0.0 | 276 ms | 0 |
| Wed 21 | 0 | 0.0 | 321 ms | 0 |
| Wed 23 | 0 | 0.0 | 290 ms | 0 |
| Thu 01 | 0 | 0.0 | 254 ms | 0 |
| Thu 04 | 0 | 0.0 | 290 ms | 0 |
| Thu 06 | 0 | 0.0 | 193 ms | 0 |
| Thu 08 | 0 | 0.0 | 403 ms | 0 |
| Thu 10 | 0 | 0.0 | 337 ms | 0 |
| Thu 12 | 0 | 0.0 | 410 ms | 0 |
| Thu 14 | 0 | 0.0 | 284 ms | 0 |
| Thu 16 | 0 | 0.0 | 369 ms | 0 |
| Thu 18 | 0 | 0.0 | 180 ms | 0 |
| Thu 20 | 0 | 0.0 | 300 ms | 0 |
| Thu 22 | 0 | 0.0 | 203 ms | 0 |
| Fri 00 | 0 | 0.0 | 223 ms | 0 |
| Fri 02 | 0 | 0.0 | 179 ms | 0 |
| Fri 04 | 0 | 0.0 | 297 ms | 0 |
| Fri 06 | 0 | 0.0 | 198 ms | 0 |
| Fri 08 | 0 | 0.0 | 275 ms | 0 |
| Fri 10 | 0 | 0.0 | 309 ms | 0 |
| Fri 11 | 0 | 0.0 | 248 ms | 0 |
| Fri 13 | 0 | 0.0 | 382 ms | 0 |
| Fri 15 | 0 | 0.0 | 321 ms | 0 |
| Fri 17 | 0 | 0.0 | 202 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 Jitsu 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 Jitsu goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Jitsu alerts to Slack, Discord or a webhook — free.
Jitsu, at jitsu.com, is one of the Entertainment services we monitor. Capture event data from websites, apps, and servers with Jitsu, then stream clean customer data into warehouses and tools in real time for analytics.
Jitsu publishes an official status page at status.jitsu.com; when we can read it, its incident level is folded into the status shown here.
Common problems for entertainment services: streams buffering or not starting, playback errors, and app 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: 255 ms average, 179–382 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Jitsu incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
255 ms on average over the last 24 hours (179–382 ms).
Yes, at https://status.jitsu.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For entertainment services, watch for streams buffering or not starting, playback errors, and app sign-in problems. If many people report Jitsu here at once, the problem is on Jitsu'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 Jitsu. 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.