Update -
The scope of this maintenance has been extended to also include migration of the database infrastructure supporting Customer Portal authentication and analytics services. In addition to the content-related impacts already announced, Portal two-factor authentication may be temporarily unavailable for enrolling a new authenticator device or signing in with an existing time-based one-time password, embedded analytics dashboards may not load, and some Portal account-management operations may be temporarily unavailable.
Oct 27, 2026 - 10:52 UTC
Scheduled -
We will be performing planned maintenance on database infrastructure supporting content-related services at our Europe Region-locked data centers. The goal of this work is to migrate the underlying database to an upgraded, more resilient cluster and ensure the stability and optimal performance of the affected services.
Preventive measures have been implemented to minimize any potential impact; however, customers may experience the following temporary limitations during the maintenance window:
1. Voice: Processing of new voice recordings may be delayed, and downloading recordings may be unavailable.
2. Conversations: Saving a note attachment permanently may fail. Sending an email through a web form with an attachment may also fail.
3. Broadcast: Downloading or reviewing recipient lists may be unavailable. Campaigns whose recipient files have expired may fail to launch.
4. Email: Loading or previewing uploaded HTML, retrieving attachments or images through the Portal, and managing stored content may fail or be delayed. New content uploads, direct download links, template processing, and inbound email-content uploads are expected to remain available.
Any disruption is expected to last no longer than 20 minutes within the scheduled maintenance window.
Start (UTC): 03 November 2026 05:00
End (UTC): 03 November 2026 06:00
Purpose: Database migration and infrastructure maintenance
Oct 16, 2026 - 12:35 UTC
We will be conducting routine database patching at our Indonesia, Malaysia, India and Hong Kong data centers.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
The disruption may occur during a specific database restart, but each restart should take no longer than a few minutes, with a maximum duration of 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 at peak performance.
Start (UTC): 03 November 2026 16:00
End (UTC): 03 November 2026 20:00
Purpose: Database patching and maintenance
Posted on
Oct 21, 2026 - 09:02 UTC
We will be conducting routine database patching at our EU Region-locked and South Africa data centers.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
The disruption may occur during a specific database restart, but each restart should take no longer than a few minutes, with a maximum duration of 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 at peak performance.
Start (UTC): 03 November 2026 22:00
End (UTC): 04 November 2026 02:00
Purpose: Database patching and maintenance
Posted on
Oct 21, 2026 - 09:22 UTC
We will be conducting routine database patching at our United States data center.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
The disruption may occur during a specific database restart, but each restart should take no longer than a few minutes, with a maximum duration of 10 minutes. Furthermore, since components are isolated within their own databases, there will be no simultaneous disruption to multiple components. SMS traffic will remain unaffected, however, Signals service might experience brief disruptions in operation.
This patching is essential to keep our databases up-to-date and ensure they operate at peak performance.
Start (UTC): 04 November 2026 04:00
End (UTC): 04 November 2026 08:00
Purpose: Database patching and maintenance
Posted on
Oct 22, 2026 - 10:53 UTC
We will undergo routine patching of databases at the United States data center.
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): 04 November 2026 08:00
End (UTC): 04 November 2026 12:00
Purpose: Database patching and maintenance
Posted on
Oct 22, 2026 - 13:46 UTC
We will undergo routine patching of databases at our India and Singapore data centers. During this process you may experience brief service interruptions for components listed below.
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): 04 November 2026 16:00
End (UTC): 04 November 2026 20:00
Purpose: Database patching and maintenance
Posted on
Oct 22, 2026 - 08:19 UTC
We will undergo routine patching of databases at the Global (Europe) data center.
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): 04 November 2026 22:00
End (UTC): 05 November 2026 02:00
Purpose: Database patching and maintenance
Posted on
Oct 22, 2026 - 10:35 UTC
We will undergo routine patching of databases at the following data centers: Global (Europe), EU Region-locked, Great Britain.
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): 04 November 2026 22:00
End (UTC): 05 November 2026 02:00
Purpose: Database patching and maintenance
Posted on
Oct 22, 2026 - 10:08 UTC
We will undergo routine patching of databases at the following data centers: United States and Brazil.
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 November 2026 04:00
End (UTC): 05 November 2026 08:00
Purpose: Database patching and maintenance
Posted on
Oct 23, 2026 - 09:26 UTC
We will undergo routine patching of databases at India and Indonesia 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 November 2026 16:00
End (UTC): 05 November 2026 20:00
Purpose: Database patching and maintenance
Posted on
Oct 23, 2026 - 10:24 UTC
We will undergo routine patching of databases at Global (Europe) and EU Region-locked 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 November 2026 22:00
End (UTC): 06 November 2026 02:00
Purpose: Database patching and maintenance
Posted on
Oct 23, 2026 - 11:29 UTC
We will undergo routine patching of databases at the following data centers: Global (Europe), United Arab Emirates and Saudi Arabia.
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 November 2026 22:00
End (UTC): 06 November 2026 02:00
Purpose: Database patching and maintenance
Posted on
Oct 23, 2026 - 09:59 UTC
We will be performing planned maintenance of network infrastructure at our Pakistan data center to upgrade core networking equipment, ensuring stability and optimal performance.
Preventive measures have been implemented to minimize any potential impact, however, brief connectivity interruptions may occur for services hosted at the Pakistan data center.
Start (UTC): 09 November 2026 19:00
End (UTC): 09 November 2026 22:00
Purpose: Network infrastructure upgrade and optimization
Posted on
Oct 22, 2026 - 11:27 UTC
Update -
The database patching at our United States and Mexico data centers has been postponed to a new maintenance window.
The scope of the work and the expected service behavior remain unchanged, with the revised schedule below.
New start (UTC): 10 November 2026 04:00
New end (UTC): 10 November 2026 08:00
Purpose: Database patching and maintenance
Oct 28, 2026 - 07:32 UTC
Scheduled -
We will be conducting routine database patching at our United States and Mexico data centers.
During this process, you may experience brief disruptions in operation of services corresponding to the components listed below.
The disruption may occur during a specific database restart, but each restart should take no longer than a few minutes, with a maximum duration of 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 at peak performance.
Start (UTC): 03 November 2026 04:00
End (UTC): 03 November 2026 08:00
Purpose: Database patching and maintenance
Oct 21, 2026 - 10:02 UTC