Docs

Sucuri uses Eastern time; we use UTC

Sucuri uses Eastern time; we use UTC

Sucuri’s audit feed and dashboard designate times in US Eastern time (ET — observes DST). The application, the database, and all downstream metrics use UTC.

Where this matters

  • audit_trails API date=yyyy-mm-dd parameter — interpreted as an Eastern-time calendar day, not UTC. “Today” in ET is 4–5 hours behind UTC, so a UTC Date.today query around midnight may miss or double-count entries.
  • Log-entry timestamps in shipped payloads — Sucuri may emit ET-local timestamps. Our WafLogProcessor / ApacheLogParser need to handle this correctly when populating log_timestamp on WafLogEntry.
  • Customer-facing dashboards — if we show “today’s blocks” we need to decide whether “today” means the customer’s local day, our UTC day, or Sucuri’s ET day.

When converting

  • Pulling logs for “today UTC”: likely need to request both the ET-local “today” and “yesterday” dates and filter to the UTC window.
  • Cross-referencing a Sucuri audit row’s timestamp with our own logs: convert the Sucuri timestamp from ET → UTC before comparing.