PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Infobip is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Infobip. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Infobip issues today?

As of Sep 28, 2026 03:54 UTC, 0 users had reported issues with Infobip in the previous 24 hours.

How can I report a Infobip outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Social

Is Infobip down right now?

NormalOfficial status last polled Sep 28, 2026 03:38 UTCwww.infobip.com Official status page

A global cloud communications platform that enables businesses to build connected customer experiences.

Are you on the Infobip team and see something inaccurate? Report it to us. We respond within one business day.

Is Infobip down right now?

No. Infobip has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 03:54 UTC

Normal

Infobip is operating normally

As of Sep 28, 2026 03:54 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 19, 2026 16:14 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Infobip.

Incident days

No recorded incident

9h 57m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Infobip. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

2 incidents

Busiest day

9h 57m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Infobip outage on September 19 — 2h 19m disruption

Sep 19, 01:54 PM → Sep 19, 04:14 PM · 2h 19m · medium

An incident affecting Infobip services was detected by automated monitoring systems, including the vendor's own status page. The disruption began at 2026-09-19T13:54:59.299Z and was resolved at 2026-09-19T16:14:17.395Z.

Peak reports

in 15 min

Total reports

during outage

Duration

2h 19m

until recovery

Impact

This incident affected Infobip services for a duration of 2 hours and 19 minutes, from 2026-09-19T13:54:59.299Z to 2026-09-19T16:14:17.395Z. The severity of the disruption was classified as medium. This incident was detected through automated signals, and no user-reported data was collected.

Outage timeline

Sep 19, 01:54 PM
PulseWatch detected the incident from automated vendor and probe signals (medium severity)
Sep 19, 01:54 PM
Status updated: possible issue
Sep 19, 04:14 PM
Signals cleared — incident resolved

Official updates

Sep 19, 01:54 PM
Infobip status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.6%

90-day uptime

99.45%

Calculated from Infobip's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other social services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Infobip: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/19/2026, 1:54:59 PM · 2h 19m

01:54 PM04:14 PM

Detection9/19/2026, 1:54:59 PM · 8d ago

Detected — medium severity

ResolvedHigh

Infobip: the vendor reports a critical-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Infobip or have an alert rule on it can be alerted, labelled vendor-reported.

9/17/2026, 3:34:23 PM · 3h 44m

03:34 PM07:19 PM

Detection9/17/2026, 3:34:23 PM · 10d ago

Detected — high severity

ResolvedMedium