← HonkWatch.com

Is Telesign down in Belgium?

Telesign has problems

People in Belgium: 0 reports in the last hour Official page: Partial outage reported, checked 2 min ago Our checks: loads from 35 of 35 places

2 open incidents: Subscriber status and Number deactivation addon Service Alert - Philippines, Important Announcement: Update regarding SMS and Voice traffic delivery to China.3 notices

Partial outage reported by Telesign Open incident: Subscriber status and Number deactivation addon Service Alert - Philippines. Going on for 5 d 9 h. Updated 7 Nov, 22:55 UTC, 2 min ago · Official status page
Report a problem
Change country

Known issues (from Telesign System's status page)

Incidents

  • Quality degradation Phone ID Number Deactivation - United States (US) (investigating) Since 4 Nov, 15:13 UTC. Affects United States · Details Latest update (4 Nov, 15:13 UTC): Issue: Quality Degradation Phone ID Number Deactivation - United States (US) We are currently experiencing a decline in quality for the Phone ID Number Deactivation - United States (US). We'd like to apologize for any inconvenience and appreciate your patience during this service interruption. If yo
  • Possible Delays (investigating) Since 3 Nov, 23:08 UTC · Details Latest update (3 Nov, 23:08 UTC): Dear Customers and Partners, We are experiencing intermittent disruptions/degradation on our platform which could cause some delays in delivery. Our team is investigating the issue and we will make sure to keep you updated as soon as we have preliminary findings. If you have any questions, please co
  • PhoneID Live Service Alert - Lost Coverage to Australia Telstra (identified) Since 30 Sep 2026, 11:59 UTC. Affects Australia · Details Latest update (30 Sep 2026, 11:59 UTC): Date: 09/30/26 End Time: Ongoing Please note that we have lost coverage for PhoneID Live for Australia Telstra. We will inform you once there is a resolution. We'd like to apologize for any inconvenience and appreciate your patience on this matter. If you have any questions, please contact us at sup
Show 2 more incidents
  • Subscriber status and Number deactivation addon Service Alert - Philippines (identified, minor impact) Since 9 May 2026, 12:06 UTC. Affects APAC - All countries, Subscriber status · Details Latest update (9 May 2026, 12:06 UTC): Date: 05/08/2026 Start Time: 04:00 PM PDT End Time: Ongoing We received notification from our partner that the Number Deactivation and Subscriber Status Addon is currently having issues in the Philippines, which may cause some delays. We will inform you once there is a resolution. We'd like to apolo
  • Important Announcement: Update regarding SMS and Voice traffic delivery to China. (identified, minor impact) Since 7 Jan 2025, 21:12 UTC. Affects APAC - All countries, APAC - All countries, APAC - All countries, China and 3 more · Details Latest update (7 Jan 2025, 21:12 UTC): 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, Telesi

Maintenance

  • Regulatory Update - UK SID Whitelisting Introduced (planned) 6 Jan 2025, 11:29 UTC to 7 Jun 2025, 13:29 UTC. Affects EMEA · Details Latest update (6 Jan 2025, 11:27 UTC): 📢 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
  • TLS certificate lifecycle change and certificate pinning guidance (planned) 6 Apr 2026, 17:00 UTC to 3 Sep 2026, 17:00 UTC. Affects EMEA, APAC, NA & LATAM · Details Latest update (6 Apr 2026, 17:15 UTC): Who is affected: Customers whose systems perform certificate pinning for our TLS certificates. Products affected: All services and APIs secured with our TLS certificates. Changes: - Certificate lifecycle update: Due to upcoming industry-wide changes in certificate validation and lifecycle management
  • Regulatory Update: 📢 Important Update: Austria Sender ID Registration Requirement (under way) 12 Jun 2026, 20:45 UTC to 9 Nov, 20:45 UTC. Affects EMEA · Details Latest update (22 Oct, 11:11 UTC): We will be undergoing scheduled maintenance during this time.
Show 7 more maintenance windows
  • Regulatory Update 📢 Australia and ACMA's SMS Sender ID Register - Jun 2026 (under way) 19 Jun 2026, 06:33 UTC to 16 Nov, 06:33 UTC. Affects APAC · Details Latest update (19 Jun 2026, 06:32 UTC): Summary Following up on our earlier update (https://status.telesign.com/incidents/hg1jmtfjdfj1), Telesign can now fully support all registration scenarios listed below, with an alternative verification option available for direct brand owners with ABN (Australia Business Number). The required docume
  • Upcoming Mandatory Template Requirement — Effective July 15th, 2026 (under way) 1 Jul 2026, 23:30 UTC to 4 Jul 2026, 11:30 UTC. Affects Viber, EMEA, APAC, NA & LATAM · Details Latest update (1 Jul 2026, 23:30 UTC): Scheduled maintenance is currently in progress. We will provide updates as necessary.
  • Regulatory Update: 📢 Important Update: UAE Sender ID Verification Requirement (under way) 31 Jul 2026, 21:30 UTC to 28 Dec 2026, 21:30 UTC. Affects EMEA · Details Latest update (31 Jul 2026, 20:30 UTC): Maintenance will begin as scheduled in 60 minutes.
  • Regulatory Update: 📢 Important Update: Spain Sender ID Registration Requirement (under way) 6 Aug 2026, 22:00 UTC to 3 Jan 2027, 22:00 UTC. Affects EMEA · Details Latest update (6 Aug 2026, 21:00 UTC): Maintenance will begin as scheduled in 60 minutes.
  • Regulatory Update 📢 Vietnam - Mandatory URL whitelisting for Local SenderIDs for Vietnamobile (under way) 17 Aug 2026, 08:08 UTC to 14 Jan 2027, 08:08 UTC. Affects APAC · Details Latest update (17 Aug 2026, 08:07 UTC): Vietnamobile (also known as Hanoi Telecom) has updated its regulatory requirements for local messaging traffic. Effective 1 September 2026, all URLs included in messages sent using local Sender IDs must be whitelisted. Messages containing unregistered URLs will fail. Telesign’s Vietnam URL and messa
  • Regulatory Update 📢 Australia and ACMA's SMS Sender ID Register - Aug 2026 (under way) 17 Aug 2026, 08:11 UTC to 14 Jan 2027, 08:11 UTC. Affects APAC · Details Latest update (17 Aug 2026, 08:10 UTC): Summary Telesign is providing updates to our verification process for Brand Owners with and without Australian Business Number (ABN) who wish to register their alphanumeric senderID in Australia. There is no change to the registration scenarios and the required documents in Registration Pre-steps. I
  • Regulatory Update: 📢 Important Announcement: United Arab Emirates Operators Freeze (under way) 3 Sep 2026, 23:45 UTC to 31 Jan 2027, 23:45 UTC. Affects EMEA · Details Latest update (3 Sep 2026, 22:45 UTC): Maintenance will begin as scheduled in 60 minutes.

We keep the first 10 of 17 maintenance windows; the rest are on Telesign System's status page.

In Telesign System's own words, as we read them every 15 minutes, last 2 min ago. Read Telesign System's status page

Reports from people in Belgium

Last 24 hours · Belgium · times in UTC

0 reports

No community reports in the last 24 hours from Belgium. Having trouble? Add your report.

Status page: partial outage, 2 Nov, 13:34 to now 024 00:0006:0012:0018:00 23:00-23:05 UTC: 35 of 35 places loaded it, typical 139 ms23:05-23:15 UTC: 34 of 34 places loaded it, typical 151 ms23:15-23:20 UTC: 33 of 33 places loaded it, typical 120 ms23:20-00:20 UTC: 35 of 35 places loaded it, typical 116 to 183 ms00:20-00:25 UTC: 34 of 34 places loaded it, typical 155 ms00:25-01:45 UTC: 35 of 35 places loaded it, typical 118 to 160 ms01:45-01:50 UTC: 34 of 34 places loaded it, typical 128 ms01:50-02:50 UTC: 35 of 35 places loaded it, typical 110 to 153 ms02:50-02:55 UTC: 34 of 34 places loaded it, typical 132 ms02:55-03:35 UTC: 35 of 35 places loaded it, typical 105 to 146 ms03:35-03:40 UTC: 34 of 34 places loaded it, typical 128 ms03:40-05:00 UTC: 35 of 35 places loaded it, typical 112 to 153 ms05:00-05:05 UTC: 34 of 34 places loaded it, typical 120 ms05:05-05:25 UTC: 35 of 35 places loaded it, typical 125 to 139 ms05:25-05:30 UTC: 34 of 34 places loaded it, typical 127 ms05:30-06:00 UTC: 35 of 35 places loaded it, typical 120 to 140 ms06:00-06:05 UTC: 34 of 34 places loaded it, typical 136 ms06:05-07:25 UTC: 35 of 35 places loaded it, typical 113 to 158 ms07:25-07:30 UTC: 34 of 34 places loaded it, typical 148 ms07:30-08:10 UTC: 35 of 35 places loaded it, typical 115 to 150 ms08:10-08:15 UTC: 34 of 34 places loaded it, typical 134 ms08:15-08:30 UTC: 35 of 35 places loaded it, typical 135 to 157 ms08:30-08:35 UTC: 34 of 34 places loaded it, typical 136 ms08:35-09:15 UTC: 35 of 35 places loaded it, typical 121 to 135 ms09:15-09:20 UTC: 30 of 30 places loaded it, typical 147 ms09:20-09:40 UTC: 35 of 35 places loaded it, typical 121 to 151 ms09:40-09:45 UTC: 34 of 34 places loaded it, typical 133 ms09:45-10:00 UTC: 35 of 35 places loaded it, typical 127 to 149 ms10:00-10:05 UTC: 34 of 34 places loaded it, typical 144 ms10:05-10:15 UTC: 35 of 35 places loaded it, typical 124 to 169 ms10:15-10:20 UTC: 20 of 20 places loaded it, typical 116 ms10:20-10:55 UTC: 35 of 35 places loaded it, typical 122 to 159 ms10:55-11:00 UTC: 34 of 34 places loaded it, typical 148 ms11:00-11:30 UTC: 35 of 35 places loaded it, typical 127 to 146 ms11:30-11:35 UTC: 34 of 34 places loaded it, typical 126 ms11:35-11:40 UTC: 17 of 17 places loaded it, typical 122 ms11:40-12:15 UTC: 35 of 35 places loaded it, typical 116 to 146 ms12:15-12:20 UTC: 34 of 34 places loaded it, typical 165 ms12:20-12:50 UTC: 35 of 35 places loaded it, typical 128 to 155 ms12:50-12:55 UTC: 28 of 28 places loaded it, typical 168 ms12:55-13:15 UTC: 35 of 35 places loaded it, typical 124 to 162 ms13:15-13:20 UTC: 34 of 34 places loaded it, typical 150 ms13:20-13:45 UTC: 35 of 35 places loaded it, typical 130 to 172 ms13:45-13:50 UTC: 34 of 34 places loaded it, typical 148 ms13:50-14:40 UTC: 35 of 35 places loaded it, typical 120 to 151 ms14:40-14:45 UTC: 34 of 34 places loaded it, typical 146 ms14:45-15:45 UTC: 35 of 35 places loaded it, typical 133 to 186 ms15:45-15:50 UTC: 34 of 34 places loaded it, typical 136 ms15:50-17:05 UTC: 35 of 35 places loaded it, typical 119 to 184 ms17:05-17:10 UTC: 34 of 34 places loaded it, typical 134 ms17:10-18:15 UTC: 35 of 35 places loaded it, typical 118 to 184 ms18:15-18:20 UTC: 34 of 34 places loaded it, typical 134 ms18:20-18:50 UTC: 35 of 35 places loaded it, typical 132 to 173 ms18:50-18:55 UTC: 34 of 34 places loaded it, typical 148 ms18:55-19:05 UTC: 35 of 35 places loaded it, typical 138 to 142 ms19:05-19:10 UTC: 33 of 33 places loaded it, typical 130 ms19:10-19:30 UTC: 35 of 35 places loaded it, typical 131 to 163 ms19:30-19:35 UTC: 34 of 34 places loaded it, typical 126 ms19:35-19:55 UTC: 35 of 35 places loaded it, typical 114 to 169 ms19:55-20:00 UTC: 34 of 34 places loaded it, typical 131 ms20:00-20:15 UTC: 35 of 35 places loaded it, typical 153 to 161 ms20:15-20:20 UTC: 33 of 33 places loaded it, typical 154 ms20:20-20:40 UTC: 35 of 35 places loaded it, typical 143 to 162 ms20:40-20:45 UTC: 34 of 34 places loaded it, typical 142 ms20:45-21:30 UTC: 35 of 35 places loaded it, typical 124 to 167 ms21:30-21:35 UTC: 34 of 34 places loaded it, typical 137 ms21:35-22:35 UTC: 35 of 35 places loaded it, typical 120 to 164 ms22:35-22:40 UTC: 34 of 34 places loaded it, typical 142 ms22:40-22:55 UTC: 35 of 35 places loaded it, typical 134 to 156 ms22:55-23:00 UTC: 1 of 1 place loaded it Typical response time of the places that loaded it, at most 186 ms

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Tinted columns: when Telesign's status page showed a partial outage, a major outage, as we read it every 15 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded telesign.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Belgium only.

Latest checks, 22:55-23:00 UTC: 1 of 1 place loaded it.

Report totals as of 7 Nov, 22:58 UTC

Report a problem with Telesign

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Belgium

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Belgium. The report chart above is filtered to Belgium.

Our own checks of telesign.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

St. Louis: loaded in 152 ms Cape Town: loaded in 165 ms Bangalore: loaded in 256 ms Johannesburg: loaded in 70 ms Jakarta: loaded in 70 ms Port Louis: loaded in 412 ms Hamina: loaded in 120 ms Los Angeles: loaded in 134 ms Seattle: loaded in 68 ms London: loaded in 186 ms Seoul: loaded in 226 ms Querétaro: loaded in 247 ms Toronto: loaded in 73 ms New Jersey: loaded in 114 ms New York: loaded in 488 ms São Paulo: loaded in 77 ms Doha: loaded in 511 ms Madrid: loaded in 140 ms Amsterdam: loaded in 156 ms Sydney: loaded in 84 ms Santiago: loaded in 343 ms Tel Aviv: loaded in 82 ms Hong Kong: loaded in 68 ms Mumbai: loaded in 88 ms Osaka: loaded in 254 ms Lauterbourg: loaded in 111 ms Portsmouth: loaded in 110 ms Frankfurt: loaded in 140 ms Atlanta: loaded in 203 ms Tokyo: loaded in 66 ms Melbourne: loaded in 137 ms Delhi: loaded in 66 ms Dallas: loaded in 370 ms Warsaw: loaded in 447 ms Singapore: loaded in 68 ms
  • St. LouisReachable152 ms, 3 min ago
  • Cape TownReachable165 ms, 3 min ago
  • BangaloreReachable256 ms, 3 min ago
  • JohannesburgReachable70 ms, 3 min ago
  • JakartaReachable70 ms, 3 min ago
  • Port LouisReachable412 ms, 3 min ago
  • HaminaReachable120 ms, 3 min ago
  • Los AngelesReachable134 ms, 3 min ago
  • SeattleReachable68 ms, 3 min ago
  • LondonReachable186 ms, 3 min ago
  • SeoulReachable226 ms, 3 min ago
  • QuerétaroReachable247 ms, 3 min ago
  • TorontoReachable73 ms, 4 min ago
  • New JerseyReachable114 ms, 4 min ago
  • New YorkReachable488 ms, 4 min ago
  • São PauloReachable77 ms, 4 min ago
  • DohaReachable511 ms, 4 min ago
  • MadridReachable140 ms, 4 min ago
  • AmsterdamReachable156 ms, 4 min ago
  • SydneyReachable84 ms, 4 min ago
  • SantiagoReachable343 ms, 4 min ago
  • Tel AvivReachable82 ms, 4 min ago
  • Hong KongReachable68 ms, 4 min ago
  • MumbaiReachable88 ms, 4 min ago
  • OsakaReachable254 ms, 4 min ago
  • LauterbourgReachable111 ms, 4 min ago
  • PortsmouthReachable110 ms, 4 min ago
  • FrankfurtReachable140 ms, 5 min ago
  • AtlantaReachable203 ms, 5 min ago
  • TokyoReachable66 ms, 5 min ago
  • MelbourneReachable137 ms, 5 min ago
  • DelhiReachable66 ms, 5 min ago
  • DallasReachable370 ms, 5 min ago
  • WarsawReachable447 ms, 5 min ago
  • SingaporeReachable68 ms, 5 min ago

This is separate from the status page: we request telesign.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Telesign

Telesign System

All 201 listed parts are working.

Incidents and maintenance

Open incidents

  • Quality degradation Phone ID Number Deactivation - United States (US) (investigating) Since 4 Nov, 15:13 UTC. Affects United States · Details
  • Possible Delays (investigating) Since 3 Nov, 23:08 UTC · Details
  • PhoneID Live Service Alert - Lost Coverage to Australia Telstra (identified) Since 30 Sep 2026, 11:59 UTC. Affects Australia · Details
  • Subscriber status and Number deactivation addon Service Alert - Philippines (identified) Since 9 May 2026, 12:06 UTC. Affects APAC - All countries, Subscriber status · Details
  • Important Announcement: Update regarding SMS and Voice traffic delivery to China. (identified) Since 7 Jan 2025, 21:12 UTC. Affects APAC - All countries, APAC - All countries, APAC - All countries, China and 3 more · Details

Maintenance

  • Regulatory Update - UK SID Whitelisting Introduced (planned) 6 Jan 2025, 11:29 UTC to 7 Jun 2025, 13:29 UTC. Affects EMEA · Details
  • TLS certificate lifecycle change and certificate pinning guidance (planned) 6 Apr 2026, 17:00 UTC to 3 Sep 2026, 17:00 UTC. Affects EMEA, APAC, NA & LATAM · Details
  • Regulatory Update: 📢 Important Update: Austria Sender ID Registration Requirement (now) 12 Jun 2026, 20:45 UTC to 9 Nov, 20:45 UTC. Affects EMEA · Details
  • Regulatory Update 📢 Australia and ACMA's SMS Sender ID Register - Jun 2026 (now) 19 Jun 2026, 06:33 UTC to 16 Nov, 06:33 UTC. Affects APAC · Details
  • Upcoming Mandatory Template Requirement — Effective July 15th, 2026 (now) 1 Jul 2026, 23:30 UTC to 4 Jul 2026, 11:30 UTC. Affects Viber, EMEA, APAC, NA & LATAM · Details
  • Regulatory Update: 📢 Important Update: UAE Sender ID Verification Requirement (now) 31 Jul 2026, 21:30 UTC to 28 Dec 2026, 21:30 UTC. Affects EMEA · Details
  • Regulatory Update: 📢 Important Update: Spain Sender ID Registration Requirement (now) 6 Aug 2026, 22:00 UTC to 3 Jan 2027, 22:00 UTC. Affects EMEA · Details
  • Regulatory Update 📢 Vietnam - Mandatory URL whitelisting for Local SenderIDs for Vietnamobile (now) 17 Aug 2026, 08:08 UTC to 14 Jan 2027, 08:08 UTC. Affects APAC · Details
  • Regulatory Update 📢 Australia and ACMA's SMS Sender ID Register - Aug 2026 (now) 17 Aug 2026, 08:11 UTC to 14 Jan 2027, 08:11 UTC. Affects APAC · Details
  • Regulatory Update: 📢 Important Announcement: United Arab Emirates Operators Freeze (now) 3 Sep 2026, 23:45 UTC to 31 Jan 2027, 23:45 UTC. Affects EMEA · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 2 Nov

Of the last 90 days, 6 had a partial or major outage, 0 had maintenance only and 84 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

2 Nov, 13:34 UTCPartial outagegoing on, 5 d 9 hOpen incident: Subscriber status and Number deactivation addon Service Alert - Philippines
What can I try?

Having trouble with Telesign?

  1. Compare reports from Belgium and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is Telesign down, or is it just me?

Telesign itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Telesign status page and load telesign.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 15 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Other services in Communication

Each card shows that service's own status, not Telesign's. A problem listed here does not mean Telesign has one.

See the live outage feed for Belgium · Find another service