Telesign system status

Telesign system status history

This page offers API uptime information for Telesign services, in addition to incident history reports and service issues alerts.

Active events

See more

Operational

Degraded performance

Partial Outage

Major Outage

Under maintenance

Identified - Date: 03/08/22
End Time: Ongoing

We received notification that due to the current political situation certain operators (carriers) in Russia are currently experiencing network issues, and this may cause a delay or failure in the delivery of SMS messages. We will inform you once the situation is resolved.


We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact support@telesign.com.

Jan 13, 2025 - 01:01 PST
Investigating - Start Time: 10:57PM PST - 01/30/25
End Time: Ongoing

We received notification that Onatel (642/03) from Burundi (BI) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00945556

Feb 04, 2025 - 22:32 PST
Identified - Telesign is currently unable to ensure that messages sent to mainland China are reliably delivered because of restrictions around content, encoding, signatures, and use case. These restrictions have resulted in the blocking of seemingly legitimate and registered customer traffic. Due to this, Telesign is currently able to support China Signature/Short Code registration only for local companies and messages sent through Telesign would be delivered on a best-effort basis with limited support only.

The signature/short code registration process for local companies or those with a local presence typically takes 3-4 weeks.

Recent Telesign StatusPage updates regarding China:
o Telesign system status Incident - Important Update: China Signature Changes for Non-Local Companies - China Mobile - 12 August 2024
o Telesign system status Incident - 2-Way service interruptions China (CN) - China Mobile (460/00;02;07;28;04;08) - 21 June 2024
o Telesign system status Incident - 2-Way service interruptions China (CN) - China Unicom (460/01;06;09) - 12 July 2024
o Telesign system status Incident - Quality degradation - China (CN) - Voice Api Issue - [04/11/24] - 15 April 2024
o Telesign system status Incident - Quality degradation - China (CN) - China Mobile (460/00;02;07;28;04;08) - 8/7/24 - 7 August 2024
o Telesign system status Incident - Operator Alert - China (CN) - China Mobile 8/23/24 - 23 August 2024
o Telesign system status Incident - Voice Quality Degradation - China - 8/28/24 - 28 August 2024

Jan 07, 2025 - 13:12 PST
API Availability Operational
App Verify Operational
Bulk SMS Operational
Deactivated Numbers Operational
Inbound SMS Operational
Intelligence Operational
Messaging API Operational
Number Masking Operational
Phone ID Operational
Phone ID Contact Operational
Phone ID Live Operational
Phone ID Number deactivation Operational
Phone ID Porting status Operational
Phone ID SIM swap Operational
Silent Verify Operational
SMS Operational
SMS Verify Operational
Verify API Operational
Voice Operational
Voice verify Operational
SMS/SMS Verify - EMEA Operational
EMEA - All countries Operational
Belgium Operational
France Operational
Germany Operational
United Kingdom Operational
Italy Operational
Poland Operational
Romania Operational
Spain Operational
Turkey Operational
Russia Operational
Egypt Operational
Saudi Arabia Operational
Yemen Operational
Ukraine Operational
U.A.E. Operational
Portugal Operational
SMS/SMS Verify - APAC Operational
APAC - All countries Operational
China Operational
Australia Operational
Indonesia Operational
India Operational
New Zealand Operational
South Korea Operational
Pakistan Operational
Vietnam Operational
Japan Operational
Philipines Operational
Cambodia Operational
Thailand Operational
Singapore Operational
Malaysia Operational
SMS/SMS Verify - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Argentina Operational
Brazil Operational
Canada Operational
Colombia Operational
Mexico Operational
Chile Operational
Peru Operational
Panama Operational
Voice Verify - EMEA Operational
EMEA - All countries Operational
Algeria Operational
Germany Operational
Egypt Operational
Morocco Operational
Iraq Operational
Zimbabwe Operational
Kenya Operational
Saudi Arabia Operational
United Kingdom Operational
Belgium Operational
Jordan Operational
U.A.E. Operational
Spain Operational
Poland Operational
France Operational
Romania Operational
Qatar Operational
Senegal Operational
Voice Verify - APAC Operational
APAC - All countries Operational
China Operational
India Operational
Bangladesh Operational
Pakistan Operational
Malaysia Operational
Myanmar Operational
Philipines Operational
Australia Operational
Voice Verify - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Brazil Operational
Ecuador Operational
Colombia Operational
Canada Operational
Peru Operational
Guatemala Operational
El Salvador Operational
Argentina Operational
Portals Operational
Unified Portal - https://my.telesign.com Operational
Teleportal - https://teleportal.telesign.com/ Operational
Portal - https://portal.telesign.com Operational
Verify API - Other channels Operational
Viber Operational
WhatsApp Operational
Silent Verify Operational
Voice verify Operational
Email Operational
RCS Operational
Phone ID Contact - EMEA Operational
EMEA - All countries Operational
Germany Operational
Phone ID Contact - APAC Operational
APAC - All countries Operational
China Operational
Myanmar Operational
Phone ID Contact - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Phone ID Number Deactivation - EMEA Operational
EMEA - All countries Operational
Germany Operational
Italy Operational
Switzerland Operational
Sweden Operational
Ireland Operational
Denmark Operational
Phone ID Number Deactivation - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Mexico Operational
Phone ID Number Deactivation - APAC Operational
APAC - All countries Operational
China Operational
Phone ID Porting Status - EMEA Operational
EMEA - All countries Operational
Germany Operational
France Operational
United Kingdom Operational
Netherlands Operational
Phone ID Porting Status - APAC Operational
APAC - All countries Operational
Japan Operational
Indonesia Operational
Phone ID Porting Status - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Brazil Operational
Canada Operational
Phone ID Live - EMEA Operational
EMEA - All countries Operational
Germany Operational
United Kingdom Operational
Phone ID Live - APAC Operational
APAC - All countries Operational
Indonesia Operational
Philipines Operational
Australia Operational
New Zealand Operational
Pakistan Operational
Thailand Operational
Bangladesh Operational
Phone ID Additional add-ons Operational
Age verify Operational
Breached number check Operational
Call forward detection Operational
Contact match Operational
Contact plus Operational
Device info Operational
Subscriber status Operational
Phone ID Live - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Canada Operational
Phone ID Porting History - EMEA Operational
EMEA - All countries Operational
South Africa Operational
Phone ID Porting History - APAC Operational
APAC - All countries Operational
Phone ID Porting History - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Colombia Operational
Brazil Operational
Phone ID SIM Swap - EMEA Operational
EMEA - All countries Operational
Germany Operational
United Kingdom Operational
Netherlands Operational
South Africa Operational
Phone ID SIM Swap - APAC Operational
APAC - All countries Operational
Australia Operational
Phone ID SIM Swap - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Canada Operational
Colombia Operational
Brazil Operational
Puerto Rico Operational
Messaging API - Other channels Operational
Email Operational
RCS Operational
Viber Operational
WhatsApp Operational
Voice - EMEA Operational
EMEA - All countries Operational
Germany Operational
Voice - APAC Operational
APAC - All countries Operational
China Operational
Voice - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Phone ID - EMEA Operational
EMEA - All countries Operational
Germany Operational
Phone ID - NA & LATAM Operational
NA & LATAM - All countries Operational
United States Operational
Phone ID - APAC Operational
APAC - All countries Operational
China Operational
Intelligence Operational
Intelligence Operational
Regulatory Updates Operational
EMEA Operational
APAC Operational
NA & LATAM Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Regulatory Update - UK SID Whitelisting Introduced Jan 6, 2025 03:29 - Jun 7, 2025 06:29 PDT
📢 Dear valued clients, we bring you a crucial update! To streamline operations in the UK, SID approval/whitelist is now a prerequisite. Going forward, it is imperative for the end client or brand to provide the following details:

1. Sender ID (case sensitive)
2. Message Content Sample (including any URLs if present in the content)
3. Expected Monthly Volume

Generic SIDs are no longer allowed.

Your cooperation in meeting these requirements is highly appreciated.

Posted on Jan 06, 2025 - 03:27 PST
Scheduled - We will be undergoing scheduled maintenance during this time.
Jan 07, 2025 - 13:07 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 07, 2025 - 13:07 PST
Scheduled - Due to recent changes in Chinese Telecom regulations, signature registrations will now only be supported for companies based in China or have a local presence in China. As a result, all non-local registered dedicated signatures will be replaced by the generic signature 【优速通】 or 【速验通】 effective immediately for China Mobile users, which represents approximately 58% of the market. We anticipate that this change may soon extend to all operating networks with little or no prior notice. While your service will continue to function as usual, the only change will be the use of the signature 【优速通】 or 【速验通】in place of your previously registered signature. For further details, please refer to the official Telecom documentation here: https://www.miit.gov.cn/zwgk/zcwj/flfg/art/2020/art_77bc7219833c4a08b4563ba42ad23e1f.html

We do not expect any negative impact on the delivery of previously registered dedicated codes, and no changes to these codes are anticipated. However, if you are using our Telesign "shared" routes (non-registered traffic), please note the following potential impacts:

- Content containing URLs may experience delivery issues. To mitigate this, Telesign is finalizing a standard signature and code for use via our shared routes:
- Signature: 【通乐信】
- Code: 7654321

If your company is based in China and you wish to retain your previously registered signature, please contact our support team at Support@telesign.com with the following information:

- Previously registered signature
- Chinese company name
- Business Certificate
- Unified credit code of the company
- Contact Name
- Contact ID number

Please note that processing may take 1-3 weeks.

For those wishing to register for a new dedicated code in China, please follow our detailed instructions here: https://support.telesign.com/s/article/How-do-I-register-for-a-Sender-ID.

Jan 07, 2025 - 13:05 PST
Issue: US Operator - AT&T Mobility 10DLC Maintenance

Date: 02/26/25
Start Time: 01:00am PST
End Time: 05:00am PST

Summary:
We received notification that AT&T Mobility from United States (US) will perform planned maintenance on the date and time specified above.
During this time period, customers with 10DLC that send SMS messages to AT&T Mobility users may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

On behalf of the operator, we'd like to apologize for any inconvenience and appreciate your patience during this service window.

If you have any questions, please contact us at support@telesign.com.

Posted on Feb 26, 2025 - 01:00 PST
Issue: US Operator - AT&T Mobility 10DLC Maintenance

Start Time: 01:00am PST - 03/03/25
End Time: 05:00am PST - 03/03/25

Summary:
We received notification that AT&T Mobility from United States (US) will perform planned maintenance on the date and time specified above.
During this time period, customers with 10DLC that send SMS messages to AT&T Mobility users may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00951683

Posted on Feb 12, 2025 - 08:19 PST
ssue: US Operator - AT&T Mobility 10DLC Maintenance

Start Time: 01:00am PST - 03/10/25
End Time: 05:00am PST - 03/10/25

Summary:
We received notification that AT&T Mobility from United States (US) will perform planned maintenance on the date and time specified above.
During this time period, customers with 10DLC that send SMS messages to AT&T Mobility users may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00951683

Posted on Feb 12, 2025 - 08:20 PST
Past Incidents
Feb 15, 2025
Resolved - Start Time: 12:35 AM PST - 02/15/25
End Time: 03:05 AM PST - 02/15/25


We received notification that the network issues previously reported by Smart Communications (515/03;05;18) from Philippines (PH) have been resolved. Smart Communications (515/03;05;18) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF - 00953089

Feb 15, 03:10 PST
Investigating - Start Time: 12:35 AM PST - 02/15/25
End Time: Ongoing

We received notification that Smart Communications (515/03;05;18) from Philippines (PH) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF - 00953089

Feb 15, 00:36 PST
Resolved - Start Time: 9:45 PM PST - 2/14/25
End Time: 1:05 AM PST - 2/15/25

We received notification that the network issues previously reported by Multiple MNOs from China(CN) have been resolved. End users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

Feb 15, 01:13 PST
Investigating - Issue: China (CN) - Multiple MNOs - Quality degradation

Start Time: 9:45 PM PST - 2/14/25
End Time: Ongoing

Summary:

We received notification that Multiple MNOs from China(CN) are currently experiencing network issues, and this may cause a delay in the delivery of SMS messages.

Telesign is engaged with the operators for updates on resolution.

We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact support@telesign.com.

Feb 14, 23:58 PST
Feb 14, 2025
Feb 13, 2025
Completed - The scheduled maintenance has been completed.
Feb 13, 20:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 13, 14:00 PST
Scheduled - Date: 02/13/2025
Start Time: 02:00 PM PST
End Time: 08:00 PM PST

We have been informed that one of our partners in United Kingdom will conduct planned maintenance at the specified date and time. Customers using the Phone ID Contact Match, Number Deactivation and Sim Swap to Orange and T-Mobile numbers during this maintenance period may experience temporary delays. We recommend planning accordingly.

If you have any questions, please contact us at support@telesign.com.

Feb 11, 15:21 PST
Resolved - Start Time: 3:06 PM - 2/13/25
End Time: 3:30 PM - 2/13/25

We received notification that the network issues previously reported by Iraq (IQ) - KorekTel (418/40;82) from Iraq (IQ) have been resolved. Iraq (IQ) - KorekTel (418/40;82) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00952410

Feb 13, 18:48 PST
Investigating - Start Time: 3:06 PM - 2/13/25
End Time: Ongoing

We received notification that Iraq (IQ) - KorekTel (418/40;82) from Iraq (IQ) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00952410

Feb 13, 15:12 PST
Resolved - Date: 02/13/2025
Start Time: 03:14 PM PST
End Time: 03:35 PM PST

We received notification from our partner that the issue previously noticed in Canada has been resolved. End users should no longer experience delays, as all services are back to functioning properly.

Feb 13, 16:09 PST
Identified - Date: 02/13/2025
Start Time: 03:14 PM PST
End Time: Ongoing

We received notification from our partner that Contact_match, Sim_swap, Subscriber Status Service Alert is currently having issues in Canada, which may cause some delays. We will inform you once there is a resolution.

We'd like to apologize for any inconvenience and appreciate your patience during this service window.

If you have any questions, please contact us at support@telesign.com.

Feb 13, 15:45 PST
Resolved - Start Time: 03:30 AM PST - 02/13/25
End Time: 10:33 AM PST - 02/13/25

We received notification that the network issues previously reported by Oman Telecommunications Company (OmanTel) from Oman (OM) have been resolved. Oman Telecommunications Company (OmanTel) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00952118

Feb 13, 14:06 PST
Investigating - Start Time: 03:30 AM PST - 02/13/25
End Time: Ongoing

We received notification that Oman Telecommunications Company (OmanTel) (422/02;04) from Oman (OM) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF[00952118]

Feb 13, 03:35 PST
Resolved - Start Time: 11:52 AM PST - 02/13/25
End Time: 01:34 PM PST - 02/13/25

We received notification that the network issues previously reported by ATT Mobility from United States (US) have been resolved. ATT Mobility end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00952346

Feb 13, 14:02 PST
Investigating - Issue: United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670) - Quality degradation

Start Time: 11:52 AM PST - 02/13/25
End Time: Ongoing

Summary:

We currently experience quality degradation toward United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670).
SMS messages towards these operator(s) may face delays or difficulties in delivery.

TeleSign is engaged with carrier partners for updates on resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption.

If you have any questions, please contact support@telesign.com.

SF 00952346

Feb 13, 12:04 PST
Resolved - Start Time: 08:10 AM PST - 2/13/25
End Time: 1:52 PM PST - 2/13/25

We received notification that the network issues previously reported by Brazil - Algar (724/07;32;33;34) from Brazil (BR) have been resolved. Brazil - Algar (724/07;32;33;34) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00952210

Feb 13, 13:52 PST
Investigating - Issue: Operator - Brazil - Algar (724/07;32;33;34) - Quality degradation

Start Time:08:10 AM PST - 2/13/25
End Time: Ongoing

Summary:

We received notification that Brazil - Algar (724/07;32;33;34) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages.

Telesign is engaged with the operators for updates on resolution.

We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If you have any questions, please contact support@telesign.com.

SF 00952210

Feb 13, 08:46 PST
Resolved - Start Time: 03:51 AM PST - 02/13/25
End Time: 05:13 AM PST - 02/13/25

We received notification that the network issues previously reported by ZONG (CMPak) (410/04) from Pakistan (PK) have been resolved. ZONG (CMPak) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00952124

Feb 13, 05:42 PST
Investigating - Start Time: 03:51 AM PST - 02/13/25
End Time: Ongoing

We received notification that ZONG (CMPak) (410/04) from Pakistan (PK) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF[00952124]

Feb 13, 03:55 PST
Resolved - Start Time: 03:51 AM PST- 02/13/25
End Time: 04:40 AM PST-02/13/25

Previously reported issues with 2-Way SMS delivery toward Belgium(BE) have been resolved. End users should no longer experience any issues as all services are back to functioning properly.

We apologize for any inconvenience this issue may have caused. If you have additional questions, please feel free to contact support@telesign.com.

SF[00952123]

Feb 13, 04:51 PST
Investigating - Start Time: 03:51 AM PST- 02/13/25
End Time: Ongoing

We are currently experiencing issues with 2-Way SMS delivery toward Belgium (BE)
Please note that all DLC are impacted].
Our team is investigating this issue and we will inform you once we come to a resolution.

SF[00952123]

Feb 13, 04:01 PST
Feb 12, 2025
Resolved - Start Time: 03:40 PM PST - 02/12/25
Start Time: 05:30 PM PST - 02/12/25

We received notification that the network issues previously reported by Moviles Argentina SA (Movistar) (722/01;001;07;007;10;010;070;70) from Argentina (AR) have been resolved. Moviles Argentina SA (Movistar) (722/01;001;07;007;10;010;070;70) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00951839

Feb 12, 17:31 PST
Investigating - Start Time: 03:40 PM PST - 02/12/25
End Time: Ongoing

We received notification that Telefonica Moviles Argentina SA (Movistar) (722/01;001;07;007;10;010;070;70) from Argentina (AR) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00951839

Feb 12, 15:55 PST
Resolved - Start Time: 00:56 PST - 02/12/25
End Time: 07:15 PST - 02/12/25

We received notification that the network issues previously reported by ENTEL Movil (736/02) from Bolivia (BO) have been resolved. ENTEL Movil (736/02) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00951457]

Feb 12, 07:17 PST
Investigating - Start Time: 00:56 PST - 02/12/25
End Time: Ongoing

We received notification that ENTEL Movil (736/02) from Bolivia (BO) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF00951457]

Feb 12, 01:04 PST
Feb 11, 2025
Resolved - Start Time: 08:11AM PST - 02/11/24
End Time: 02:00PM PST - 02/11/24

We received notification that the network issues previously reported toward Small Carriers in United States have been resolved. Small Carriers end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00951146

Feb 11, 15:08 PST
Investigating - Issue: US Operator - Small carriers - Quality degradation

Start Time: 08:11am PST - 02/11/24
End Time: Ongoing

Summary:

We currently experience quality degradation toward Small Carriers in US
Customers that send SMS messages to Small Carrier users may notice a difficulties in message delivery.

Telesign is engaged with carrier partners for updates on resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption.

If you have any questions, please contact support@telesign.com.

SF 00951146

Feb 11, 11:20 PST
Completed - The scheduled maintenance has been completed.
Feb 11, 03:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 10, 22:30 PST
Scheduled - Issue: US Operator - T-Mobile Maintenance

Date: 2/11/25
Start Time: 10PM PST 2/10/25
End Time: 3AM PST 2/11/25

Summary:
We have received notification that US Operator T-Mobile will perform planned maintenance on the date and time specified above. During this time period, customers with Dedicated Short Codes that send SMS messages to T-Mobile users may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly. This T-Mobile operator maintenance will not affect other US operators.

On behalf of the operator, we'd like to apologize for any inconvenience and appreciate your patience during this service window.

If you have any questions, please contact us at support@telesign.com.

Feb 10, 22:25 PST
Feb 10, 2025
Resolved - Start Time: 06:17 AM PST - 02/05/25
End Time: 11:48 PM PST - 2/10/25

We received notification that the network issues previously reported by Orange (612/03) from Cote d'Ivoire (CI) have been resolved. Orange (612/03) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00948270

Feb 10, 23:49 PST
Investigating - Start Time: 06:17 AM PST - 02/05/25
End Time: Ongoing

We received notification that Orange (612/03) from Cote d'Ivoire (CI) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00948270

Feb 8, 07:25 PST
Completed - The scheduled maintenance has been completed.
Feb 10, 04:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 9, 22:00 PST
Scheduled - Issue: Planned Maintenance -US/CA T-MOBILE

Start Time: 22:00 PM PST - 02/09/25
End Time: 04:00 AM PST - 02/10/25

Summary:
We received notification that T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) from US/CA will perform planned maintenance on the date and time specified above.
SMS messages to T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF[00949026]

Feb 6, 11:40 PST
Feb 9, 2025
Resolved - Date: 02/09/2025
Start Time: 04:20 PM PST
End Time: 07:20 PM PST

We received notification from our partner that the issue previously noticed in the United States has been resolved. End users should no longer experience delays, as all services are back to functioning properly.

Feb 9, 20:43 PST
Update - We are continuing to work on a fix for this issue.
Feb 9, 18:47 PST
Identified - Date: 02/09/2025
Start Time: 04:20 PM PST
End Time: Ongoing

We received notification from our partner that Phone ID Contact Addon is currently having issues in the United States, which may cause some delays. We will inform you once there is a resolution.

We'd like to apologize for any inconvenience and appreciate your patience during this service window.

If you have any questions, please contact us at support@telesign.com.

Feb 9, 17:39 PST
Resolved - Start Time: 02:54 PM PST - 02/09/25
End Time: 05:02 PM PST - 02/010/25

We received notification that the network issues previously reported by ATM Mobilis (603/01) from Algeria (DZ) have been resolved. ATM Mobilis (603/01 end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00950205

Feb 9, 16:51 PST
Investigating - Start Time: 02:54 PM PST - 02/09/25
End Time: Ongoing

We received notification that ATM Mobilis (603/01) from Algeria (DZ) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00950205

Feb 9, 14:55 PST
Resolved - This incident has been resolved.
Feb 9, 09:02 PST
Update - We are continuing to investigate this issue.
Feb 9, 09:01 PST
Update - Dear Customers and Partners,

Please note that the issue with the possible delays has been resolved.
Start Time: 08:27 AM PST
End Time: 08:28 AM PST

If you have any questions, please contact us at support@telesign.com.

Feb 9, 08:59 PST
Investigating - Dear Customers and Partners,

We are experiencing instability on our platform which could cause some delays in delivery.

Our team is investigating the issue and we will make sure to keep you updated as soon as we have preliminary findings.

If you have any questions, please contact us at support@telesign.com.

Feb 9, 08:57 PST
Feb 8, 2025
Completed - This emergency maintenance has been completed.
We apologize for any inconvenience.

Start Date/Time: 05/12/24 02:00 AM PST
End Date/Time: 30/12/24 04:00 AM PST

Feb 8, 14:21 PST
Scheduled - Date: 05/12/24
Start Time: 02:00 AM PST
End Time: TBA

TeleSign is performing emergency maintenance in one of TeleSign's data centers during the above-mentioned time frame.

Although connectivity issues and service degradation are not expected, this is a notice to inform you, in case of intermittent service delays during this period.

We apologize for any inconvenience and appreciate your patience during this maintenance.

If you have any questions, please get in touch with us at support@telesign.com.

Jan 6, 04:23 PST
Resolved - Start Time: 4:36 AM PST - 02/08/25
End Time: 7:51 AM PST - 02/08/25

We received notification that the network issues previously reported by Airtel (621/20) from Nigeria (NG) have been resolved. Airtel (621/20) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949912

Feb 8, 09:52 PST
Investigating - Start Time: 4:36 AM PST - 02/08/25
End Time: Ongoing

We received notification that Airtel (621/20) from Nigeria (NG) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF - 00949912

Feb 8, 04:39 PST
Feb 7, 2025
Resolved - Start Time: 5:54 PM PST - 2/7/25
End Time: 8:56 PM PST - 2/7/25

We received notification that the network issues previously reported by Mossel (Digicel) (338/05;050) from Jamaica (JM) have been resolved. Mossel (Digicel) (338/05;050) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949771

Feb 7, 21:00 PST
Investigating - Start Time: 5:54 PM PST - 2/7/25
End Time: Ongoing

We received notification that Jamaica (JM) - Mossel (Digicel) (338/05;050) from Jamaica (JM) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00949771

Feb 7, 17:59 PST
Resolved - Start Time: 07:24 AM PST - 02/07/25
End Time: 11:06 AM PST - 02/07/25

We received notification that the network issues previously reported by ScanCom Ltd (MTN) (620/01) from Ghana (GH) have been resolved. ScanCom Ltd (MTN) (620/01) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949587

Feb 7, 13:14 PST
Investigating - Start Time: 07:24 AM PST - 02/07/25
End Time: Ongoing

We received notification that ScanCom Ltd (MTN) (620/01) from Ghana (GH) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF[00949587]

Feb 7, 07:28 PST
Resolved - Start Time: 05:52 AM PST - 02/07/25
End Time: 10:39 AM PST - 02/07/25

We received notification that the network issues previously reported by Nigeria Communications Ltd (MTN) from Nigeria (NG) have been resolved. Nigeria Communications Ltd (MTN) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949531

Feb 7, 12:03 PST
Investigating - Start Time: 05:52 AM PST - 02/07/25
End Time: Ongoing

We received notification that Nigeria Communications Ltd (MTN) from Nigeria (NG) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00949531

Feb 7, 05:59 PST
Resolved - Start Time: 07:10 AM PST - 02/07/25
End Time: 10:260AM PST - 02/07/25

We received notification that the network issues previously reported by Mobile TeleSystems (MTS) (250/01) from Russia (RU) have been resolved. Mobile TeleSystems (MTS) (250/01) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949575

Feb 7, 10:27 PST
Investigating - Start Time: 07:10 AM PST - 02/07/25
End Time: Ongoing

We received notification that Mobile TeleSystems (MTS) (250/01) from Russia (RU) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF[ 00949575]

Feb 7, 07:15 PST
Resolved - Start Time: 02:33 AM PST - 02/07/25
End Time: 06:33 AM PST - 02/07/25

We received notification that the network issues previously reported by Globacom (621/50) from Nigeria (NG) have been resolved. Globacom (621/50) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949419

Feb 7, 08:01 PST
Investigating - Start Time: 02:33AM PST - 02/07/25
End Time: Ongoing

We received notification that Globacom (621/50) from Nigeria (NG) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00949419

Feb 7, 02:38 PST
Resolved - Start Time: 01:04AM PST - 02/07/25
End Time: 04:35AM PST - 02/07/25

We received notification that the network issues previously reported by ATM Mobilis (603/01) from Algeria (DZ) have been resolved. ATM Mobilis (603/01) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF00949388

Feb 7, 04:37 PST
Investigating - Start Time: 01:04AM PST - 02/07/25
End Time: Ongoing

We received notification that ATM Mobilis (603/01) from Algeria (DZ) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF00949388

Feb 7, 02:00 PST
Feb 6, 2025
Resolved - Start Time: 3:51 PM PST - 2/6/25
End Time: 4:47 PM PST - 2/6/25

We received notification that the network issues previously reported by Dominican Republic (DO) - Compania Dominicana de Telefonos S.A. (CLARO GSM) (370/02) from Dominican Republic (DO) have been resolved. Dominican Republic (DO) - Compania Dominicana de Telefonos S.A. (CLARO GSM) (370/02) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00949109

Feb 6, 17:04 PST
Investigating - Start Time: 3:51 PM PST - 2/6/25
End Time: Ongoing

We received notification that Dominican Republic (DO) - Compania Dominicana de Telefonos S.A. (CLARO GSM) (370/02) from Dominican Republic (DO) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00949109

Feb 6, 15:55 PST
Resolved - Date: 02/06/2025
Start Time: 05:40 AM PST
End Time: 11:29 AM PST

We received notification from our partner that previously noticed Phone ID Contact problem has been resolved. You should no longer experience delays as all services are back to functioning properly.

Feb 6, 11:59 PST
Investigating - We have received notification that services for Phone ID Contact are experiencing delays. We will inform you as soon as we receive a resolution.
Feb 6, 06:53 PST
Completed - The scheduled maintenance has been completed.
Feb 6, 05:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 19:00 PST
Scheduled - Issue: Planned Maintenance -United States - T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830)

Start Time: 07:00 PM PDT - 02/05/25
End Time: 05:00 AM PDT - 02/06/25

Summary:
We received notification that T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) from United States will perform planned maintenance on the date and time specified above.
SMS messages to T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00947077

Feb 3, 16:25 PST
Completed - The scheduled maintenance has been completed.
Feb 6, 00:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 5, 20:00 PST
Scheduled - Issue: Planned Maintenance - Canada

Start Time: 08 PM PST - 02/05/25
End Time: 12 AM PST - 02/06/25

Summary:

We received notification that the SMS carrier partner from Canada will perform planned maintenance on the date and time specified above.

During this time period, customers with DSC that send SMS messages to Multiple Operators users may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00947791

Feb 5, 20:00 PST
Feb 5, 2025
Resolved - Start Time: 10:27 PM PST - 02/04/25
End Time: 06:38 AM PST - 02/05/25

We received notification that the network issues previously reported by Telefonica Celular S.A (CELTEL) from Honduras (HN) have been resolved. Telefonica Celular S.A (CELTEL) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00947960

Feb 5, 07:43 PST
Investigating - Start Time: 11:27 PST - 02/04/25
End Time: Ongoing

We received notification that Telefonica Celular S.A (CELTEL) (708/02) from Honduras (HN) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00947960

Feb 5, 01:01 PST
Completed - The scheduled maintenance has been completed.
Feb 5, 05:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 4, 19:00 PST
Update - We will be undergoing scheduled maintenance during this time.
Feb 3, 19:29 PST
Scheduled - Issue: Planned Maintenance - United States (US) - T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830)

Start Time: 08:00 PM PST - 02/04/25
End Time: 05:00 AM PST - 02/05/25

Summary:
We received notification that T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) from United States (US) will perform planned maintenance on the date and time specified above.
SMS messages to T-MOBILE (310/023;024;025;026;053;120;160;200;210;220;230;240;250;260;270;310;490;530;580;660;770;800;830) during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00947064

Feb 3, 19:24 PST
Resolved - Start Time: 11:01 PM PST - 02/04/25
End Time: 01:20 AM PST - 02/05/25

We received notification that the network issues previously reported by Airtel operators have been resolved. End users of Airtel operators should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00948008

Feb 5, 02:26 PST
Investigating - Start Time: 11:01 PM PST - 02/04/25
End Time: Ongoing

We received notification that Airtel operators is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

Feb 4, 23:16 PST
Resolved - Start Time: 08:44 PM PST - 02/04/25
End Time: 01:20 AM PST - 02/05/25

We received notification that the network issues previously reported by Robi Axiata (Airtel) (470/02;06;07) from Bangladesh (BD) have been resolved. Robi Axiata (Airtel) (470/02;06;07) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00947903

Feb 5, 02:12 PST
Investigating - Start Time: 08:44 PM PST - 02/04/25
End Time: Ongoing

We received notification that Robi Axiata (Airtel) (470/02;06;07) from Bangladesh (BD) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF00947903

Feb 4, 20:46 PST
Completed - The scheduled maintenance has been completed.
Feb 5, 00:00 PST
Scheduled - Starting October 17, 2024, The Campaign Registry (TCR) is launching a new brand identity verification process called Authentication+ to prevent fraud like impersonation, smishing, and spoofing. This will apply first to all brands with a Public Profit entity type. The process includes Two-Factor Authentication (2FA) as part of the brand registration. Future updates will expand support for additional entity types, and it will also lay the groundwork for RCS verification.

What You Need to Know:
Public Profit brands must complete a new 2FA step during registration starting October 17, 2024.
A 2FA email will be sent to the "Brand Contact Email" with a link and PIN code.
The brand contact must provide their first name, last name, job title, and the PIN from the email to complete the verification.
Once verified, the brand will be marked as VERIFIED and can create 10DLC campaigns.

Important Deadlines:
If the 2FA email link is not used within 7 days, you can request a new email. The verification must be completed within 30 days or the brand will become "unverified," requiring a new registration.
Existing Public Profit brands must update their brand contact email and complete the 2FA process by October 17, 2024, to avoid losing the ability to register new campaigns.
Current active campaigns won't be affected immediately, but a future deadline will be announced for compliance.

Make sure to complete the verification by the October 17 deadline to avoid any disruptions

Feb 4, 00:21 PST
Completed - The scheduled maintenance has been completed.
Feb 5, 00:00 PST
Scheduled - Effective December 1st, UAE mobile network operators Du and Etisalat have introduced mandatory Sender ID registration fees.

Key Details:
• Setup Fee: $80 per network (total $160 for both networks).
• Monthly Fee: $40 per network (total $80 for both networks).
For New Sender IDs:
• Both the setup fee and monthly fee will apply.
For Existing Registered Sender IDs:
• Only the monthly fee will apply.

Please ensure your Sender ID registration is up to date to avoid disruptions.

Thank you for your understanding.

Feb 4, 23:56 PST
Feb 4, 2025
Completed - The scheduled maintenance has been completed.
Feb 4, 23:58 PST
Scheduled - We want to inform you of a regulatory change in Kazakhstan that prohibits all promotional gambling traffic. This includes advertisements for electronic casinos, internet casinos, and any form of gambling or betting activities, as per the Law of the Republic of Kazakhstan.

What’s Allowed:
While promotional gambling traffic is banned, OTP (One-Time Password) traffic for gambling and betting companies is still permitted.

Thank you for your attention to this important update.

Feb 4, 23:55 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:57 PST
Scheduled - Sender ID registration is now mandatory for the Romanian network Telekom Romania (Cosmote).

Registration Requirements:
To register a Sender ID, you will need to provide:
• Sender ID
• Company Name
• Message Sample
• URL
• Letter of Authorization (LOA)

Important Notes:
• Case-Sensitivity: Sender IDs are case-sensitive. For example, "Alpha" and "ALPHA" are treated as distinct Sender IDs.
• Generic Sender IDs: Generic terms (e.g., "Info" or "Support") are not allowed.
• Numeric Sender IDs: Registration of numeric Sender IDs is not permitted.
• No Fees: Registration is free of charge.
• Bulk Requests: If you need to register multiple Sender IDs, a single document can be submitted containing all the required details for each Sender ID.

Please ensure compliance with these requirements to avoid disruptions in message delivery.

Thank you for your cooperation.

Feb 4, 23:53 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:56 PST
Scheduled - Attention to all customers using operators in Finland! Effective immediately, a URL whitelisting requirement is now in place for all messages containing URLs.

URL Whitelisting Requirement:

Company name:
Provide the complete message content.
Include the exact URL link. If the URL is dynamic, please specify and ensure the domain URL is whitelisted (example: https://www.telesign.com/). Note that URL shorteners are not permitted.

Thank you for your cooperation in adhering to this new requirement.

Feb 4, 23:52 PST
Resolved - Start Time: 8:46 PM PST - 2/4/25
End Time: 10:46 PM PST -2/4/25

We received notification that the network issues previously reported by Orange (Transmisiones y Proy.) (370/01) from Dominican Republic (DO) have been resolved. Orange (Transmisiones y Proy.) (370/01) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF00947905

Feb 4, 23:54 PST
Investigating - Start Time: 8:46 PM - 2/4/25
End Time: Ongoing

We received notification that Dominican Republic (DO) - Orange (Transmisiones y Proy.) (370/01) from Dominican Republic (DO) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00947905

Feb 4, 20:54 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:53 PST
Scheduled - Attention all users of the Russia - Sberbank(250/50) network! Mandatory Sender ID registration is now in effect.

Here's what you need to know:

1. Due Date for Applications: The operator requires all Sender ID (SID) submissions by the 20th of each month. SIDs submitted by this deadline will be activated on the 1st of the following month. Any submissions after the 20th of the current month will be processed for activation in the month after the next.
2. No Monthly SID Fee: Good news! Starting this month, there will be no monthly fee for registered SIDs.

To register your Sender ID, the details below are required:

- Sender ID
- Message Sample
- Company Name
- Company Website
- Company Business Category
- Tax ID

Please note that generic senders are not permitted. If you need to register new sender IDs, kindly submit a request.

Thank you for your cooperation!

Feb 4, 23:50 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:53 PST
Scheduled - To enhance compliance with Taiwan’s latest messaging regulations, whitelisting both URLs and phone numbers in message content is now required for all operators in Taiwan. Please review the updated registration process below to ensure uninterrupted message delivery.


How to Register URLs and Phone Numbers for Messaging in Taiwan

To register URLs or phone numbers included in your message content, provide the following details:
1 • Brand Legal Entity Name: The official name of your company or entity.
2 • Entity Registration Number: The registered business number of your organization.
3 • Entity Website: The official website of your company or entity.
4 • Entity Contact Number: A primary contact number.
5 • Message Templates: Examples of message content containing the URLs and/or phone numbers you wish to register.

Submission Notes for URLs and Phone Numbers:

• Each URL must be submitted separately.
• Sub-domains must be registered independently (e.g., www.battle.net, s.battle.net).
• Dynamic URLs and URL shorteners are not allowed.
• Only URLs owned by your entity are eligible for registration.
• Any phone numbers included in your message content must also be registered.


***Compliance Reminder

Messages containing unregistered URLs and/or phone numbers will not be delivered. Please ensure all relevant details are submitted alongside your message templates to avoid disruptions.
At this time, no delivery issues have been reported related to this regulation.

We appreciate your cooperation as we align with these updated requirements.

Feb 4, 23:49 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:36 PST
Scheduled - We have crucial update regarding upcoming changes mandated by the Malaysian Communications and Multimedia Commission (MCMC) that could impact your service. These changes will restrict the content of messages, prohibiting the inclusion of URLs and phone numbers.

Key dates and information:

- Starting June 1, 2024: Changes will be implemented affecting how certain services are accessed through Malaysian operators.
- Transition Period: A three-month transition period has been allocated for Telcos to fully implement these changes. This gives you ample time to smoothly adapt to the new system and make necessary content adjustments.
- Whitelisting Process: During this transition, traffic containing URLs and phone numbers can still be whitelisted, ensuring they are delivered. This measure will be in place until August 31, 2024.
- Post-Transition: After August 31, 2024, any traffic with URLs and phone numbers in the content will be blocked, including messages that were previously whitelisted. Please use the transition period effectively for content adjustments.

Thank you for your cooperation and understanding.

Feb 4, 23:29 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:26 PST
Scheduled - We would like to inform you about the latest TRAI directive dated 20th August 2024 on CTA (Call To Action) whitelisting (URL/OTT URL/APK/Callback number), aimed at preventing the misuse of Headers and Content Templates.

- The TRAI rule will impact only the local traffic of India to India and for the Indian Brands who are sending the domestic traffic.

- The Brand owners (Local Entities) are required to complete the URL whitelisting procedure through the DLT portal if their template contents (message text) contain any URLs, OTT links, APKS or callback numbers, regardless of whether they are static or dynamic.


***For your convenience, the entire clause from the Direction is provided below:***

Now, therefore, on holistic review of the implementation related issues raised by the Access Providers, the Authority, in exercise of the powers conferred upon it under section 13, read with sub-clauses (i) and (v) of clause (b) of sub-section (1) of section 11, of the Telecom Regulatory Authority of India Act, 1997 (24 of 1997) and the provisions of the Telecom Commercial Communications Customer Preference Regulations, 2018 (6 of 2018) and in partial modification of Direction No. D-27/1/(2)/2024-Q0S (E-13563) dated the 20th August 2024, hereby directs all the Access Providers to ensure that the traffic containing URLs/ APKS/ OTT links, which are not whitelisted, is not permitted with effect from the 1* October, 2024; 7.

(c) as far as the implementation of call back numbers is concerned, it requires further deliberation among Access Providers;

6. The revised timelines for implementation of call back numbers shall be fixed separately;

Additionally, please be informed that the URLs/OTT URLs/APK/Callback whitelisting capabilities have been recently fully developed and are operational on all DLT portals. Operators are also routinely communicating this information to all of their DLT registered entities.

To ensure compliance, kindly verify and whitelist all your message templates containing URLs/OTT URLs/APK/Callback numbers on the DLT portal.

In an effort to streamline the process, we have included the CTA Whitelisting User Manual and an FAQ document for various operators.
******************************************
Further important clarification on CTA Whitelisting given by the Operators:
• Whitelist all your URLs/APK files/OTT links/Callback Numbers that will be sent as part of the variable or static in the actual SMS.
• You can whitelist either the complete URL or a dynamic URL up to the domain name.
• For URLs with both static and dynamic parts, register the static part of the URL.

For Long / Static URL: While scrubbing the message, TSPs will ensure full match with the long/ static URLs whitelisted. No redirection is permitted from these long URLs.
For Long with Dynamic URL:
No redirection is permitted.
The Dynamic URL must end with query parameter (?).
Messages with dynamic path will NOT be allowed, unless they end in query parameter (?).

Whitelist Short URL –
If a PE intends to use URL shortening in their message content, then they must associate an Active Header with domain of URL Shortening service provider and whitelist the same.
e.g https://t.jio/JIODLT where JIODLT is a registered header of the PE
https://bit.ly/ABCDBK/ where ABCDBK is a registered header of the PE
Similar rules are applicable for Social Media links (e.g. wa.me, fb.me, ig.me, etc.)
Whitelisting of URL should begin with only and only http or https (for Static and Dynamic) and shorten URL should begin with only http or https.
During submission, only https or https will be acceptable.
Whitelist Short Codes –
We have Introduced the option for whitelisting “Short Code” under “Number” -> "Toll-Free"
e.g. – 1909, 100, 121
Short Codes will be allowed ranging from 3 to 6 digits


Please note that CTA whitelisting is mandatory; failure to whitelist any URLs whether in variable or static content registered in your templates will result in blocked messages to your customers starting October 1, 2024.

Feb 4, 23:22 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:21 PST
Scheduled - Shared Sender IDs are no longer permitted in Singapore.

What Does This Mean?

*Telesign's Role:
As a participating aggregator with Singapore's IMDA (Infocomm Media Development Authority), Telesign is authorized to provide the generic shared Sender ID "Likely-SCAM" for SMS traffic directed to Singapore users.
No other shared generic Sender IDs are permitted.

*Impact on Unregistered Sender IDs:
Telesign does not expect delivery errors, but any unregistered Sender IDs will automatically be replaced with "Likely-SCAM" (For more details on this regulation, visit this Status Page: https://status.telesign.com/incidents/n6z5wkq0xpm5)

*Action Steps:

1. Register Your Sender ID:
We strongly recommend registering your Sender ID with IMDA to avoid your messages being labeled as "Likely-SCAM".
--- Organizations can register their Sender IDs through the SSIR portal (https://smsregistry.sg/web/login).
--- Visit the SSIR website (https://www.sgnic.sg/smsregistry/overview);
FAQ page (https://www.sgnic.sg/faq/sms-sender-id-registry);
Rules of Registration (https://www.sgnic.sg/smsregistry/rules-of-registration) for more information.
--- Check your Sender ID registration status via the SSIR portal or through your SSIR admin account holder.

2. Notify Telesign:
Once your Sender ID registration is complete, notify Telesign to adjust your Sender ID settings and ensure your messages are not flagged as "Likely-SCAM."
--- Submit a request through our client portal at Telesign Login (https://my.telesign.com/login) or Telesign Signup (https://portal.telesign.com/signup).
--- For additional help, review the Telesign Portal User Guide (https://support.telesign.com/s/article/Telesign-Portal-User-Guide).


Thank you for your attention to this important update.

Feb 4, 23:18 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 23:21 PST
Scheduled - We’d like to inform you of important compliance requirements issued by the Telecom Regulatory Authority of India (TRAI) to address unauthorized activities and ensure the proper use of telecom resources.


Key Updates

- New Requirement for Principal Entities (PE) on DLT Portals
All Principal Entities (PE) must now declare their associated Telemarketers (TM), Aggregators (TMA), and Delivery Telemarketers (TMD) on DLT portals. This is referred to as the PE-TM Binding setup and is crucial for maintaining end-to-end communication visibility.

- Scope of Regulation
This requirement applies to local traffic within India.

- Non-Compliance Impact
Any message with an undefined or incomplete telemarketer chain will be rejected by India Telecom Service Providers (TSPs).

- Effective Date
The regulation will take effect on December 1, 2024, and will be enforced across all Indian TSPs.


What You Need to Do

If you handle local traffic through Telesign, please ensure compliance by working with us to set up the PE-TM Binding.
- Contact your Customer Success Manager (CSM) or reach out to our Support Team at support@telesign.com to initiate the process.
- For more detailed information about India DLT requirements, please refer to this article: https://support.telesign.com/s/article/India-DLT-Update.


We’re here to help ensure a smooth transition to compliance. Please don’t hesitate to reach out if you have any questions or need assistance.

Feb 4, 23:15 PST
Resolved - Start Time: 09:03PM PST - 02/04/25
End Time: 09:59PM PST - 02/04/25

We received notification that the network issues previously reported by PT. XL Axiata Tbk (510/11;08) from Indonesia (ID) have been resolved. PT. XL Axiata Tbk (510/11;08) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00947920

Feb 4, 22:27 PST
Investigating - Start Time: 09:53PM PST - 02/04/25
End Time: Ongoing

We received notification that PT. XL Axiata Tbk (510/11;08) from Indonesia (ID) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00947920

Feb 4, 21:08 PST
Resolved - This incident has been resolved.
Feb 4, 20:31 PST
Update - We are continuing to work on a fix for this issue.
Jan 21, 00:37 PST
Identified - As the Lunar New Year approaches, Vietnam operators have shared important updates regarding their holiday freeze period. Please review the key details below to ensure uninterrupted service:

Freeze Period:
- Starts: January 25th
- Ends: February 2nd

Registration Deadlines:
- Submit Sender ID Registrations by: January 23rd
This ensures your submissions reach the operators before the freeze begins.

Registration Resumption:
- Normal processing will resume on February 3rd.

During the freeze period, you may still submit new Sender ID registration requests; however, they will only be processed by operators after the freeze ends.

We appreciate your understanding and cooperation during this time.

Jan 20, 23:16 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 20:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 4, 14:00 PST
Scheduled - Start Date: 02/04/25
Start Time: 02:00 PM PST

End Date: 02/05/25
End Time: 08:00 PM PST

We have been informed that one of our partners in the United Kingdom will conduct planned maintenance at the specified date and time. Customers using the Phone ID (contat_match, number_deactivation, sim_swap, call_forward_detection, age_verify) during this maintenance period may experience temporary delays. We recommend planning accordingly.

If you have any questions, please contact us at support@telesign.com.

Jan 31, 02:08 PST
Resolved - Start Time: 03:56 PM PST - 02/04/24
End Time: 05:06 PM PST - 02/04/24

We received notification that the network issues previously reported by ATM Mobilis (603/01) from Algeria (DZ) from Algeria (DZ) have been resolved. ATM Mobilis (603/01) from Algeria (DZ) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00947755

Feb 4, 17:25 PST
Investigating - Start Time: 03:56 PM PST - 02/04/24
End Time: Ongoing

We received notification that ATM Mobilis (603/01) from Algeria (DZ) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00947755

Feb 4, 16:00 PST
Resolved - We received notification that the issue previously noticed in Philippines affecting Phone ID Subscriber Status and Number Deactivation has been resolved. End users should no longer experience delays, as all services are back to functioning properly.
Feb 4, 06:05 PST
Update - We are continuing to investigate this issue.
Feb 4, 02:35 PST
Investigating - We have received notification that services for Phone ID Subscriber Status and Number Deactivation in Philippines is experiencing delays. We will inform you as soon as we receive a resolution.
Feb 4, 02:34 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 04:15 PST
Scheduled - To ensure accurate identification of brands and applications in messages sent to mobile subscribers, Viettel requests that you take additional measures to clearly display brand names and application names in the content of international A2P SMS.

Effective Date: June 17th, 2024

Viettel will implement blocking measures for all traffic without brandname/appname since 1st July 2024. To ensure compliance with the new regulations, please proceed with registering your new templates.

Thank you for your cooperation.

Feb 4, 02:55 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 04:00 PST
Scheduled - Key Updates:
• New Requirement for OTP SMS: All OTP (One-Time Password) SMS messages must now include the brand/service/program/community name within the message content. At this point, this regulation applies only to OTP (One-time passcode) messages and does not extend to other types of content such as ARN (Alerts, Reminders, Notifications) or MKT (Marketing).
• Applicable to All Traffic: This regulation applies to both local and international traffic as well as Sender IDs.
• Non-Compliance Impact: Non-compliant traffic will result in Sender ID blockage. To restore service, the Sender ID must be re-registered. Currently, no Sender ID blockages have been reported at Telesign.
• Effective Date: This regulation is now in effect as per the operator’s announcement.

What You Need to Do:
• Review and Update OTP (One-Time Password) Message Content:
Please ensure that your OTP messages include the required brand/service/program/community name to comply with the new regulation.
• If You Encounter Delivery Issues:
If you notice that your Sender ID is experiencing delivery issues for OTP messages in Indonesia, please contact Telesign Support immediately. Our team will investigate the issue, and if it’s related to this regulatory update, please be aware that we may need to re-register your Sender ID with the updated brand name content.
o Note: Registration in Indonesia can take approximately 3-4 weeks, so your patience is appreciated during this process

Best Practice Recommendation:
To comply with the new regulation and avoid Sender ID blockage, we recommend that you include your brand name at the start of every OTP message. This means your OTP message should begin with your company's name followed by the actual OTP code. For example, if your company is called "ABC Services," your OTP message should look like this:
ABC Services: Your OTP is 123456.
This structure helps ensure that your message complies with the operator's requirements by clearly identifying the brand at the beginning of the message.

Thank you for your cooperation. For any questions, please feel free to contact support@telesign.com.

Feb 4, 02:53 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 03:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 3, 21:00 PST
Scheduled - Issue: Planned Maintenance -United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670)

Start Time: 09:00pm PST- 02/03/24
End Time: 03:00am PST- 02/04/24

Summary:
We received notification that ATT Mobility from United States (US) will perform planned maintenance on the date and time specified above.
SMS messages to ATT Mobility during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.

If you have any questions, please contact support@telesign.com.

SF 00945929

Jan 31, 13:23 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 02:01 PST
Scheduled - URL whitelisting is now mandatory for Viettel operator in Vietnam. At this time, there are no delivery issues related to URL blocking.

URL Whitelisting Requirements:
- Sender ID
- Message content
- Exact URL link (please indicate if the URL is dynamic and include the domain used in URLs, e.g., https://abc.abc/...)

To comply with new regulations, please ensure that your URL is registered along with your Sender ID and message templates when submitting them for Vietnam. Messages containing unregistered URLs will not be delivered to Viettel subscribers starting in September.

Thank you for your cooperation with these new requirements.

Feb 4, 00:50 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 02:00 PST
Scheduled - The US Short Code Registry and CTIA are introducing new requirements for short code leasing. Here’s what you need to know:

KEY DATES:
October 15, 2024: New Brand Fields will be required for all new short code leases.
January 15, 2025: New Brand Fields will be required for existing short codes.

NEW REQUIREMENTS
Vetting Process:
All brands must undergo a vetting process before a short code can be leased or extended. The US Short Code Registry will complete the vetting process to confirm the brand details provided during the short code lease request.

Leasing Eligibility:
Leasing will only be approved after a successful brand vetting result.

WHAT YOU NEED TO DO:
For customers with existing or new short code requests in the US, additional information must be collected as soon as possible to ensure compliance:

1) Legal Company Name (matching the legally registered name)
Legal Entity Type (select one):
> Corporation
> Limited Liability Corporation (LLC)
> Partnership
> S Corporation
> Sole Proprietorship
>Other (please specify)

2) Doing Business As (DBA) – Optional, if applicable
3) Stock Market Symbol – If publicly traded
4).Country of Registration (or State of Incorporation, if applicable)
5) Federal Tax ID (must match the Legal Organization Name registered with the IRS, found in the EIN Confirmation Letter)
6) Legal Organization Address (Street Address, City, State/Province, Zip/Postal Code, Country – this must match the company’s legally registered address)
7) Organization Point of Contact (POC) – First and Last Name, Phone Number, Email Address (email domain must match the Legal
9) Organization Name to avoid vetting issues)
10) DUNS, GIIN, or LEI (if applicable)

ENSURE ACCURACY
Please verify that all submitted information is accurate to avoid delays in leasing or renewing your short code.

Feb 4, 00:47 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 01:45 PST
Scheduled - Brazilian law 14.790/2023 has officially regulated the operation of fixed-odds betting, commonly known as BETS.

Key Points:
Authorization Requirement:
All fixed-odds betting companies that have not yet requested authorization from the Ministry of Finance (MF) must suspend operations nationwide starting October 1, 2024, until they receive permission from the Ministry's Secretariat of Prizes and Betting (SPA).

Temporary Operating Period:
From October 2024 to the end of December 2024, only betting companies that have already applied for authorization to engage in fixed-odds betting may continue to operate. Companies that have not applied will be classified as illegal until they secure authorization.

Final Deadline:
The deadline for obtaining full authorization is December 31, 2024. After that, companies that have not received approval will be unable to operate legally.

Starting January 2025:
Only companies that fully comply with Law No. 13,756/2018, Law No. 14,790/2023, and all relevant regulatory ordinances will be allowed to operate. Approved companies will also need to pay a R$30 million fee and comply with regulations related to fraud prevention, anti-money laundering, and advertising restrictions.

SMS Traffic Impact:
Betting companies will require government authorization to send SMS traffic. Unauthorized companies will not be allowed to transmit SMS messages.

Timeline:
October 1, 2024:
Only betting companies that have applied for authorization can continue operations. All others will be classified as illegal.

By December 2024:
The Ministry of Finance is expected to complete the review of initial authorization requests.

January 1, 2025:
The regulated betting market in Brazil officially begins. Only fully authorized companies can operate under the new regulations.

For more information, please ensure compliance with Law No. 14,790/2023, and stay updated with the Ministry of Finance’s guidelines.

Feb 4, 00:41 PST
Completed - The scheduled maintenance has been completed.
Feb 4, 00:50 PST
Scheduled - Attention valued customers! As of January 31, 2024, regulatory changes will take effect. Currently, you are able to send messages through pending toll-free phone numbers, provided they adhere to existing industry-wide sending limits. However, starting January 31, 2024, messages originating from toll-free phone numbers still in the pending verification process will be blocked.

In anticipation of these changes, we kindly request you to keep in mind the importance of the dates mentioned. We appreciate your understanding and cooperation as we navigate this transition.

Feb 4, 00:38 PST
Feb 3, 2025
Completed - The scheduled maintenance has been completed.
Feb 3, 15:15 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 3, 14:00 PST
Scheduled - Date: 02/03/25
Start Time: 02:00 PM PST
End Time: 03:15 PM PST

We have been informed that one of our partners in the United Kingdom will conduct planned maintenance at the specified date and time. Customers using the Phone ID (contat_match, number_deactivation, sim_swap, call_forward_detection, age_verify) during this maintenance period may experience temporary delays. We recommend planning accordingly.

If you have any questions, please contact us at support@telesign.com.

Jan 27, 03:51 PST
Resolved - Start Time: 07:52 AM PST - 02/03/25
End Time: 08:10 AM PST - 02/03/25

We received notification that the network issues previously reported by Personal GSM 1900 (722/02;020;34;034;340;341;36;036) from Argentina (AR) have been resolved. Personal GSM 1900 (722/02;020;34;034;340;341;36;036) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00946881

Feb 3, 08:17 PST
Investigating - Start Time: 07:52 PST - 02/03/25
End Time: Ongoing

We received notification that Personal GSM 1900 (722/02;020;34;034;340;341;36;036) fromArgentina (AR) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00946881

Feb 3, 07:57 PST
Resolved - Start Time:: 04:54 AM PST - 02/03/25
End Time: 06:40 AM PST - 02/03/25

We received notification that the network issues previously reported have been resolved.The End users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF[00946729]

Feb 3, 06:43 PST
Investigating - Issue: United States (US) Multiple Operators 10DLC Quality degradation

Start Time: 04:54 AM PST - 02/03/25
End Time: Ongoing

Summary:

We currently experience quality degradation toward United States for 10DLC traffic only.
SMS messages sent with 10DLC SID may face delays or difficulties in delivery.

Telesign is engaged with carrier partners for updates on resolution. We'd like to apologize for any inconvenience and appreciate your patience during this service interruption.

If you have any questions, please contact support@telesign.com.

SF 00946729

Feb 3, 04:58 PST
Resolved - Start Time: 12:10AM PST - 02/03/25
End Time: 03:10AM PST - 02/03/25

We received notification that the network issues previously reported towards United Arab Emirates (AE) have been resolved. End users should no longer experience delays in receiving Voice and Voice API transactions as all services are back to functioning properly.

SF 00946591

Feb 3, 04:47 PST
Investigating - Start Time: 12:10AM PST - 02/03/25
End Time: Ongoing

Summary:

We received notification that ALL mobile network operators from United Arab Emirates (AE) are currently experiencing network issues, and this may cause a latency in Voice and Voice API transactions. We will inform you once the operator has come to a resolution.
If you have any questions, please contact us at support@telesign.com.

SF 00946591

Feb 3, 01:00 PST
Feb 2, 2025
Resolved - Start Time: 7:10 PM PST - 02/02/25
End Time: 8:30 PM PST - 02/02/25

We received notification that the network issues previously reported by Smart Communications (515/03;05;18) from Philippines (PH) have been resolved. Smart Communications (515/03;05;18) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF - 00946494

Feb 2, 20:31 PST
Update - We are continuing to investigate this issue.
Feb 2, 19:13 PST
Investigating - Start Time: 7:10 PM PST - 02/02/25
End Time: Ongoing

We received notification that Smart Communications (515/03;05;18) from Philippines (PH) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF - 00946494

Feb 2, 19:13 PST
Resolved - Start Time: 7:55 AM PST - 02/02/25
End Time: 9:17 AM PST - 02/02/25

We received notification that the network issues previously reported by Nepal Mobile (Nepal Telecom) (429/01;03) from Nepal (NP) have been resolved. Nepal Mobile (Nepal Telecom) (429/01;03) end users should no longer experience delays receiving SMS messages as all services are back to functioning properly.

SF 00946372

Feb 2, 10:14 PST
Investigating - Start Time: 7:55 AM PST - 02/02/25
End Time: Ongoing

We received notification that Nepal Mobile (Nepal Telecom) (429/01;03) from Nepal (NP) is currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operator has come to a resolution.

SF 00946372

Feb 2, 07:59 PST
Feb 1, 2025

No incidents reported.