DNS response history for ns2.xserv.jp

ns2.xserv.jp 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 533 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.xserv.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

533 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

183.90.180.104

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 ns2.xserv.jp

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:26 639231703815441688
245 ms 183.90.180.104
29 2026-08-24 12:09 639231693747052549
480 ms 183.90.180.104
28 2026-08-24 11:52 639231683712487276
502 ms 183.90.180.104
27 2026-08-24 11:35 639231673513573868
501 ms 183.90.180.104
26 2026-08-24 10:42 639231641791249939
495 ms 183.90.180.104
25 2026-08-24 10:26 639231631866211033
502 ms 183.90.180.104
24 2026-08-24 10:09 639231621644955316
237 ms 183.90.180.104
23 2026-08-24 09:52 639231611478799259
281 ms 183.90.180.104
22 2026-08-24 08:59 639231579923718211
5 ms 183.90.180.104
21 2026-08-24 08:43 639231569810702936
477 ms 183.90.180.104
20 2026-08-24 08:25 639231559762411619
252 ms 183.90.180.104
19 2026-08-24 08:09 639231549663595407
244 ms 183.90.180.104
18 2026-08-24 07:16 639231518076817246
280 ms 183.90.180.104
17 2026-08-24 07:00 639231508078650885
951 ms 183.90.180.104
16 2026-08-24 06:43 639231498210697093
460 ms 183.90.180.104
15 2026-08-24 06:26 639231488109699360
237 ms 183.90.180.104
14 2026-08-24 05:34 639231456772510692
4257 ms 183.90.180.104
13 2026-08-24 05:18 639231447084631185
489 ms 183.90.180.104
12 2026-08-24 05:01 639231437208519473
922 ms 183.90.180.104
11 2026-08-24 04:45 639231427209627490
6 ms 183.90.180.104
10 2026-08-24 03:52 639231395791246644
255 ms 183.90.180.104
9 2026-08-24 03:36 639231386075551458
259 ms 183.90.180.104
8 2026-08-24 03:20 639231376208713791
315 ms 183.90.180.104
7 2026-08-24 03:03 639231366170589276
930 ms 183.90.180.104
6 2026-08-24 02:11 639231334732159368
914 ms 183.90.180.104
5 2026-08-24 01:54 639231325035670078
3 ms 183.90.180.104
4 2026-08-24 01:38 639231315132253837
489 ms 183.90.180.104
3 2026-08-24 01:21 639231305014280808
263 ms 183.90.180.104
2 2026-08-24 00:29 639231273779380675
251 ms 183.90.180.104
1 2026-08-24 00:13 639231264180839154
491 ms 183.90.180.104