DNS response history for h2.net50.ne.jp

h2.net50.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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 1071 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 h2.net50.ne.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

1071 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.133.167.2

Most recently resolved hosting IP on selected date

Successful Responses

31

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 h2.net50.ne.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
31 2026-08-25 10:22 639232492740373468
1065 ms 210.133.167.2
30 2026-08-25 10:05 639232482235303141
1126 ms 210.133.167.2
29 2026-08-25 09:48 639232471861770303
1113 ms 210.133.167.2
28 2026-08-25 09:31 639232461630217327
1148 ms 210.133.167.2
27 2026-08-25 09:13 639232451282965990
1112 ms 210.133.167.2
26 2026-08-25 08:56 639232440814614938
1166 ms 210.133.167.2
25 2026-08-25 08:39 639232430410720425
1128 ms 210.133.167.2
24 2026-08-25 08:21 639232420003096185
1124 ms 210.133.167.2
23 2026-08-25 08:04 639232409467287444
1137 ms 210.133.167.2
22 2026-08-25 07:47 639232399077195997
1165 ms 210.133.167.2
21 2026-08-25 07:29 639232388731528337
1100 ms 210.133.167.2
20 2026-08-25 07:12 639232378288598612
1118 ms 210.133.167.2
19 2026-08-25 06:18 639232346196373643
1129 ms 210.133.167.2
18 2026-08-25 06:01 639232336112370741
1109 ms 210.133.167.2
17 2026-08-25 05:44 639232326146508970
1099 ms 210.133.167.2
16 2026-08-25 05:28 639232316189381720
1191 ms 210.133.167.2
15 2026-08-25 05:11 639232306217998913
1127 ms 210.133.167.2
14 2026-08-25 04:55 639232296255744174
3 ms 210.133.167.2
13 2026-08-25 04:38 639232286095760789
1075 ms 210.133.167.2
12 2026-08-25 04:21 639232276086186273
1133 ms 210.133.167.2
11 2026-08-25 04:04 639232265900986425
304 ms 210.133.167.2
10 2026-08-25 03:47 639232255723518075
1382 ms 210.133.167.2
9 2026-08-25 03:30 639232245484452890
1142 ms 210.133.167.2
8 2026-08-25 03:13 639232235157175331
1154 ms 210.133.167.2
7 2026-08-25 02:20 639232203197189095
1101 ms 210.133.167.2
6 2026-08-25 02:03 639232192844564298
2007 ms 210.133.167.2
5 2026-08-25 01:45 639232182496008942
1091 ms 210.133.167.2
4 2026-08-25 01:28 639232172197053132
1377 ms 210.133.167.2
3 2026-08-25 00:35 639232140250307418
1153 ms 210.133.167.2
2 2026-08-25 00:18 639232129927860324
1109 ms 210.133.167.2
1 2026-08-25 00:01 639232119551972438
4 ms 210.133.167.2