DNS response history for ns2.peturang.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.20.190.80

Most recently resolved hosting IP on selected date

Successful Responses

34

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.peturang.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
34 2026-08-25 12:05 639232556111768563
353 ms 103.20.190.80
33 2026-08-25 11:48 639232545839529039
9 ms 103.20.190.80
32 2026-08-25 11:31 639232535349285207
5 ms 103.20.190.80
31 2026-08-25 11:13 639232524938080723
390 ms 103.20.190.80
30 2026-08-25 10:20 639232492740373468
174 ms 103.20.190.80
29 2026-08-25 10:03 639232482235303141
7 ms 103.20.190.80
28 2026-08-25 09:45 639232471861770303
180 ms 103.20.190.80
27 2026-08-25 09:28 639232461630217327
176 ms 103.20.190.80
26 2026-08-25 09:11 639232451282965990
349 ms 103.20.190.80
25 2026-08-25 08:53 639232440814614938
3 ms 103.20.190.80
24 2026-08-25 08:36 639232430410720425
4006 ms 103.20.190.80
23 2026-08-25 08:19 639232420003096185
4 ms 103.20.190.80
22 2026-08-25 08:01 639232409467287444
2219 ms 103.20.190.80
21 2026-08-25 07:44 639232399077195997
15 ms 103.20.190.80
20 2026-08-25 07:26 639232388731528337
4 ms 103.20.190.80
19 2026-08-25 07:09 639232378288598612
355 ms 103.20.190.80
18 2026-08-25 06:15 639232346196373643
3 ms 103.20.190.80
17 2026-08-25 05:58 639232336112370741
197 ms 103.20.190.80
16 2026-08-25 05:42 639232326146508970
4 ms 103.20.190.80
15 2026-08-25 05:25 639232316189381720
3 ms 103.20.190.80
14 2026-08-25 05:09 639232306217998913
345 ms 103.20.190.80
13 2026-08-25 04:52 639232296255744174
389 ms 103.20.190.80
12 2026-08-25 04:35 639232286095760789
2 ms 103.20.190.80
11 2026-08-25 04:18 639232276086186273
388 ms 103.20.190.80
10 2026-08-25 04:02 639232265900986425
4 ms 103.20.190.80
9 2026-08-25 03:45 639232255723518075
377 ms 103.20.190.80
8 2026-08-25 03:28 639232245484452890
362 ms 103.20.190.80
7 2026-08-25 03:10 639232235157175331
348 ms 103.20.190.80
6 2026-08-25 02:17 639232203197189095
344 ms 103.20.190.80
5 2026-08-25 02:00 639232192844564298
672 ms 103.20.190.80
4 2026-08-25 01:43 639232182496008942
404 ms 103.20.190.80
3 2026-08-25 01:25 639232172197053132
232 ms 103.20.190.80
2 2026-08-25 00:32 639232140250307418
374 ms 103.20.190.80
1 2026-08-25 00:15 639232129927860324
390 ms 103.20.190.80