System Status
This page offers API uptime information for Telesign services, in addition to incident history reports and service issues alerts.
Contact Match and Number Deactivation Scheduled Maintenance - United Kingdom Vodafone - 10/21/2024
Subscribe
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 21, 2024 - 15:00 PDT
Oct 21, 2024 - 15:00 PDT
Scheduled - Date: 10/21/2024
Start Time: 03:00 PM PDT
End Time: 08:15 PM PDT
We have been informed that one of our partners in United Kingdom will conduct planned maintenance on their connections to Vodafone carrier at the specified date and time. Customers using the Phone ID Contact Match and Number Deactivation during this maintenance period may experience temporary delays. We recommend planning accordingly.
If you have any questions, please contact us at support@telesign.com.
Oct 21, 2024 15:00-20:15 PDT
Start Time: 03:00 PM PDT
End Time: 08:15 PM PDT
We have been informed that one of our partners in United Kingdom will conduct planned maintenance on their connections to Vodafone carrier at the specified date and time. Customers using the Phone ID Contact Match and Number Deactivation during this maintenance period may experience temporary delays. We recommend planning accordingly.
If you have any questions, please contact us at support@telesign.com.
Oct 21, 2024 15:00-20:15 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 21, 2024 - 00:00 PDT
Oct 21, 2024 - 00:00 PDT
Scheduled - Intelligence Model Enhancements
Start time: October 21, 2024
End time: October 25, 2024
During the week of October 21, Telesign will be performing scheduled maintenance to release enhancements to our Intelligence model. There’s no integration work, preparation, or actions customers need to take. API responses, product configuration and latency will remain the same. There is no downtime expected during the maintenance event.
These enhancements will be made with the goal of increasing model accuracy, decreasing false positives, improving the true-positive rate, and decreasing false positives by:
Integration of new data sources enhancing our monitoring of IP and phone number behavior
Adopting new detection methods of artificially inflated traffic (AIT)
Refining fraud detection by using improved insights into email address behavior
Improving understanding of very low-risk behavior though the detection of regular, continuous activity
If you have any questions, please reach out to support@telesign.com
Oct 21, 2024 00:00 - Oct 25, 2024 00:00 PDT
Start time: October 21, 2024
End time: October 25, 2024
During the week of October 21, Telesign will be performing scheduled maintenance to release enhancements to our Intelligence model. There’s no integration work, preparation, or actions customers need to take. API responses, product configuration and latency will remain the same. There is no downtime expected during the maintenance event.
These enhancements will be made with the goal of increasing model accuracy, decreasing false positives, improving the true-positive rate, and decreasing false positives by:
Integration of new data sources enhancing our monitoring of IP and phone number behavior
Adopting new detection methods of artificially inflated traffic (AIT)
Refining fraud detection by using improved insights into email address behavior
Improving understanding of very low-risk behavior though the detection of regular, continuous activity
If you have any questions, please reach out to support@telesign.com
Oct 21, 2024 00:00 - Oct 25, 2024 00:00 PDT
📢 Important Update: New Requirements for OTP Messages from Indosat Ooredoo Hutchison - Indonesia
Subscribe
Identified - 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.
Oct 18, 2024 - 03:49 PDT
• 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.
Oct 18, 2024 - 03:49 PDT
Identified - The issue has been identified and a fix is being implemented.
Oct 15, 2024 - 12:45 PDT
Oct 15, 2024 - 12:45 PDT
Investigating - 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
Oct 15, 2024 - 12:44 PDT
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
Oct 15, 2024 - 12:44 PDT
📢 Important Update: US Short Code Registry and CTIA New Requirements for Short Code Leasing
Subscribe
Identified - 📢 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.
Oct 03, 2024 - 11:29 PDT
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.
Oct 03, 2024 - 11:29 PDT
Identified - 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.
Oct 03, 2024 - 01:41 PDT
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.
Oct 03, 2024 - 01:41 PDT
Identified - 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.
Oct 02, 2024 - 22:11 PDT
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.
Oct 02, 2024 - 22:11 PDT
Identified - 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.
Oct 02, 2024 - 13:51 PDT
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.
Oct 02, 2024 - 13:51 PDT
📢 Important Update: New Regulatory Direction for India LOCAL Traffic as issued by the Telecom Regulatory Authority of India (TRAI)
Subscribe
Identified - 📢 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;
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.
Sep 30, 2024 - 16:36 PDT
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.
Sep 30, 2024 - 16:36 PDT
Identified - 📢 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.
Sep 26, 2024 - 08:55 PDT
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.
Sep 26, 2024 - 08:55 PDT
Identified - 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.
Sep 11, 2024 - 19:49 PDT
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.
Sep 11, 2024 - 19:49 PDT
Update - We are continuing to work on a fix for this issue.
Sep 06, 2024 - 09:09 PDT
Sep 06, 2024 - 09:09 PDT
Identified - 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 【优速通】 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/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.
Aug 12, 2024 - 23:48 PDT
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.
Aug 12, 2024 - 23:48 PDT
Investigating - 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
Aug 28, 2024 - 08:10 PDT
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
Aug 28, 2024 - 08:10 PDT
Update - We are continuing to work on a fix for this issue.
Jul 10, 2024 - 02:15 PDT
Jul 10, 2024 - 02:15 PDT
Identified - 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.
Jul 09, 2024 - 07:59 PDT
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.
Jul 09, 2024 - 07:59 PDT
Identified - 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.
Jun 25, 2024 - 01:25 PDT
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.
Jun 25, 2024 - 01:25 PDT
Investigating - 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
Jun 26, 2024 - 22:09 PDT
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
Jun 26, 2024 - 22:09 PDT
Identified - 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.
May 31, 2024 - 00:55 PDT
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.
May 31, 2024 - 00:55 PDT
Investigating - Start Time: 07:16 AM PDT - 05/14/24
End Time: Ongoing
We received notification that Land Line (234/76;00;77) from United Kingdom (GB) 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 00818105
May 14, 2024 - 07:27 PDT
End Time: Ongoing
We received notification that Land Line (234/76;00;77) from United Kingdom (GB) 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 00818105
May 14, 2024 - 07:27 PDT
Identified - Dear Customers and Partners,
On May 5th 2024 the certificate for *.tsentcloud.com will expire. The renewed Identity Certificate has a new Root Certificate Authority and Issuer. Please verify your client's certificate store or ca-bundle trust the new Root CA "DigiCert Global Root G2" by April 22nd 2024. No other action is required if this RootCA is trusted and using standard PKI path validation for TLS.
Existing Cert: "DigiCert Global Root CA" --> "Thawte RSA CA 2018" --> "*.tsentcloud.com"
New Cert: "DigiCert Global Root G2" --> "Thawte TLS RSA CA G1" --> "*.tsentcloud.com"
If you have an implementation that requires certificate pinning a PEM file with the full chain is attached to this email. Certificate pinning is not a best practice, recommended nor explicitly supported by Telesign and 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.
Apr 11, 2024 - 00:13 PDT
On May 5th 2024 the certificate for *.tsentcloud.com will expire. The renewed Identity Certificate has a new Root Certificate Authority and Issuer. Please verify your client's certificate store or ca-bundle trust the new Root CA "DigiCert Global Root G2" by April 22nd 2024. No other action is required if this RootCA is trusted and using standard PKI path validation for TLS.
Existing Cert: "DigiCert Global Root CA" --> "Thawte RSA CA 2018" --> "*.tsentcloud.com"
New Cert: "DigiCert Global Root G2" --> "Thawte TLS RSA CA G1" --> "*.tsentcloud.com"
If you have an implementation that requires certificate pinning a PEM file with the full chain is attached to this email. Certificate pinning is not a best practice, recommended nor explicitly supported by Telesign and 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.
Apr 11, 2024 - 00:13 PDT
Identified - 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!
Apr 11, 2024 - 02:35 PDT
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!
Apr 11, 2024 - 02:35 PDT
Identified - 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.
Mar 14, 2024 - 17:40 PDT
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.
Mar 14, 2024 - 17:40 PDT
Update - We are continuing to work on a fix for this issue.
Feb 29, 2024 - 09:07 PST
Feb 29, 2024 - 09:07 PST
Identified - 📢 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.
Feb 29, 2024 - 08:54 PST
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.
Feb 29, 2024 - 08:54 PST
Update - We are continuing to investigate this issue.
Nov 29, 2023 - 12:56 PST
Nov 29, 2023 - 12:56 PST
Investigating - 🚨 Important Update: New TFN Regulations Effective January 31, 2024! 🚨
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.
Nov 29, 2023 - 12:55 PST
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.
Nov 29, 2023 - 12:55 PST
Identified - Dear Customer and Partners,
You are currently subscribing to Telesign Services which was provided to you pursuant to a Master Services Agreement (“MSA”) as set out in https://www.telesign.com/master-services-agreement/, the terms of which were accepted or executed between yourself and Telesign.
Additionally per the MSA, your use and obligation regarding the use of Telesign Services and any Licensed Data returned from such Services are further governed by Telesign’s Acceptable Use Policy located at https://www.telesign.com/acceptable-use-policy (“AUP”). Per the terms of the MSA, we may, from time to time, update such AUP at Telesign’s discretion.
With effect from August 1, 2023, we are replacing the existing Section 3(d) of the AUP with a new section:
Existing Section 3(d):
(d) not use the Services or the Licensed Data for the purpose of assessing creditworthiness;
New Section 3(d):
(d) not use the Services or the Licensed Data for the purpose(s) of solely automated decision-making producing legal effects or similarly affecting the User, such as:
1. Cancellation of a contract;
2. Entitlement to or denial of a particular social benefit granted by law, such as child or housing benefit;
3. Refused admission to a country or denial of citizenship;
4. Decisions that affect someone’s financial circumstances, such as their eligibility to credit (i.e.: assessing creditworthiness);
5. Decisions that affect Users’ access to health services;
6. Decisions that deny Users’ an employment opportunity;
7. Decisions that affect Users’ access to education, for example university admissions;
8. Decisions that affect Users’ access to housing;
9. Decisions that affect Users’ access to insurance;
10. Decisions that affect Users’ access to criminal justice; or
11. Decisions that affect Users’ access to basic necessities, or essential goods or services.
The MSA (and the AUP) shall, save as amended by the above change, continue in full force and effect.
Should you have any questions, please forward them to Telesign Support.
Jul 31, 2023 - 16:43 PDT
You are currently subscribing to Telesign Services which was provided to you pursuant to a Master Services Agreement (“MSA”) as set out in https://www.telesign.com/master-services-agreement/, the terms of which were accepted or executed between yourself and Telesign.
Additionally per the MSA, your use and obligation regarding the use of Telesign Services and any Licensed Data returned from such Services are further governed by Telesign’s Acceptable Use Policy located at https://www.telesign.com/acceptable-use-policy (“AUP”). Per the terms of the MSA, we may, from time to time, update such AUP at Telesign’s discretion.
With effect from August 1, 2023, we are replacing the existing Section 3(d) of the AUP with a new section:
Existing Section 3(d):
(d) not use the Services or the Licensed Data for the purpose of assessing creditworthiness;
New Section 3(d):
(d) not use the Services or the Licensed Data for the purpose(s) of solely automated decision-making producing legal effects or similarly affecting the User, such as:
1. Cancellation of a contract;
2. Entitlement to or denial of a particular social benefit granted by law, such as child or housing benefit;
3. Refused admission to a country or denial of citizenship;
4. Decisions that affect someone’s financial circumstances, such as their eligibility to credit (i.e.: assessing creditworthiness);
5. Decisions that affect Users’ access to health services;
6. Decisions that deny Users’ an employment opportunity;
7. Decisions that affect Users’ access to education, for example university admissions;
8. Decisions that affect Users’ access to housing;
9. Decisions that affect Users’ access to insurance;
10. Decisions that affect Users’ access to criminal justice; or
11. Decisions that affect Users’ access to basic necessities, or essential goods or services.
The MSA (and the AUP) shall, save as amended by the above change, continue in full force and effect.
Should you have any questions, please forward them to Telesign Support.
Jul 31, 2023 - 16:43 PDT
Restriction of non-10DLC (non-Authorized Messaging) long codes in countries outside US/CAN
Subscribe
Identified - Country: +1 countries (Non-US/CA, i.e. Puerto Rico, Guam, Northern Mariana Islands, etc.)
Effective Date: TBD
Description: Carriers are continuing to enforce the restriction of non-10DLC (non-Authorized Messaging) long codes in countries like the United States and Canada. We now expect restrictions on long codes in other countries within the +1 dialing code (i.e. Puerto Rico, Guam, Northern Mariana Islands). Many customers are currently using shared TFNs (Toll-Free Numbers) as a solution for delivery toward these regions, however these will no longer permit non-One-Time Passcode (OTP) traffic.
All customers who send messages to +1 countries, that are not US/CA, must obtain a dedicated TFN to ensure uninterrupted transactions to these destinations. We strongly encourage customers to use the "My Telesign" portal to proceed with the procurement process.
Jul 23, 2023 - 12:48 PDT
Effective Date: TBD
Description: Carriers are continuing to enforce the restriction of non-10DLC (non-Authorized Messaging) long codes in countries like the United States and Canada. We now expect restrictions on long codes in other countries within the +1 dialing code (i.e. Puerto Rico, Guam, Northern Mariana Islands). Many customers are currently using shared TFNs (Toll-Free Numbers) as a solution for delivery toward these regions, however these will no longer permit non-One-Time Passcode (OTP) traffic.
All customers who send messages to +1 countries, that are not US/CA, must obtain a dedicated TFN to ensure uninterrupted transactions to these destinations. We strongly encourage customers to use the "My Telesign" portal to proceed with the procurement process.
Jul 23, 2023 - 12:48 PDT
Update - 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.
Mar 31, 2022 - 16:44 PDT
Mar 31, 2022 - 16:44 PDT
Update - Date: 03/08/22
Start Time: 06:49 PM PST
End Time: Ongoing
We received notification that multiple operators from Russia are currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operators have come to a resolution.
Mar 09, 2022 - 01:20 PST
Start Time: 06:49 PM PST
End Time: Ongoing
We received notification that multiple operators from Russia are currently experiencing network issues, and this may cause a delay in the delivery of SMS messages. We will inform you once the operators have come to a resolution.
Mar 09, 2022 - 01:20 PST
Identified - Date: 03/08/2022
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 in the delivery of SMS messages. We will inform you once the situation is resolved.
Mar 08, 2022 - 18:49 PST
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 in the delivery of SMS messages. We will inform you once the situation is resolved.
Mar 08, 2022 - 18:49 PST
Identified - Date: 03/10/22
End Time: Ongoing
We received notification that multiple operators in Russia are currently experiencing network issues, and this may cause a delay in the delivery of Voice services. We will inform you once the operators have come to a resolution.
Mar 10, 2022 - 07:31 PST
End Time: Ongoing
We received notification that multiple operators in Russia are currently experiencing network issues, and this may cause a delay in the delivery of Voice services. We will inform you once the operators have come to a resolution.
Mar 10, 2022 - 07:31 PST
Standard Services
Under Maintenance
SMS
Operational
Voice
Operational
PhoneID
Under Maintenance
Score
Operational
App Verify
Operational
Developer Portal
Operational
2-Way SMS
Operational
Enterprise Services
Under Maintenance
SMS & SMS Verify
Operational
Voice Verify
Operational
Smart Verify
Operational
Push Verify
Operational
PhoneID Standard
Under Maintenance
PhoneID Contact
Under Maintenance
PhoneID Live
Under Maintenance
TelePortal
Operational
Score
Operational
2-Way SMS
Operational
Messaging
Operational
Operator Alerts
Under Maintenance
Operator Alerts WW
Under Maintenance
Operator Alerts EMEA
Under Maintenance
Operator Alerts APAC
Operational
Operator Alerts North America
Operational
Operator Alerts LATAM
Operational
Regulatory Updates
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Operator Service Alert - Planned Maintenance - United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670) - 10/21/24-10/22/24
Oct 21, 2024 20:00 - Oct 22, 2024 02:00 PDT
Scheduled -
Date: 10/21/24-10/22/24
Start Time: 8:00PM PDT 10/21/24
End Time: 2:00AM PDT 10/22/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
Oct 18, 2024 - 07:20 PDT
Start Time: 8:00PM PDT 10/21/24
End Time: 2:00AM PDT 10/22/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
Oct 18, 2024 - 07:20 PDT
Operator Service Alert - Planned Maintenance - T-Mobile - 10/21/24 - 10/22/24
Oct 21, 2024 22:00 - Oct 22, 2024 04:00 PDT
Issue: US Operator - T-Mobile Maintenance
Date: 10/21/24 - 10/22/24
Start Time: 10PM PST 10/21/24
End Time: 4AM PST 10/22/24
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.
Posted on Oct 21, 2024 - 01:19 PDT
Date: 10/21/24 - 10/22/24
Start Time: 10PM PST 10/21/24
End Time: 4AM PST 10/22/24
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.
Posted on Oct 21, 2024 - 01:19 PDT
Operator Service Alert -Planned Maintenance - United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670) - 10DLC - 10/22/24
Oct 22, 2024 02:00-04:00 PDT
Issue: Planned Maintenance - United States (US) - ATT Mobility
Start Time: 2 AM PDT - 10/22/24
End Time: 4 AM PDT - 10/22/24
Summary:
We received notification that ATT 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 ATT 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 00889126
Posted on Oct 08, 2024 - 02:52 PDT
Start Time: 2 AM PDT - 10/22/24
End Time: 4 AM PDT - 10/22/24
Summary:
We received notification that ATT 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 ATT 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 00889126
Posted on Oct 08, 2024 - 02:52 PDT
Operator Service Alert - Planned Maintenance - United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670) - 10/23/24-10/24/24
Oct 23, 2024 20:00 - Oct 24, 2024 02:00 PDT
Planned Maintenance - United States (US) - ATT Mobility (310/016;030;150;170;280;380;410;670) - 10/23/24-10/24/24
Date: 10/23/24-10/24/24
Start Time: 8:00PM PDT 10/23/24
End Time: 2:00AM PDT 10/24/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
Posted on Oct 18, 2024 - 07:27 PDT
Date: 10/23/24-10/24/24
Start Time: 8:00PM PDT 10/23/24
End Time: 2:00AM PDT 10/24/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
Posted on Oct 18, 2024 - 07:27 PDT
Operator Service Alert -Planned Maintenance - United States (US) - Verizon Wireless (310/004;006;010;012;590) - 10/27/24
Oct 27, 2024 21:00 - Oct 28, 2024 01:00 PDT
Issue: Planned Maintenance - United States (US) - Verizon Wireless (310/004;006;010;012;590)
Start Time: 09:00 PM PDT - 10/27/24
End Time: 01:00 AM PDT - 10/28/24
Summary:
We received notification that Verizon Wireless (310/004;006;010;012;590) from United States (US) will perform planned maintenance on the date and time specified above.
SMS messages to Verizon Wireless (310/004;006;010;012;590) during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.
The expected impact is 15 minutes of message latency while our connections are moved, which is expected during the first hour of maintenance.
If you have any questions, please contact support@telesign.com.
SF 00895883
Posted on Oct 21, 2024 - 14:21 PDT
Start Time: 09:00 PM PDT - 10/27/24
End Time: 01:00 AM PDT - 10/28/24
Summary:
We received notification that Verizon Wireless (310/004;006;010;012;590) from United States (US) will perform planned maintenance on the date and time specified above.
SMS messages to Verizon Wireless (310/004;006;010;012;590) during the maintenance window may experience a temporary delay in message delivery, so we kindly ask that you plan accordingly.
The expected impact is 15 minutes of message latency while our connections are moved, which is expected during the first hour of maintenance.
If you have any questions, please contact support@telesign.com.
SF 00895883
Posted on Oct 21, 2024 - 14:21 PDT