Status Page Must Match the Send Pause

Status Page Must Match the Send Pause.

Aligning Platform State with Public Status

When an operational incident forces an administrator to pause live traffic, the public status page must immediately reflect this state. Keeping the status indicator green while outbound SMS or OTP delivery is paused creates immediate distrust among API consumers. In the IOSOR console, any manual or automated pause of routing profiles must trigger an API call to update the status page.

Triggering the Automated Status Update

To prevent human error, the pause action must be coupled with status page automation. When the outbound queue is suspended, the system must transition the corresponding service (such as E.164 SMS routing or Verify OK endpoints) to 'Degraded' or 'Major Outage'. This prevents developers from debugging their own webhook integrations when the issue lies entirely within the paused delivery path.

Ledger Holds and Prepaid Balance Controls

During a send pause, the platform manages financial transactions strictly. IOSOR operates on a prepaid model where a USD 20 prepaid floor is required to keep active routes open. If a pause occurs, active JIT number assignments and MRC calculations are held to prevent unfair billing. For high-volume accounts, especially those approaching a soft review near USD 1,000/month, the system automatically halts balance deductions for failed DLR sequences during the incident window.

Webhook Alerts and DLR Discrepancy Audits

When traffic is paused, the platform generates specific DLR codes indicating a temporary administrative hold. Clients monitoring their integrations via webhook will receive immediate payloads with custom error states rather than generic timeouts. This allows client-side logic to queue messages or trigger fallback paths instead of repeatedly hitting the paused API.

Incident Resolution and Related Resources

Resolving a status mismatch requires auditing the synchronization scripts between the core routing engine and the public status dashboard. Ensure that any STOP command handling or route freeze is reflected in real-time.

Related: Buyer Incident Language vs Internal Smoke Signals · Handling Active Traffic with a Stale Webhook Heartbeat · Prepaid hold before first debit.

Start with IOSOR

Access the IOSOR console to verify the synchronization between your routing gate and the public status dashboard. Ensure that any manual pause command initiated in the delivery queue triggers an immediate API call to update the service state. Monitor the DLR logs to confirm that administrative holds are reflected as 'Degraded' rather than generic system errors.

IOSOR takeaway

This article proved that operational transparency is the foundation of API reliability. A green status page during a manual traffic pause is a failure of communication that leads to wasted client resources and integration errors.

Do automate the transition to 'Major Outage' or 'Degraded' whenever a routing freeze is active. Don't allow the public dashboard to remain 'Healthy' if the outbound SMS or OTP delivery is intentionally suspended by the platform administrator.