We started checking Infobip on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Infobip reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Infobip's own status page declared. Below it, any public chatter we saw about Infobip and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Infobip's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Infobip in the last 24 hours, which is not evidence that nothing is wrong.
Infobip's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Infobip's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Infobip next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Confirmation probe15:11 UTC, Asia-Pacific: our own first failed reading prompted an extra probe. Result: Infobip answered normally.
Confirmation probe08:37 UTC, Asia-Pacific: our own first failed reading prompted an extra probe. Result: Infobip answered normally.
Confirmation probe05:32 UTC, Asia-Pacific: our own first failed reading prompted an extra probe. Result: Infobip answered normally.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
450
US-West
99.71%
350
Europe
100.00%
320
Asia-Pacific
98.48%
198
Their declared record
Infobip's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Indonesia - Issues with file processing in multiple servicesPartial outage
Nov 4, 2026, 11:23 AM UTC to Nov 4, 2026, 11:23 AM UTC (0 min)resolved
their latest update (Nov 4, 2026, 11:23 AM UTC): We experienced an incident on our platform affecting multiple services on our Indonesia data center.
During the incident timeframe, you may have observed difficulty uploading, downloading and deleting files utilized in Voice, Moments, Conversations, Email, WhatsApp and Viber ser…
Pakistan - General connectivity degradationMinor incident
Nov 4, 2026, 10:21 AM UTC to Nov 4, 2026, 10:43 AM UTC (22 min)resolved
their latest update (Nov 4, 2026, 10:43 AM UTC): This is to inform you that the issue is no longer present as the affected services recover to their full functionality. It was concluded that the cause of the issue was networking and connectivity issues.
Start (UTC): 04 November 2026 09:37
End (UTC): 04 November 2026 10:23
United States - MMS service degradationMinor incident
Nov 3, 2026, 2:26 PM UTC to Nov 3, 2026, 6:40 PM UTC (4h 14m)resolved
their latest update (Nov 3, 2026, 6:40 PM UTC): The issue affecting the MMS service has been resolved. We're no longer observing errors affecting request processing.
During the affected period, you may have experienced submission timeouts and rejections when using /api/mm7 and /mms/v2/send endpoints.
Start (UTC): 03 November …
Multiple Locations - Salesforce Marketing Cloud Service DegradationMinor incident
Nov 2, 2026, 2:48 PM UTC to Nov 2, 2026, 3:43 PM UTC (56 min)resolved
their latest update (Nov 2, 2026, 3:43 PM UTC): The issue affecting the Salesforce Marketing Cloud integration has been resolved. During the incident, you may have experienced issues with creating new Journeys; message delivery for existing journeys was not affected.
Start (UTC): 02 November 14:28
End (UTC): 02 November 15:35…
Global (Europe) - Partial Packet LossMinor incident
Oct 31, 2026, 4:05 AM UTC to Oct 31, 2026, 4:13 AM UTC (8 min)resolved
their latest update (Oct 31, 2026, 4:13 AM UTC): The issue causing intermittent packet loss in our Global (Europe) data centre has been resolved. Email and SMS products have returned to normal, and service performance has recovered.
Start time (UTC): 31 October 2026 02:34
End time (UTC): 31 October 2026 04:00
Global (Europe) - Zalo service degradationMinor incident
Oct 29, 2026, 1:53 PM UTC to Oct 29, 2026, 3:03 PM UTC (1h 9m)resolved
their latest update (Oct 29, 2026, 3:03 PM UTC): The issue has been successfully resolved and the service is once again operational.
During the below timeframe, you may have experienced processing delays for inbound Zalo traffic.
Start (UTC): 29 October 2026 06:10
End (UTC): 29 October 2026 15:02
Impact: Zalo inbound message p…
Oct 29, 2026, 1:50 AM UTC to Oct 29, 2026, 2:11 AM UTC (21 min)resolved
their latest update (Oct 29, 2026, 2:11 AM UTC): The incident affecting SMS and Zalo traffic has been resolved. During the incident, you may have experienced traffic processing issues.
Start time (UTC): 29 October 2026, 01:00
End time (UTC): 29 October 2026, 01:48
Impact: Traffic processing issues, and requests returned 5xx er…
United States - HTTP API DegradationMinor incident
Oct 28, 2026, 5:15 PM UTC to Oct 28, 2026, 5:42 PM UTC (27 min)resolved
their latest update (Oct 28, 2026, 5:42 PM UTC): This is to inform you that the degradation affecting our HTTP API services has been resolved. We're no longer observing errors affecting request processing.
During the affected period, customers may have experienced message submission issues when using the Messages API. Addition…
Global (Europe)- Conversations Slowness and ErrorsMinor incident
Oct 23, 2026, 4:14 PM UTC to Oct 23, 2026, 5:07 PM UTC (54 min)resolved
their latest update (Oct 23, 2026, 5:07 PM UTC): A noted Issue with connections through Cloudfare has caused slowness and issues on Conversations through our Global (Europe) DC. Our internal teams working on the issue have confirmed this has since then been stabilized.
Start time (UTC): 23-10-2026 16:04
End time (UTC): 23-10-2…
United States - Moments service degradationPartial outage
Oct 23, 2026, 9:50 AM UTC to Oct 23, 2026, 9:56 AM UTC (5 min)resolved
their latest update (Oct 23, 2026, 9:56 AM UTC): The issue has been successfully resolved and the service is once again operational.
During the below timeframe you may have observed processing delays for Flow events or traffic processed within Flows, and issues when attempting to launch new Flows.
Start (UTC): 23 October 2026 …
Showing the 10 most recent of 54 incidents Infobip has declared in the history we hold.
These entries are Infobip's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Infobip's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.