DNS response history for ns2.washkom.net

ns2.washkom.net 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 30 DNS check records, 30 successful responses, 0 failed responses, and 255 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.washkom.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

255 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.241.170.101

Most recently resolved hosting IP on selected date

Successful Responses

30

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.washkom.net

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
30 2026-08-25 10:18 639232492740373468
270 ms 162.241.170.101
29 2026-08-25 10:01 639232482235303141
137 ms 162.241.170.101
28 2026-08-25 09:44 639232471861770303
266 ms 162.241.170.101
27 2026-08-25 09:26 639232461630217327
275 ms 162.241.170.101
26 2026-08-25 09:09 639232451282965990
141 ms 162.241.170.101
25 2026-08-25 08:52 639232440814614938
275 ms 162.241.170.101
24 2026-08-25 08:35 639232430410720425
281 ms 162.241.170.101
23 2026-08-25 08:17 639232420003096185
148 ms 162.241.170.101
22 2026-08-25 08:00 639232409467287444
272 ms 162.241.170.101
21 2026-08-25 07:42 639232399077195997
159 ms 162.241.170.101
20 2026-08-25 07:25 639232388731528337
280 ms 162.241.170.101
19 2026-08-25 07:08 639232378288598612
268 ms 162.241.170.101
18 2026-08-25 06:14 639232346196373643
4 ms 162.241.170.101
17 2026-08-25 05:57 639232336112370741
3 ms 162.241.170.101
16 2026-08-25 05:41 639232326146508970
272 ms 162.241.170.101
15 2026-08-25 05:24 639232316189381720
3 ms 162.241.170.101
14 2026-08-25 05:07 639232306217998913
162 ms 162.241.170.101
13 2026-08-25 04:51 639232296255744174
4 ms 162.241.170.101
12 2026-08-25 04:34 639232286095760789
4 ms 162.241.170.101
11 2026-08-25 04:17 639232276086186273
135 ms 162.241.170.101
10 2026-08-25 04:00 639232265900986425
269 ms 162.241.170.101
9 2026-08-25 03:43 639232255723518075
268 ms 162.241.170.101
8 2026-08-25 03:26 639232245484452890
270 ms 162.241.170.101
7 2026-08-25 03:09 639232235157175331
273 ms 162.241.170.101
6 2026-08-25 02:16 639232203197189095
269 ms 162.241.170.101
5 2026-08-25 01:59 639232192844564298
151 ms 162.241.170.101
4 2026-08-25 01:41 639232182496008942
2131 ms 162.241.170.101
3 2026-08-25 01:24 639232172197053132
134 ms 162.241.170.101
2 2026-08-25 00:31 639232140250307418
268 ms 162.241.170.101
1 2026-08-25 00:14 639232129927860324
264 ms 162.241.170.101