Availability Statement

We host on managed, redundant infrastructure, monitor errors continuously with alerting to our engineering contact, apply rate limits so one client cannot exhaust capacity for others, and maintain encrypted off-site backups with a separate vendor so that data can be restored if the primary platform fails. Current platform state is published on our status page, and the /api/health endpoint can be polled by your own monitoring.

Routine deployments are designed to be zero-downtime. Where planned maintenance requires disruption we will give advance notice by in-product or email notice where reasonably practicable, and aim for low traffic periods. Emergency maintenance for security or stability may be performed without notice.

TimeSpan relies on third-party hosting, database, payment, mapping and AI providers listed on our sub-processor page. An outage, throttle, price change or withdrawal by any of them can affect the Service. Where a dependency is unavailable we aim to degrade gracefully — for example, routing falls back to straight-line distance estimates, and Copilot returns a clear error rather than failing a solve.

A committed availability target with service credits is available only under a separate written service level agreement forming part of an Enterprise plan. Where such an SLA is in place, service credits are your sole and exclusive financial remedy for a failure to meet the target, and credits do not carry a right to a cash refund. To discuss an SLA, contact support@timespan.online.