DNS response history for mail.syscom.ne.jp

mail.syscom.ne.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 26 DNS check records, 26 successful responses, 0 failed responses, and 415 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 mail.syscom.ne.jp.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

415 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.225.64.3

Most recently resolved hosting IP on selected date

Successful Responses

26

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 mail.syscom.ne.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
26 2026-08-26 08:26 639233287487159094
555 ms 210.225.64.3
25 2026-08-26 08:09 639233276995531707
638 ms 210.225.64.3
24 2026-08-26 07:51 639233266521568229
306 ms 210.225.64.3
23 2026-08-26 07:33 639233256081047431
289 ms 210.225.64.3
22 2026-08-26 06:39 639233223620132921
561 ms 210.225.64.3
21 2026-08-26 06:22 639233213287814244
536 ms 210.225.64.3
20 2026-08-26 06:05 639233202925983161
535 ms 210.225.64.3
19 2026-08-26 05:48 639233192644780696
552 ms 210.225.64.3
18 2026-08-26 05:30 639233182401183833
280 ms 210.225.64.3
17 2026-08-26 05:13 639233172074181051
291 ms 210.225.64.3
16 2026-08-26 04:56 639233161808421455
559 ms 210.225.64.3
15 2026-08-26 04:39 639233151357344052
288 ms 210.225.64.3
14 2026-08-26 04:22 639233141034116946
552 ms 210.225.64.3
13 2026-08-26 04:05 639233130828334142
531 ms 210.225.64.3
12 2026-08-26 03:47 639233120373450007
284 ms 210.225.64.3
11 2026-08-26 03:30 639233110066216193
375 ms 210.225.64.3
10 2026-08-26 02:37 639233078065410564
559 ms 210.225.64.3
9 2026-08-26 02:20 639233067787457832
567 ms 210.225.64.3
8 2026-08-26 02:02 639233057501801162
3 ms 210.225.64.3
7 2026-08-26 01:45 639233047089431703
326 ms 210.225.64.3
6 2026-08-26 01:28 639233036754790688
535 ms 210.225.64.3
5 2026-08-26 01:11 639233026412602472
295 ms 210.225.64.3
4 2026-08-26 00:53 639233016064066127
2 ms 210.225.64.3
3 2026-08-26 00:36 639233005922655772
292 ms 210.225.64.3
2 2026-08-26 00:19 639232995672256907
527 ms 210.225.64.3
1 2026-08-26 00:02 639232985300872416
548 ms 210.225.64.3