DNS response history for ns11.sinfony.ad.jp

ns11.sinfony.ad.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-26. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 290 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 ns11.sinfony.ad.jp.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.213.195.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 ns11.sinfony.ad.jp

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:13 639233424567558554
236 ms 202.213.195.6
36 2026-08-26 11:55 639233414056832719
235 ms 202.213.195.6
35 2026-08-26 11:38 639233403515141099
239 ms 202.213.195.6
34 2026-08-26 10:43 639233370841350248
224 ms 202.213.195.6
33 2026-08-26 10:26 639233360361507238
469 ms 202.213.195.6
32 2026-08-26 10:08 639233350067824371
478 ms 202.213.195.6
31 2026-08-26 09:51 639233339545274518
246 ms 202.213.195.6
30 2026-08-26 09:34 639233329214918079
229 ms 202.213.195.6
29 2026-08-26 09:16 639233318749762337
236 ms 202.213.195.6
28 2026-08-26 08:59 639233308387917838
227 ms 202.213.195.6
27 2026-08-26 08:42 639233297961740122
715 ms 202.213.195.6
26 2026-08-26 08:24 639233287487159094
493 ms 202.213.195.6
25 2026-08-26 08:07 639233276995531707
225 ms 202.213.195.6
24 2026-08-26 07:49 639233266521568229
225 ms 202.213.195.6
23 2026-08-26 07:32 639233256081047431
225 ms 202.213.195.6
22 2026-08-26 06:38 639233223620132921
223 ms 202.213.195.6
21 2026-08-26 06:21 639233213287814244
259 ms 202.213.195.6
20 2026-08-26 06:03 639233202925983161
470 ms 202.213.195.6
19 2026-08-26 05:46 639233192644780696
460 ms 202.213.195.6
18 2026-08-26 05:29 639233182401183833
237 ms 202.213.195.6
17 2026-08-26 05:12 639233172074181051
225 ms 202.213.195.6
16 2026-08-26 04:55 639233161808421455
469 ms 202.213.195.6
15 2026-08-26 04:38 639233151357344052
225 ms 202.213.195.6
14 2026-08-26 04:20 639233141034116946
229 ms 202.213.195.6
13 2026-08-26 04:03 639233130828334142
235 ms 202.213.195.6
12 2026-08-26 03:46 639233120373450007
7 ms 202.213.195.6
11 2026-08-26 03:28 639233110066216193
233 ms 202.213.195.6
10 2026-08-26 02:35 639233078065410564
227 ms 202.213.195.6
9 2026-08-26 02:18 639233067787457832
241 ms 202.213.195.6
8 2026-08-26 02:01 639233057501801162
472 ms 202.213.195.6
7 2026-08-26 01:44 639233047089431703
229 ms 202.213.195.6
6 2026-08-26 01:26 639233036754790688
223 ms 202.213.195.6
5 2026-08-26 01:09 639233026412602472
230 ms 202.213.195.6
4 2026-08-26 00:52 639233016064066127
231 ms 202.213.195.6
3 2026-08-26 00:35 639233005922655772
224 ms 202.213.195.6
2 2026-08-26 00:18 639232995672256907
470 ms 202.213.195.6
1 2026-08-26 00:01 639232985300872416
223 ms 202.213.195.6