DNS response history for ns3.voicecall.jp

ns3.voicecall.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 517 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 ns3.voicecall.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

517 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.126.130.210

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.voicecall.jp

Showing DNS history for 2026-08-27 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
34 2026-08-27 10:59 639234243654907465
540 ms 153.126.130.210
33 2026-08-27 10:42 639234233269654413
538 ms 153.126.130.210
32 2026-08-27 10:25 639234222943951923
541 ms 153.126.130.210
31 2026-08-27 10:08 639234212558002823
544 ms 153.126.130.210
30 2026-08-27 09:50 639234202117531850
569 ms 153.126.130.210
29 2026-08-27 09:33 639234191649612722
544 ms 153.126.130.210
28 2026-08-27 09:15 639234181105879568
543 ms 153.126.130.210
27 2026-08-27 08:58 639234170713214496
535 ms 153.126.130.210
26 2026-08-27 08:41 639234160341037652
532 ms 153.126.130.210
25 2026-08-27 08:23 639234149799404224
532 ms 153.126.130.210
24 2026-08-27 08:05 639234139553286469
583 ms 153.126.130.210
23 2026-08-27 07:12 639234107183588293
554 ms 153.126.130.210
22 2026-08-27 06:55 639234096905435724
533 ms 153.126.130.210
21 2026-08-27 06:38 639234086579410775
545 ms 153.126.130.210
20 2026-08-27 06:20 639234076291157956
544 ms 153.126.130.210
19 2026-08-27 06:03 639234065981939454
530 ms 153.126.130.210
18 2026-08-27 05:46 639234055548642997
8 ms 153.126.130.210
17 2026-08-27 05:29 639234045267979603
528 ms 153.126.130.210
16 2026-08-27 05:12 639234034999717463
536 ms 153.126.130.210
15 2026-08-27 04:54 639234024739225358
515 ms 153.126.130.210
14 2026-08-27 04:37 639234014311170162
544 ms 153.126.130.210
13 2026-08-27 04:20 639234003806017640
544 ms 153.126.130.210
12 2026-08-27 04:02 639233993356203030
527 ms 153.126.130.210
11 2026-08-27 03:09 639233961301716608
524 ms 153.126.130.210
10 2026-08-27 02:52 639233950834200647
533 ms 153.126.130.210
9 2026-08-27 02:34 639233940431849026
300 ms 153.126.130.210
8 2026-08-27 02:17 639233930110596398
547 ms 153.126.130.210
7 2026-08-27 02:00 639233919705434540
556 ms 153.126.130.210
6 2026-08-27 01:42 639233909452807845
526 ms 153.126.130.210
5 2026-08-27 01:25 639233899096420820
532 ms 153.126.130.210
4 2026-08-27 01:08 639233888707824939
527 ms 153.126.130.210
3 2026-08-27 00:51 639233878461203802
545 ms 153.126.130.210
2 2026-08-27 00:33 639233868060868209
541 ms 153.126.130.210
1 2026-08-27 00:16 639233857450922991
549 ms 153.126.130.210