Start Time: Approximately 02:00 UTC on March 8, 2026 Duration: 1 hour Affected Services:

Main website (seemynudes.com) Status page (status.seemynudes.com)

What happened: Both the main site and status page experienced intermittent failures, primarily SQL errors (SQLSTATE[22007]: Invalid datetime format: 1292) when updating user records, such as the last_active_at and updated_at timestamps in the database. This prevented normal user activity tracking, page loads in some cases, and status page updates. Impact:

Users may have seen errors, slow performance, or failed interactions on the main site. Status page was unable to report accurate/up-to-date information due to the same underlying issue. No data loss occurred; the issue was isolated to timestamp handling during a specific time window.

Root Cause: The errors were triggered by the Daylight Saving Time (DST) "spring forward" transition on March 8, 2026, at 2:00 AM local time in the server's timezone (America/New_York). During this change, clocks skip from 2:00 AM to 3:00 AM, creating a one-hour block of "non-existent" local times. The application attempted to store timestamps that fell into this skipped period (e.g., 2026-03-08 02:00:49), which MySQL rejected—even after converting the affected columns to DATETIME. The mismatch occurred because the database connection session inherited the server's DST-aware timezone, causing it to interpret incoming UTC timestamps as invalid in local time.