DNS response history for ns02.tennisrecord.com

ns02.tennisrecord.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 368 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 ns02.tennisrecord.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

368 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

75.130.60.3

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 ns02.tennisrecord.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
118 ms 75.130.60.3
29 2026-08-24 12:07 639231693747052549
236 ms 75.130.60.3
28 2026-08-24 11:50 639231683712487276
231 ms 75.130.60.3
27 2026-08-24 11:33 639231673513573868
237 ms 75.130.60.3
26 2026-08-24 10:40 639231641791249939
238 ms 75.130.60.3
25 2026-08-24 10:24 639231631866211033
235 ms 75.130.60.3
24 2026-08-24 10:07 639231621644955316
233 ms 75.130.60.3
23 2026-08-24 09:50 639231611478799259
232 ms 75.130.60.3
22 2026-08-24 08:57 639231579923718211
299 ms 75.130.60.3
21 2026-08-24 08:41 639231569810702936
351 ms 75.130.60.3
20 2026-08-24 08:24 639231559762411619
338 ms 75.130.60.3
19 2026-08-24 08:07 639231549663595407
232 ms 75.130.60.3
18 2026-08-24 07:14 639231518076817246
234 ms 75.130.60.3
17 2026-08-24 06:58 639231508078650885
2153 ms 75.130.60.3
16 2026-08-24 06:41 639231498210697093
233 ms 75.130.60.3
15 2026-08-24 06:25 639231488109699360
239 ms 75.130.60.3
14 2026-08-24 05:32 639231456772510692
228 ms 75.130.60.3
13 2026-08-24 05:16 639231447084631185
231 ms 75.130.60.3
12 2026-08-24 04:59 639231437208519473
290 ms 75.130.60.3
11 2026-08-24 04:43 639231427209627490
2314 ms 75.130.60.3
10 2026-08-24 03:50 639231395791246644
233 ms 75.130.60.3
9 2026-08-24 03:34 639231386075551458
231 ms 75.130.60.3
8 2026-08-24 03:18 639231376208713791
251 ms 75.130.60.3
7 2026-08-24 03:01 639231366170589276
234 ms 75.130.60.3
6 2026-08-24 02:09 639231334732159368
237 ms 75.130.60.3
5 2026-08-24 01:52 639231325035670078
237 ms 75.130.60.3
4 2026-08-24 01:36 639231315132253837
123 ms 75.130.60.3
3 2026-08-24 01:19 639231305014280808
237 ms 75.130.60.3
2 2026-08-24 00:27 639231273779380675
232 ms 75.130.60.3
1 2026-08-24 00:11 639231264180839154
121 ms 75.130.60.3