Infobip outage, 28 October 2026

United States - Messages-API degradation

Started
Resolved
28 Oct 2026, 17:42 UTC (after 27 min)
Impact
Minor
Affected
United States

Is this still happening?

No. Infobip marked this incident resolved on 28 Oct 2026, 17:42 UTC, 27 min after it began.

Right now: Infobip reports all systems operational. (as of 28 Oct, 18:47 UTC) Live Infobip status

Last update from Infobip

This is to inform you that the degradation affecting the Messages API service has been resolved. We're no longer observing errors when processing requests through the Messages API endpoint. Customers may have experienced HTTP 500 errors while submitting requests, which could have impacted message submission. Start (UTC): 28 October 2026 16:30 End (UTC): 28 October 2026 17:08 Impact: HTTP 500 errors and message submission issues affecting traffic sent through the Messages API endpoint.

28 Oct 2026, 17:42 UTC

Read the full incident on the official Infobip status page

Similar Infobip incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 5 min

    United States - Moments service degradation

  2. , resolved after 21 min

    United States - SMPP service degradation

  3. , resolved after 16 min

    United States - Multiple Service Degradation

  4. , resolved after 1 h 16 min

    Multiple Locations - Customer Portal Login Service Degradation

  5. , resolved

    Multiple Locations - Portal Payments Service Degradation

Other recent Infobip incidents

  1. Global (Europe)- Conversations Slowness and Errors

  2. Vietnam - General service degradation

  3. Smpp System down For Accounts Located In The Us Infrastructure.

  4. EU Region-locked - Multiple Service Degradation

  5. Colombia - Voice Service Distruption

  6. India - Degradation of Conversations Services

  7. Multiple Locations - Degradation Of SaaS, CPaaS and Broadcast Services

  8. Saudi Arabia - Customer Portal Services Degradation

All recorded Infobip incidents