DNS response history for ns2.perhosting.com

ns2.perhosting.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, 37 successful responses, 0 failed responses, and 237 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.perhosting.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

237 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.0.138.4

Most recently resolved hosting IP on selected date

Successful Responses

37

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.perhosting.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:58 639232587225721862
124 ms 173.0.138.4
36 2026-08-25 12:41 639232576780683689
239 ms 173.0.138.4
35 2026-08-25 12:24 639232566381512620
122 ms 173.0.138.4
34 2026-08-25 12:06 639232556111768563
144 ms 173.0.138.4
33 2026-08-25 11:49 639232545839529039
123 ms 173.0.138.4
32 2026-08-25 11:32 639232535349285207
125 ms 173.0.138.4
31 2026-08-25 11:15 639232524938080723
251 ms 173.0.138.4
30 2026-08-25 10:21 639232492740373468
250 ms 173.0.138.4
29 2026-08-25 10:04 639232482235303141
125 ms 173.0.138.4
28 2026-08-25 09:46 639232471861770303
122 ms 173.0.138.4
27 2026-08-25 09:29 639232461630217327
200 ms 173.0.138.4
26 2026-08-25 09:12 639232451282965990
372 ms 173.0.138.4
25 2026-08-25 08:55 639232440814614938
127 ms 173.0.138.4
24 2026-08-25 08:37 639232430410720425
3 ms 173.0.138.4
23 2026-08-25 08:20 639232420003096185
496 ms 173.0.138.4
22 2026-08-25 08:02 639232409467287444
7 ms 173.0.138.4
21 2026-08-25 07:45 639232399077195997
126 ms 173.0.138.4
20 2026-08-25 07:28 639232388731528337
4 ms 173.0.138.4
19 2026-08-25 07:10 639232378288598612
4 ms 173.0.138.4
18 2026-08-25 06:16 639232346196373643
126 ms 173.0.138.4
17 2026-08-25 06:00 639232336112370741
374 ms 173.0.138.4
16 2026-08-25 05:43 639232326146508970
126 ms 173.0.138.4
15 2026-08-25 05:26 639232316189381720
2259 ms 173.0.138.4
14 2026-08-25 05:10 639232306217998913
390 ms 173.0.138.4
13 2026-08-25 04:53 639232296255744174
4 ms 173.0.138.4
12 2026-08-25 04:36 639232286095760789
124 ms 173.0.138.4
11 2026-08-25 04:19 639232276086186273
3 ms 173.0.138.4
10 2026-08-25 04:03 639232265900986425
378 ms 173.0.138.4
9 2026-08-25 03:46 639232255723518075
372 ms 173.0.138.4
8 2026-08-25 03:29 639232245484452890
138 ms 173.0.138.4
7 2026-08-25 03:12 639232235157175331
251 ms 173.0.138.4
6 2026-08-25 02:18 639232203197189095
126 ms 173.0.138.4
5 2026-08-25 02:01 639232192844564298
126 ms 173.0.138.4
4 2026-08-25 01:44 639232182496008942
248 ms 173.0.138.4
3 2026-08-25 01:27 639232172197053132
374 ms 173.0.138.4
2 2026-08-25 00:33 639232140250307418
371 ms 173.0.138.4
1 2026-08-25 00:16 639232129927860324
15 ms 173.0.138.4