User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 332 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 293 ms | 0 |
| Mon 18 | 0 | 0.0 | 317 ms | 0 |
| Mon 20 | 0 | 0.0 | 366 ms | 0 |
| Mon 22 | 0 | 0.0 | 350 ms | 0 |
| Tue 00 | 0 | 0.0 | 384 ms | 0 |
| Tue 02 | 0 | 0.0 | 320 ms | 0 |
| Tue 04 | 0 | 0.0 | 315 ms | 0 |
| Tue 06 | 0 | 0.0 | 373 ms | 0 |
| Tue 08 | 0 | 0.0 | 314 ms | 0 |
| Tue 10 | 0 | 0.0 | 292 ms | 0 |
| Tue 13 | 0 | 0.0 | 362 ms | 0 |
| Tue 15 | 0 | 0.0 | 271 ms | 0 |
| Tue 17 | 0 | 0.0 | 198 ms | 0 |
| Tue 19 | 0 | 0.0 | 297 ms | 0 |
| Tue 22 | 0 | 0.0 | 275 ms | 0 |
| Wed 00 | 0 | 0.0 | 346 ms | 0 |
| Wed 02 | 0 | 0.0 | 374 ms | 0 |
| Wed 04 | 0 | 0.0 | 243 ms | 0 |
| Wed 07 | 0 | 0.0 | 360 ms | 0 |
| Wed 09 | 0 | 0.0 | 318 ms | 0 |
| Wed 11 | 0 | 0.0 | 431 ms | 0 |
| Wed 13 | 0 | 0.0 | 392 ms | 0 |
| Wed 15 | 0 | 0.0 | 289 ms | 0 |
| Wed 17 | 0 | 0.0 | 229 ms | 0 |
| Wed 20 | 0 | 0.0 | 234 ms | 0 |
| Wed 22 | 0 | 0.0 | 324 ms | 0 |
| Thu 00 | 0 | 0.0 | 262 ms | 0 |
| Thu 02 | 0 | 0.0 | 167 ms | 0 |
| Thu 04 | 0 | 0.0 | 442 ms | 0 |
| Thu 06 | 0 | 0.0 | 290 ms | 0 |
| Thu 08 | 0 | 0.0 | 265 ms | 0 |
| Thu 11 | 0 | 0.0 | 355 ms | 0 |
| Thu 13 | 0 | 0.0 | 283 ms | 0 |
| Thu 15 | 0 | 0.0 | 322 ms | 0 |
| Thu 17 | 0 | 0.0 | 305 ms | 0 |
| Thu 19 | 0 | 0.0 | 297 ms | 0 |
| Thu 21 | 0 | 0.0 | 239 ms | 0 |
| Thu 23 | 0 | 0.0 | 262 ms | 0 |
| Fri 01 | 0 | 0.0 | 219 ms | 0 |
| Fri 03 | 0 | 0.0 | 318 ms | 0 |
| Fri 05 | 0 | 0.0 | 290 ms | 0 |
| Fri 07 | 0 | 0.0 | 345 ms | 0 |
| Fri 09 | 0 | 0.0 | 176 ms | 0 |
| Fri 10 | 0 | 0.0 | 242 ms | 0 |
| Fri 11 | 0 | 0.0 | 276 ms | 0 |
| Fri 13 | 0 | 0.0 | 376 ms | 0 |
| Fri 15 | 0 | 0.0 | 335 ms | 0 |
| Fri 17 | 0 | 0.0 | 332 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 Juniper Square 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 Juniper Square goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Juniper Square alerts to Slack, Discord or a webhook — free.
Juniper Square, at junipersquare.com, is one of the AI services we monitor. 2,300+ private markets GPs rely on Juniper Square’s connected technology, unified data, fund administration expertise, and AI to raise capital more efficiently, streamline operations, and improve the LP experience.
Juniper Square publishes an official status page at status.junipersquare.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 277 ms average, 144–376 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 Juniper Square incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
277 ms on average over the last 24 hours (144–376 ms).
Yes, at https://status.junipersquare.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Juniper Square here at once, the problem is on Juniper Square'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 Juniper Square. 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.