DNS response history for ns2.tetrayazilim.com

ns2.tetrayazilim.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-26. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 249 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 ns2.tetrayazilim.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

249 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.98.48.136

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns2.tetrayazilim.com

Showing DNS history for 2026-08-26 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
37 2026-08-26 12:26 639233434974187439
48 ms 141.98.48.136
36 2026-08-26 12:09 639233424567558554
101 ms 141.98.48.136
35 2026-08-26 11:52 639233414056832719
326 ms 141.98.48.136
34 2026-08-26 11:34 639233403515141099
2053 ms 141.98.48.136
33 2026-08-26 10:39 639233370841350248
59 ms 141.98.48.136
32 2026-08-26 10:22 639233360361507238
90 ms 141.98.48.136
31 2026-08-26 10:05 639233350067824371
12 ms 141.98.48.136
30 2026-08-26 09:48 639233339545274518
92 ms 141.98.48.136
29 2026-08-26 09:30 639233329214918079
2104 ms 141.98.48.136
28 2026-08-26 09:13 639233318749762337
74 ms 141.98.48.136
27 2026-08-26 08:55 639233308387917838
98 ms 141.98.48.136
26 2026-08-26 08:38 639233297961740122
102 ms 141.98.48.136
25 2026-08-26 08:21 639233287487159094
97 ms 141.98.48.136
24 2026-08-26 08:03 639233276995531707
48 ms 141.98.48.136
23 2026-08-26 07:46 639233266521568229
60 ms 141.98.48.136
22 2026-08-26 07:28 639233256081047431
64 ms 141.98.48.136
21 2026-08-26 06:34 639233223620132921
90 ms 141.98.48.136
20 2026-08-26 06:17 639233213287814244
90 ms 141.98.48.136
19 2026-08-26 06:00 639233202925983161
93 ms 141.98.48.136
18 2026-08-26 05:42 639233192644780696
92 ms 141.98.48.136
17 2026-08-26 05:25 639233182401183833
66 ms 141.98.48.136
16 2026-08-26 05:08 639233172074181051
53 ms 141.98.48.136
15 2026-08-26 04:51 639233161808421455
93 ms 141.98.48.136
14 2026-08-26 04:34 639233151357344052
49 ms 141.98.48.136
13 2026-08-26 04:16 639233141034116946
2076 ms 141.98.48.136
12 2026-08-26 03:59 639233130828334142
11 ms 141.98.48.136
11 2026-08-26 03:42 639233120373450007
8 ms 141.98.48.136
10 2026-08-26 03:25 639233110066216193
324 ms 141.98.48.136
9 2026-08-26 02:32 639233078065410564
11 ms 141.98.48.136
8 2026-08-26 02:14 639233067787457832
48 ms 141.98.48.136
7 2026-08-26 01:57 639233057501801162
92 ms 141.98.48.136
6 2026-08-26 01:40 639233047089431703
101 ms 141.98.48.136
5 2026-08-26 01:23 639233036754790688
46 ms 141.98.48.136
4 2026-08-26 01:06 639233026412602472
91 ms 141.98.48.136
3 2026-08-26 00:48 639233016064066127
169 ms 141.98.48.136
2 2026-08-26 00:31 639233005922655772
97 ms 141.98.48.136
1 2026-08-26 00:14 639232995672256907
94 ms 141.98.48.136