Infobip Outage History

Started Jul 14, 2026, 08:33 AM UTC· resolved Jul 14, 2026, 08:33 AM UTC

1. resolved Jul 14, 2026, 08:33 AM UTC

   We experienced a service degradation affecting RCS, SMS, and WhatsApp over API services in the India data center, which caused delays in traffic processing and intermittent 503 errors. Start (UTC): 14 July 2026 06:07 End (UTC): 14 July 2026 06:10 Impact: Delays in processing and intermittent 503 errors for RCS, SMS, and WhatsApp traffic over API services in the India data center. 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 Jul 09, 2026, 10:19 AM UTC· resolved Jul 09, 2026, 12:30 PM UTC

1. investigating Jul 09, 2026, 10:19 AM UTC

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

2. investigating Jul 09, 2026, 11:01 AM UTC

   The team is still investigating this issue. We'll continue sharing updates.

3. resolved Jul 09, 2026, 12:30 PM UTC

   The issue has been successfully resolved and the service is once again operational. Some sender might not have been able receive inbound messages. Start (UTC): 09 July 2026 08:22 End (UTC): 09 July 2026 11:49 Impact: Some sender might not have been able receive inbound messages.

Read the full incident report →

Started Jul 02, 2026, 07:39 PM UTC· resolved Jul 02, 2026, 08:35 PM UTC

1. investigating Jul 02, 2026, 07:39 PM UTC

   We are currently experiencing a general connectivity degradation at the Pakistan data center. Our clients may notice issues when using services hosted or routed through this location, including Portal access, Email, Voice, WhatsApp, Broadcast and People. The impact may include errors, degraded performance, pages not loading, or intermittent service availability. Our team is working with the relevant provider to resolve the issue. More details will be shared in the next update.

2. identified Jul 02, 2026, 08:10 PM UTC

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

3. monitoring Jul 02, 2026, 08:19 PM UTC

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

4. resolved Jul 02, 2026, 08:35 PM UTC

   The incident has been resolved. Start (UTC): 02 July 2026 13:03 End (UTC): 02 July 2026 19:54

Read the full incident report →

Started Jul 01, 2026, 05:09 AM UTC· resolved Jul 01, 2026, 05:49 AM UTC

1. investigating Jul 01, 2026, 05:09 AM UTC

   We are currently experiencing degraded performance affecting our Mobile Push Notifications service. You may experience issues sending push notifications through the API. Our team is actively investigating the issue and will provide further updates as soon as they become available.

2. monitoring Jul 01, 2026, 05:44 AM UTC

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

3. resolved Jul 01, 2026, 05:49 AM UTC

   The issue has been successfully resolved, and the service is once again fully operational. During the incident, you may have experienced issues in sending push notifications through API. Start time (UTC): 01-07-2026 03:33 End time (UTC): 01-07-2026 05:30 Impact: Clients are not able to send push notifications through API

Read the full incident report →

Started Jun 30, 2026, 09:10 AM UTC· resolved Jun 30, 2026, 09:40 AM UTC

1. investigating Jun 30, 2026, 09:10 AM UTC

   We are currently experiencing an issue with our SMPP service at India data center. Our clients may notice an issue with establishing SMPP bind. Our team is working on resolving the issue, more details will be shared in the next update.

2. investigating Jun 30, 2026, 09:29 AM UTC

   We are continuing to investigate this issue.

3. resolved Jun 30, 2026, 09:40 AM UTC

   The incident has been resolved. Start (UTC): 30 June 2026 07:10 End (UTC): 30 June 2026 09:37

Read the full incident report →

Started Jun 30, 2026, 07:47 AM UTC· resolved Jun 30, 2026, 08:01 AM UTC

1. investigating Jun 30, 2026, 07:47 AM UTC

   We are experiencing a degradation of our Customer Portal services. You may experience a blank page or an unexpected error being returned on portal pages. Our team is investigating the issue, and we will post further updates.

2. investigating Jun 30, 2026, 07:48 AM UTC

   We are continuing to investigate this issue.

3. resolved Jun 30, 2026, 08:01 AM UTC

   The issue has been successfully resolved, and the service is once again operational. During the incident, you may have experienced issues with portal access. Start (UTC): 30 June 2026 07:22 End (UTC): 30 June 2026 07:49 Impact: Customer portal access

Read the full incident report →

Started Jun 29, 2026, 03:00 PM UTC· resolved Jun 29, 2026, 03:00 PM UTC

1. investigating Jun 29, 2026, 02:51 PM UTC

   We are experiencing a degradation of our Customer portal services. You may experience issues while login in.

2. identified Jun 29, 2026, 02:52 PM UTC

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

3. monitoring Jun 29, 2026, 02:55 PM UTC

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

4. resolved Jun 29, 2026, 03:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 24, 2026, 01:10 PM UTC· resolved Jun 24, 2026, 05:04 PM UTC

1. investigating Jun 24, 2026, 01:10 PM UTC

   This is to inform you that we are currently experiencing degradation with our Moments service. You may observe delays with usage and processing of service. Our team is working on this and more updates will follow in the next update.

2. identified Jun 24, 2026, 01:30 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.

3. identified Jun 24, 2026, 01:48 PM UTC

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

4. identified Jun 24, 2026, 03:41 PM UTC

   We have identified the root cause of this incident, and our engineering team is actively working on a solution. Some messages processed during the incident window may experience delays and will be reprocessed once services are fully restored. We will provide further updates once the services have been confirmed to have recovered.

5. resolved Jun 24, 2026, 05:04 PM UTC

   The issue affecting Moments Services has been successfully resolved and the product is once again fully operational. Start: 21 June 2026 12:46 UTC End: 21 June 2026 16:37 UTC Impact: The incident caused a general degradation of the Moments service, resulting in delayed processing of messages and actions across all channels when used via Moments. Traffic outside of Moments was not affected. The issue has been fully resolved, all queued messages have been processed, and the system is now operating normally.

Read the full incident report →

Started Jun 21, 2026, 07:51 PM UTC· resolved Jun 21, 2026, 08:27 PM UTC

1. investigating Jun 21, 2026, 07:51 PM UTC

   We are experiencing a degradation of our Customer portal services. You may experience issues while login in.

2. monitoring Jun 21, 2026, 07:59 PM UTC

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

3. monitoring Jun 21, 2026, 08:08 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 21, 2026, 08:27 PM UTC

   The issue has been successfully resolved and the service is once again fully operational. We had experienced degradation of our Customer Portal in all of our Data Centers. Start: 21 June 2026 18:55 UTC End: 21 June 2026 19:53 UTC Impact: You may have experienced issue to log in the Customer Portal.

Read the full incident report →

Started Jun 18, 2026, 01:01 PM UTC· resolved Jun 18, 2026, 01:11 PM UTC

1. investigating Jun 18, 2026, 01:01 PM UTC

   We are currently experiencing issues with our Voice Service on Singapore data center. You may experience issues with calls failing. Our Team is already investigating and more updates will follow.

2. resolved Jun 18, 2026, 01:11 PM UTC

   The issue has been successfully resolved and the service is once again operational. Difficulties reaching our Voice service and failing calls could have been observed during the below-specified timeframe. Start (UTC): 18 June 2026 12:37 End (UTC): 18 June 2026 13:05 Impact: Voice calls processing disruption

Read the full incident report →

Started Jun 18, 2026, 07:45 AM UTC· resolved Jun 19, 2026, 12:50 PM UTC

1. investigating Jun 18, 2026, 07:45 AM UTC

   We are currently encountering delays in processing of WhatsApp traffic. Our dedicated team is already checking this and more updates will follow.

2. investigating Jun 18, 2026, 07:45 AM UTC

   We are continuing to investigate this issue.

3. investigating Jun 18, 2026, 08:10 AM UTC

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

4. identified Jun 18, 2026, 08:39 AM UTC

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

5. identified Jun 18, 2026, 09:37 AM 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.

6. monitoring Jun 18, 2026, 12:21 PM UTC

   Our dedicated team has deployed a fix and is currently monitoring the situation.

7. monitoring Jun 18, 2026, 02:38 PM UTC

   Our dedicated team has deployed a fix and remains actively engaged in monitoring the situation.

8. monitoring Jun 18, 2026, 07:53 PM UTC

   The delays and processing issues appear to have been resolved. Our teams are continuing to monitor the situation to ensure it is fully resolved.

9. monitoring Jun 19, 2026, 12:38 AM UTC

   Our team is continuing to monitor the situation to confirm it is completely resolved.

10. monitoring Jun 19, 2026, 04:55 AM UTC

    Our team is actively monitoring the situation to ensure that the issue has been completely resolved and does not reoccur.

11. monitoring Jun 19, 2026, 10:26 AM UTC

    Our teams are continuously monitoring the situation to ensure it is fully resolved.

12. resolved Jun 19, 2026, 12:50 PM UTC

    The issue has been successfully resolved and the service is once again operational. Start (UTC): 18 June 2026 07:29 End (UTC): 19 June 2026 11:37 Impact: You might have experienced delays in processing of WhatsApp traffic

Read the full incident report →

Started Jun 12, 2026, 02:26 PM UTC· resolved Jun 12, 2026, 05:42 PM UTC

1. investigating Jun 12, 2026, 02:26 PM UTC

   Hello, We are currently experiencing a general degradation affecting Meta channels, which has been identified as originating from the Meta side. Our development team is actively working in coordination with the Meta team to assess the situation and determine the full scope and impact of the issue. We will continue to monitor the situation closely and will provide updates as soon as more information becomes available. Thank you for your understanding.

2. identified Jun 12, 2026, 02:38 PM UTC

   Meta has identified a degradation in their services. This is the link to their status page: {https://metastatus.com/whatsapp-business-api}

3. identified Jun 12, 2026, 02:41 PM UTC

   Due to the degradation of Meta services, all data centers where WhatsApp Business Messaging is hosted are affected.

4. identified Jun 12, 2026, 03:44 PM UTC

   The issue is still ongoing on Meta’s side. We continue to monitor the situation. For updates regarding the incident on Meta’s side, please check the following URL: https://metastatus.com/whatsapp-business-api

5. resolved Jun 12, 2026, 05:42 PM UTC

   We would like to inform you that the disruptions reported by Meta, which affected our WhatsApp Business Messaging service, have been successfully resolved, and the service is now fully operational. Start (UTC): 12 June 2026, 13:34 End (UTC): 12 June 2026, 17:26 Impact: You may have experienced degradation in WhatsApp Business messaging during this period.

Read the full incident report →

Started Jun 11, 2026, 01:44 PM UTC· resolved Jun 11, 2026, 01:44 PM UTC

1. resolved Jun 11, 2026, 01:44 PM UTC

   We experienced an issue with the People API on the following timestamps: Start (UTC): 11-06-2026 12:29 End (UTC): 11-06-2026 12:52 Impact: During this period, you may have experienced Error 500 being returned on People API requests. Other services interacting with the People API may have also experienced residual/cascading side effects We apologise 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 Jun 10, 2026, 08:13 AM UTC· resolved Jun 10, 2026, 12:27 PM UTC

1. investigating Jun 10, 2026, 08:13 AM UTC

   We are currently experiencing issues with auto assignment in Conversations affecting users in Global (Europe). Our teams are actively working on a fix. As a temporary workaround, affected users are advised to log out of the interface, wait two minutes, and then log back in.

2. investigating Jun 10, 2026, 08:13 AM UTC

   We are continuing to investigate this issue.

3. investigating Jun 10, 2026, 08:47 AM UTC

   During the incident, some customers may have experienced irregular Workflow execution behavior. The issue has been resolved and Workflow functionality is stabilizing. We are continuing to investigate the auto‑assignment behavior and will provide further updates as they become available.

4. resolved Jun 10, 2026, 12:27 PM UTC

   The issue has been resolved, and we are seeing improvements related to auto‑assignment and capacity as the errors for the affected services are gradually reducing. Start (UTC): 09 June 2026 14:01 UTC End (UTC): 10 June 2026 11:58 UTC Impact: Auto‑Assignment and Capacity in Conversations processing issues

Read the full incident report →

Started Jun 06, 2026, 09:29 PM UTC· resolved Jun 06, 2026, 10:14 PM UTC

1. investigating Jun 06, 2026, 09: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. investigating Jun 06, 2026, 09:41 PM UTC

   We are continuing to investigate this issue.

3. resolved Jun 06, 2026, 10:14 PM UTC

   The issue has been successfully resolved and the service is once again operational. The reason was a network issue thus affecting all services. Start (UTC): 06 June 20:11 End (UTC): 06 June 21:48 Impact: You may have experienced degraded performance on all services.

Read the full incident report →

Started May 26, 2026, 11:40 AM UTC· resolved May 26, 2026, 11:46 AM UTC

1. investigating May 26, 2026, 11:40 AM UTC

   This is to inform you that we are currently experiencing issues with our Advanced Analytics service hosted in our EU region‑locked data centers. Our designated engineering team is actively investigating the issue and will share more information as soon as possible.

2. resolved May 26, 2026, 11:46 AM UTC

   The issue with the Advanced Analytics service hosted in our EU region‑locked data center has been resolved. During the timeframe below, you may have experienced issues with loading Analytics dashboards and viewing the data. Start time (UTC): 26 May 2026 11:02 End time (UTC): 26 May 2026 11:35 Impact: Processing issues and loading of Advanced Analytics dashboards.

Read the full incident report →

Started May 25, 2026, 11:32 AM UTC· resolved May 25, 2026, 12:00 PM UTC

1. investigating May 25, 2026, 11:32 AM UTC

   Our dedicated development team is currently investigating the root cause of the issue.

2. resolved May 25, 2026, 12:00 PM UTC

   We want to inform you that the previously reported degradation affecting the Conversations service has been resolved. During the timeframe listed below, users may have experienced difficulties with Conversation statuses, which may not have been updated or updated with delays in the My Work and All Work sections. Start time (UTC): 25-05-2026 10:30 End time (UTC): 25-05-2026 11:54 Impact: Conversations status updates in My Work and All Work Sections

Read the full incident report →

Started May 22, 2026, 10:06 AM UTC· resolved May 22, 2026, 12:47 PM UTC

1. investigating May 22, 2026, 10:06 AM UTC

   We are currently experiencing issues with our WhatsApp template management service. You may experience issues with updating, fetching, or creating WhatsApp templates over the HTTP API and customer portal. Our dedicated team is currently working on this and more updates will follow.

2. identified May 22, 2026, 10:43 AM UTC

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

3. identified May 22, 2026, 11:29 AM UTC

   Our dedicated team is still working to resolve the issue.

4. resolved May 22, 2026, 12:47 PM UTC

   We want to inform you that the previously reported degradation affecting the WhatsApp template management service has been resolved. During the timeframe listed below, users may have experienced difficulties with creating, updating, and fetching WhatsApp templates via the HTTP API and Customer Portal, across multiple locations. Start time (UTC): 22 May 2026 09:17 End time (UTC): 22 May 2026 11:59 Impact: WhatsApp template creation, update, and retrieval via HTTP API and Customer Portal.

Read the full incident report →

Started May 21, 2026, 02:03 PM UTC· resolved May 22, 2026, 04:12 AM UTC

1. investigating May 21, 2026, 02:03 PM UTC

   We are currently experiencing issues with RCS service towards Vodafone India. You may experience issues with RCS templates not being available or issues with delivering messages towards Vodafone India recipient. Our team is investigating this with the operator and more information will follow in next update.

2. investigating May 21, 2026, 05:26 PM UTC

   The situation continues to be investigated by Vodafone India. Rest assured, we’ll share any new updates we receive from their side as soon as they become available.

3. identified May 21, 2026, 11:08 PM UTC

   The partner operator is currently working on implementing a fix for this issue. You’ll be informed as soon as there are any updates on the progress.

4. identified May 22, 2026, 01:02 AM UTC

   The partner operator is actively working on a solution for this issue, and you will be notified as soon as there are any updates on their progress.

5. resolved May 22, 2026, 04:12 AM UTC

   The issue has been successfully resolved, and RCS service is again operational. Start (UTC): 30 April 2026 03:58 End (UTC): 22 May 2026 02:50 Impact: Clients may have experienced RCA delivery issues towards Vodafone network in India

Read the full incident report →

Started May 18, 2026, 12:32 PM UTC· resolved May 19, 2026, 11:12 AM UTC

1. investigating May 18, 2026, 12:32 PM UTC

   We are currently experiencing issues with accessing, creating and modification of WhatsApp Flows. Our dedicated team is already checking this and more updates will follow.

2. identified May 18, 2026, 12:55 PM UTC

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

3. identified May 18, 2026, 01:23 PM UTC

   Our dedicated teams are continuing to work on a fix for this issue and we will follow up with more information.

4. identified May 18, 2026, 01:51 PM UTC

   We are continuing to work on a fix for this issue and our engineering team is actively checking. Further update will be provided as soon as new information becomes available.

5. identified May 18, 2026, 02:27 PM UTC

   We are continuing to work on a fix for this issue, and our engineering team is actively investigating. We have identified the root cause and are already working on a resolution. We will provide further updates as soon as additional information becomes available.

6. identified May 18, 2026, 06:13 PM UTC

   Our engineering team has identified the root cause and is actively working on a fix. Currently, the API and WhatsApp channel applications responsible for WhatsApp Flow creation and management are experiencing errors, including issues retrieving flow content, which may affect the creation of new flows. We will continue to monitor the situation and provide updates as more information becomes available.

7. identified May 18, 2026, 06:23 PM UTC

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

8. identified May 18, 2026, 06:55 PM UTC

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

9. identified May 18, 2026, 10:02 PM UTC

   Our engineering team has identified the root cause and is actively working on a fix. Investigation and monitoring efforts are ongoing, and we will provide additional updates as more information becomes available.

10. identified May 19, 2026, 12:30 AM UTC

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

11. identified May 19, 2026, 02:30 AM UTC

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

12. identified May 19, 2026, 05:02 AM UTC

    We are continuing to work on a fix for this issue, and our engineering team is actively checking. Further update will be provided as soon as new information becomes available.

13. identified May 19, 2026, 07:04 AM UTC

    Our team keeps recovering WhatsApp Flows services on different data centers. We will share new updates as they become available.

14. resolved May 19, 2026, 11:12 AM UTC

    The issue has been successfully resolved and the service is once again operational. Start (UTC): 16 May 03:00 End (UTC): 19 May 11:08 Impact: The users might have experienced issues with accessing, creating and modifying WhatsApp Flows.

Read the full incident report →

Started May 18, 2026, 12:06 PM UTC· resolved May 18, 2026, 12:30 PM UTC

1. investigating May 18, 2026, 12:06 PM UTC

   We are currently experiencing issues with Add Funds page over our Customer Portal. You may experience difficulties with adding funds to your accounts. The issue is being investigated and more updates will follow shortly.

2. identified May 18, 2026, 12:17 PM UTC

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

3. resolved May 18, 2026, 12:30 PM UTC

   The issue has been successfully resolved and the service is once again operational. Start (UTC): 18 May 2026 11:14 End (UTC): 18 May 2026 12:21 Impact: Add-Funds page unavailable (error 404 reverted)

Read the full incident report →

Started May 12, 2026, 07:09 PM UTC· resolved May 12, 2026, 07:21 PM UTC

1. investigating May 12, 2026, 07:09 PM UTC

   Our engineering and network teams are actively investigating reports of service degradation affecting our data centers in the UAE, South Africa, and Pakistan. Upon further investigation, we can confirm that customers in these regions may experience delays, missing messages, timeouts, or errors affecting SMS, Voice, WhatsApp, and Email services, as well as traffic processing across multiple channels. We will continue monitoring the situation closely and will share additional updates as soon as new information becomes available.

2. resolved May 12, 2026, 07:21 PM UTC

   The issue has been successfully resolved, and the service is once again operational. Start (UTC): 12 May 2026 17:09 End (UTC): 12 May 2026 19:04 Impact: Customers in the UAE, South Africa, and Pakistan regions may have experienced delays, missing messages, or errors on SMS, Voice, WhatsApp, and Email services

Read the full incident report →

Started Apr 28, 2026, 08:19 AM UTC· resolved Apr 28, 2026, 08:53 AM UTC

1. investigating Apr 28, 2026, 08:19 AM UTC

   We are currently experiencing issues with Customer Portal services. Users may encounter errors when accessing the portal or attempting to log in.

2. investigating Apr 28, 2026, 08:24 AM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 28, 2026, 08:36 AM UTC

   A fix has been implemented, and we are monitoring the system to ensure stability.

4. resolved Apr 28, 2026, 08:53 AM UTC

   The incident has been resolved. Start (UTC): 28 April 2026 07:59 End (UTC): 28 April 2026 08:23 Impact: Users may encounter errors when accessing the portal or attempting to log in. Thank you for your understanding and patience.

Read the full incident report →

Started Apr 27, 2026, 07:14 AM UTC· resolved Apr 27, 2026, 07:36 AM UTC

1. investigating Apr 27, 2026, 07:14 AM UTC

   This is to inform you that we are currently experiencing an issue on Customer Portal. Our Self-Service users might notice that they can not add Whatsapp or Viber channel over Customer Portal. The issue is being inspected by our engineering team, more details will follow in the next update.

2. resolved Apr 27, 2026, 07:36 AM UTC

   The incident has been resolved. Start (UTC): 27 April 2026 07:07 End (UTC): 27 April 2026 07:34 Impact: Self-service users could not add (activate) WhatsApp and Viber channels over Customer Portal.

Read the full incident report →

Started Apr 26, 2026, 09:54 AM UTC· resolved Apr 26, 2026, 10:08 AM UTC

1. investigating Apr 26, 2026, 09:54 AM UTC

   We are currently experiencing issues with the SMS service over the Vietnam data center. The issue is currently being investigated. You might see 5xx errors showing up on HTTP API SMS endpoints, more information will follow in the next update.

2. resolved Apr 26, 2026, 10:08 AM UTC

   The issue has been successfully resolved, and the service is now fully operational. During the incident, you may have encountered 5xx errors when accessing the HTTP API SMS endpoints. Start (UTC): 26 April, 08:48 End (UTC): 26 April, 9:51 Impact: Problems with the HTTP API SMS endpoints at the Vietnam data center

Read the full incident report →