The UTC range for 2026 starts at 1767225600 and ends at the exclusive boundary 1798761600. The year has 365 days.
Use the year as a half-open range
WHERE event_time >= 1767225600
AND event_time < 1798761600
The exclusive upper boundary is safer than “December 31 at 23:59:59.” It works whether the database stores whole seconds, milliseconds, or fractions of a second.
Month starts in UTC
| Month start | Unix seconds | ISO 8601 UTC |
|---|---|---|
| January 1 | 1767225600 | 2026-01-01T00:00:00Z |
| February 1 | 1769904000 | 2026-02-01T00:00:00Z |
| March 1 | 1772323200 | 2026-03-01T00:00:00Z |
| April 1 | 1775001600 | 2026-04-01T00:00:00Z |
| May 1 | 1777593600 | 2026-05-01T00:00:00Z |
| June 1 | 1780272000 | 2026-06-01T00:00:00Z |
| July 1 | 1782864000 | 2026-07-01T00:00:00Z |
| August 1 | 1785542400 | 2026-08-01T00:00:00Z |
| September 1 | 1788220800 | 2026-09-01T00:00:00Z |
| October 1 | 1790812800 | 2026-10-01T00:00:00Z |
| November 1 | 1793491200 | 2026-11-01T00:00:00Z |
| December 1 | 1796083200 | 2026-12-01T00:00:00Z |
Quarter boundaries
- Q1: 1767225600 (2026-01-01T00:00:00Z)
- Q2: 1775001600 (2026-04-01T00:00:00Z)
- Q3: 1782864000 (2026-07-01T00:00:00Z)
- Q4: 1790812800 (2026-10-01T00:00:00Z)
- Next year: 1798761600 (2027-01-01T00:00:00Z)
These are UTC values. If the business timezone is not UTC, its local year begins at a different instant; calculate those boundaries in the named location before storing the result.