DNS response history for ns1.meguroku-med.jp

ns1.meguroku-med.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-27. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 874 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 ns1.meguroku-med.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

874 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.133.240.172

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.meguroku-med.jp

Showing DNS history for 2026-08-27 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
30 2026-08-27 09:51 639234202117531850
1166 ms 27.133.240.172
29 2026-08-27 09:34 639234191649612722
1012 ms 27.133.240.172
28 2026-08-27 09:17 639234181105879568
960 ms 27.133.240.172
27 2026-08-27 08:59 639234170713214496
995 ms 27.133.240.172
26 2026-08-27 08:42 639234160341037652
990 ms 27.133.240.172
25 2026-08-27 08:24 639234149799404224
933 ms 27.133.240.172
24 2026-08-27 08:07 639234139553286469
1196 ms 27.133.240.172
23 2026-08-27 07:13 639234107183588293
1047 ms 27.133.240.172
22 2026-08-27 06:56 639234096905435724
1003 ms 27.133.240.172
21 2026-08-27 06:39 639234086579410775
921 ms 27.133.240.172
20 2026-08-27 06:21 639234076291157956
1138 ms 27.133.240.172
19 2026-08-27 06:04 639234065981939454
493 ms 27.133.240.172
18 2026-08-27 05:47 639234055548642997
911 ms 27.133.240.172
17 2026-08-27 05:30 639234045267979603
905 ms 27.133.240.172
16 2026-08-27 05:13 639234034999717463
932 ms 27.133.240.172
15 2026-08-27 04:55 639234024739225358
906 ms 27.133.240.172
14 2026-08-27 04:38 639234014311170162
909 ms 27.133.240.172
13 2026-08-27 04:21 639234003806017640
705 ms 27.133.240.172
12 2026-08-27 04:03 639233993356203030
932 ms 27.133.240.172
11 2026-08-27 03:10 639233961301716608
1063 ms 27.133.240.172
10 2026-08-27 02:53 639233950834200647
896 ms 27.133.240.172
9 2026-08-27 02:35 639233940431849026
917 ms 27.133.240.172
8 2026-08-27 02:18 639233930110596398
918 ms 27.133.240.172
7 2026-08-27 02:01 639233919705434540
3 ms 27.133.240.172
6 2026-08-27 01:44 639233909452807845
822 ms 27.133.240.172
5 2026-08-27 01:26 639233899096420820
749 ms 27.133.240.172
4 2026-08-27 01:09 639233888707824939
3 ms 27.133.240.172
3 2026-08-27 00:52 639233878461203802
939 ms 27.133.240.172
2 2026-08-27 00:35 639233868060868209
930 ms 27.133.240.172
1 2026-08-27 00:17 639233857450922991
923 ms 27.133.240.172