CheckUpstream measured Infobip at 100.000% availability across 2025 independent checks (global · api). 55 incidents were recorded in the past 12 months; the most recent resolved 3 days ago after 58 minutes. Status signals are polled from Infobip's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2025 · p95 1036ms (30d)
Share of our own checks against Infobip endpoints that returned Infobip's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 16 incidents · 22 of 30 days with none posted · 7h 51m of declared impact
Fewer incidents in the last 30 days than 5% of 232 tracked services.
Share of each window with no impact declared by Infobip
7d
98.817%
30d
98.908%
90d
99.625%
180d
99.627%
1y
99.816%
Downtime like this can be refundable
If you're a paying Infobip customer, outages in these windows may count against Infobip's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Infobip entitlement →Does Infobip actually matter to you?
A Infobip outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 16 incidents Infobip published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Infobip takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 28, 11:57 UTC · resolved in 58m · Resolved
Aug 27, 16:10 UTC · resolved in 54m · Resolved
Aug 27, 16:10 UTC · resolved in 9m · Resolved
Live Infobip status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/infobip)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Infobip 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 3 days ago and lasted 58 minutes (degraded performance).
Looking for the live "is Infobip down" view? See the Infobip Live status page.
Aug 26, 11:41 UTC · resolved in 1h 18m · Resolved
Aug 14, 10:01 UTC · resolved in 48m · Resolved
Aug 13, 09:54 UTC · resolved in 1h 16m · Resolved
Aug 10, 11:36 UTC · resolved in 58m · Resolved
Aug 10, 10:13 UTC · resolved in 37m · Resolved
Aug 5, 08:18 UTC · resolved in 21m · Resolved
Aug 3, 12:46 UTC · resolved in 44m · Resolved
Jul 31, 18:31 UTC · resolved in 1h 3m · Resolved
Jul 23, 15:39 UTC · resolved in 21m · Resolved
Jul 16, 14:51 UTC · resolved in 3h 58m · Resolved
Jul 14, 20:55 UTC · resolved in 2h 45m · Resolved
Infobip's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Infobip endpoints. It is the share of checks that returned the expected response, not a figure taken from Infobip's status page.
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.