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

Source: [DEV Community: backend](https://dev.to/kashif_manzer/the-column-nobody-monitored-how-a-32-bit-integer-stopped-clickposts-orders-for-54-minutes-24gf) · 2026-11-22 · Backend
Page: https://themorning.dev/story/the-column-nobody-monitored-how-a-32-bit-integer-stopped-clickpost-s-orders-for-aa7c55d6d6d6d2e6
Kind: outage · Impact: high

## In 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.

## Timeline

- 2026-11-02: Order creation API begins returning HTTP 5xx errors for orders to most carriers

## Coverage

- [The column nobody monitored: how a 32-bit integer stopped Clickpost's orders for 54 minutes](https://dev.to/kashif_manzer/the-column-nobody-monitored-how-a-32-bit-integer-stopped-clickposts-orders-for-54-minutes-24gf) — DEV Community: backend, 2026-11-22

Tags: outage, integer-overflow, order-management, api, postmortem

---

Brief generated by AI (claude-haiku-5-5) from the reporting listed under Coverage. Headlines belong to their publishers. The Morning Dev – https://themorning.dev
