---
title: "Comment by BridgeXAPI on \"The anatomy of SMS delivery: from request to carrier\" | Hashnode"
description: "One thing that became clear after writing this: Delivery itself is not the main problem. Timing is. You can have a perfectly “delivered” message that still fail"
url: "https://hashnode.com/posts/the-anatomy-of-sms-delivery-from-request-to-carrier/69d1bf646792e486f6ef1ffe/comment/69d82fabfa7251682e11b528"
---

[Discussion](https://hashnode.com/posts/the-anatomy-of-sms-delivery-from-request-to-carrier/69d1bf646792e486f6ef1ffe)

Comment [The anatomy of SMS delivery: from request to carrier](https://hashnode.com/posts/the-anatomy-of-sms-delivery-from-request-to-carrier/69d1bf646792e486f6ef1ffe)

[BridgeXAPI](https://hashnode.com/@bridgexapi)

[Apr 9](https://hashnode.com/posts/the-anatomy-of-sms-delivery-from-request-to-carrier/69d1bf646792e486f6ef1ffe/comment/69d82fabfa7251682e11b528)

One thing that became clear after writing this:

Delivery itself is not the main problem.

Timing is.

You can have a perfectly “delivered” message that still fails in practice — especially for OTP and time-sensitive flows.

I wrote a follow-up that focuses specifically on that layer:

how timing, routing and execution paths actually define reliability

[blog.bridgexapi.io/you-dont-control-sms-delivery-…](https://blog.bridgexapi.io/you-dont-control-sms-delivery-you-control-routing)
