Driver mobile app (PWA)
Offline shift, stops and ePOD capture
99.98%30-day uptime142 msmedian
Status
All Depot2Door systems operational.
Live availability for every service drivers and dispatchers depend on, plus 90 days of history and past incident reports.
All systems operationallast checked — CET
Service availability
Rolling 30-day uptime and median response time.
Dispatcher mission control
Live map, manifest grid, assignments
99.97%30-day uptime168 msmedian
Manifest sync API
Route push, handshakes and acknowledgements
99.99%30-day uptime96 msmedian
Media storage & signed links
Delivery photos and signatures
100.00%30-day uptime112 msmedian
Notifications & email
PoD reports, alerts and auth mail
99.95%30-day uptime204 msmedian
Authentication
Portal login and role sessions
100.00%30-day uptime88 msmedian
Last 90 days
90 days ago 99.98% overallToday
How we monitor
What happens between a failed check and the update you read here.
Continuous checks
Every service is probed every 30 seconds from multiple European regions. A check only counts as healthy when the full request path — including the database — answers in time.
Alerting & escalation
Two consecutive failed checks page the on-call engineer. If a customer-facing service is degraded for more than five minutes, the incident is posted on this page and workspace admins are emailed.
Data safety
The platform is hosted in EU data centres with encrypted backups every six hours and 30-day point-in-time recovery. Delivery media lives in EU object storage with short-lived signed access links.
Incident history
Resolved
Delayed proof-of-delivery emails
Outbound mail queued for 38 minutes after an upstream provider throttle. No delivery data was lost; all reports were sent once the queue drained.
Completed
Scheduled database maintenance
20-minute read-only window during the 02:00–03:00 CET maintenance slot. Drivers continued working offline and synced afterwards.
Maintenance & communication policy
Planned maintenance
Maintenance happens in the 02:00–03:00 CET window and is announced on this page at least 72 hours in advance. Because the driver app is offline-first, drivers keep working during read-only windows and sync when the platform returns.
During an incident
We post a first update within 15 minutes of confirming a customer-facing incident, then at least hourly until resolution. A written postmortem follows within five business days for any incident that affected delivery data or driver workflows.