System Status


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

Service Metrics

📢 Important Update: Singapore SMS Shared Sender IDs
Incident Report for Telesign system status
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.
Posted Oct 02, 2024 - 22:11 PDT
This incident affects: Regulatory Updates.