DNS response history for ns2.nyspinept.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

426 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.3.117.103

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

Showing DNS history for 2026-08-24 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-24 12:24 639231703815441688
1546 ms 50.3.117.103
29 2026-08-24 12:08 639231693747052549
85 ms 50.3.117.103
28 2026-08-24 11:51 639231683712487276
121 ms 50.3.117.103
27 2026-08-24 11:34 639231673513573868
1249 ms 50.3.117.103
26 2026-08-24 10:41 639231641791249939
84 ms 50.3.117.103
25 2026-08-24 10:24 639231631866211033
1705 ms 50.3.117.103
24 2026-08-24 10:08 639231621644955316
4 ms 50.3.117.103
23 2026-08-24 09:51 639231611478799259
95 ms 50.3.117.103
22 2026-08-24 08:58 639231579923718211
5 ms 50.3.117.103
21 2026-08-24 08:41 639231569810702936
16 ms 50.3.117.103
20 2026-08-24 08:24 639231559762411619
5 ms 50.3.117.103
19 2026-08-24 08:07 639231549663595407
92 ms 50.3.117.103
18 2026-08-24 07:15 639231518076817246
5 ms 50.3.117.103
17 2026-08-24 06:58 639231508078650885
3 ms 50.3.117.103
16 2026-08-24 06:42 639231498210697093
3 ms 50.3.117.103
15 2026-08-24 06:25 639231488109699360
94 ms 50.3.117.103
14 2026-08-24 05:33 639231456772510692
86 ms 50.3.117.103
13 2026-08-24 05:16 639231447084631185
91 ms 50.3.117.103
12 2026-08-24 05:00 639231437208519473
680 ms 50.3.117.103
11 2026-08-24 04:43 639231427209627490
88 ms 50.3.117.103
10 2026-08-24 03:51 639231395791246644
4 ms 50.3.117.103
9 2026-08-24 03:35 639231386075551458
1570 ms 50.3.117.103
8 2026-08-24 03:18 639231376208713791
662 ms 50.3.117.103
7 2026-08-24 03:02 639231366170589276
84 ms 50.3.117.103
6 2026-08-24 02:09 639231334732159368
89 ms 50.3.117.103
5 2026-08-24 01:53 639231325035670078
2 ms 50.3.117.103
4 2026-08-24 01:37 639231315132253837
82 ms 50.3.117.103
3 2026-08-24 01:20 639231305014280808
3543 ms 50.3.117.103
2 2026-08-24 00:27 639231273779380675
9 ms 50.3.117.103
1 2026-08-24 00:12 639231264180839154
673 ms 50.3.117.103