DNS response history for ns2.protect-jp.net

ns2.protect-jp.net 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 37 DNS check records, 37 successful responses, 0 failed responses, and 472 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.protect-jp.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

472 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.249.72.6

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 ns2.protect-jp.net

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
37 2026-08-26 12:15 639233424567558554
467 ms 103.249.72.6
36 2026-08-26 11:57 639233414056832719
472 ms 103.249.72.6
35 2026-08-26 11:40 639233403515141099
490 ms 103.249.72.6
34 2026-08-26 10:45 639233370841350248
468 ms 103.249.72.6
33 2026-08-26 10:28 639233360361507238
482 ms 103.249.72.6
32 2026-08-26 10:10 639233350067824371
468 ms 103.249.72.6
31 2026-08-26 09:53 639233339545274518
476 ms 103.249.72.6
30 2026-08-26 09:36 639233329214918079
476 ms 103.249.72.6
29 2026-08-26 09:18 639233318749762337
465 ms 103.249.72.6
28 2026-08-26 09:01 639233308387917838
475 ms 103.249.72.6
27 2026-08-26 08:44 639233297961740122
469 ms 103.249.72.6
26 2026-08-26 08:26 639233287487159094
480 ms 103.249.72.6
25 2026-08-26 08:09 639233276995531707
489 ms 103.249.72.6
24 2026-08-26 07:51 639233266521568229
477 ms 103.249.72.6
23 2026-08-26 07:34 639233256081047431
474 ms 103.249.72.6
22 2026-08-26 06:40 639233223620132921
472 ms 103.249.72.6
21 2026-08-26 06:22 639233213287814244
470 ms 103.249.72.6
20 2026-08-26 06:05 639233202925983161
475 ms 103.249.72.6
19 2026-08-26 05:48 639233192644780696
469 ms 103.249.72.6
18 2026-08-26 05:31 639233182401183833
466 ms 103.249.72.6
17 2026-08-26 05:14 639233172074181051
472 ms 103.249.72.6
16 2026-08-26 04:56 639233161808421455
471 ms 103.249.72.6
15 2026-08-26 04:39 639233151357344052
462 ms 103.249.72.6
14 2026-08-26 04:22 639233141034116946
475 ms 103.249.72.6
13 2026-08-26 04:05 639233130828334142
471 ms 103.249.72.6
12 2026-08-26 03:48 639233120373450007
471 ms 103.249.72.6
11 2026-08-26 03:30 639233110066216193
468 ms 103.249.72.6
10 2026-08-26 02:37 639233078065410564
468 ms 103.249.72.6
9 2026-08-26 02:20 639233067787457832
479 ms 103.249.72.6
8 2026-08-26 02:03 639233057501801162
474 ms 103.249.72.6
7 2026-08-26 01:46 639233047089431703
469 ms 103.249.72.6
6 2026-08-26 01:28 639233036754790688
461 ms 103.249.72.6
5 2026-08-26 01:11 639233026412602472
476 ms 103.249.72.6
4 2026-08-26 00:54 639233016064066127
471 ms 103.249.72.6
3 2026-08-26 00:37 639233005922655772
482 ms 103.249.72.6
2 2026-08-26 00:20 639232995672256907
466 ms 103.249.72.6
1 2026-08-26 00:02 639232985300872416
460 ms 103.249.72.6