Telesign system Status
Real-time updates of Telesign system issues and outages
Telesign system status is Operational
SMS
Voice
PhoneID
Score
App Verify
Developer Portal
2-Way SMS
Active Incidents
Issue: Planned Maintenance - United States (US) - T-MOBILE
Start Time: 12/15/2024 9:00 PM PST End Time: 12/16/2024 03:00 AM PST
Summary: We received notification that T-MOBILE from United States (US) will perform planned maintenance on the date and time specified above. SMS messages to T-MOBILE 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 00923365
📢 Important Announcement: Temporary Freeze on SID Registrations in Mexico
We have been informed by Telcel and Movistar that they have temporarily paused the processing of SID registration requests (both Alpha and Numeric). Please note the following:
Ongoing Requests: Registrations submitted prior to this announcement are still being processed. Reason for the Freeze: The networks are currently updating their internal policies and implementing new system procedures.
Resumption Timeline: The date for resuming SID registrations: January 8, 2025
We appreciate your patience and understanding during this period of adjustment.
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.
Start Time: 11:42 PM PST - 12/05/24 End Time: Ongoing
We received notification that Pegaso PCS. (Movistar) from Mexico (MX) 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 00919906
We’d like to inform our valued customers about the upcoming holiday freeze period announced by the Romanian network RCS & RDS DigiMobil (226/05):
• 🗓 Freeze Period: December 20th, 2024 – January 7th, 2025 • 📌 Important Deadline: o To ensure registrations are processed before the freeze, please submit requests by December 17th, 2024. o Any requests submitted after this date will be processed after the freeze ends.
We appreciate your understanding and cooperation during this time as we work to align with network schedules.
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.
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.
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.
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.
Issue: US/CA Operator - Verizon Wireless (310/004;006;010;012;590) Quality degradation
Start Time: 10:15 AM PST - 11/20/24
Summary:
We currently experience quality degradation toward United States (US) - Verizon Wireless (310/004;006;010;012;590). SMS messages to this operator 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 00911065
Issue: Planned Maintenance - United States (US) - T-MOBILE
Start Time: 11:00 PM PST 11/19/2024 End Time: 02:00 AM PST 11/20/2024
Summary:
We received notification that the SMS carrier partner from United States (US) - T-MOBILE will perform planned maintenance on the date and time specified above.
During this time period, customers with DSC, DLC, 2-way, 1-way that send SMS messages to T-MOBILE 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 00909808
AT&T Freeze Schedule
Short Codes Only: November Freeze Dates – No Provisioning >11/26 to 12/02 (Black Friday / Cyber Monday) >Provisioning will take place on 11/25 >Post-freeze provisioning on 12/09/2024 December Freeze Dates – No Provisioning >12/23/24 to 01/03/25 (Christmas and New Years Holidays) >Provisioning will take place on 12/16 >Provisioning will NOT take place on 12/23 >Post-freeze provisioning on 01/06/2025
T-Mobile Freeze Schedule
Short Code Freezes: >Nov. 28, 2024 – Nov. 29, 2024 >Dec. 23, 2024 – Jan. 3, 2025** Please note that while campaigns won’t be certified during these dates, onboarding can proceed. Long Code Special Business Reviews (Messaging Volumes): >Nov. 28, 2024 – Nov. 29, 2024 >Dec. 24, 2024 – Dec. 25, 2024 >Jan. 1, 2025 NNID/Number Pool Provisioning Maintenance Windows: >Oct. 30, 2024 – Submit NNID/Number Pool Requests by 10/23 EOD >Nov. 13, 2024 – Submit NNID/Number Pool Requests by 11/6 EOD >Dec. 4, 2024 – Submit NNID/Number Pool Requests by 11/27 EOD* ***Please submit only business-critical requests during these dates.
Thank you for planning accordingly during these freeze periods to ensure a smooth holiday season.
New Zealand operators have announced the Christmas/New Year freeze period dates: Freeze Dates: The freeze will begin on December 6th and last until January 27th. Registration Deadline: To ensure that Short Code (SC) registrations are completed before the freeze, the last day to submit registrations is November 29th. Approvals/Activations Resumption: Short Code approvals and activations will resume on January 27th.
During the freeze period, you can still submit requests for new Short Codes. However, they will not be activated or approved until after the freeze ends on January 27th
Thank you for your understanding and cooperation during this time.
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
Issue: Brazil (BR) - Claro (724/05;12;38) - Quality degradation
Start Time: 09:45 PM PDT - 10/20/24 End Time: Ongoing
Summary:
We received notification that Claro (724/05;12;38) from Brazil 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 00895432
Planned maintenance: United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670)
Date: 10/20/24-10/21/24 Start Time: 8:00PM PDT 10/20/24 End Time: 2:00AM PDT 10/21/24
Summary: We received notification that ATT Mobility (310/016;030;150;170;280;380;410;670) 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.
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.
SF 00894640
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.
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
📢 Important Update: US Short Code Registry and CTIA New Requirements for Short Code Leasing
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.
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.
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:
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.
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.
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.
Issue: Planned Maintenance - Canada (CA) - Bell Mobility Inc
Start Time: 9 PM PDT 10/09/24 End Time: 3 AM PDT 10/10/24
Summary: We received notification that Bell Mobility Inc from Canada will perform planned maintenance on the date and time specified above. SMS messages to Bell Mobility Inc 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 00886474
Issue: Planned Maintenance - Canada (CA) - Bell Mobility Inc
Start Time: 10 PM PDT - 10/07/24 End Time: 3 AM PDT - 10/08/24
Summary: We received notification that Bell Mobility Inc from Canada will perform planned maintenance on the date and time specified above. SMS messages to Bell Mobility Inc 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 00886472
📢 Important Update: New Regulatory Direction for India LOCAL Traffic as issued by the Telecom Regulatory Authority of India (TRAI)
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;
- 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.
📢 Important Announcement: Annual Canadian Carrier Brownout Notice
The Canadian Carrier Brownout is an annual freeze period during which no new Short Codes or network updates to existing Short Codes (such as aggregator migrations or price point changes) are processed.
Please be aware of the updated timeline for the 2024-2025 Canadian Short Code provisioning:
Key Dates: To have your Short Code provisioned or migrated by all carriers before the freeze, applications must be submitted by Thursday, October 24, 2024, at 1:00 PM ET. Applications submitted by this deadline will be processed by participating carriers between November 12 – November 18, 2024. Any applications submitted after the October 24 deadline will be scheduled for provisioning in January 2025.
The Short Code Council will continue to meet throughout November and December to review applications for provisioning starting January 6, 2025, with Bell, Freedom, Rogers, and TELUS beginning provisioning on January 14, 2025.
Please note that applications will be processed on a first-come, first-served basis, and provisioning timelines may vary depending on the volume of submissions.
Thank you for your attention to these important deadlines.
Details: 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.
Start Time: 8AM PDT - 8/28/24 End Time: Ongoing
Summary:
We received notification that ALL mobile network operators from China are currently experiencing network issues, and this may cause a latency in Voice 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 00862573
Dear Customers and Partners,
We are experiencing instability on our platform with Phone ID Contact Addon, which could cause some delays.
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.
Due to recent changes in Chinese Telecom regulations, signature registrations will now only be supported for companies based in China. As a result, all non-local registered dedicated signatures will be replaced by the generic signature 【优速通】, 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 【优速通】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/wjfb/txy/art/2020/art_fbb560830ecd4f3eb983a844d31230a6.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.
Sender ID registration is now in place for the Cambodia - MetFone (456/08) network.
Details:
- One-time Setup Fee:
- Main provider: $20 per Sender ID
- To register with all providers: $40 per Sender ID
- No monthly fees
Required Information for Registration:
- Sender ID
- Company name
- Company website
- Message sample
Note: Generic senders are supported. If you wish to register new Sender IDs, please submit a request.
Thank you for your cooperation with this new requirement.
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Certificate pinning is not a best practice and is not explicitly supported by Telesign, which can cause outages. https://developer.telesign.com/enterprise/docs/authentication#tls-and-certificates
All Digicert Roots and Intermediate certificates can also be found and downloaded directly from their site: https://www.digicert.com/kb/digicert-root-certificates.htm#roots
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Start Time: 11:44 PM PDT - 06/20/24 End Time: Ongoing
We received notification that Communications Corporation (539/01) from Tonga (TO) 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 00837258
Recently Resolved Incidents
No recent incidents
Telesign system Outage Survival Guide
Telesign system Components
Telesign system Standard Services
SMS
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Issue: US/CA Operator - Verizon Wireless (310/004;006;010;012;590) Quality degradation
Start Time: 10:15 AM PST - 11/20/24
Summary:
We currently experience quality degradation toward United States (US) - Verizon Wireless (310/004;006;010;012;590). SMS messages to this operator 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 00911065
Voice
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Start Time: 8AM PDT - 8/28/24 End Time: Ongoing
Summary:
We received notification that ALL mobile network operators from China are currently experiencing network issues, and this may cause a latency in Voice 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 00862573
PhoneID
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Score
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
App Verify
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Developer Portal
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
2-Way SMS
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Issue: US/CA Operator - Verizon Wireless (310/004;006;010;012;590) Quality degradation
Start Time: 10:15 AM PST - 11/20/24
Summary:
We currently experience quality degradation toward United States (US) - Verizon Wireless (310/004;006;010;012;590). SMS messages to this operator 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 00911065
Telesign system Enterprise Services
SMS & SMS Verify
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Voice Verify
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Start Time: 8AM PDT - 8/28/24 End Time: Ongoing
Summary:
We received notification that ALL mobile network operators from China are currently experiencing network issues, and this may cause a latency in Voice 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 00862573
Smart Verify
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Push Verify
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
PhoneID Standard
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
PhoneID Contact
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
PhoneID Live
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
TelePortal
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Score
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
2-Way SMS
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Messaging
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
Telesign system Operator Alerts
Operator Alerts WW
Start Time: 11:44 PM PDT - 06/20/24 End Time: Ongoing
We received notification that Communications Corporation (539/01) from Tonga (TO) 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 00837258
Planned maintenance: United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670)
Date: 10/20/24-10/21/24 Start Time: 8:00PM PDT 10/20/24 End Time: 2:00AM PDT 10/21/24
Summary: We received notification that ATT Mobility (310/016;030;150;170;280;380;410;670) 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.
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.
SF 00894640
Issue: Brazil (BR) - Claro (724/05;12;38) - Quality degradation
Start Time: 09:45 PM PDT - 10/20/24 End Time: Ongoing
Summary:
We received notification that Claro (724/05;12;38) from Brazil 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 00895432
Issue: Planned Maintenance - United States (US) - T-MOBILE
Start Time: 11:00 PM PST 11/19/2024 End Time: 02:00 AM PST 11/20/2024
Summary:
We received notification that the SMS carrier partner from United States (US) - T-MOBILE will perform planned maintenance on the date and time specified above.
During this time period, customers with DSC, DLC, 2-way, 1-way that send SMS messages to T-MOBILE 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 00909808
Issue: US/CA Operator - Verizon Wireless (310/004;006;010;012;590) Quality degradation
Start Time: 10:15 AM PST - 11/20/24
Summary:
We currently experience quality degradation toward United States (US) - Verizon Wireless (310/004;006;010;012;590). SMS messages to this operator 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 00911065
Dear Customers and Partners,
We are experiencing instability on our platform with Phone ID Contact Addon, which could cause some delays.
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.
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.
Start Time: 8AM PDT - 8/28/24 End Time: Ongoing
Summary:
We received notification that ALL mobile network operators from China are currently experiencing network issues, and this may cause a latency in Voice 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 00862573
Issue: Planned Maintenance - Canada (CA) - Bell Mobility Inc
Start Time: 10 PM PDT - 10/07/24 End Time: 3 AM PDT - 10/08/24
Summary: We received notification that Bell Mobility Inc from Canada will perform planned maintenance on the date and time specified above. SMS messages to Bell Mobility Inc 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 00886472
Issue: Planned Maintenance - Canada (CA) - Bell Mobility Inc
Start Time: 9 PM PDT 10/09/24 End Time: 3 AM PDT 10/10/24
Summary: We received notification that Bell Mobility Inc from Canada will perform planned maintenance on the date and time specified above. SMS messages to Bell Mobility Inc 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 00886474
Start Time: 11:42 PM PST - 12/05/24 End Time: Ongoing
We received notification that Pegaso PCS. (Movistar) from Mexico (MX) 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 00919906
Issue: Planned Maintenance - United States (US) - T-MOBILE
Start Time: 12/15/2024 9:00 PM PST End Time: 12/16/2024 03:00 AM PST
Summary: We received notification that T-MOBILE from United States (US) will perform planned maintenance on the date and time specified above. SMS messages to T-MOBILE 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 00923365
Operator Alerts EMEA
Operator Alerts APAC
Start Time: 11:44 PM PDT - 06/20/24 End Time: Ongoing
We received notification that Communications Corporation (539/01) from Tonga (TO) 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 00837258
Start Time: 8AM PDT - 8/28/24 End Time: Ongoing
Summary:
We received notification that ALL mobile network operators from China are currently experiencing network issues, and this may cause a latency in Voice 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 00862573
Operator Alerts North America
Planned maintenance: United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670)
Date: 10/20/24-10/21/24 Start Time: 8:00PM PDT 10/20/24 End Time: 2:00AM PDT 10/21/24
Summary: We received notification that ATT Mobility (310/016;030;150;170;280;380;410;670) 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.
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.
SF 00894640
Issue: Planned Maintenance - United States (US) - T-MOBILE
Start Time: 11:00 PM PST 11/19/2024 End Time: 02:00 AM PST 11/20/2024
Summary:
We received notification that the SMS carrier partner from United States (US) - T-MOBILE will perform planned maintenance on the date and time specified above.
During this time period, customers with DSC, DLC, 2-way, 1-way that send SMS messages to T-MOBILE 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 00909808
Issue: US/CA Operator - Verizon Wireless (310/004;006;010;012;590) Quality degradation
Start Time: 10:15 AM PST - 11/20/24
Summary:
We currently experience quality degradation toward United States (US) - Verizon Wireless (310/004;006;010;012;590). SMS messages to this operator 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 00911065
Operator Alerts LATAM
Issue: Brazil (BR) - Claro (724/05;12;38) - Quality degradation
Start Time: 09:45 PM PDT - 10/20/24 End Time: Ongoing
Summary:
We received notification that Claro (724/05;12;38) from Brazil 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 00895432
Start Time: 11:42 PM PST - 12/05/24 End Time: Ongoing
We received notification that Pegaso PCS. (Movistar) from Mexico (MX) 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 00919906
Telesign system Regulatory Updates
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.
Dear Customers and Partners,
The SSL certificate for *.callback.telesign.com will soon expire. Our dedicated teams will work on certificate replacement from July 22nd to July 25th.
Certificate pinning is not a best practice and is not explicitly supported by Telesign, which can cause outages. https://developer.telesign.com/enterprise/docs/authentication#tls-and-certificates
All Digicert Roots and Intermediate certificates can also be found and downloaded directly from their site: https://www.digicert.com/kb/digicert-root-certificates.htm#roots
Thank you.
Please do not hesitate to contact us at support@telesign.com with any questions or concerns.
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
New Zealand operators have announced the Christmas/New Year freeze period dates: Freeze Dates: The freeze will begin on December 6th and last until January 27th. Registration Deadline: To ensure that Short Code (SC) registrations are completed before the freeze, the last day to submit registrations is November 29th. Approvals/Activations Resumption: Short Code approvals and activations will resume on January 27th.
During the freeze period, you can still submit requests for new Short Codes. However, they will not be activated or approved until after the freeze ends on January 27th
Thank you for your understanding and cooperation during this time.
Sender ID registration is now in place for the Cambodia - MetFone (456/08) network.
Details:
- One-time Setup Fee:
- Main provider: $20 per Sender ID
- To register with all providers: $40 per Sender ID
- No monthly fees
Required Information for Registration:
- Sender ID
- Company name
- Company website
- Message sample
Note: Generic senders are supported. If you wish to register new Sender IDs, please submit a request.
Thank you for your cooperation with this new requirement.
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.
Due to recent changes in Chinese Telecom regulations, signature registrations will now only be supported for companies based in China. As a result, all non-local registered dedicated signatures will be replaced by the generic signature 【优速通】, 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 【优速通】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/wjfb/txy/art/2020/art_fbb560830ecd4f3eb983a844d31230a6.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.
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.
Details: 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.
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.
📢 Important Announcement: Annual Canadian Carrier Brownout Notice
The Canadian Carrier Brownout is an annual freeze period during which no new Short Codes or network updates to existing Short Codes (such as aggregator migrations or price point changes) are processed.
Please be aware of the updated timeline for the 2024-2025 Canadian Short Code provisioning:
Key Dates: To have your Short Code provisioned or migrated by all carriers before the freeze, applications must be submitted by Thursday, October 24, 2024, at 1:00 PM ET. Applications submitted by this deadline will be processed by participating carriers between November 12 – November 18, 2024. Any applications submitted after the October 24 deadline will be scheduled for provisioning in January 2025.
The Short Code Council will continue to meet throughout November and December to review applications for provisioning starting January 6, 2025, with Bell, Freedom, Rogers, and TELUS beginning provisioning on January 14, 2025.
Please note that applications will be processed on a first-come, first-served basis, and provisioning timelines may vary depending on the volume of submissions.
Thank you for your attention to these important deadlines.
AT&T Freeze Schedule
Short Codes Only: November Freeze Dates – No Provisioning >11/26 to 12/02 (Black Friday / Cyber Monday) >Provisioning will take place on 11/25 >Post-freeze provisioning on 12/09/2024 December Freeze Dates – No Provisioning >12/23/24 to 01/03/25 (Christmas and New Years Holidays) >Provisioning will take place on 12/16 >Provisioning will NOT take place on 12/23 >Post-freeze provisioning on 01/06/2025
T-Mobile Freeze Schedule
Short Code Freezes: >Nov. 28, 2024 – Nov. 29, 2024 >Dec. 23, 2024 – Jan. 3, 2025** Please note that while campaigns won’t be certified during these dates, onboarding can proceed. Long Code Special Business Reviews (Messaging Volumes): >Nov. 28, 2024 – Nov. 29, 2024 >Dec. 24, 2024 – Dec. 25, 2024 >Jan. 1, 2025 NNID/Number Pool Provisioning Maintenance Windows: >Oct. 30, 2024 – Submit NNID/Number Pool Requests by 10/23 EOD >Nov. 13, 2024 – Submit NNID/Number Pool Requests by 11/6 EOD >Dec. 4, 2024 – Submit NNID/Number Pool Requests by 11/27 EOD* ***Please submit only business-critical requests during these dates.
Thank you for planning accordingly during these freeze periods to ensure a smooth holiday season.
📢 Important Update: New Regulatory Direction for India LOCAL Traffic as issued by the Telecom Regulatory Authority of India (TRAI)
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;
- 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.
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.
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:
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.
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.
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.
📢 Important Update: US Short Code Registry and CTIA New Requirements for Short Code Leasing
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.
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
We’d like to inform our valued customers about the upcoming holiday freeze period announced by the Romanian network RCS & RDS DigiMobil (226/05):
• 🗓 Freeze Period: December 20th, 2024 – January 7th, 2025 • 📌 Important Deadline: o To ensure registrations are processed before the freeze, please submit requests by December 17th, 2024. o Any requests submitted after this date will be processed after the freeze ends.
We appreciate your understanding and cooperation during this time as we work to align with network schedules.
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.
📢 Important Announcement: Temporary Freeze on SID Registrations in Mexico
We have been informed by Telcel and Movistar that they have temporarily paused the processing of SID registration requests (both Alpha and Numeric). Please note the following:
Ongoing Requests: Registrations submitted prior to this announcement are still being processed. Reason for the Freeze: The networks are currently updating their internal policies and implementing new system procedures.
Resumption Timeline: The date for resuming SID registrations: January 8, 2025
We appreciate your patience and understanding during this period of adjustment.
Telesign system Alternatives
User Authentication
We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
Machine to Machine Authentication
We are currently investigating an incident that impacted our services. Our team is actively working to understand the root cause and mitigate the issue. We will provide updates as we gather more information.
