Skip to content

Email rates

This document describes the end-to-end performance characteristics of large-scale email execution, including: * Internal activity processing and batching

  • Email provider throughput

  • Performance Summary

  • Key assumptions and limiting factors

Internal activity processing and batching

To ensure stable performance across multiple campaigns, email audiences are processed in controlled batches. The current default processing rate is 1,000 email recipients per second.

Email provider throughput

Under peak conditions, the provider can handle up to 33,000 requests per second, with each request including 1,000 recipients. However, the standard operating rate is 4,000 requests per second, which corresponds to a total throughput of 4,000,000 recipients per second. This refers to the rate at which the provider can accept inbound email send requests from our platform and enqueue them into its outbound delivery infrastructure.

In addition to high throughput capacity, the provider reports an average delivery time of approximately 2 seconds. This represents the typical time between:

  1. The provider accepting the API request, and

  2. The email being handed off to (and acknowledged by) the recipient’s mail server.

Performance Summary

Metric Value
Internal processing rate 1,000 recipients/sec
Provider intake capacity 4,000,000 recipients/sec
Average delivery time ~2 seconds
1M emails ~16–20 minutes
2.5M emails ~42 minutes

ℹ️ Note: The estimated duration for sending 1M or 2.5M emails represents the time required for Lobyco and the email provider to process the audience, submit the send requests, and hand off the emails to recipient mail servers (e.g., Gmail, Outlook, etc.). It does not represent the time at which recipients will actually see the email in their inbox, as final delivery timing depends on downstream email services and their individual processing, filtering, and queuing mechanisms.

Key assumptions and limiting factors

  • Standard HTML emails

  • No large attachments

  • Proper IP/domain warmup

  • Clean recipient database