Platform status and incidents

Check Infobip platform health on the public status page, which tracks incidents and maintenance per service and location in real time. For automated reachability checks, a lightweight API status endpoint is also available. For network-level issues originating outside the Infobip platform (operator or MNO outages), see Operator connectivity status.

Incident status page

The status.infobip.com(opens in new tab) page contains information about ongoing and past incidents on the Infobip platform. It also shows active or upcoming maintenance that may affect service performance.

SSL certificate changes are announced on the status page at least 60 days in advance. For details, see REST API traffic encryption. Network delivery degradations and planned operator maintenance are not available on the Infobip Status page. See Operator connectivity status for those.

Status page sections [#status-page-sections-incident-status-page]

The status page is divided into three main sections:

• Applications: All applications and services accessible through the Infobip web interface
• Channels: Communication channels in the Infobip portfolio. Some channels are grouped together.
• Interface/API: Connection points of Infobip data centers where requests and traffic are submitted. Each location under Interface/API represents a different data center with its unique connection points, visible under the question mark (?) icon. If an incident is listed, the data center location is indicated in the subject for easier identification of impact.

Each specific service under any main section is mapped to the locations (data centers) where it is deployed. Availability information (incidents, maintenance) is shown per combination of service and location.

Component status indicators [#component-status-indicators-incident-status-page]

The status page uses the following component status indicators:

Incident status levels [#incident-status-levels-incident-status-page]

When an incident occurs, it progresses through the following stages:

An active incident or maintenance is always displayed prominently on the page. The status and color of the affected location update under the corresponding service. For example, a web interface outage in the Germany data center appears as Applications > Customer Portal Signup/Login > Global (Germany) > Major outage.

Subscribe to alerts [#subscribe-to-alerts-incident-status-page]

Subscribe directly from status.infobip.com(opens in new tab) to receive updates for specific combinations of service and location through:

• Email notifications
• Slack notifications
• Webhook URL integration
• Atom or RSS feed

For email subscriptions, enter your email address, and select the services and the location (data center) you use. Then confirm through the confirmation email you receive.

Subscribe to the combination of service and location (data center) you use. The following are examples:

• SMS to the Indonesia data center (api-id.infobip.com): Subscribe to the Indonesia location under SMS channel and the HTTP API component of Interface/API
• Germany-based web interface (portal.infobip.com): Subscribe to Global (Germany) under Customer Portal Signup/Login and any other UI services you use
• SMS traffic to US data centers (smpp-us2.infobip.com): Subscribe to United States under SMS channel and the SMPP component of Interface/API
• WhatsApp for Business in India: Subscribe to India under the WhatsApp Business channel

To report an issue, or if you cannot find an active incident related to your problem, use the Contact support button on the status page. It opens a ticket with Support.

Previous incidents and maintenance [#previous-incidents-and-maintenance-incident-status-page]

Previous incidents and maintenance activities are listed under Past Incidents in chronological order, from latest to oldest. Select the title of a specific event to access all details, progress updates, and affected components.

The full incident history(opens in new tab) is accessible through Incident History on the status page.

Incident management

An incident is any unexpected disruption, service degradation, or decline in the quality of the Infobip platform and services. Incidents can range from minor issues (such as a product feature not working as intended) to complete platform outages. Infobip handles incidents in defined stages, from detection to resolution and, on request, root cause analysis.

How Infobip handles an incident [#how-infobip-handles-an-incident-incident-management]

Infobip monitors the platform continuously using automated tooling, internal checks, and customer reports. Incident management has three stages:

1. Identification: Detect incidents using monitoring tools, internal discovery, or customer feedback.
2. Intervention: Restore the functionality of affected services.
3. Review: Document the incident to support learning and future improvements.

A detected incident is assigned a severity, escalated to the responsible engineering team, and mitigated to restore service as quickly as possible. Once service is stable, Infobip works on a permanent fix for the root cause.

Maintenance types [#maintenance-types-incident-management]

Infobip performs the following maintenance types:

What to expect during an incident [#what-to-expect-during-an-incident-incident-management]

When an incident is detected, Infobip performs an initial impact assessment. It covers the affected locations (data centers or regions), channels (SMS, RCS, WhatsApp), and products or interfaces (Inbox, HTTP API, SMPP).

Infobip Support monitors the incident and publishes a status page notification. The initial notification is typically issued within 15 minutes and includes:

• Location of affected products and channels
• Affected channels and products or interfaces
• A brief description of the known impact

Updates follow as more information becomes available. Once resolved, the status page is updated and the incident is moved to the history log.

Root cause analysis [#root-cause-analysis-incident-management]

For major incidents that originate on the Infobip platform, Infobip produces a root cause analysis (RCA). The RCA describes the impact, the contributing causes, and the corrective and preventive actions taken.

For other incidents, Infobip decides case by case, based on factors such as the duration of the incident and its impact.

To request an RCA for an incident that affected your account, contact Support or your account manager.

API status endpoint

For automated reachability checks, Infobip exposes a lightweight health-check endpoint at api.infobip.com/status. Use it to verify general API availability from your own infrastructure.

A healthy response returns HTTP 200 with the body "OK". The response is JSON by default. To get XML, set the Accept: application/xml header.