How we notify you
If an incident affects a service you use, your account manager and our support team notify affected customers directly by email, with updates through to resolution.
Contact supportService status & reliability
BroadNet platform status
No incidents are posted. The reachability checks below are measured: synthetic probes from our web host test the website, developer docs and public API endpoints every 5 minutes. They are not the messaging platform's internal delivery status — a live platform status feed is coming. The contractual figure is the 99.99% uptime SLA.
INCIDENTS · NONE POSTED·SYNTHETIC CHECKS · 2 of 7 up·LAST CHECK · Oct 21, 2026, 10:15 AM UTC·SLA · 99.99%·CARRIER-GRADE SINCE · 2003
Website & public API reachability
Measured by synthetic checks from our web host — not the messaging platform's internal delivery status.
Each check is an outside-in HTTPS request with a 5-second timeout, run every 5 minutes. No credentials are used and no messages are sent: the API check only confirms a valid TLS certificate and the expected 401 refusal of an unauthenticated request. Uptime is the share of passed checks among the samples stored in each window — nothing is estimated or back-filled.
Collecting data since Oct 2, 2026, 12:55 AM UTC. Windows longer than that cover only the samples collected so far.
All checks passedSome checks failedAll checks failedNo samples
Messaging platform status
Coming soonPlatform status feed: coming soon. A live feed from the messaging platform's own monitoring is being built by our platform team. Until it is published, this page shows no component states or uptime figures for these services. Incidents that affect them are posted in the incident history below, and affected customers are notified directly.
The feed will cover
Messaging channels
- SMS API — Application-to-person SMS over operator-direct routes.
- SMPP Gateway — SMPP 3.4 binds for high-volume enterprise senders.
- WhatsApp Business — Template, session and interactive WhatsApp messaging.
- RCS Business Messaging — Verified-sender rich messaging and suggested replies.
- Voice & OTP — Voice calls, IVR and one-time-passcode delivery.
Platform & APIs
- HLR Lookup — Real-time number lookup and portability checks.
- Customer Dashboard — Account, analytics, billing and routing controls.
- Webhooks & DLR Callbacks — Outbound delivery receipts and inbound callbacks.
Incident history
Incidents and their resolution over the last 90 days.
No incidents reported in the last 90 days
When an incident affects a service you use, it appears here with a timeline of updates through to resolution — and affected customers are notified directly.
Subscribe to status updates
Get notified about incidents and scheduled maintenance by email, or follow the RSS feed. Enterprise customers are also kept informed directly by their account manager.
Incident communication
We keep incident communication direct and human. Here is how you hear from us, and how to reach us.
Your account manager
Every enterprise account has a named account manager as a direct point of contact for escalations, questions and incident updates — not an anonymous queue.
Talk to your teamReport or check an issue
Seeing something that looks like a problem? Reach our support team any time. We will confirm whether it is a known issue and keep you posted.
Get helpScheduled maintenance
Planned maintenance is announced in advance to affected customers. We schedule work in low-traffic windows and design changes to be non-disruptive wherever possible — using redundant routing so traffic fails over rather than pauses. If a window could affect your traffic, your account manager will let you know ahead of time with the expected impact.
No maintenance currently scheduled
- Advance notice to affected customers
- Low-traffic windows
- Redundant routing keeps traffic flowing
- Expected impact stated up front
Questions buyers ask
Status questions, answered.
Production API endpoints carry a 99.99% uptime SLA, with service credits for breaches and higher premium tiers available under custom contract.
Customers affected by an incident are notified directly, and enterprise customers also hear from their account manager. Incidents are listed on this page once posted, with a root-cause summary after resolution, and the RSS feed carries the same updates.
The machine-readable feed is at /status/rss.xml — subscribe to receive component-health changes and incident updates automatically.
Yes, but only for what our web host can check from the outside. The website and public API reachability section is measured by synthetic checks every 5 minutes, and its uptime percentages are computed only from stored samples — nothing is estimated or back-filled. It is not the messaging platform's internal delivery status: a live platform status feed is being built by our platform team. The contractual commitment is the 99.99% uptime SLA on production API endpoints.
Question not here? Ask our engineering team
Evaluating BroadNet for a production workload?
Our Trust Center covers security, compliance, data handling and the certifications behind the platform.