Skip to main content
Infobip logo

Is Infobip Down?

No — Infobip is up

Reachable from all 8 checked regions

Average response time: 241ms

Last checked · checks run every 6 hours

Official status page: https://status.infobip.com

Components the vendor reports as affected: India Under Maintenance India Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Infobip fail from enough regions to rule out probe noise.

Infobip uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
223ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 56 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

56-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 39 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 31 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 31 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
265ms
DNS 219ms TCP 2ms TLS 11ms TTFB 249ms
iad
221ms
DNS 162ms TCP 1ms TLS 11ms TTFB 201ms
jnb
260ms
DNS 206ms TCP 0ms TLS 12ms TTFB 239ms
lax
152ms
DNS 97ms TCP 2ms TLS 10ms TTFB 136ms
lhr
136ms
DNS 79ms TCP 2ms TLS 11ms TTFB 117ms
nrt
298ms
DNS 257ms TCP 1ms TLS 8ms TTFB 286ms
ord
138ms
DNS 82ms TCP 1ms TLS 8ms TTFB 120ms
sin
465ms
DNS 389ms TCP 1ms TLS 17ms TTFB 448ms

What Infobip does

Infobip sends SMS, voice, email, WhatsApp, RCS, MMS and push messages through one set of APIs, and adds tools such as Moments for campaigns and Conversations for agent inboxes. Companies use it for one-time passcodes, delivery notifications and marketing in countries where local carrier connectivity matters more than a single global route.

What an outage looks like

Message submission returns errors from the HTTP API or SMPP, or messages are accepted and then sit without a delivery report. One-time passcodes arrive late enough that customers fail login before the code lands. Channels fail independently, so WhatsApp can be degraded while SMS is fine. The customer portal may not load, hiding logs while sending itself continues.

What to do about it

status.infobip.com is unusually granular: it lists SMS, Voice, Email, WhatsApp Business, RCS, MMS, Push, HTTP API, SMTP and SMPP, and reports many of them per region, including Global (Europe), Brazil and an EU region-locked entry. Find your channel and region rather than reading the banner. For passcodes, extend code validity before adding a fallback channel.

Is it down for everyone, or just you?

If this page says Infobip is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Infobip outage FAQ

Messages are accepted but never delivered. Is that an outage?
It can be. Acceptance means Infobip took the message; delivery depends on downstream carrier connectivity, which is what the per-channel components track. Look for delivery reports stalling rather than submission errors, and check the component for your channel and region. Carrier-side delays also happen with no Infobip incident at all, particularly on international routes.
Is WhatsApp affected when SMS is down?
Usually not. Infobip lists each channel as its own component, and they sit on different downstream connections, so SMS, WhatsApp, Voice, Email and RCS commonly fail independently. That is also why moving traffic to another channel can work during an incident. Confirm the alternative is healthy on the status page before switching, rather than assuming it is.
Our one-time passcodes are arriving late. What should we do?
Extend the validity window rather than letting users request codes repeatedly. Each retry sends another message, and when the backlog clears the customer receives several codes with only the newest valid, which produces more failed logins than it solves. If the delay runs long and another channel is healthy, offer that openly instead of sending a silent duplicate.
The Infobip portal will not load. Are our messages still sending?
Possibly. The portal applications and the sending channels are separate components, so the interface can be unavailable while the HTTP API and SMPP keep accepting traffic. Check your own send and delivery-report metrics rather than the portal during an incident. If both the portal and your API calls fail, the problem is broader than the interface.

How we measure this

  • We request Infobip's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Infobip publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Infobip goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required