DNS response history for ns2.yerelrehber.com

ns2.yerelrehber.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 37 DNS check records, 36 successful responses, 1 failed responses, and 276 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.yerelrehber.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

276 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.143.4.37

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.yerelrehber.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
37 2026-08-25 12:48 639232587225721862
83 ms 45.143.4.37
36 2026-08-25 12:30 639232576780683689
131 ms 45.143.4.37
35 2026-08-25 12:13 639232566381512620
105 ms 45.143.4.37
34 2026-08-25 11:56 639232556111768563
72 ms 45.143.4.37
33 2026-08-25 11:39 639232545839529039
2166 ms 45.143.4.37
32 2026-08-25 11:21 639232535349285207
50 ms 45.143.4.37
31 2026-08-25 11:04 639232524938080723
62 ms 45.143.4.37
30 2026-08-25 10:10 639232492740373468
61 ms 45.143.4.37
29 2026-08-25 09:53 639232482235303141
96 ms 45.143.4.37
28 2026-08-25 09:35 639232471861770303
111 ms 45.143.4.37
27 2026-08-25 09:18 639232461630217327
91 ms 45.143.4.37
26 2026-08-25 09:01 639232451282965990
5 ms 45.143.4.37
25 2026-08-25 08:44 639232440814614938
46 ms 45.143.4.37
24 2026-08-25 08:26 639232430410720425
155 ms 45.143.4.37
23 2026-08-25 08:09 639232420003096185
43 ms 45.143.4.37
22 2026-08-25 07:52 639232409467287444
94 ms 45.143.4.37
21 2026-08-25 07:34 639232399077195997
88 ms 45.143.4.37
20 2026-08-25 07:17 639232388731528337
121 ms 45.143.4.37
19 2026-08-25 07:00 639232378288598612
739 ms 45.143.4.37
18 2026-08-25 06:06 639232346196373643
148 ms 45.143.4.37
17 2026-08-25 05:49 639232336112370741
59 ms 45.143.4.37
16 2026-08-25 05:33 639232326146508970
44 ms 45.143.4.37
15 2026-08-25 05:16 639232316189381720
114 ms 45.143.4.37
14 2026-08-25 04:59 639232306217998913
2087 ms 45.143.4.37
13 2026-08-25 04:43 639232296255744174
129 ms 45.143.4.37
12 2026-08-25 04:26 639232286095760789
2095 ms 45.143.4.37
11 2026-08-25 04:09 639232276086186273
127 ms 45.143.4.37
10 2026-08-25 03:52 639232265900986425
58 ms 45.143.4.37
9 2026-08-25 03:35 639232255723518075
108 ms 45.143.4.37
8 2026-08-25 03:18 639232245484452890
66 ms 45.143.4.37
7 2026-08-25 03:01 639232235157175331
114 ms 45.143.4.37
6 2026-08-25 02:08 639232203197189095
92 ms 45.143.4.37
5 2026-08-25 01:51 639232192844564298
-
4 2026-08-25 01:33 639232182496008942
95 ms 45.143.4.37
3 2026-08-25 01:16 639232172197053132
99 ms 45.143.4.37
2 2026-08-25 00:23 639232140250307418
89 ms 45.143.4.37
1 2026-08-25 00:06 639232129927860324
104 ms 45.143.4.37