DNS response history for ns.tedla.com

ns.tedla.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 264 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns.tedla.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.240.51.153

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns.tedla.com

Showing DNS history for 2026-08-27 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
36 2026-08-27 12:03 639234286253196126
144 ms 50.240.51.153
35 2026-08-27 11:09 639234253963286387
146 ms 50.240.51.153
34 2026-08-27 10:52 639234243654907465
43 ms 50.240.51.153
33 2026-08-27 10:35 639234233269654413
169 ms 50.240.51.153
32 2026-08-27 10:18 639234222943951923
3 ms 50.240.51.153
31 2026-08-27 10:00 639234212558002823
164 ms 50.240.51.153
30 2026-08-27 09:43 639234202117531850
6 ms 50.240.51.153
29 2026-08-27 09:26 639234191649612722
187 ms 50.240.51.153
28 2026-08-27 09:08 639234181105879568
149 ms 50.240.51.153
27 2026-08-27 08:51 639234170713214496
152 ms 50.240.51.153
26 2026-08-27 08:33 639234160341037652
153 ms 50.240.51.153
25 2026-08-27 08:16 639234149799404224
180 ms 50.240.51.153
24 2026-08-27 07:59 639234139553286469
283 ms 50.240.51.153
23 2026-08-27 07:05 639234107183588293
134 ms 50.240.51.153
22 2026-08-27 06:48 639234096905435724
11 ms 50.240.51.153
21 2026-08-27 06:31 639234086579410775
46 ms 50.240.51.153
20 2026-08-27 06:13 639234076291157956
11 ms 50.240.51.153
19 2026-08-27 05:56 639234065981939454
151 ms 50.240.51.153
18 2026-08-27 05:39 639234055548642997
118 ms 50.240.51.153
17 2026-08-27 05:22 639234045267979603
974 ms 50.240.51.153
16 2026-08-27 05:05 639234034999717463
127 ms 50.240.51.153
15 2026-08-27 04:48 639234024739225358
130 ms 50.240.51.153
14 2026-08-27 04:30 639234014311170162
242 ms 50.240.51.153
13 2026-08-27 04:13 639234003806017640
33 ms 50.240.51.153
12 2026-08-27 03:55 639233993356203030
2032 ms 50.240.51.153
11 2026-08-27 03:02 639233961301716608
156 ms 50.240.51.153
10 2026-08-27 02:45 639233950834200647
2121 ms 50.240.51.153
9 2026-08-27 02:27 639233940431849026
119 ms 50.240.51.153
8 2026-08-27 02:10 639233930110596398
128 ms 50.240.51.153
7 2026-08-27 01:53 639233919705434540
126 ms 50.240.51.153
6 2026-08-27 01:35 639233909452807845
299 ms 50.240.51.153
5 2026-08-27 01:18 639233899096420820
151 ms 50.240.51.153
4 2026-08-27 01:01 639233888707824939
142 ms 50.240.51.153
3 2026-08-27 00:44 639233878461203802
196 ms 50.240.51.153
2 2026-08-27 00:26 639233868060868209
154 ms 50.240.51.153
1 2026-08-27 00:09 639233857450922991
123 ms 50.240.51.153