DNS response history for ns2.hepsi1otobcs.com

ns2.hepsi1otobcs.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-24. For this date, NameServerHistory found 30 DNS check records, 28 successful responses, 2 failed responses, and 361 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.hepsi1otobcs.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

361 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.135.79.55

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

7%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.hepsi1otobcs.com

Showing DNS history for 2026-08-24 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
30 2026-08-24 12:17 639231703815441688
156 ms 78.135.79.55
29 2026-08-24 12:01 639231693747052549
95 ms 78.135.79.55
28 2026-08-24 11:44 639231683712487276
111 ms 78.135.79.55
27 2026-08-24 11:27 639231673513573868
126 ms 78.135.79.55
26 2026-08-24 10:34 639231641791249939
-
25 2026-08-24 10:17 639231631866211033
51 ms 78.135.79.55
24 2026-08-24 10:01 639231621644955316
94 ms 78.135.79.55
23 2026-08-24 09:44 639231611478799259
2048 ms 78.135.79.55
22 2026-08-24 08:51 639231579923718211
29 ms 78.135.79.55
21 2026-08-24 08:34 639231569810702936
2030 ms 78.135.79.55
20 2026-08-24 08:17 639231559762411619
9 ms 78.135.79.55
19 2026-08-24 08:01 639231549663595407
89 ms 78.135.79.55
18 2026-08-24 07:08 639231518076817246
27 ms 78.135.79.55
17 2026-08-24 06:51 639231508078650885
2050 ms 78.135.79.55
16 2026-08-24 06:35 639231498210697093
172 ms 78.135.79.55
15 2026-08-24 06:18 639231488109699360
4 ms 78.135.79.55
14 2026-08-24 05:26 639231456772510692
81 ms 78.135.79.55
13 2026-08-24 05:10 639231447084631185
-
12 2026-08-24 04:53 639231437208519473
86 ms 78.135.79.55
11 2026-08-24 04:36 639231427209627490
84 ms 78.135.79.55
10 2026-08-24 03:44 639231395791246644
131 ms 78.135.79.55
9 2026-08-24 03:28 639231386075551458
79 ms 78.135.79.55
8 2026-08-24 03:12 639231376208713791
80 ms 78.135.79.55
7 2026-08-24 02:55 639231366170589276
80 ms 78.135.79.55
6 2026-08-24 02:02 639231334732159368
29 ms 78.135.79.55
5 2026-08-24 01:46 639231325035670078
80 ms 78.135.79.55
4 2026-08-24 01:30 639231315132253837
2097 ms 78.135.79.55
3 2026-08-24 01:13 639231305014280808
98 ms 78.135.79.55
2 2026-08-24 00:21 639231273779380675
78 ms 78.135.79.55
1 2026-08-24 00:05 639231264180839154
11 ms 78.135.79.55