User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 1 hr ago. Last stored result reached it in 297 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 214 ms | 0 |
| Mon 23 | 0 | 0.0 | 368 ms | 0 |
| Tue 01 | 0 | 0.0 | 338 ms | 0 |
| Tue 03 | 0 | 0.0 | 266 ms | 0 |
| Tue 05 | 0 | 0.0 | 280 ms | 0 |
| Tue 08 | 0 | 0.0 | 250 ms | 0 |
| Tue 10 | 0 | 0.0 | 471 ms | 0 |
| Tue 12 | 0 | 0.0 | 293 ms | 0 |
| Tue 14 | 0 | 0.0 | 306 ms | 0 |
| Tue 16 | 0 | 0.0 | 377 ms | 0 |
| Tue 18 | 0 | 0.0 | 363 ms | 0 |
| Tue 21 | 0 | 0.0 | 341 ms | 0 |
| Tue 23 | 0 | 0.0 | 320 ms | 0 |
| Wed 01 | 0 | 0.0 | 282 ms | 0 |
| Wed 03 | 0 | 0.0 | 245 ms | 0 |
| Wed 06 | 0 | 0.0 | 318 ms | 0 |
| Wed 08 | 0 | 0.0 | 249 ms | 0 |
| Wed 10 | 0 | 0.0 | 324 ms | 0 |
| Wed 12 | 0 | 0.0 | 385 ms | 0 |
| Wed 14 | 0 | 0.0 | 287 ms | 0 |
| Wed 16 | 0 | 0.0 | 331 ms | 0 |
| Wed 19 | 0 | 0.0 | 44 ms | 0 |
| Wed 21 | 0 | 0.0 | 329 ms | 0 |
| Wed 23 | 0 | 0.0 | 334 ms | 0 |
| Thu 01 | 0 | 0.0 | 309 ms | 0 |
| Thu 03 | 0 | 0.0 | 652 ms | 0 |
| Thu 05 | 0 | 0.0 | 231 ms | 0 |
| Thu 07 | 0 | 0.0 | 314 ms | 0 |
| Thu 09 | 0 | 0.0 | 164 ms | 0 |
| Thu 12 | 0 | 0.0 | 317 ms | 0 |
| Thu 14 | 0 | 0.0 | 318 ms | 0 |
| Thu 16 | 0 | 0.0 | 318 ms | 0 |
| Thu 18 | 0 | 0.0 | 304 ms | 0 |
| Thu 19 | 0 | 0.0 | 311 ms | 0 |
| Thu 21 | 0 | 0.0 | 330 ms | 0 |
| Thu 23 | 0 | 0.0 | 250 ms | 0 |
| Fri 01 | 0 | 0.0 | 386 ms | 0 |
| Fri 03 | 0 | 0.0 | 182 ms | 0 |
| Fri 05 | 0 | 0.0 | 337 ms | 0 |
| Fri 07 | 0 | 0.0 | 474 ms | 0 |
| Fri 09 | 0 | 0.0 | 320 ms | 0 |
| Fri 11 | 0 | 0.0 | 40 ms | 0 |
| Fri 13 | 0 | 0.0 | 280 ms | 0 |
| Fri 15 | 0 | 0.0 | 336 ms | 0 |
| Fri 17 | 0 | 0.0 | 258 ms | 0 |
| Fri 19 | 0 | 0.0 | 322 ms | 0 |
| Fri 21 | 0 | 0.0 | 80 ms | 0 |
| Fri 23 | 0 | 0.0 | 297 ms | 0 |
93.42% 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.
One report per service every 10 minutes from this network. No account.
Get an email when Limestone Networks goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Limestone Networks alerts to Slack, Discord or a webhook — free.
Limestone Networks is listed in our Cloud & developer category and checked at lstn.net. Bare metal, GPU compute, cloud, and colocation — deployed across 20+ points of presence worldwide, on infrastructure we build, own, and operate ourselves. Every environment is custom-architected around your workload.
Limestone Networks publishes an official status page at status.lstn.net; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 93.42% over 7 days of checks. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 276 ms average, 40–474 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-09 and lasted 2 h 14 min. 1 incident since monitoring began 7 days ago.
From our own checks: 93.42% over 7 days of checks.
276 ms on average over the last 24 hours (40–474 ms).
Yes, at https://status.lstn.net.
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 Limestone Networks here at once, the problem is on Limestone Networks'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 Limestone Networks. 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.