DNS response history for ns2.watchbuyerjerseycity.com

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

18

Historical checks stored for this nameserver on selected date

Average Latency

236 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.173.126

Most recently resolved hosting IP on selected date

Successful Responses

18

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.watchbuyerjerseycity.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
18 2026-08-25 06:12 639232346196373643
4 ms 135.148.173.126
17 2026-08-25 05:55 639232336112370741
112 ms 135.148.173.126
16 2026-08-25 05:38 639232326146508970
217 ms 135.148.173.126
15 2026-08-25 05:22 639232316189381720
2224 ms 135.148.173.126
14 2026-08-25 05:05 639232306217998913
206 ms 135.148.173.126
13 2026-08-25 04:48 639232296255744174
208 ms 135.148.173.126
12 2026-08-25 04:32 639232286095760789
203 ms 135.148.173.126
11 2026-08-25 04:15 639232276086186273
8 ms 135.148.173.126
10 2026-08-25 03:58 639232265900986425
205 ms 135.148.173.126
9 2026-08-25 03:41 639232255723518075
17 ms 135.148.173.126
8 2026-08-25 03:24 639232245484452890
8 ms 135.148.173.126
7 2026-08-25 03:07 639232235157175331
110 ms 135.148.173.126
6 2026-08-25 02:13 639232203197189095
115 ms 135.148.173.126
5 2026-08-25 01:56 639232192844564298
204 ms 135.148.173.126
4 2026-08-25 01:39 639232182496008942
41 ms 135.148.173.126
3 2026-08-25 01:22 639232172197053132
108 ms 135.148.173.126
2 2026-08-25 00:28 639232140250307418
31 ms 135.148.173.126
1 2026-08-25 00:11 639232129927860324
221 ms 135.148.173.126