DNS response history for peace2.sibername.com

peace2.sibername.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 33 DNS check records, 33 successful responses, 0 failed responses, and 337 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 peace2.sibername.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

337 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.168.122.106

Most recently resolved hosting IP on selected date

Successful Responses

33

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 peace2.sibername.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
33 2026-08-25 11:39 639232545839529039
460 ms 68.168.122.106
32 2026-08-25 11:22 639232535349285207
41 ms 68.168.122.106
31 2026-08-25 11:04 639232524938080723
10 ms 68.168.122.106
30 2026-08-25 10:11 639232492740373468
5 ms 68.168.122.106
29 2026-08-25 09:53 639232482235303141
12 ms 68.168.122.106
28 2026-08-25 09:36 639232471861770303
34 ms 68.168.122.106
27 2026-08-25 09:19 639232461630217327
4033 ms 68.168.122.106
26 2026-08-25 09:02 639232451282965990
2027 ms 68.168.122.106
25 2026-08-25 08:44 639232440814614938
15 ms 68.168.122.106
24 2026-08-25 08:27 639232430410720425
26 ms 68.168.122.106
23 2026-08-25 08:09 639232420003096185
25 ms 68.168.122.106
22 2026-08-25 07:52 639232409467287444
35 ms 68.168.122.106
21 2026-08-25 07:35 639232399077195997
27 ms 68.168.122.106
20 2026-08-25 07:17 639232388731528337
26 ms 68.168.122.106
19 2026-08-25 07:00 639232378288598612
46 ms 68.168.122.106
18 2026-08-25 06:06 639232346196373643
6 ms 68.168.122.106
17 2026-08-25 05:49 639232336112370741
33 ms 68.168.122.106
16 2026-08-25 05:33 639232326146508970
40 ms 68.168.122.106
15 2026-08-25 05:16 639232316189381720
9 ms 68.168.122.106
14 2026-08-25 05:00 639232306217998913
6 ms 68.168.122.106
13 2026-08-25 04:43 639232296255744174
9 ms 68.168.122.106
12 2026-08-25 04:26 639232286095760789
2031 ms 68.168.122.106
11 2026-08-25 04:09 639232276086186273
6 ms 68.168.122.106
10 2026-08-25 03:53 639232265900986425
8 ms 68.168.122.106
9 2026-08-25 03:36 639232255723518075
21 ms 68.168.122.106
8 2026-08-25 03:19 639232245484452890
4 ms 68.168.122.106
7 2026-08-25 03:01 639232235157175331
34 ms 68.168.122.106
6 2026-08-25 02:08 639232203197189095
2015 ms 68.168.122.106
5 2026-08-25 01:51 639232192844564298
4 ms 68.168.122.106
4 2026-08-25 01:34 639232182496008942
3 ms 68.168.122.106
3 2026-08-25 01:16 639232172197053132
48 ms 68.168.122.106
2 2026-08-25 00:23 639232140250307418
4 ms 68.168.122.106
1 2026-08-25 00:06 639232129927860324
5 ms 68.168.122.106