DNS response history for ns2.sheer.co.jp

ns2.sheer.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 34 DNS check records, 34 successful responses, 0 failed responses, and 510 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.sheer.co.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

510 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.137.113.166

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 ns2.sheer.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
34 2026-08-25 12:06 639232556111768563
553 ms 203.137.113.166
33 2026-08-25 11:49 639232545839529039
260 ms 203.137.113.166
32 2026-08-25 11:32 639232535349285207
4 ms 203.137.113.166
31 2026-08-25 11:14 639232524938080723
17 ms 203.137.113.166
30 2026-08-25 10:21 639232492740373468
2299 ms 203.137.113.166
29 2026-08-25 10:03 639232482235303141
3 ms 203.137.113.166
28 2026-08-25 09:46 639232471861770303
3 ms 203.137.113.166
27 2026-08-25 09:29 639232461630217327
257 ms 203.137.113.166
26 2026-08-25 09:11 639232451282965990
540 ms 203.137.113.166
25 2026-08-25 08:54 639232440814614938
261 ms 203.137.113.166
24 2026-08-25 08:37 639232430410720425
251 ms 203.137.113.166
23 2026-08-25 08:19 639232420003096185
546 ms 203.137.113.166
22 2026-08-25 08:02 639232409467287444
273 ms 203.137.113.166
21 2026-08-25 07:45 639232399077195997
340 ms 203.137.113.166
20 2026-08-25 07:27 639232388731528337
501 ms 203.137.113.166
19 2026-08-25 07:10 639232378288598612
270 ms 203.137.113.166
18 2026-08-25 06:16 639232346196373643
250 ms 203.137.113.166
17 2026-08-25 05:59 639232336112370741
2254 ms 203.137.113.166
16 2026-08-25 05:43 639232326146508970
507 ms 203.137.113.166
15 2026-08-25 05:26 639232316189381720
512 ms 203.137.113.166
14 2026-08-25 05:09 639232306217998913
254 ms 203.137.113.166
13 2026-08-25 04:53 639232296255744174
495 ms 203.137.113.166
12 2026-08-25 04:36 639232286095760789
499 ms 203.137.113.166
11 2026-08-25 04:19 639232276086186273
564 ms 203.137.113.166
10 2026-08-25 04:02 639232265900986425
2275 ms 203.137.113.166
9 2026-08-25 03:46 639232255723518075
494 ms 203.137.113.166
8 2026-08-25 03:28 639232245484452890
264 ms 203.137.113.166
7 2026-08-25 03:11 639232235157175331
537 ms 203.137.113.166
6 2026-08-25 02:18 639232203197189095
249 ms 203.137.113.166
5 2026-08-25 02:01 639232192844564298
252 ms 203.137.113.166
4 2026-08-25 01:44 639232182496008942
255 ms 203.137.113.166
3 2026-08-25 01:26 639232172197053132
513 ms 203.137.113.166
2 2026-08-25 00:33 639232140250307418
259 ms 203.137.113.166
1 2026-08-25 00:16 639232129927860324
525 ms 203.137.113.166