DNS response history for ns2.syslog.jp

ns2.syslog.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 33 DNS check records, 33 successful responses, 0 failed responses, and 371 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.syslog.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

371 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

145.239.26.145

Most recently resolved hosting IP on selected date

Successful Responses

33

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.syslog.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
33 2026-08-26 10:25 639233360361507238
159 ms 145.239.26.145
32 2026-08-26 10:08 639233350067824371
2208 ms 145.239.26.145
31 2026-08-26 09:51 639233339545274518
31 ms 145.239.26.145
30 2026-08-26 09:33 639233329214918079
162 ms 145.239.26.145
29 2026-08-26 09:16 639233318749762337
160 ms 145.239.26.145
28 2026-08-26 08:58 639233308387917838
148 ms 145.239.26.145
27 2026-08-26 08:41 639233297961740122
56 ms 145.239.26.145
26 2026-08-26 08:24 639233287487159094
158 ms 145.239.26.145
25 2026-08-26 08:06 639233276995531707
131 ms 145.239.26.145
24 2026-08-26 07:49 639233266521568229
425 ms 145.239.26.145
23 2026-08-26 07:31 639233256081047431
160 ms 145.239.26.145
22 2026-08-26 06:37 639233223620132921
166 ms 145.239.26.145
21 2026-08-26 06:20 639233213287814244
161 ms 145.239.26.145
20 2026-08-26 06:03 639233202925983161
2124 ms 145.239.26.145
19 2026-08-26 05:45 639233192644780696
157 ms 145.239.26.145
18 2026-08-26 05:28 639233182401183833
158 ms 145.239.26.145
17 2026-08-26 05:11 639233172074181051
159 ms 145.239.26.145
16 2026-08-26 04:54 639233161808421455
179 ms 145.239.26.145
15 2026-08-26 04:37 639233151357344052
31 ms 145.239.26.145
14 2026-08-26 04:19 639233141034116946
157 ms 145.239.26.145
13 2026-08-26 04:02 639233130828334142
31 ms 145.239.26.145
12 2026-08-26 03:45 639233120373450007
172 ms 145.239.26.145
11 2026-08-26 03:28 639233110066216193
157 ms 145.239.26.145
10 2026-08-26 02:34 639233078065410564
2141 ms 145.239.26.145
9 2026-08-26 02:17 639233067787457832
156 ms 145.239.26.145
8 2026-08-26 02:00 639233057501801162
154 ms 145.239.26.145
7 2026-08-26 01:43 639233047089431703
171 ms 145.239.26.145
6 2026-08-26 01:26 639233036754790688
32 ms 145.239.26.145
5 2026-08-26 01:08 639233026412602472
156 ms 145.239.26.145
4 2026-08-26 00:51 639233016064066127
1531 ms 145.239.26.145
3 2026-08-26 00:34 639233005922655772
152 ms 145.239.26.145
2 2026-08-26 00:17 639232995672256907
162 ms 145.239.26.145
1 2026-08-26 00:00 639232985300872416
128 ms 145.239.26.145