Hosting in New Zealand

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.

Local date boundariesCron on local timeReports that match the day
Local date logicTimezone-safe cronDST handlingDaily backupsFree SSL24/7 support
Built for New Zealand sites

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.

Local midnight

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.

Local schedule

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.

Time

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
Date boundary
Basis
local midnight
Cron
Basis
local time
DST
Handled
yes
Origin
Placement
running
Correctness

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.

Local
date boundaries
Local
cron scheduling
Folded
te reo macrons
MagicWP105 ms
Typical shared host980 ms
European origin serving New Zealand470 ms

Illustrative comparison of a page request from a New Zealand connection. Your numbers depend on origin placement and page weight.

Configuration

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.

SettingWhat we doWhy
Date range calculationComputed against local midnight rather than UTCAt up to thirteen hours ahead, a UTC day covers most of the previous local afternoon, so a daily report reconciles against nothing.
Scheduled jobsExpressed in local timeA 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 savingTransitions handled rather than assumed awayA schedule pinned to a fixed UTC hour shifts by one twice a year, and the drift is noticed weeks later if at all.
Origin placementDecided explicitly with the customerNew Zealand is further from most infrastructure than any other market, so an inherited default is an unmeasured latency cost.
Macron foldingApplied for matching, preserved for displayTe reo Māori names carry macrons that are routinely omitted when typing, so strict matching fails against correct content.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Why do my daily reports not match my trading day?
Because the date range is computed in UTC. At thirteen hours ahead a UTC day covers most of the previous local afternoon, so the total reconciles against nothing.
Why do overnight jobs run during business hours?
They are scheduled in UTC. Midnight UTC is the middle of the working day in New Zealand, so an overnight task has to be expressed in local time.
Does daylight saving cause problems?
It does when a schedule is pinned to a fixed UTC hour — the local time shifts by one twice a year and nobody notices for weeks.
Where should a New Zealand site be hosted?
That is worth deciding rather than defaulting. New Zealand is further from most infrastructure than any other market, so an inherited origin is an unmeasured cost.

Agree with the local calendar.

Move the site across — migration is free, timezone handling reviewed.