IOSOR
LearnSign InConnection applicationRestore Access
  1. IOSOR
  2. /Knowledge hub
  3. /Incidents & status

Incidents & status

Buyer-facing incident language you can publish — not internal smoke-test signals.

3 guides in this topic

  • Status Page Must Match the Send Pause

    Learn how to automatically align your public status page with active send pauses in IOSOR to maintain trust and prevent unnecessary API retries.

  • Handling Active Traffic with a Stale Webhook Heartbeat

    Learn how to manage active SMS and OTP traffic when your webhook heartbeat goes stale, avoiding false positive failovers on the IOSOR platform.

  • Buyer Incident Language vs Internal Smoke Signals

    Learn how to translate internal CPaaS telemetry and stale heartbeats into clear, buyer-facing traffic_ok status updates without exposing raw infrastructure logs.

Adjacent topics

  • Launch readiness
  • Trust & AI clarity

Not this hub: Observability & ops signals

Ready for a controlled prepaid path?

Tell us destinations, monthly volume, and compliance constraints. We will map onboarding clearly.

Apply for access
AboutKnowledge hubSite mapnFADP Privacy PolicyGDPR ComplianceTerms of ServiceSLA AgreementB2B Master AgreementApply for access

English is the sole legally binding language of IOSOR legal documents. Summaries in other languages are for convenience only.

© 2026 IOSOR · All rights reserved.🇨🇭 Switzerland