kaputly

Is t.me down?

Current status and availability of t.me

Independent status service · No affiliation with t.me

t.me is reachable

Our latest availability check succeeded.

Last checked: · Check interval: 10 minutes

t.me open ↗
Website availability · 24 hours98.64 %Conclusive checks
Ø Response time83 msSuccessful checks
Outages · 24 hours 2 Confirmed outage periods
Monitoring locationGermanyOne monitoring location

t.me uptime and outage history

Results of our automated checks

Over the last 24 hours, kaputly recorded 145 successful and 2 failed HTTP availability checks for t.me (t.me). Measured availability was 98.64 % across 147 conclusive checks; 0 inconclusive checks were excluded. Gaps in monitoring are not counted as successful checks.

100 %50 %0 % 10-14 01:00: Reachable (6 checks) 10-14 02:00: Reachable (6 checks) 10-14 03:00: Reachable (6 checks) 10-14 04:00: Reachable (6 checks) 10-14 05:00: Reachable (6 checks) 10-14 06:00: Reachable (6 checks) 10-14 07:00: Reachable (5 checks) 10-14 07:00: Unreachable (1 checks) 10-14 08:00: Reachable (6 checks) 10-14 09:00: Reachable (6 checks) 10-14 10:00: Reachable (6 checks) 10-14 11:00: Reachable (6 checks) 10-14 12:00: Reachable (6 checks) 10-14 13:00: Reachable (6 checks) 10-14 14:00: Reachable (6 checks) 10-14 15:00: Reachable (6 checks) 10-14 16:00: Reachable (6 checks) 10-14 17:00: Reachable (6 checks) 10-14 18:00: Reachable (6 checks) 10-14 19:00: Reachable (6 checks) 10-14 20:00: Reachable (6 checks) 10-14 21:00: Reachable (6 checks) 10-14 22:00: Reachable (5 checks) 10-14 22:00: Unreachable (1 checks) 10-14 23:00: Reachable (6 checks) 10-15 00:00: Reachable (6 checks) 10-15 01:00: Reachable (3 checks) 01:0007:0613:1319:1901:26
ReachableUnreachableUnknownNo measurement

Response time

500 ms250 ms0 ms 10-14 01:00: 81 ms 10-14 02:00: 80 ms 10-14 03:00: 88 ms 10-14 04:00: 87 ms 10-14 05:00: 84 ms 10-14 06:00: 90 ms 10-14 07:00: 121 ms 10-14 08:00: 87 ms 10-14 09:00: 89 ms 10-14 10:00: 76 ms 10-14 11:00: 80 ms 10-14 12:00: 92 ms 10-14 13:00: 86 ms 10-14 14:00: 93 ms 10-14 15:00: 68 ms 10-14 16:00: 70 ms 10-14 17:00: 87 ms 10-14 18:00: 82 ms 10-14 19:00: 80 ms 10-14 20:00: 79 ms 10-14 21:00: 72 ms 10-14 22:00: 80 ms 10-14 23:00: 66 ms 10-15 00:00: 73 ms 10-15 01:00: 87 ms 01:0013:1301:26

147 measurements · Hourly totals including partial periods. Unknown checks are excluded from availability percentages. Time zone: Europe/Berlin.

Recent outages

Outage ended10 minutes

→

HTTP 404 · Confirmed by retry
Outage ended10 minutes

→

HTTP 404 · Confirmed by retry

Outage boundaries are measurement times. The actual start and end may fall between two checks.

What do we check?

Check target
t.me
Method
Website check (HTTP)
Interval
Every 10 minutes
Last HTTP code
200

The website is requested over HTTP(S). If access protection or rate limits interfere, we additionally check the server connection. The website status remains inconclusive. Individual features such as login or payment are not checked.

Our methodology →

About this service

This description comes from the publicly accessible metadata of the provider's website. Original provider text; not our own review or translation.

Fast. Secure. Powerful.

Source ↗ · og:description · Retrieved: 2026-10-14, 23:23 CEST

t.me not working for you?

Check your internet connection and reload the page. Even if our check succeeds, individual features or regional connections may be affected.

More services telegram.org status →news.yahoo.co.jp status →duckduckgo.com status →actapp.misa.vn status →