DNS response history for ns2.onpick.com

ns2.onpick.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-28. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 577 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.onpick.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

577 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.105.80

Most recently resolved hosting IP on selected date

Successful Responses

28

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.onpick.com

Showing DNS history for 2026-08-28 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
28 2026-08-28 11:38 639235132147470568
354 ms 162.240.105.80
27 2026-08-28 11:21 639235121907744088
352 ms 162.240.105.80
26 2026-08-28 11:04 639235111428014262
349 ms 162.240.105.80
25 2026-08-28 10:46 639235100921813626
352 ms 162.240.105.80
24 2026-08-28 09:53 639235068670703481
353 ms 162.240.105.80
23 2026-08-28 09:35 639235058337459445
355 ms 162.240.105.80
22 2026-08-28 09:18 639235047825109146
360 ms 162.240.105.80
21 2026-08-28 09:01 639235037383229033
2181 ms 162.240.105.80
20 2026-08-28 08:07 639235005619242711
4 ms 162.240.105.80
19 2026-08-28 07:50 639234995310346584
4 ms 162.240.105.80
18 2026-08-28 07:33 639234984946548933
353 ms 162.240.105.80
17 2026-08-28 07:16 639234974608077290
362 ms 162.240.105.80
16 2026-08-28 06:22 639234942529845595
354 ms 162.240.105.80
15 2026-08-28 06:05 639234932259126627
356 ms 162.240.105.80
14 2026-08-28 05:48 639234921916735988
356 ms 162.240.105.80
13 2026-08-28 05:31 639234911470038027
370 ms 162.240.105.80
12 2026-08-28 04:38 639234879588411654
347 ms 162.240.105.80
11 2026-08-28 04:21 639234869341589104
2009 ms 162.240.105.80
10 2026-08-28 04:03 639234859012216675
352 ms 162.240.105.80
9 2026-08-28 03:46 639234848695364934
351 ms 162.240.105.80
8 2026-08-28 02:53 639234816952458162
359 ms 162.240.105.80
7 2026-08-28 02:36 639234806773081598
358 ms 162.240.105.80
6 2026-08-28 02:19 639234796382955255
367 ms 162.240.105.80
5 2026-08-28 02:02 639234786015782563
2007 ms 162.240.105.80
4 2026-08-28 01:08 639234753811917646
692 ms 162.240.105.80
3 2026-08-28 00:51 639234743739767811
1699 ms 162.240.105.80
2 2026-08-28 00:34 639234733372362811
379 ms 162.240.105.80
1 2026-08-28 00:17 639234723048550337
420 ms 162.240.105.80