DNS response history for ns2.the370z.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

250 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.1.80.108

Most recently resolved hosting IP on selected date

Successful Responses

34

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

Showing DNS history for 2026-08-26 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
34 2026-08-26 10:42 639233370841350248
323 ms 198.1.80.108
33 2026-08-26 10:25 639233360361507238
291 ms 198.1.80.108
32 2026-08-26 10:07 639233350067824371
294 ms 198.1.80.108
31 2026-08-26 09:50 639233339545274518
314 ms 198.1.80.108
30 2026-08-26 09:33 639233329214918079
294 ms 198.1.80.108
29 2026-08-26 09:15 639233318749762337
161 ms 198.1.80.108
28 2026-08-26 08:58 639233308387917838
331 ms 198.1.80.108
27 2026-08-26 08:41 639233297961740122
317 ms 198.1.80.108
26 2026-08-26 08:23 639233287487159094
241 ms 198.1.80.108
25 2026-08-26 08:06 639233276995531707
315 ms 198.1.80.108
24 2026-08-26 07:48 639233266521568229
292 ms 198.1.80.108
23 2026-08-26 07:31 639233256081047431
291 ms 198.1.80.108
22 2026-08-26 06:37 639233223620132921
7 ms 198.1.80.108
21 2026-08-26 06:20 639233213287814244
290 ms 198.1.80.108
20 2026-08-26 06:02 639233202925983161
291 ms 198.1.80.108
19 2026-08-26 05:45 639233192644780696
157 ms 198.1.80.108
18 2026-08-26 05:28 639233182401183833
318 ms 198.1.80.108
17 2026-08-26 05:11 639233172074181051
340 ms 198.1.80.108
16 2026-08-26 04:54 639233161808421455
232 ms 198.1.80.108
15 2026-08-26 04:36 639233151357344052
32 ms 198.1.80.108
14 2026-08-26 04:19 639233141034116946
296 ms 198.1.80.108
13 2026-08-26 04:02 639233130828334142
155 ms 198.1.80.108
12 2026-08-26 03:45 639233120373450007
291 ms 198.1.80.108
11 2026-08-26 03:27 639233110066216193
317 ms 198.1.80.108
10 2026-08-26 02:34 639233078065410564
7 ms 198.1.80.108
9 2026-08-26 02:17 639233067787457832
318 ms 198.1.80.108
8 2026-08-26 02:00 639233057501801162
288 ms 198.1.80.108
7 2026-08-26 01:43 639233047089431703
146 ms 198.1.80.108
6 2026-08-26 01:25 639233036754790688
287 ms 198.1.80.108
5 2026-08-26 01:08 639233026412602472
287 ms 198.1.80.108
4 2026-08-26 00:51 639233016064066127
290 ms 198.1.80.108
3 2026-08-26 00:34 639233005922655772
254 ms 198.1.80.108
2 2026-08-26 00:17 639232995672256907
292 ms 198.1.80.108
1 2026-08-26 00:00 639232985300872416
150 ms 198.1.80.108