User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Jam 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 → jam.dev—
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 43 min ago. Last stored result reached it in 124 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 12 | 0 | 0.0 | 435 ms | 0 |
| Mon 14 | 0 | 0.0 | 401 ms | 0 |
| Mon 17 | 0 | 0.0 | 347 ms | 0 |
| Mon 19 | 0 | 0.0 | 360 ms | 0 |
| Mon 21 | 0 | 0.0 | 215 ms | 0 |
| Mon 23 | 0 | 0.0 | 438 ms | 0 |
| Tue 01 | 0 | 0.0 | 285 ms | 0 |
| Tue 03 | 0 | 0.0 | 292 ms | 0 |
| Tue 05 | 0 | 0.0 | 366 ms | 0 |
| Tue 07 | 0 | 0.0 | 340 ms | 0 |
| Tue 09 | 0 | 0.0 | 386 ms | 0 |
| Tue 12 | 0 | 0.0 | 279 ms | 0 |
| Tue 14 | 0 | 0.0 | 331 ms | 0 |
| Tue 16 | 0 | 0.0 | 226 ms | 0 |
| Tue 18 | 0 | 0.0 | 340 ms | 0 |
| Tue 21 | 0 | 0.0 | 318 ms | 0 |
| Tue 23 | 0 | 0.0 | 364 ms | 0 |
| Wed 01 | 0 | 0.0 | 409 ms | 0 |
| Wed 03 | 0 | 0.0 | 420 ms | 0 |
| Wed 06 | 0 | 0.0 | 194 ms | 0 |
| Wed 08 | 0 | 0.0 | 392 ms | 0 |
| Wed 10 | 0 | 0.0 | 275 ms | 0 |
| Wed 12 | 0 | 0.0 | 242 ms | 0 |
| Wed 14 | 0 | 0.0 | 364 ms | 0 |
| Wed 16 | 0 | 0.0 | 339 ms | 0 |
| Wed 19 | 0 | 0.0 | 355 ms | 0 |
| Wed 21 | 0 | 0.0 | 278 ms | 0 |
| Wed 23 | 0 | 0.0 | 497 ms | 0 |
| Thu 01 | 0 | 0.0 | 174 ms | 0 |
| Thu 03 | 0 | 0.0 | 553 ms | 0 |
| Thu 05 | 0 | 0.0 | 437 ms | 0 |
| Thu 07 | 0 | 0.0 | 323 ms | 0 |
| Thu 09 | 0 | 0.0 | 303 ms | 0 |
| Thu 11 | 0 | 0.0 | 318 ms | 0 |
| Thu 13 | 0 | 0.0 | 353 ms | 0 |
| Thu 16 | 0 | 0.0 | 279 ms | 0 |
| Thu 18 | 0 | 0.0 | 344 ms | 0 |
| Thu 20 | 0 | 0.0 | 329 ms | 0 |
| Thu 22 | 0 | 0.0 | 308 ms | 0 |
| Fri 00 | 0 | 0.0 | 277 ms | 0 |
| Fri 02 | 0 | 0.0 | 305 ms | 0 |
| Fri 04 | 0 | 0.0 | 360 ms | 0 |
| Fri 06 | 0 | 0.0 | 357 ms | 0 |
| Fri 08 | 0 | 0.0 | 388 ms | 0 |
| Fri 11 | 0 | 0.0 | 263 ms | 0 |
| Fri 12 | 0 | 0.0 | 278 ms | 0 |
| Fri 14 | 0 | 0.0 | 349 ms | 0 |
| Fri 16 | 0 | 0.0 | 264 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Jam 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 Jam yet. Outages of 10 minutes or more get their own page here.
Having trouble with Jam?
One report per service every 10 minutes from this network. No account.
Follow Jam
Get an email when Jam goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Jam alerts to Slack, Discord or a webhook — free.
About Jam
Jam is listed in our Cloud & developer category and checked at jam.dev. Jam is a screen recorder for software teams. Capture bugs, feedback, and ideas with available console logs, network requests, device details, and user events.
Jam publishes an official status page at status.jam.dev; 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: 315 ms average, 124–403 ms range across 15 successful checks.
Questions
Is Jam down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Jam last down?
We have not recorded a public Jam incident since monitoring began 8 days ago.
What is Jam's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Jam respond?
315 ms on average over the last 24 hours (124–403 ms).
Does Jam have an official status page?
Yes, at https://status.jam.dev.
Jam 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 Jam here at once, the problem is on Jam'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 Jam. 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.