This is to inform you that a service database maintenance will be done on the side of our KakaoTalk provider.
You may notice brief interruptions in the functionality of KakaoTalk service during the maintenance.
Start (UTC): 26 May 2025 06:00
End (UTC): 26 May 2025 07:00
Posted on
May 12, 2025 - 13:27 UTC
We will be undergoing a planned maintenance of database infrastructure at our India data center. During this process you may experience brief service interruptions for components listed below. You may notice that new data inserted in Do Not Contact list over Portal is not updated during the maintenance. We suggest that you update that data after the maintenance is completed.
Also, you may notice inconsistent results for Number Lookup service.
This maintenance is essential to keep our databases up-to-date and ensure they operate optimally.
Start (UTC): 28 May 2025 12:00
End (UTC): 28 May 2025 22:00
Purpose: Database upgrade and optimization.
Posted on
May 13, 2025 - 13:53 UTC
We will be conducting a planned maintenance of database infrastructure at our Global (Europe) data center within the specified time-frame.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
You may notice disruptions in Logs section and while creating Reports.
Start (UTC): 28 May 2025 18:00
End (UTC): 28 May 2025 22:00
Purpose: Database infrastructure maintenance.
Posted on
May 14, 2025 - 09:37 UTC
Update -
This is to inform you that the time of the maintenance has been changed.
Time of the maintenance is below:
Start (UTC): 02 June 2025 20:00
End (UTC): 02 June 2025 00:00
May 23, 2025 - 09:09 UTC
Scheduled -
We will be conducting a planned database maintenance at our Global (Europe) data center within the specified time-frame.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
This maintenance is essential to keep our databases and services up-to-date and ensure they operate at peak performance.
Start (UTC): 02 June 2025 18:00
End (UTC): 02 June 2025 22:00
Purpose: Database maintenance
May 16, 2025 - 13:50 UTC
We will be undergoing an upgrade of media components used by our Voice service hosted on United States data center to ensure the ongoing reliability and optimal performance. During this period, customers utilizing the Voice service hosted on United States data center may experience intermittent voice quality issues.
Start (UTC): 05 June 2025 04:00
End (UTC): 05 June 2025 08:00
Purpose: Voice service upgrade and optimization.
Posted on
May 22, 2025 - 08:08 UTC
We will undergo a planned maintenance of the Bulk Message Scheduling Service hosted on the Global (Europe) data center. During the activity, Infobip customers submitting bulk traffic via HTTP API or the Customer Portal within the specified period may notice up to a cumulative 10 minutes of message processing delays.
Start (UTC): 05 June 2025 05:00
End (UTC): 05 June 2025 07:00
Purpose: Bulk Scheduling Service optimization
Posted on
May 21, 2025 - 09:50 UTC
As part of regular Business Continuity Management (BCM) requirements, we will undergo a planned Disaster Recovery test during the below specified timeframe:
Start (UTC): 05 June 2025 07:00
End (UTC): 05 June 2025 11:00
Purpose: Business Continuity Management requirements
Impact on Infobip services hosted at the United States data center is not expected.
Posted on
May 19, 2025 - 10:23 UTC
We will undergo a planned maintenance of the Bulk Message Scheduling Service hosted on the India data center. During the activity, Infobip customers submitting bulk traffic via HTTP API or the Customer Portal within the specified period may notice up to a cumulative 10 minutes of message processing delays.
Start (UTC): 05 June 2025 12:00
End (UTC): 05 June 2025 14:00
Purpose: Bulk Scheduling Service optimization
Posted on
May 21, 2025 - 09:40 UTC
We will undergo routine patching of databases at the Saudi Arabia and United Arab Emirates data centers. During this activity you may experience brief service interruptions for components listed in the section below.
Component downtime may occur during a specific database restart, but each restart should take no longer than 10 minutes. Furthermore, since components are isolated within their own databases, there will be no simultaneous disruption to multiple components.
This patching is essential to keep our databases up-to-date and ensure they operate optimally
Start (UTC): 05 June 2025 22:00
End (UTC): 06 June 2025 02:00
Purpose: Database patching and maintenance
Posted on
May 22, 2025 - 09:24 UTC