DNS response history for ns2.performancedata.co.jp

ns2.performancedata.co.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 636 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.performancedata.co.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

636 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.95.51.99

Most recently resolved hosting IP on selected date

Successful Responses

32

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.performancedata.co.jp

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:32 639232535349285207
513 ms 54.95.51.99
31 2026-08-25 11:15 639232524938080723
501 ms 54.95.51.99
30 2026-08-25 10:21 639232492740373468
492 ms 54.95.51.99
29 2026-08-25 10:04 639232482235303141
489 ms 54.95.51.99
28 2026-08-25 09:46 639232471861770303
479 ms 54.95.51.99
27 2026-08-25 09:29 639232461630217327
3 ms 54.95.51.99
26 2026-08-25 09:12 639232451282965990
497 ms 54.95.51.99
25 2026-08-25 08:55 639232440814614938
491 ms 54.95.51.99
24 2026-08-25 08:37 639232430410720425
484 ms 54.95.51.99
23 2026-08-25 08:20 639232420003096185
518 ms 54.95.51.99
22 2026-08-25 08:02 639232409467287444
740 ms 54.95.51.99
21 2026-08-25 07:45 639232399077195997
502 ms 54.95.51.99
20 2026-08-25 07:28 639232388731528337
511 ms 54.95.51.99
19 2026-08-25 07:10 639232378288598612
488 ms 54.95.51.99
18 2026-08-25 06:17 639232346196373643
2264 ms 54.95.51.99
17 2026-08-25 06:00 639232336112370741
3 ms 54.95.51.99
16 2026-08-25 05:43 639232326146508970
503 ms 54.95.51.99
15 2026-08-25 05:26 639232316189381720
513 ms 54.95.51.99
14 2026-08-25 05:10 639232306217998913
491 ms 54.95.51.99
13 2026-08-25 04:53 639232296255744174
499 ms 54.95.51.99
12 2026-08-25 04:36 639232286095760789
2243 ms 54.95.51.99
11 2026-08-25 04:19 639232276086186273
501 ms 54.95.51.99
10 2026-08-25 04:03 639232265900986425
493 ms 54.95.51.99
9 2026-08-25 03:46 639232255723518075
2333 ms 54.95.51.99
8 2026-08-25 03:29 639232245484452890
511 ms 54.95.51.99
7 2026-08-25 03:12 639232235157175331
511 ms 54.95.51.99
6 2026-08-25 02:18 639232203197189095
499 ms 54.95.51.99
5 2026-08-25 02:01 639232192844564298
251 ms 54.95.51.99
4 2026-08-25 01:44 639232182496008942
514 ms 54.95.51.99
3 2026-08-25 01:27 639232172197053132
500 ms 54.95.51.99
2 2026-08-25 00:33 639232140250307418
489 ms 54.95.51.99
1 2026-08-25 00:16 639232129927860324
515 ms 54.95.51.99