Skip to main content
Limestone Networks logo

Is Limestone Networks Down?

No — Limestone Networks is up

Reachable from all 6 checked regions

Average response time: 1106ms

Last checked · checks run every 6 hours

Official status page: https://status.lstn.net

Limestone Networks uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1020ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 32 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

32-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 31 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 37 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 39 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 31 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 22 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
904ms
DNS 60ms TCP 113ms TLS 120ms TTFB 418ms
nrt
1326ms
DNS 382ms TCP 127ms TLS 133ms TTFB 781ms
ord
243ms
DNS 69ms TCP 22ms TLS 28ms TTFB 152ms
sin
1877ms
DNS 348ms TCP 206ms TLS 213ms TTFB 986ms
syd
1895ms
DNS 573ms TCP 178ms TLS 185ms TTFB 1126ms
yyz
391ms
DNS 137ms TCP 32ms TLS 40ms TTFB 255ms

What Limestone Networks does

Limestone Networks rents dedicated and bare metal servers, with customers managing them through OnePortal, its control panel and API. Servers are hosted across twelve locations and the company reports each one separately. Customers run their own workloads directly on the hardware, so Limestone is the layer underneath an application rather than the application itself.

What an outage looks like

Either your servers stop answering or your ability to manage them does, and the two are separate failures. A location incident takes the machines in that data centre offline while servers elsewhere keep running. A control-plane incident leaves every server serving traffic normally while OnePortal will not load, so reboots, provisioning and support tickets are unavailable.

What to do about it

Read status.lstn.net and identify which of the two halves failed. Limestone reports OnePortal Web and OnePortal API separately from twelve named locations: DFW, FRA, IAD, JFK, LAX, MIA, ORD, PAR, PDX, SIN, SLC and TYO. Find your server's location rather than reading the headline. If only OnePortal is affected, your servers are still serving and no emergency action is needed.

Is it down for everyone, or just you?

If this page says Limestone Networks is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Hetzner
Hetzner
DigitalOcean
DigitalOcean
Linode
Linode
R
Rackspace

Limestone Networks outage FAQ

OnePortal will not load. Are my servers down?
Not necessarily, and this is the distinction Limestone's status page is built around. OnePortal Web and OnePortal API are listed as components separate from the twelve service locations, so the control panel can be unavailable while every server keeps serving traffic normally. What you lose is management: reboots, provisioning and ticket submission. Check whether your own applications are still responding before treating it as an outage.
A Limestone location is down. Does that affect my server?
Only if your server is in that location. Limestone reports DFW, FRA, IAD, JFK, LAX, MIA, ORD, PAR, PDX, SIN, SLC and TYO as twelve separate rows, and an incident is usually scoped to one data centre. A customer in Dallas is unaffected by a Paris incident. Find your server's location from your own records, since the headline state at the top of the page averages across all of them.
Why is Limestone's status page on a different domain?
Limestone publishes its status at status.lstn.net rather than under limestonenetworks.com, so the address does not match the company's main site. That is worth knowing mainly so you trust the page when you find it. The general reason to separate the two is that a status page served from the same network it reports on becomes unreachable in exactly the incident you need it for.
Can I reboot my server while OnePortal is down?
Not through the control panel, and that is often the frustrating part of a control-plane incident: the machine is reachable and misbehaving but the remote reboot is not available. If the server itself is still responding, a reboot from inside the operating system works and does not involve Limestone. If it is not responding and OnePortal is down, the practical route is support once ticketing returns.
Is Limestone down for everyone or just me?
Scope it by location rather than globally. Because Limestone reports twelve data centres separately, being down is rarely a whole-company state, and another customer's server being fine tells you nothing unless it sits in your location. Check the row for your data centre, then check whether OnePortal is a separate failure. The regional measurements on this page show what our probes reached from several locations.

How we measure this

  • We request Limestone Networks's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 6 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Limestone Networks publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Limestone Networks goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required