International
The Morning Dev

Only the news worth knowing

‹
 

Outage · High impact

The column nobody monitored: how a 32-bit integer stopped Clickpost's orders for 54 minutes

DEV · By Kashif Manzer ·

The Brief

  • On 2 November 2026, just after 4 pm India time, Clickpost's order creation API began returning HTTP 5xx server errors.
  • Orders for 91 carriers went through normally, while orders for all other carriers failed.
  • The outage was caused by a 32-bit integer overflow and lasted 54 minutes.

Why it matters

A 32-bit integer limit in an unmonitored column halted order creation for most carriers, showing how a single data type limit can take down a core workflow.

Who’s affected

  • Clickpost API integrators
  • Teams sending orders to carriers through Clickpost
  • #outage
  • #integer-overflow
  • #order-management
  • #api
  • #postmortem

Monday 2 November 2026, just after four in the afternoon, India time. Clickpost's order creation API started returning server errors. Not for every order. Orders for 91 carriers went through as normal. Orders for every other carrier failed with HTTP 5xx errors, the code a server…

Timeline

  1. Order creation API begins returning HTTP 5xx errors for orders to most carriers

  2. DEV Community: backend

    The column nobody monitored: how a 32-bit integer stopped Clickpost's orders for 54 minutes

How do you feel about this?

0 Comments