IndiGo booking website hit by second disruption in a week

IndiGo’s website prevented some users from searching and booking flights, displaying a “No Data Available” error and redirecting visitors to its homepage. The issue follows intermittent reservation-platform disruptions reported on August 19.

— Source published Fri, 21 Aug, 2026, 11:56 IST · First seen Fri, 21 Aug, 2026, 12:02 IST · Source ET Small Business

What happened

IndiGo’s website prevented some users from searching and booking flights, showing a “No Data Available” error and redirecting them to its homepage. The

Key facts

  • Second disruption in a week
  • August 19

Why this matters

The incidents underscore the strategic value of resilient reservation technology and contingency partnerships, while raising diligence questions around IndiGo’s platform architecture and vendor dependencies.

What to watch

  • A third outage or prolonged disruption during a weekend, holiday or weather-related demand spike.
  • Material increase in OTA visibility, OTA booking share or calls for fare-hold protections from affected customers.
  • Elevated app-store reviews, social-media complaints, refund requests or call-center wait times.
  • Disclosure of a common reservation-platform, cloud, network or third-party vendor dependency behind both incidents.
  • Evidence of flight inventory mismatch, duplicate bookings, payment captures without ticket issuance, or delayed disruption communications.
  • Publish a transparent incident update, restoration status and alternate booking paths across app, social, SMS and airport/call-center channels.
  • Prioritize root-cause analysis across reservation, inventory, API, payment and web-routing dependencies; test failover under peak-load conditions.
  • Offer affected users preserved fares, fee waivers or targeted recovery incentives to limit abandoned bookings and OTA migration.
  • Track direct-web conversion, search-to-book abandonment, call-center volumes, OTA booking share, payment failures and social-service complaints by hour.
  • Deploy a customer-facing status page and queue/fallback booking experience rather than redirecting users to the homepage.