DNS response history for ns.jp-tourism.biz

ns.jp-tourism.biz 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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 519 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 ns.jp-tourism.biz.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

519 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.51.14.86

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns.jp-tourism.biz

Showing DNS history for 2026-09-01 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
37 2026-09-01 12:48 639238628486902752
536 ms 202.51.14.86
36 2026-09-01 12:31 639238617906743100
778 ms 202.51.14.86
35 2026-09-01 12:13 639238607506044626
540 ms 202.51.14.86
34 2026-09-01 11:56 639238597040761406
516 ms 202.51.14.86
33 2026-09-01 11:38 639238586261546969
495 ms 202.51.14.86
32 2026-09-01 11:20 639238575587642333
516 ms 202.51.14.86
31 2026-09-01 10:26 639238543127398267
521 ms 202.51.14.86
30 2026-09-01 10:08 639238532668234016
482 ms 202.51.14.86
29 2026-09-01 09:51 639238522029321761
521 ms 202.51.14.86
28 2026-09-01 09:33 639238511519050351
505 ms 202.51.14.86
27 2026-09-01 09:16 639238500942239673
492 ms 202.51.14.86
26 2026-09-01 08:58 639238490412377398
504 ms 202.51.14.86
25 2026-09-01 08:40 639238479833203021
485 ms 202.51.14.86
24 2026-09-01 08:23 639238469140507479
505 ms 202.51.14.86
23 2026-09-01 08:05 639238458443560361
488 ms 202.51.14.86
22 2026-09-01 07:47 639238447694851502
484 ms 202.51.14.86
21 2026-09-01 07:29 639238436624109087
487 ms 202.51.14.86
20 2026-09-01 07:11 639238425565611335
553 ms 202.51.14.86
19 2026-09-01 06:15 639238392250222581
495 ms 202.51.14.86
18 2026-09-01 05:57 639238381322537831
525 ms 202.51.14.86
17 2026-09-01 05:39 639238370248186084
498 ms 202.51.14.86
16 2026-09-01 05:20 639238359264687845
515 ms 202.51.14.86
15 2026-09-01 05:02 639238348534621818
498 ms 202.51.14.86
14 2026-09-01 04:44 639238337725739433
510 ms 202.51.14.86
13 2026-09-01 04:26 639238326844749368
498 ms 202.51.14.86
12 2026-09-01 04:08 639238315792024737
507 ms 202.51.14.86
11 2026-09-01 03:50 639238304931064768
503 ms 202.51.14.86
10 2026-09-01 03:31 639238294131483803
517 ms 202.51.14.86
9 2026-09-01 03:13 639238283314985519
520 ms 202.51.14.86
8 2026-09-01 02:55 639238272374093187
519 ms 202.51.14.86
7 2026-09-01 02:01 639238240032549922
544 ms 202.51.14.86
6 2026-09-01 01:43 639238229204177368
517 ms 202.51.14.86
5 2026-09-01 01:25 639238218326150282
533 ms 202.51.14.86
4 2026-09-01 01:07 639238207574700853
508 ms 202.51.14.86
3 2026-09-01 00:49 639238196660283915
517 ms 202.51.14.86
2 2026-09-01 00:31 639238185782358546
525 ms 202.51.14.86
1 2026-09-01 00:13 639238175054391781
549 ms 202.51.14.86