DNS response history for ns2.peshmek.com

ns2.peshmek.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 32 DNS check records, 32 successful responses, 0 failed responses, and 287 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.peshmek.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

287 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

13.140.138.229

Most recently resolved hosting IP on selected date

Successful Responses

32

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.peshmek.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
32 2026-08-25 11:22 639232535349285207
49 ms 13.140.138.229
31 2026-08-25 11:05 639232524938080723
1461 ms 13.140.138.229
30 2026-08-25 10:11 639232492740373468
2019 ms 13.140.138.229
29 2026-08-25 09:53 639232482235303141
29 ms 13.140.138.229
28 2026-08-25 09:36 639232471861770303
53 ms 13.140.138.229
27 2026-08-25 09:19 639232461630217327
23 ms 13.140.138.229
26 2026-08-25 09:02 639232451282965990
113 ms 13.140.138.229
25 2026-08-25 08:44 639232440814614938
93 ms 13.140.138.229
24 2026-08-25 08:27 639232430410720425
24 ms 13.140.138.229
23 2026-08-25 08:10 639232420003096185
139 ms 13.140.138.229
22 2026-08-25 07:52 639232409467287444
62 ms 13.140.138.229
21 2026-08-25 07:35 639232399077195997
19 ms 13.140.138.229
20 2026-08-25 07:18 639232388731528337
81 ms 13.140.138.229
19 2026-08-25 07:00 639232378288598612
18 ms 13.140.138.229
18 2026-08-25 06:07 639232346196373643
32 ms 13.140.138.229
17 2026-08-25 05:50 639232336112370741
98 ms 13.140.138.229
16 2026-08-25 05:33 639232326146508970
65 ms 13.140.138.229
15 2026-08-25 05:17 639232316189381720
55 ms 13.140.138.229
14 2026-08-25 05:00 639232306217998913
20 ms 13.140.138.229
13 2026-08-25 04:44 639232296255744174
8 ms 13.140.138.229
12 2026-08-25 04:27 639232286095760789
84 ms 13.140.138.229
11 2026-08-25 04:10 639232276086186273
107 ms 13.140.138.229
10 2026-08-25 03:53 639232265900986425
10 ms 13.140.138.229
9 2026-08-25 03:36 639232255723518075
34 ms 13.140.138.229
8 2026-08-25 03:19 639232245484452890
28 ms 13.140.138.229
7 2026-08-25 03:02 639232235157175331
61 ms 13.140.138.229
6 2026-08-25 02:08 639232203197189095
33 ms 13.140.138.229
5 2026-08-25 01:51 639232192844564298
29 ms 13.140.138.229
4 2026-08-25 01:34 639232182496008942
72 ms 13.140.138.229
3 2026-08-25 01:17 639232172197053132
2060 ms 13.140.138.229
2 2026-08-25 00:23 639232140250307418
2156 ms 13.140.138.229
1 2026-08-25 00:06 639232129927860324
39 ms 13.140.138.229