Stasysstatus
Downloads and updates (updates.lbreeze.com)
← Back to status

httphttps://updates.lbreeze.com/health

Operational
Uptime 24h
100%
Uptime 7d
100%
Uptime 30d
100%
Uptime 90d
100%

Uptime (last 7 days · one slice per hour · click a failure for its times)

31/10/2026, 04:00 CET – 31/10/2026, 16:00 CET · all checks passed31/10/2026, 16:00 CET – 31/10/2026, 18:00 CET · all checks passed · planned maintenance31/10/2026, 18:00 CET – 01/11/2026, 01:00 CET · all checks passed01/11/2026, 01:00 CET – 01/11/2026, 02:00 CET · all checks passed · planned maintenance01/11/2026, 02:00 CET – 01/11/2026, 14:00 CET · all checks passed01/11/2026, 14:00 CET – 01/11/2026, 15:00 CET · all checks passed · maintenance window open, no impact01/11/2026, 15:00 CET – 01/11/2026, 23:00 CET · all checks passed01/11/2026, 23:00 CET – 02/11/2026, 00:00 CET · all checks passed · maintenance window open, no impact02/11/2026, 00:00 CET – 03/11/2026, 04:00 CET · all checks passed03/11/2026, 04:00 CET – 03/11/2026, 05:00 CET · all checks passed · maintenance window open, no impact03/11/2026, 05:00 CET – 04/11/2026, 13:00 CET · 100% uptime · 1 of 2 probes saw a timeout; the others were OK — not counted as downtime04/11/2026, 13:00 CET – 04/11/2026, 14:00 CET · all checks passed · planned maintenance04/11/2026, 14:00 CET – 05/11/2026, 03:00 CET · 100% uptime · 7 checks where fewer probes than needed failed (first: 1 of 2 probes saw a timeout); the others were OK — not counted as downtime05/11/2026, 03:00 CET – 05/11/2026, 06:00 CET · all checks passed · maintenance window open, no impact05/11/2026, 06:00 CET – 05/11/2026, 14:00 CET · all checks passed05/11/2026, 14:00 CET – 05/11/2026, 15:00 CET · all checks passed · maintenance window open, no impact05/11/2026, 15:00 CET – 06/11/2026, 20:00 CET · all checks passed06/11/2026, 20:00 CET – 06/11/2026, 21:00 CET · all checks passed · maintenance window open, no impact06/11/2026, 21:00 CET – 07/11/2026, 03:11 CET · all checks passed
all checks passedunder 10% failed10–50%50%+maintenance, service affectedno datanot yet monitored

Latency by region (p50 / p95 / p99 across last 200 probes)

Latency & probe results (last 200 probes)

07/11/2026, 01:31 CET p50 35ms · p95 39ms · p99 51ms · avg 32ms · failures 0 now

Location · Falkenstein, DE

Checked from 2 locations: Nuremberg, Germany Helsinki, Finland
target checked from probe route
IP geolocation by DB-IP

Recent probes (last 50)

min 14ms avg 32ms p95 49ms max 50ms
WhenResultLatencyRegionError
07/11/2026, 03:11 CET OK 36ms
dns 2 · connect 35 · tls 39 · answer 36 · fresh visit 116
 Helsinki, Finland
07/11/2026, 03:10 CET OK 20ms
dns 32 · connect 4 · tls 12 · answer 20 · fresh visit 69
 Nuremberg, Germany
07/11/2026, 03:10 CET OK 35ms
dns 4 · connect 35 · tls 39 · answer 35 · fresh visit 114
 Helsinki, Finland
07/11/2026, 03:09 CET OK 34ms
dns 1 · connect 4 · tls 11 · answer 34 · fresh visit 51
 Nuremberg, Germany
07/11/2026, 03:09 CET OK 35ms
dns 2 · connect 35 · tls 42 · answer 35 · fresh visit 115
 Helsinki, Finland
07/11/2026, 03:08 CET OK 20ms
dns 49 · connect 4 · tls 13 · answer 20 · fresh visit 86
 Nuremberg, Germany
07/11/2026, 03:08 CET OK 36ms
dns 3 · connect 40 · tls 39 · answer 36 · fresh visit 121
 Helsinki, Finland
07/11/2026, 03:07 CET OK 20ms
dns 31 · connect 4 · tls 11 · answer 20 · fresh visit 66
 Nuremberg, Germany
07/11/2026, 03:07 CET OK 36ms
dns 5 · connect 36 · tls 43 · answer 36 · fresh visit 125
 Helsinki, Finland
07/11/2026, 03:06 CET OK 50ms
dns 40 · connect 9 · tls 7 · answer 50 · fresh visit 106
 Nuremberg, Germany
07/11/2026, 03:06 CET OK 35ms
dns 4 · connect 35 · tls 39 · answer 35 · fresh visit 114
 Helsinki, Finland
07/11/2026, 03:05 CET OK 37ms
dns 33 · connect 3 · tls 13 · answer 37 · fresh visit 86
 Nuremberg, Germany
07/11/2026, 03:05 CET OK 36ms
dns 4 · connect 36 · tls 40 · answer 36 · fresh visit 117
 Helsinki, Finland
07/11/2026, 03:04 CET OK 36ms
dns 1 · connect 9 · tls 12 · answer 36 · fresh visit 58
 Nuremberg, Germany
07/11/2026, 03:04 CET OK 35ms
dns 4 · connect 35 · tls 39 · answer 35 · fresh visit 113
 Helsinki, Finland
07/11/2026, 03:03 CET OK 20ms
dns 1 · connect 4 · tls 12 · answer 20 · fresh visit 37
 Nuremberg, Germany
07/11/2026, 03:03 CET OK 36ms
dns 2 · connect 40 · tls 43 · answer 36 · fresh visit 122
 Helsinki, Finland
07/11/2026, 03:02 CET OK 31ms
dns 17 · connect 4 · tls 11 · answer 31 · fresh visit 63
 Nuremberg, Germany
07/11/2026, 03:02 CET OK 36ms
dns 2 · connect 40 · tls 39 · answer 36 · fresh visit 122
 Helsinki, Finland
07/11/2026, 03:01 CET OK 20ms
dns 0 · connect 9 · tls 11 · answer 20 · fresh visit 40
 Nuremberg, Germany
07/11/2026, 03:01 CET OK 36ms
dns 1 · connect 36 · tls 40 · answer 36 · fresh visit 117
 Helsinki, Finland
07/11/2026, 03:00 CET OK 19ms
dns 2 · connect 3 · tls 13 · answer 19 · fresh visit 37
 Nuremberg, Germany
07/11/2026, 03:00 CET OK 37ms
dns 5 · connect 36 · tls 43 · answer 37 · fresh visit 124
 Helsinki, Finland
07/11/2026, 02:59 CET OK 29ms
dns 1 · connect 4 · tls 6 · answer 29 · fresh visit 41
 Nuremberg, Germany
07/11/2026, 02:59 CET OK 39ms
dns 4 · connect 39 · tls 44 · answer 39 · fresh visit 130
 Helsinki, Finland
07/11/2026, 02:58 CET OK 34ms
dns 32 · connect 8 · tls 12 · answer 34 · fresh visit 86
 Nuremberg, Germany
07/11/2026, 02:58 CET OK 37ms
dns 2 · connect 39 · tls 43 · answer 37 · fresh visit 123
 Helsinki, Finland
07/11/2026, 02:57 CET OK 20ms
dns 16 · connect 4 · tls 13 · answer 20 · fresh visit 54
 Nuremberg, Germany
07/11/2026, 02:57 CET OK 35ms
dns 1 · connect 35 · tls 42 · answer 35 · fresh visit 118
 Helsinki, Finland
07/11/2026, 02:56 CET OK 35ms
dns 1 · connect 4 · tls 11 · answer 35 · fresh visit 51
 Nuremberg, Germany
07/11/2026, 02:56 CET OK 37ms
dns 2 · connect 39 · tls 43 · answer 37 · fresh visit 123
 Helsinki, Finland
07/11/2026, 02:55 CET OK 49ms
dns 1 · connect 9 · tls 11 · answer 49 · fresh visit 71
 Nuremberg, Germany
07/11/2026, 02:55 CET OK 37ms
dns 4 · connect 36 · tls 43 · answer 37 · fresh visit 121
 Helsinki, Finland
07/11/2026, 02:54 CET OK 37ms
dns 16 · connect 9 · tls 13 · answer 37 · fresh visit 76
 Nuremberg, Germany
07/11/2026, 02:54 CET OK 37ms
dns 2 · connect 36 · tls 43 · answer 37 · fresh visit 120
 Helsinki, Finland
07/11/2026, 02:53 CET OK 14ms
dns 15 · connect 4 · tls 12 · answer 14 · fresh visit 45
 Nuremberg, Germany
07/11/2026, 02:53 CET OK 35ms
dns 7 · connect 38 · tls 41 · answer 35 · fresh visit 126
 Helsinki, Finland
07/11/2026, 02:52 CET OK 19ms
dns 1 · connect 4 · tls 11 · answer 19 · fresh visit 35
 Nuremberg, Germany
07/11/2026, 02:52 CET OK 35ms
dns 2 · connect 35 · tls 42 · answer 35 · fresh visit 120
 Helsinki, Finland
07/11/2026, 02:51 CET OK 19ms
dns 1 · connect 4 · tls 11 · answer 19 · fresh visit 36
 Nuremberg, Germany
07/11/2026, 02:51 CET OK 36ms
dns 2 · connect 36 · tls 43 · answer 36 · fresh visit 120
 Helsinki, Finland
07/11/2026, 02:50 CET OK 50ms
dns 31 · connect 3 · tls 11 · answer 50 · fresh visit 95
 Nuremberg, Germany
07/11/2026, 02:50 CET OK 35ms
dns 2 · connect 35 · tls 42 · answer 35 · fresh visit 120
 Helsinki, Finland
07/11/2026, 02:49 CET OK 15ms
dns 16 · connect 4 · tls 8 · answer 15 · fresh visit 44
 Nuremberg, Germany
07/11/2026, 02:49 CET OK 36ms
dns 7 · connect 39 · tls 43 · answer 36 · fresh visit 127
 Helsinki, Finland
07/11/2026, 02:48 CET OK 19ms
dns 38 · connect 4 · tls 11 · answer 19 · fresh visit 73
 Nuremberg, Germany
07/11/2026, 02:48 CET OK 37ms
dns 5 · connect 36 · tls 44 · answer 37 · fresh visit 124
 Helsinki, Finland
07/11/2026, 02:47 CET OK 21ms
dns 16 · connect 5 · tls 11 · answer 21 · fresh visit 53
 Nuremberg, Germany
07/11/2026, 02:47 CET OK 36ms
dns 7 · connect 35 · tls 42 · answer 36 · fresh visit 122
 Helsinki, Finland
07/11/2026, 02:46 CET OK 35ms
dns 1 · connect 4 · tls 11 · answer 35 · fresh visit 51
 Nuremberg, Germany

Related incidents (last 90 days)

No incidents in the last 90 days.