Client: Voyagr · Logistics, Travel & Marketplaces · UK online travel agency (110 staff)

Faster Travel Search and Booking at Peak

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team covered peak-period technical incidents for Voyagr’s Node.js travel booking platform. Over eight weeks, client Datadog records show p95 search time falling from 1.8 seconds to 480 ms and booking failures from 3.4% to 0.7%.

Client and engagement facts

Client
Voyagr
Industry
Logistics, Travel & Marketplaces
Business context
UK online travel agency (110 staff)
Delivery model
Peak search and booking technical coverage
Application
OTA search and booking platform
Supplied geography
UK
Company size in source
110 staff
Coverage
24/7 during peak season only

Application stack and tools

Application stack

  • Node.js
  • Elasticsearch
  • Redis
  • AWS

Tools used

  • Datadog
  • Zendesk

Why Support Was Needed

School holidays brought four times normal volume for six weeks. A misconfigured Elasticsearch replica and a Redis pool sized for normal traffic slowed search and booking.

Technical Work

  • Found the misconfigured Elasticsearch replica causing half of search latency.
  • Fixed the Redis connection pool sized for baseline.
  • Wrote runbooks for peak-week failure patterns.

Representative Incident

A payment provider outage affected bookings for 40 minutes in week five. The engineers documented the impact and added the dependency to the next peak coverage plan.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSample / populationSource and scope
Search P951.8 s480 msBaseline: s; Result: ms8 weeksClient Datadog
Booking failures3.4%0.7%%8 weeksClient Datadog
Queue first response45 min6 minmin8 weeksClient Zendesk support queue.Client Zendesk

Evidence and Limitations

The eight-week comparison excludes one payment provider outage. The Zendesk response figure describes the client’s queue. Around-the-clock coverage applied during the peak period.

Peak Traffic Baseline

School holiday traffic ran at four times baseline for six weeks.

Scope a Similar Engagement

Share your busiest booking period and which search, cache and payment incidents need technical coverage. Request a support plan or explore 24/7 technical support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.