User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
loadninja.com · Cloud & developer
Is LoadNinja 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 → loadninja.com—
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 46 min ago. Last stored result reached it in 291 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 14 | 0 | 0.0 | 147 ms | 0 |
| Mon 17 | 0 | 0.0 | 249 ms | 0 |
| Mon 19 | 0 | 0.0 | 131 ms | 0 |
| Mon 21 | 0 | 0.0 | 123 ms | 0 |
| Mon 23 | 0 | 0.0 | 123 ms | 0 |
| Tue 01 | 0 | 0.0 | 132 ms | 0 |
| Tue 03 | 0 | 0.0 | 157 ms | 0 |
| Tue 05 | 0 | 0.0 | 107 ms | 0 |
| Tue 07 | 0 | 0.0 | 140 ms | 0 |
| Tue 10 | 0 | 0.0 | 126 ms | 0 |
| Tue 12 | 0 | 0.0 | 68 ms | 0 |
| Tue 14 | 0 | 0.0 | 121 ms | 0 |
| Tue 16 | 0 | 0.0 | 146 ms | 0 |
| Tue 18 | 0 | 0.0 | 188 ms | 0 |
| Tue 21 | 0 | 0.0 | 106 ms | 0 |
| Tue 23 | 0 | 0.0 | 112 ms | 0 |
| Wed 01 | 0 | 0.0 | 167 ms | 0 |
| Wed 03 | 0 | 0.0 | 97 ms | 0 |
| Wed 06 | 0 | 0.0 | 87 ms | 0 |
| Wed 08 | 0 | 0.0 | 65 ms | 0 |
| Wed 10 | 0 | 0.0 | 146 ms | 0 |
| Wed 12 | 0 | 0.0 | 147 ms | 0 |
| Wed 14 | 0 | 0.0 | 124 ms | 0 |
| Wed 16 | 0 | 0.0 | 84 ms | 0 |
| Wed 19 | 0 | 0.0 | 149 ms | 0 |
| Wed 21 | 0 | 0.0 | 163 ms | 0 |
| Wed 23 | 0 | 0.0 | 158 ms | 0 |
| Thu 01 | 0 | 0.0 | 168 ms | 0 |
| Thu 03 | 0 | 0.0 | 244 ms | 0 |
| Thu 05 | 0 | 0.0 | 147 ms | 0 |
| Thu 07 | 0 | 0.0 | 155 ms | 0 |
| Thu 09 | 0 | 0.0 | 91 ms | 0 |
| Thu 11 | 0 | 0.0 | 139 ms | 0 |
| Thu 14 | 0 | 0.0 | 160 ms | 0 |
| Thu 16 | 0 | 0.0 | 232 ms | 0 |
| Thu 18 | 0 | 0.0 | 210 ms | 0 |
| Thu 20 | 0 | 0.0 | 123 ms | 0 |
| Thu 22 | 0 | 0.0 | 197 ms | 0 |
| Fri 00 | 0 | 0.0 | 226 ms | 0 |
| Fri 02 | 0 | 0.0 | 187 ms | 0 |
| Fri 04 | 0 | 0.0 | 178 ms | 0 |
| Fri 06 | 0 | 0.0 | 156 ms | 0 |
| Fri 08 | 0 | 0.0 | 126 ms | 0 |
| Fri 10 | 0 | 0.0 | 125 ms | 0 |
| Fri 11 | 0 | 0.0 | 112 ms | 0 |
| Fri 13 | 0 | 0.0 | 124 ms | 0 |
| Fri 15 | 0 | 0.0 | 132 ms | 0 |
| Fri 17 | 0 | 0.0 | 291 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live LoadNinja 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 LoadNinja yet. Outages of 10 minutes or more get their own page here.
Having trouble with LoadNinja?
One report per service every 10 minutes from this network. No account.
Follow LoadNinja
Get an email when LoadNinja goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send LoadNinja alerts to Slack, Discord or a webhook — free.
About LoadNinja
LoadNinja is listed in our Cloud & developer category and checked at loadninja.com. The only load testing tool to record, replay, and test in real browsers at scale. Performance testing doesn't have to be the bottleneck. Cut your load testing time in half by running website performance tests in real browsers at scale. LoadNinja is the only load testing tool to record and replay scripts in minutes, leverage real browsers, and deliver actionable website performance data straight from the browser’s DOM.
LoadNinja publishes an official status page at status.loadninja.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 161 ms average, 103–291 ms range across 13 successful checks.
Questions
Is LoadNinja down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was LoadNinja last down?
We have not recorded a public LoadNinja incident since monitoring began 7 days ago.
What is LoadNinja's uptime?
From our own checks: 100% over 7 days of checks.
How fast does LoadNinja respond?
161 ms on average over the last 24 hours (103–291 ms).
Does LoadNinja have an official status page?
Yes, at https://status.loadninja.com.
LoadNinja 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 LoadNinja here at once, the problem is on LoadNinja'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 LoadNinja. 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.