Exotel Outage History

Exotel major outage View live status →

Pingoru has recorded 5 incidents for Exotel: 5 in the last 12 months and 0 in the last 90 days.

Source: status.exotel.com

5incidents recorded
5last 12 months
0last 90 days
107 minutestypical duration

Incidents, newest first

Minor June 23, 2026 Intermittent elevated incoming-call failures — Mumbai – Mumbai

Started Jun 23, 2026, 12:00 AM UTC· resolved Jun 23, 2026, 12:00 AM UTC

  1. resolved Jun 23, 2026, 12:00 AM UTC

    Incoming calls in the Mumbai region experienced brief intermittent failures over Jun 22–23 IST. Resolved; service operating normally.

Read the full incident report →

Minor June 22, 2026 Intermittent elevated outgoing-call failures — Karnataka 8h 40m Karnataka

Started Jun 22, 2026, 09:30 PM UTC· resolved Jun 23, 2026, 06:10 AM UTC

  1. resolved Jun 23, 2026, 12:00 AM UTC

    Between ~03:00 and 11:40 IST, outgoing calls in the Karnataka region saw intermittent elevated failure rates. Service recovered and monitoring confirmed normal operation.

Read the full incident report →

Minor June 22, 2026 Brief international voice degradation 15m International

Started Jun 22, 2026, 09:05 AM UTC· resolved Jun 22, 2026, 09:20 AM UTC

  1. resolved Jun 22, 2026, 12:00 AM UTC

    Brief degraded performance on international voice routes on Jun 22 (~14:35–14:50 IST). Resolved.

Read the full incident report →

Minor June 22, 2026 Brief elevated outgoing-call failures — Andhra Pradesh – Andhra Pradesh

Started Jun 22, 2026, 12:00 AM UTC· resolved Jun 22, 2026, 12:00 AM UTC

  1. resolved Jun 22, 2026, 12:00 AM UTC

    A brief period of elevated outgoing-call failures in Andhra Pradesh on Jun 22 (~13:37 IST). Resolved within minutes.

Read the full incident report →

Minor June 22, 2026 Brief elevated incoming-call failures — Karnataka – Karnataka

Started Jun 22, 2026, 12:00 AM UTC· resolved Jun 22, 2026, 12:00 AM UTC

  1. resolved Jun 22, 2026, 12:00 AM UTC

    A brief period of elevated incoming-call failures in Karnataka on Jun 22 (~12:50 IST). Resolved within minutes.

Read the full incident report →