Infobip Outage History

Started Feb 12, 2026, 02:08 AM UTC· resolved Feb 12, 2026, 03:19 AM UTC

1. investigating Feb 12, 2026, 02:08 AM UTC

   We are currently experiencing degradation with our Broadcast service. You might experience issues when uploading the recipient file and receiving the "Something went wrong while uploading the file. Please try again. " error. Our Team is investigating, and more updates will follow.

2. monitoring Feb 12, 2026, 02:52 AM UTC

   We are no longer observing new occurrences of file upload error. We are closely monitoring the situation with the engineering team as they work towards a resolution to ensure that the issue is entirely resolved.

3. resolved Feb 12, 2026, 03:19 AM UTC

   The incident has been resolved and the Broadcast service is again fully operational. During the specified timeframe, you may had experienced failure in uploading recipient file on Broadcast Start (UTC): 12 February 2026 02:00 End (UTC): 12 February 2026 02:43 Impact: Failure on uploading recipient file on Broadcast Service The disruption arose from unexpected events that occurred during the planned maintenance that was underway between 22:00 and 02:00 UTC (https://status.infobip.com/incidents/t56vylwddbbf) and continued affecting our services after the planned completion time. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Feb 05, 2026, 08:34 PM UTC· resolved Feb 05, 2026, 09:06 PM UTC

1. investigating Feb 05, 2026, 08:34 PM UTC

   We are currently experiencing issues with Conversations services. You might experience issues while using the portal and its services and receive errors while trying to access the Conversations

2. resolved Feb 05, 2026, 09:06 PM UTC

   This is to inform you that we experienced an incident that affected multiple services on our India, Indonesia and United States data centres. Our clients may have noticed issues while using the portal and its services and receive errors while trying to access the Conversations Start (UTC): 05 February 2026 12:03 End (UTC): 05 February 2026 20:44 Impact: During this period, you may have observed issues with accessing the Conversations service. We apologize for any inconvenience this may have caused. Our engineering team has resolved the issue, and our services are now fully operational.

Read the full incident report →

Started Feb 05, 2026, 11:13 AM UTC· resolved Feb 05, 2026, 11:13 AM UTC

1. resolved Feb 05, 2026, 11:13 AM UTC

   This is to inform you that we experienced an incident that affected multiple services on our India data center. Our clients may have noticed issues while sending SMS and WhatsApp messages over HTTP API endpoints and issues when logging in to Customer Portal. Start (UTC): 05 February 2026 10:33 End (UTC): 05 February 2026 10:52 Impact: During this period, you may have observed issues with utilizing HTTP API and Customer Portal. We apologize for any inconvenience this may have caused. Our team has resolved the issue, and our services are now fully operational.

Read the full incident report →

Started Feb 05, 2026, 09:07 AM UTC· resolved Feb 05, 2026, 09:07 AM UTC

1. resolved Feb 05, 2026, 09:07 AM UTC

   This is to inform you that we experienced an incident affecting Conversations and Answers services on our United States data center. Our clients may have observed delay with message processing in Conversations and Answers services. The issue has been resolved. Start (UTC): 05 February 2026 08:13 End (UTC): 05 February 2026 08:43 Impact: Message processing delay. We apologize for any inconvenience this may have caused. Our team has resolved the issue, and our services are now fully operational.

Read the full incident report →

Started Feb 05, 2026, 05:39 AM UTC· resolved Feb 05, 2026, 06:36 AM UTC

1. investigating Feb 05, 2026, 05:39 AM UTC

   We are currently experiencing issues with the India data center. You may encounter problems logging in to the portal, as well as sending SMS or voice traffic. The issue is currently under investigation, and more information will be shared in the next update.

2. investigating Feb 05, 2026, 06:17 AM UTC

   Our dedicated engineering teams continue to actively investigate the issue.

3. resolved Feb 05, 2026, 06:36 AM UTC

   This incident has been resolved. Start time (UTC): 5 February 2026, 04:30 End time (UTC): 5 February 2026, 05:50 Impact: Users may have experienced issues accessing the portal, and failures in message processing for SMS and voice traffic.

Read the full incident report →

Started Feb 02, 2026, 01:11 PM UTC· resolved Feb 02, 2026, 07:02 PM UTC

1. investigating Feb 02, 2026, 01:11 PM UTC

   We are currently experiencing issues with Customer Portal services. You might experience issues while using the portal and its services and receive errors while trying to login.

2. investigating Feb 02, 2026, 01:13 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 02, 2026, 01:38 PM UTC

   Our engineering team is actively investigating the issue and we will share additional updates as soon as new information becomes available.

4. investigating Feb 02, 2026, 02:08 PM UTC

   We are continuing to work on a fix for this issue and our engineering team is actively investigating. We will provide further updates as soon as new information becomes available.

5. identified Feb 02, 2026, 02:30 PM UTC

   The issue has been identified and a fix is being implemented.

6. identified Feb 02, 2026, 02:53 PM UTC

   We are continuing to work on the fix. Upon further investigation we can confirm that in addition to Customer Portal, the incident also affected overall traffic processing across multiple channels on the Global (Europe) data center that are reflected in the form of delays.

7. identified Feb 02, 2026, 05:13 PM UTC

   We are continuing to work on a fix for this issue.

8. monitoring Feb 02, 2026, 05:30 PM UTC

   A fix has been implemented and we are monitoring the results.

9. resolved Feb 02, 2026, 07:02 PM UTC

   Dear Customer, The issue that was affecting Customer Portal log-in, as well as overall traffic processing across multiple channels on the Global (Europe) data center, which resulted in delays and affected access to the portal’s white-label and Flows views, has now been resolved. The main platform degradation has been addressed; however, please note that some isolated cases may still persist. Our developer team is actively reviewing these individual cases, and we are committed to resolving any outstanding issues as quickly as possible. If you continue to experience any problems related to the impact outlined below and require urgent assistance, please reach out to our support team at [email protected] for manual support. Start (UTC): 02 February 2026, 12:58 End (UTC): 02 February 2026, 16:55 Impact: You may have experienced problems logging into the Portal, accessing whitelabeled URLs, visualizing Flows, or noticed delays in traffic processing across multiple channels on the Global (Europe) data center. Thank you for your understanding and patience.

Read the full incident report →

Started Jan 30, 2026, 11:41 AM UTC· resolved Jan 30, 2026, 12:05 PM UTC

1. investigating Jan 30, 2026, 11:41 AM UTC

   We are currently experiencing general issues over Global (Europe) data center. You may experience issues with campaign lists slowly loading, status update delays and campaign update and creation issues. Our Team is investigating and more update will follow.

2. identified Jan 30, 2026, 12:00 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Jan 30, 2026, 12:05 PM UTC

   The issue has been successfully resolved and the service is once again operational. Start (UTC): 30 January 2026 11:37 End (UTC): 30 January 2026 12:04 Impact: Campaign service slowness

Read the full incident report →

Started Jan 27, 2026, 12:27 PM UTC· resolved Jan 27, 2026, 01:18 PM UTC

1. investigating Jan 27, 2026, 12:27 PM UTC

   We are currently experiencing issues with AI assistant service over Global (Europe) data center. The issue is currently being investigated and more information will follow in the next update.

2. identified Jan 27, 2026, 01:01 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Jan 27, 2026, 01:18 PM UTC

   The issue has been successfully resolved and the service is once again operational. AI assistant and some helper AI tools were not working affecting the products and services that utilize them. Start (UTC): 27 January 10:47 End (UTC): 27 January 13:14 Impact: The issue affected Answers and Conversations services that use AI

Read the full incident report →

Started Jan 23, 2026, 10:01 AM UTC· resolved Jan 23, 2026, 10:06 AM UTC

1. investigating Jan 23, 2026, 10:01 AM UTC

   We are currently experiencing issues with the Conversation service over the EU (Region-locked) data center. You may experience Conversations failing to load. The issue is currently being investigated, and more information will follow in the next update.

2. resolved Jan 23, 2026, 10:06 AM UTC

   Our team identified the issue, and the fix has been deployed. Service is now fully operational. Start (UTC): 23-01-2026 09:37 End (UTC): 23-01-2026 09:59 Impact: Loading of Conversations service

Read the full incident report →

Started Jan 22, 2026, 02:22 AM UTC· resolved Jan 22, 2026, 03:39 AM UTC

1. investigating Jan 22, 2026, 02:22 AM UTC

   We’re currently experiencing delays in processing RCS, WhatsApp, Viber, and Zalo traffic in our global (Europe) data center. The full scope of the issue is still under investigation, and we’ll provide more details in the next update.

2. investigating Jan 22, 2026, 02:25 AM UTC

   We are continuing to investigate this issue.

3. resolved Jan 22, 2026, 03:39 AM UTC

   The issue has been successfully resolved, and the service is once again operational. Messages are now being processed in a timely manner. Start (UTC): 22 January 2026 00:13 End (UTC): 22 January 2026 00:43 Impact: Delays in message processing.

Read the full incident report →

Started Jan 19, 2026, 03:41 PM UTC· resolved Jan 19, 2026, 04:53 PM UTC

1. investigating Jan 19, 2026, 03:41 PM UTC

   We are currently encountering delays in processing WhatsApp traffic over our global (Europe) data center. The scope of the issue is currently being investigated and more information will follow in the next update.

2. monitoring Jan 19, 2026, 04:17 PM UTC

   We have successfully identified and isolated the issue, and currently, the enqueued messages are being processed. We are monitoring the results.

3. resolved Jan 19, 2026, 04:53 PM UTC

   The issue has been successfully resolved and the service is once again operational. Start (UTC): 19 January 06:58 End (UTC): 19 January 16:15 Impact: You might have experienced delays in WhatsApp outbound messages delivery.

Read the full incident report →

Started Jan 14, 2026, 12:29 PM UTC· resolved Jan 14, 2026, 01:33 PM UTC

1. investigating Jan 14, 2026, 12:29 PM UTC

   We are currently experiencing general issues over Pakistan data center. The scope of the issue is currently being investigated and more information will follow in the next update.

2. identified Jan 14, 2026, 01:23 PM UTC

   The root cause of the issue has been identified and we are working towards resolution. More information to follow in the next update.

3. resolved Jan 14, 2026, 01:33 PM UTC

   The issue has been successfully resolved and the service is once again operational. The issue was caused by a network issue thus affecting all services. Start (UTC): 14 January 12:18 End (UTC): 14 January 13:16 Impact: Network issue affecting all services.

Read the full incident report →

Started Jan 07, 2026, 08:04 PM UTC· resolved Jan 07, 2026, 08:04 PM UTC

1. investigating Jan 07, 2026, 06:16 PM UTC

   We are experiencing a degradation with our Number registration service over Portal and API . You may experience delays over the web interface when checking Brands and Campaigns and 500 error response over the API request. Our dedicated team is working on the resolution and we will keep you informed of any updates.

2. investigating Jan 07, 2026, 07:14 PM UTC

   We are continuing to investigate this issue, taking steps to address it, and will update you as soon as we have more information.

3. resolved Jan 07, 2026, 08:04 PM UTC

   The issue has been resolved, and the service is now operational. Start (UTC): 07 January 2026, 09:35 End (UTC): 07 January 2026, 19:18 Impact: During this period, you may experience delays in the web interface when checking Brands and Campaigns, as well as 500 error responses from the API.

Read the full incident report →

Started Dec 30, 2025, 09:13 PM UTC· resolved Dec 30, 2025, 09:13 PM UTC

1. resolved Dec 30, 2025, 09:13 PM UTC

   We experienced a degradation in our Global Europe data center that affected WhatsApp Templates functionality, which caused issues when consulting WhatsApp templates During this period, you may have experienced errors or delays while checking WhatsApp Templates over Portal, and 5xx errors while calling the "/whatsapp/2/senders/{sender}/templates" endpoint via API. We apologize for any inconvenience this may have caused. Our team has resolved the issue, and our services are now fully operational. Start (UTC): 30-12-2025 19:45 End (UTC): 30-12-2025 20:52

Read the full incident report →

Started Dec 24, 2025, 11:35 AM UTC· resolved Dec 24, 2025, 07:59 PM UTC

1. investigating Dec 24, 2025, 11:35 AM UTC

   We are experiencing service degradation affecting email functionality in the Indonesia data center. Some users may notice latency or timeouts when loading email-related content. Our engineering team is investigating the issue, and we will keep you posted with further findings.

2. identified Dec 24, 2025, 01:15 PM UTC

   Our engineering team has identified the issue and is continuing to investigate. Please note that this degradation currently affects broadcasts only. We will provide further updates as soon as new information becomes available.

3. identified Dec 24, 2025, 05:18 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Dec 24, 2025, 07:59 PM UTC

   The issue has been successfully resolved and the service is once again operational. During the specified timeframe, you may have observed issues using Broadcasts services and campaigns. Start (UTC): 24 December 10:25 End (UTC): 24 December 19:30 Impact: Broadcast service issues

Read the full incident report →

Started Dec 23, 2025, 11:34 AM UTC· resolved Dec 23, 2025, 11:34 AM UTC

1. resolved Dec 23, 2025, 11:34 AM UTC

   This is to inform you that we have experienced issues with our API service on the India data centre. Start (UTC): 23 December 2025 08:30 End (UTC): 23 December 2025 09:48 Impact: We experienced increased latency when processing requests, and some requests timed out. The issue has been successfully resolved, and all services are now fully operational. We sincerely apologise for any inconvenience this may have caused. Thank you for your understanding.

Read the full incident report →

Started Dec 20, 2025, 01:23 PM UTC· resolved Dec 20, 2025, 01:23 PM UTC

1. resolved Dec 20, 2025, 01:23 PM UTC

   This is to inform you that we experienced a service degradation affecting Email, Facebook Messenger, Mobile push and In-app messages, OMNI, RCS, SMS, Voice and Whatsapp messages in the Turkey data center. Also, our clients might have encountered issues while logging in to Customer Portal and using HTTP API endpoints. Incident has been resolved. Start (UTC): 20 December 2025 12:33 End (UTC): 20 December 2025 12:41 Impact: During this period, due to intermittent networking issues, our clients might have encountered issues while using multiple services, Customer Portal and HTTP API endpoints. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Dec 19, 2025, 12:43 PM UTC· resolved Dec 19, 2025, 01:28 PM UTC

1. investigating Dec 19, 2025, 12:43 PM UTC

   We are currently experiencing issues with WhatsApp templates API over Global (Europe) data center. The issue is currently being investigated and more information will follow in the next update.

2. resolved Dec 19, 2025, 01:28 PM UTC

   The issue has been successfully resolved and the service is once again operational. The issue affected specific WhatsApp templates endpoint. Start (UTC): 19 December 12:16 End (UTC): 19 December 13:07 Impact: The endpoint /whatsapp/2/senders/(sender)/templates reverted error 500

Read the full incident report →

Started Dec 17, 2025, 01:25 PM UTC· resolved Dec 17, 2025, 01:25 PM UTC

1. resolved Dec 17, 2025, 01:25 PM UTC

   We experienced a degradation of our Broadcast service on Customer Portal. Our clients might have observed that file uploading within Broadcast service was failing. The service was returning an error "Something went wrong, please contact the support". Start (UTC): 17 December 2025 12:03 End (UTC): 17 December 2025 12:30 Impact: During this period, our clients could not use the File upload function within Broadcast service. We apologize for any inconvenience this may have caused. Our team has resolved the issue, and our services are now fully operational.

Read the full incident report →

Started Dec 16, 2025, 04:38 AM UTC· resolved Dec 16, 2025, 07:02 AM UTC

1. investigating Dec 16, 2025, 04:38 AM UTC

   We're currently experiencing degradation in our United States data center. You may experience slowness and issues while using the Voice, SIP Trunk, and SMPP related services. Our dedicated team is currently investigating, and we'll share more information in the next update.

2. investigating Dec 16, 2025, 04:41 AM UTC

   We are continuing to investigate this issue.

3. investigating Dec 16, 2025, 05:22 AM UTC

   We are continuing to monitor the situation and collaborating with the internal team to reach a resolution on a fix for this issue. We will keep you posted with any new updates.

4. investigating Dec 16, 2025, 06:25 AM UTC

   Our engineering team is monitoring the situation to reach a resolution on a fix for this issue. We will keep you posted with any new updates

5. resolved Dec 16, 2025, 07:02 AM UTC

   This incident has been resolved. Start time (UTC): 16 December 2025 02:04 End time (UTC): 16 December 2025 06:10 Impact: During the incident period, you may experience delays or undelivered Voice traffic, as well as intermittent SMPP connections.

Read the full incident report →

Started Dec 06, 2025, 09:31 AM UTC· resolved Dec 06, 2025, 09:31 AM UTC

1. resolved Dec 06, 2025, 09:31 AM UTC

   We had experienced issues affecting our WhatsApp service hosted at the Global (Europe) location. During the incident timeframe, WhatsApp outbound and inbound traffic may have experienced delayed processing, in some cases leading to expiry if messages had short validity period settings. The issues have since been resolved and WhatsApp traffic is no longer experiencing any delays. Start (UTC): 06 December 02:52 End (UTC): 06 December 08:22 Impact: WhatsApp processing delays

Read the full incident report →

Started Dec 01, 2025, 03:10 PM UTC· resolved Dec 01, 2025, 04:22 PM UTC

1. investigating Dec 01, 2025, 03:10 PM UTC

   We are currently verifying a degradation issue affecting Viber messages (MO attachments and media links). Investigations are ongoing as counter measure.

2. investigating Dec 01, 2025, 03:12 PM UTC

   We are continuing to investigate this issue.

3. identified Dec 01, 2025, 03:12 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Dec 01, 2025, 04:12 PM UTC

   We are no longer observing new occurrences of Viber messages (MO attachments and media links). Recent traffic indicates that media messages are being received and processed as expected. We are closely monitoring the situation with the engineering team as they work towards a resolution to ensure that the issue is entirely resolved.

5. resolved Dec 01, 2025, 04:22 PM UTC

   The noted incident which affected Viber Inbound messages with media has now been resolved. Start: 01 December 2025 12:49 UTC End: 01 December 2025 14:41 UTC

Read the full incident report →

Started Dec 01, 2025, 02:03 PM UTC· resolved Dec 01, 2025, 02:20 PM UTC

1. investigating Dec 01, 2025, 02:03 PM UTC

   We are currently observing a degradation affecting Viber messages with media (MOs with attachments and media links). We are actively investigating the issue.

2. identified Dec 01, 2025, 02:11 PM UTC

   The issue has been identified as originating on Viber’s side. We are in contact with their engineering team and are closely monitoring the situation while they work on a resolution.

3. resolved Dec 01, 2025, 02:20 PM UTC

   The incident affecting inbound Viber messages with media has been resolved. Start: 01 December 2025 13:12 UTC End: 01 December 2025 13:54 UTC

Read the full incident report →

Started Nov 24, 2025, 03:22 PM UTC· resolved Nov 24, 2025, 03:22 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →