IndiGo website booking outage recurs for second time in a week

IndiGo’s website faced a technical disruption on Friday, with some users unable to book flights and seeing a “no data available” message. The reported incident marks the carrier’s second website outage this week, raising near-term concerns over digital booking reliability.

— Source published Fri, 21 Aug, 2026, 12:53 IST · First seen Fri, 21 Aug, 2026, 13:00 IST · Source Mint · Companies

What happened

IndiGo’s website suffered a technical disruption on Friday, preventing some users from booking flights and displaying a “no data available” message. The

Key facts

  • Second outage affecting the carrier this week

Why this matters

The outages underscore the strategic value of resilient booking technology, creating a stronger case for partnerships or acquisitions in cloud reliability, customer-experience monitoring, and omnichannel recovery tools.

What to watch

  • A third outage within the next two weeks or an outage lasting more than a few hours.
  • Reports that the mobile app, payment gateway, check-in, manage-booking or PNR functions are also affected.
  • Spike in IndiGo complaint volumes, failed-payment posts, call-centre wait times or app-store rating deterioration.
  • Evidence of higher OTA booking share, elevated fare discrepancies or competitor gains on affected routes.
  • Formal carrier statement identifying a vendor, infrastructure, cyber or capacity-related root cause.
  • Booking disruption coinciding with holiday, weekend or high-demand travel periods.
  • Publish clear incident updates, restoration timing and alternate booking paths across social, app notifications and airport channels.
  • Prioritize booking, payment, PNR retrieval and disruption-management functions; run failover and load-testing reviews after the second incident.
  • Temporarily steer customers to the mobile app, call centre and selected OTA partners while preserving fare and inventory consistency.
  • Offer proactive fee waivers or fare holds for customers whose transactions failed during the outage.
  • Audit third-party dependencies, cloud/CDN capacity, release-management processes and monitoring alerts; communicate corrective actions once validated.