How Corvane keeps message delivery visible during peak sending hours

Peak hours without surprises at Corvane

A pipeline that cannot slow down

Corvane sends marketing messages for retail brands, and most of that volume lands in a few hours around launches and sales. A gateway that adds two seconds of latency at the wrong time can delay millions of messages. The team needed to know about it before brands did.

Monitoring every hop

The platform team added Navy monitors to every public API, every carrier gateway and the webhook endpoints brands rely on. Keyword monitors check that responses contain a valid delivery receipt, not just a 200 status. Because an outage is confirmed from 3 regions before an alert goes out, the on-call engineer only gets paged when something is actually wrong.

A status page brands trust

Corvane now runs a public status page on its own domain. When an incident starts, the timeline is created automatically and updates go out to subscribers by email. Brands check the page first, which has cut the volume of support tickets during incidents by almost two thirds.

Today every new service at Corvane ships with Navy monitors defined in the same pull request. The team reviews response time charts in its weekly reliability meeting and writes a postmortem in Navy for every customer-facing incident.