Transparency

EazyOTP delivery performance

Anonymous, aggregated SMS and WhatsApp OTP delivery statistics from EazyOTP production traffic, with the method used to calculate them. SMS and WhatsApp are always reported separately.

Report

Current report

Delivery performance report is being prepared.

We will publish SMS and WhatsApp delivery statistics here once they have been generated from validated production records using the method described below. No figures are shown until then.

Methodology

How the statistics are calculated

  • Delivery rate = delivered ÷ (delivered + failed + expired + undeliverable) × 100, using final (terminal) statuses only.
  • Pending and unknown results are not counted as delivered or failed; they are shown separately.
  • An API “success” response is not a delivery. It means the request was accepted. Only a delivery receipt (SMS) or delivered status (WhatsApp) counts as delivered.
  • Each message attempt is counted once. Duplicate status callbacks are ignored. A retry or a WhatsApp-to-SMS fallback is a separate attempt; fallback SMS is reported on its own line.
  • Delivered is not verified. Whether the user entered the code is known only to the customer’s application and is not part of these figures.
  • Excluded: sandbox and internal test messages.
  • Privacy: only aggregate counts are published – never phone numbers, OTPs, message content, customer names, IDs, IP addresses or message IDs. Country breakdowns with fewer than 100 attempts are suppressed.
  • Timezone: reporting days are UTC.

Historical reported delivery performance. Results vary by country, operator, network and messaging channel. These statistics do not guarantee future delivery.