LucidStack
Features
Solutions
Resources
Pricing

Response time

A slow website loses customers long before it goes down.

LucidStack measures the response time of every check, compares it with its usual level and flags a slowdown before it turns into an outage.

Free up to 10 monitors ·No credit card ·Hosted in Europe

Response time

Last 24 hours · per hour

400 300 200 100 0

00:00 – 01:00

Average 182 ms

01:00 – 02:00

Average 176 ms

02:00 – 03:00

Average 169 ms

03:00 – 04:00

Average 171 ms

04:00 – 05:00

Average 164 ms

05:00 – 06:00

Average 158 ms

06:00 – 07:00

Average 161 ms

07:00 – 08:00

Average 166 ms

08:00 – 09:00

Average 174 ms

09:00 – 10:00

Average 191 ms

10:00 – 11:00

Average 208 ms

11:00 – 12:00

Average 223 ms

12:00 – 13:00

Average 236 ms

13:00 – 14:00

Average 241 ms

14:00 – 15:00

Average 229 ms

15:00 – 16:00

Average 218 ms

16:00 – 17:00

Average 212 ms

17:00 – 18:00

Average 205 ms

18:00 – 19:00

Average 214 ms

19:00 – 20:00

Average 226 ms

20:00 – 21:00

Average 219 ms

21:00 – 22:00

Average 198 ms

22:00 – 23:00

Average 187 ms

23:00 – 00:00

Average 179 ms
00:00 06:00 12:00 18:00

Response time

Performance, measured seriously

Useful numbers, not just an average.

Every phase measured

DNS, connect, TLS and time to first byte, so you know where time is lost.

95th percentile

The time that 95% of your checks stay within, more telling than an average.

Slowness threshold

Above a threshold, the service switches to "degraded" without triggering a downtime alert.

Anomaly detection

A response time far from its usual level is detected and explained.

By region

Spot a network or CDN issue that only affects part of Europe.

History

24-hour, 7-day and 30-day charts for each monitor.

Getting started

Track your performance

  1. 1

    Add a monitor

    Website, API or WebSocket.

  2. 2

    Set a threshold

    Optional: the response time above which the service is degraded.

  3. 3

    Let it learn

    The usual level is calculated automatically to spot anomalies.

Questions

Response time FAQ

How long are measurements kept?

Detailed results are kept for 30 days.

How are anomalies detected?

Each measurement is compared with the service's usual level using a statistical method that is robust to outliers.

Does a slow service trigger a downtime alert?

No: above the slowness threshold, it switches to "degraded", which stays visible without waking up whoever is on call.

Are response times included in reports?

Yes, monthly reports include the response times of each service.

Start monitoring in two minutes.

Add a URL, choose where to be alerted. LucidStack takes care of the rest, day and night.