by HonkWatch

Is Turk Telekom down?

No. Turk Telekom is working. Updated 4 Nov, 12:50 UTC, 4 min ago · No status page: this is what our own checks see No problems recorded since 4 Nov 2026.
Having trouble with Turk Telekom?

Last 9030 days

Collecting since 4 Nov; the uptime figure shows after the first hour of readings

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 89 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

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of turktelekom.com.tr that failed (842 checks). Our checks showed no problem in this time. We don't collect user reports.

0%29%57% 18:0000:0006:0012:00 57% of 149 checks failed46% of 112 checks failed52% of 128 checks failed45% of 109 checks failed56% of 138 checks failed48% of 117 checks failed52% of 89 checks failed

Our own checks of turktelekom.com.tr

Every 5 minutes, from our probes

13 of 34 cities can't reach turktelekom.com.tr.

Hong Kong: loaded in 6127 ms St. Louis: loaded in 2863 ms Tokyo: loaded in 2424 ms Mumbai: loaded in 2607 ms Hamina: loaded in 1969 ms New York: loaded in 5273 ms Singapore: loaded in 1801 ms Madrid: loaded in 4577 ms New Jersey: loaded in 2201 ms Frankfurt: loaded in 4461 ms London: loaded in 4599 ms Warsaw: loaded in 3193 ms Toronto: loaded in 1088 ms Dallas: loaded in 5684 ms Johannesburg: loaded in 2881 ms Seattle: loaded in 1983 ms Los Angeles: loaded in 1311 ms Atlanta: loaded in 1516 ms Sydney: loaded in 2053 ms Lauterbourg: loaded in 875 ms Portsmouth: loaded in 615 ms Melbourne: could not load it (TimeoutError: Check took longer than 10 s) Doha: could not load it (TimeoutError: Check took longer than 10 s) Osaka: could not load it (TimeoutError: Check took longer than 10 s) Bangalore: could not load it (TimeoutError: Check took longer than 10 s) Delhi: could not load it (TimeoutError: Check took longer than 10 s) Amsterdam: could not load it (TimeoutError: Check took longer than 10 s) Santiago: could not load it (TimeoutError: Check took longer than 10 s) Tel Aviv: could not load it (TimeoutError: Check took longer than 10 s) Jakarta: could not load it (TimeoutError: Check took longer than 10 s) Seoul: could not load it (TimeoutError: Check took longer than 10 s) Querétaro: could not load it (TimeoutError: Check took longer than 10 s) São Paulo: could not load it (TimeoutError: Check took longer than 10 s) Cape Town: could not load it (TimeoutError: Check took longer than 10 s)
  • MelbourneNo answer within 10 s10000 ms, 1 min ago
  • DohaNo answer within 10 s10000 ms, 2 min ago
  • OsakaNo answer within 10 s10001 ms, 2 min ago
  • BangaloreNo answer within 10 s10000 ms, 2 min ago
  • DelhiNo answer within 10 s10000 ms, 2 min ago
  • AmsterdamNo answer within 10 s10004 ms, 2 min ago
  • SantiagoNo answer within 10 s10001 ms, 2 min ago
  • Tel AvivNo answer within 10 s10001 ms, 2 min ago
  • JakartaNo answer within 10 s10000 ms, 2 min ago
  • SeoulNo answer within 10 s10000 ms, 2 min ago
  • QuerétaroNo answer within 10 s10000 ms, 2 min ago
  • São PauloNo answer within 10 s10001 ms, 2 min ago
  • Cape TownNo answer within 10 s10000 ms, 2 min ago
  • Hong KongReachable6127 ms, 2 min ago
  • St. LouisReachable2863 ms, 2 min ago
  • TokyoReachable2424 ms, 2 min ago
  • MumbaiReachable2607 ms, 2 min ago
  • HaminaReachable1969 ms, 2 min ago
  • New YorkReachable5273 ms, 2 min ago
  • SingaporeReachable1801 ms, 2 min ago
  • MadridReachable4577 ms, 2 min ago
  • New JerseyReachable2201 ms, 2 min ago
  • FrankfurtReachable4461 ms, 2 min ago
  • LondonReachable4599 ms, 2 min ago
  • WarsawReachable3193 ms, 2 min ago
  • TorontoReachable1088 ms, 2 min ago
  • DallasReachable5684 ms, 2 min ago
  • JohannesburgReachable2881 ms, 2 min ago
  • SeattleReachable1983 ms, 2 min ago
  • Los AngelesReachable1311 ms, 2 min ago
  • AtlantaReachable1516 ms, 2 min ago
  • SydneyReachable2053 ms, 2 min ago
  • LauterbourgReachable875 ms, 2 min ago
  • PortsmouthReachable615 ms, 2 min ago

We load turktelekom.com.tr the way a visitor would and note whether it answers.

No status page

Turk Telekom does not publish a status page, so there is nothing for us to read. What you see here is what we measure ourselves: its website is loaded from our probes in 34 cities every 5 minutes. We show a problem when a quarter of the cities that are working normally can't load it, and an outage when half can't. A city that has not been able to load it once in the last two days is left out: some sites only open for people in their own country, and that is not an outage. When too few cities are left, we say we can't tell.

Recent problems

No problems recorded since 4 Nov 2026.

Alert me when Turk Telekom is down

HonkWatch can load Turk Telekom's website for you from several cities and alert you by email, Slack, Discord or Telegram when it stops answering.

Start free Log in

More in Telecom and internet

Questions

Is Turk Telekom down, or is it just me?

Our checks reach Turk Telekom's website from most of our cities. If it isn't working for you, the cause is more likely near you: your network, your browser, or a problem only in your area. Try another network or device.

How do we know?

Turk Telekom has no public status page. We load turktelekom.com.tr from our own probes in several cities and note whether it answers. We don't guess from social media posts or reports.

How often do we check?

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

Our own checks of the Turk Telekom website. HonkWatch also checks websites from 34 cities.

← All services