New Zealand WordPress hosting where today starts before UTC does.
New Zealand runs up to thirteen hours ahead of UTC. Anything that decides what today means in UTC is wrong here for most of the working day.
Ahead of everybody.
Every date calculation that defaults to UTC produces an answer a New Zealand business disagrees with.
Daily boundaries in local time
A report for today built on UTC covers most of yesterday afternoon here. Date ranges are computed in local time so a daily total matches the trading day.
Scheduled jobs that fire when intended
A nightly job set for midnight UTC runs at lunchtime in Auckland. Schedules are expressed in local time so overnight work happens overnight.
Daylight saving handled twice a year
The offset changes and a schedule pinned to a fixed UTC hour drifts by one. Local time is used so it does not.
Origin placement stated
New Zealand is further from most infrastructure than anywhere else, so where the origin sits is a decision made with you rather than a default.
Macrons in te reo Māori
Place and organisation names carry macrons that people type without. Matching folds them while display keeps them correct.
Reports for the wrong day.
A daily sales figure that includes yesterday afternoon and stops at eleven in the morning is not obviously broken. It is just consistently wrong, and it reconciles against nothing.
- Date ranges computed in local time
- Scheduled jobs expressed in local time
- Daylight saving transitions handled
- Macrons folded for matching
The day has to match the business.
The measurement here is not latency but agreement: whether the site's idea of today is the same as the one on the accountant's calendar.
What we change for New Zealand sites
A large positive offset makes every UTC-based date assumption visibly wrong, which is rare enough that most software gets it wrong by default.
| Setting | What we do | Why |
|---|---|---|
| Date range calculation | Computed against local midnight rather than UTC | At up to thirteen hours ahead, a UTC day covers most of the previous local afternoon, so a daily report reconciles against nothing. |
| Scheduled jobs | Expressed in local time | A job set for midnight UTC runs in the middle of the New Zealand working day, which is the opposite of what an overnight task is for. |
| Daylight saving | Transitions handled rather than assumed away | A schedule pinned to a fixed UTC hour shifts by one twice a year, and the drift is noticed weeks later if at all. |
| Origin placement | Decided explicitly with the customer | New Zealand is further from most infrastructure than any other market, so an inherited default is an unmeasured latency cost. |
| Macron folding | Applied for matching, preserved for display | Te reo Māori names carry macrons that are routinely omitted when typing, so strict matching fails against correct content. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why do my daily reports not match my trading day?
Why do overnight jobs run during business hours?
Does daylight saving cause problems?
Where should a New Zealand site be hosted?
Agree with the local calendar.
Move the site across. Migration is free, timezone handling reviewed.