! Scheduled Maintenance: Our server is currently undergoing scheduled maintenance. You may experience temporary interruptions, but our technical team is actively monitoring the system and working to restore full service as soon as possible. Thank you for your patience.
System Status

All systems operational

Real-time health of the adivaha platform. We commit to 99.9% uptime SLA across booking engines, APIs, payments and dashboards - with transparent incident history and 24x7 oncall.

  • 99.9% 30-day uptime
  • < 350ms median API latency
  • 24x7 oncall engineering
  • 0 critical incidents (90 days)
Component Health

Live status of every adivaha component

If a component is degraded, you'll see the colour and message change here first. Subscribe on the live status board to get notified by email or webhook.

Booking Engine (Web) 99.99% · 30 days Operational
White-Label Storefronts 99.98% · 30 days Operational
B2B Sub-Agent Portal 99.97% · 30 days Operational
Mobile Apps (iOS / Android) 99.99% · 30 days Operational
Universal Travel API Suite 99.96% · 30 days Operational
Flight API (GDS + LCC) 99.95% · 30 days Operational
Hotel API (Multi-supplier) 99.97% · 30 days Operational
Transfers + Activities API 99.98% · 30 days Operational
Payments (adivaha Pay) 99.99% · 30 days Operational
Admin Dashboard 99.98% · 30 days Operational
Webhooks & Notifications 99.97% · 30 days Operational
Sandbox Environment 99.99% · 30 days Operational
Incident History

Recent incidents and maintenance

Full transparency on every degraded-service event in the last 90 days, including post-mortems and remediations.

2026-04-12 Minor

Brief Hotel API supplier latency (Hotelbeds)

Elevated response times observed on Hotelbeds upstream for ~22 minutes. Failover to secondary supplier kept bookings flowing. Resolved at 14:48 UTC.

2026-03-04 Maintenance

Sandbox environment scheduled maintenance

Sandbox keys were rotated as part of quarterly security review. Production was unaffected. 35-minute window completed on schedule.

2026-02-18 Minor

Card-payment partner outage (3rd-party)

One regional card processor experienced a 14-minute incident. Auto-failover to alternate processor handled retries; no booking failures recorded.

Need historical data? Contact us for a downloadable incident log spanning the last 12 months.