30 days uptime
99.428%
28 of 30 days clean · 4h 7m total downtime
All windows
Last resolved incident
1 day ago · lasted 37m · Minor
5/25/2026, 11:32:33 AM · resolved 5/25/2026, 12:10:12 PM · Resolved
5/22/2026, 10:06:40 AM · resolved 5/22/2026, 12:50:11 PM · Resolved
5/21/2026, 2:03:40 PM · resolved 5/22/2026, 4:15:37 AM · Resolved
5/18/2026, 12:32:40 PM · resolved 5/19/2026, 11:20:31 AM · Resolved
Official status page: https://status.infobip.com (opens in new tab)
Live status pill for Infobip. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=infobip"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/infobip" style="border:0;width:260px;height:44px" loading="lazy" title="Infobip status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/infobip)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/infobip/badge.svgInfobip is currently Operational. CheckUpstream tracks Infobip in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
Infobip's last resolved incident started 1 day ago and lasted 37 minutes (degraded performance).
Looking for the live "is Infobip down" view? See the Infobip Status page.
Infobip's 30-day customer-perceived uptime is 99.428%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add Infobip to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection — covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Infobip's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.