SafeNow incident

Timeouts of SafeNow-API calls

Resolved after 1 hour 9 minutes, affecting Uptime and Uptime and 1 more, on February 15, 2026.

resolved Feb 15, 2026, 03:04 PM UTC

All systems operational again. Reason was preparation for a future feature that slowed down the database after running smoothly for a couple of days.

Started: Feb 15, 2026, 01:55 PM UTC
Resolved: Feb 15, 2026, 03:04 PM UTC
Duration: 1h 9m
Detected by Pingoru: Feb 15, 2026, 01:55 PM UTC

Affected components

UptimeUptimeRegistrationRegistration & LoginAlarm sendingAlarm receivingAlarm HistoryAlarm receivingSmart matching to SafeNow ZonesManage SafeNow Zones

Update timeline

investigating Feb 15, 2026, 02:31 PM UTC

We see unexpected timeouts in APIs and are investigating the problem.
identified Feb 15, 2026, 02:40 PM UTC

We identified the cause for the timeouts in a deployment for a future feature of the SafeNow app.
identified Feb 15, 2026, 02:47 PM UTC

We are continuing to work on a fix for this issue.
identified Feb 15, 2026, 02:49 PM UTC

We are continuing to work on a fix for this issue.
resolved Feb 15, 2026, 03:04 PM UTC

All systems operational again. Reason was preparation for a future feature that slowed down the database after running smoothly for a couple of days.

Your product runs on more than SafeNow

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.