User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
leaptodigital.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 31 min ago. Last stored result reached it in 311 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 263 ms | 0 |
| Mon 18 | 0 | 0.0 | 384 ms | 0 |
| Mon 20 | 0 | 0.0 | 144 ms | 0 |
| Mon 22 | 0 | 0.0 | 338 ms | 0 |
| Tue 00 | 0 | 0.0 | 371 ms | 0 |
| Tue 02 | 0 | 0.0 | 348 ms | 0 |
| Tue 04 | 0 | 0.0 | 338 ms | 0 |
| Tue 07 | 0 | 0.0 | 323 ms | 0 |
| Tue 09 | 0 | 0.0 | 301 ms | 0 |
| Tue 11 | 0 | 0.0 | 329 ms | 0 |
| Tue 13 | 0 | 0.0 | 382 ms | 0 |
| Tue 15 | 0 | 0.0 | 322 ms | 0 |
| Tue 18 | 0 | 0.0 | 342 ms | 0 |
| Tue 20 | 0 | 0.0 | 302 ms | 0 |
| Tue 22 | 0 | 0.0 | 297 ms | 0 |
| Wed 00 | 0 | 0.0 | 312 ms | 0 |
| Wed 03 | 0 | 0.0 | 309 ms | 0 |
| Wed 05 | 0 | 0.0 | 288 ms | 0 |
| Wed 07 | 0 | 0.0 | 313 ms | 0 |
| Wed 09 | 0 | 0.0 | 341 ms | 0 |
| Wed 12 | 0 | 0.0 | 320 ms | 0 |
| Wed 14 | 0 | 0.0 | 303 ms | 0 |
| Wed 16 | 0 | 0.0 | 225 ms | 0 |
| Wed 18 | 0 | 0.0 | 179 ms | 0 |
| Wed 20 | 0 | 0.0 | 341 ms | 0 |
| Wed 22 | 0 | 0.0 | 385 ms | 0 |
| Thu 00 | 0 | 0.0 | 336 ms | 0 |
| Thu 03 | 0 | 0.0 | 310 ms | 0 |
| Thu 05 | 0 | 0.0 | 175 ms | 0 |
| Thu 07 | 0 | 0.0 | 332 ms | 0 |
| Thu 09 | 0 | 0.0 | 346 ms | 0 |
| Thu 11 | 0 | 0.0 | 209 ms | 0 |
| Thu 13 | 0 | 0.0 | 303 ms | 0 |
| Thu 15 | 0 | 0.0 | 333 ms | 0 |
| Thu 17 | 0 | 0.0 | 208 ms | 0 |
| Thu 19 | 0 | 0.0 | 199 ms | 0 |
| Thu 21 | 0 | 0.0 | 292 ms | 0 |
| Thu 23 | 0 | 0.0 | 338 ms | 0 |
| Fri 01 | 0 | 0.0 | 297 ms | 0 |
| Fri 03 | 0 | 0.0 | 149 ms | 0 |
| Fri 05 | 0 | 0.0 | 348 ms | 0 |
| Fri 08 | 0 | 0.0 | 329 ms | 0 |
| Fri 10 | 0 | 0.0 | 306 ms | 0 |
| Fri 12 | 0 | 0.0 | 329 ms | 0 |
| Fri 14 | 0 | 0.0 | 349 ms | 0 |
| Fri 16 | 0 | 0.0 | 312 ms | 0 |
| Fri 17 | 0 | 0.0 | 346 ms | 0 |
| Fri 18 | 0 | 0.0 | 311 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Leap 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 Leap goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Leap alerts to Slack, Discord or a webhook — free.
We track Leap (leaptodigital.com) as part of the Cloud & developer group. Leap helps roofing, remodeling, and home improvement contractors manage jobs, build estimates, and close more deals in one platform.
Leap publishes an official status page at status.leaptodigital.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 301 ms average, 149–349 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 Leap incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
301 ms on average over the last 24 hours (149–349 ms).
Yes, at https://status.leaptodigital.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 Leap here at once, the problem is on Leap'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 Leap. 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.