DNS response history for ns2.sezyumbt.com

ns2.sezyumbt.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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 312 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.sezyumbt.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

312 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

85.111.86.8

Most recently resolved hosting IP on selected date

Successful Responses

38

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.sezyumbt.com

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:09 639232597643611557
13 ms 85.111.86.8
37 2026-08-25 12:52 639232587225721862
111 ms 85.111.86.8
36 2026-08-25 12:34 639232576780683689
181 ms 85.111.86.8
35 2026-08-25 12:17 639232566381512620
12 ms 85.111.86.8
34 2026-08-25 12:00 639232556111768563
100 ms 85.111.86.8
33 2026-08-25 11:43 639232545839529039
164 ms 85.111.86.8
32 2026-08-25 11:25 639232535349285207
120 ms 85.111.86.8
31 2026-08-25 11:08 639232524938080723
106 ms 85.111.86.8
30 2026-08-25 10:14 639232492740373468
114 ms 85.111.86.8
29 2026-08-25 09:57 639232482235303141
116 ms 85.111.86.8
28 2026-08-25 09:39 639232471861770303
2088 ms 85.111.86.8
27 2026-08-25 09:22 639232461630217327
2065 ms 85.111.86.8
26 2026-08-25 09:05 639232451282965990
175 ms 85.111.86.8
25 2026-08-25 08:48 639232440814614938
67 ms 85.111.86.8
24 2026-08-25 08:30 639232430410720425
2079 ms 85.111.86.8
23 2026-08-25 08:13 639232420003096185
33 ms 85.111.86.8
22 2026-08-25 07:56 639232409467287444
130 ms 85.111.86.8
21 2026-08-25 07:38 639232399077195997
70 ms 85.111.86.8
20 2026-08-25 07:21 639232388731528337
122 ms 85.111.86.8
19 2026-08-25 07:03 639232378288598612
62 ms 85.111.86.8
18 2026-08-25 06:10 639232346196373643
118 ms 85.111.86.8
17 2026-08-25 05:53 639232336112370741
133 ms 85.111.86.8
16 2026-08-25 05:37 639232326146508970
118 ms 85.111.86.8
15 2026-08-25 05:20 639232316189381720
68 ms 85.111.86.8
14 2026-08-25 05:03 639232306217998913
123 ms 85.111.86.8
13 2026-08-25 04:47 639232296255744174
118 ms 85.111.86.8
12 2026-08-25 04:30 639232286095760789
2114 ms 85.111.86.8
11 2026-08-25 04:13 639232276086186273
130 ms 85.111.86.8
10 2026-08-25 03:56 639232265900986425
111 ms 85.111.86.8
9 2026-08-25 03:39 639232255723518075
125 ms 85.111.86.8
8 2026-08-25 03:22 639232245484452890
116 ms 85.111.86.8
7 2026-08-25 03:05 639232235157175331
124 ms 85.111.86.8
6 2026-08-25 02:12 639232203197189095
67 ms 85.111.86.8
5 2026-08-25 01:54 639232192844564298
114 ms 85.111.86.8
4 2026-08-25 01:37 639232182496008942
123 ms 85.111.86.8
3 2026-08-25 01:20 639232172197053132
75 ms 85.111.86.8
2 2026-08-25 00:27 639232140250307418
71 ms 85.111.86.8
1 2026-08-25 00:10 639232129927860324
83 ms 85.111.86.8