DNS response history for ns03.setagayatm.or.jp

ns03.setagayatm.or.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 32 DNS check records, 32 successful responses, 0 failed responses, and 609 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 ns03.setagayatm.or.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

609 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.248.5.5

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns03.setagayatm.or.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
32 2026-08-27 10:25 639234222943951923
868 ms 202.248.5.5
31 2026-08-27 10:08 639234212558002823
751 ms 202.248.5.5
30 2026-08-27 09:51 639234202117531850
814 ms 202.248.5.5
29 2026-08-27 09:33 639234191649612722
243 ms 202.248.5.5
28 2026-08-27 09:16 639234181105879568
695 ms 202.248.5.5
27 2026-08-27 08:58 639234170713214496
618 ms 202.248.5.5
26 2026-08-27 08:41 639234160341037652
522 ms 202.248.5.5
25 2026-08-27 08:24 639234149799404224
571 ms 202.248.5.5
24 2026-08-27 08:06 639234139553286469
367 ms 202.248.5.5
23 2026-08-27 07:13 639234107183588293
756 ms 202.248.5.5
22 2026-08-27 06:55 639234096905435724
516 ms 202.248.5.5
21 2026-08-27 06:38 639234086579410775
518 ms 202.248.5.5
20 2026-08-27 06:21 639234076291157956
343 ms 202.248.5.5
19 2026-08-27 06:04 639234065981939454
515 ms 202.248.5.5
18 2026-08-27 05:47 639234055548642997
565 ms 202.248.5.5
17 2026-08-27 05:29 639234045267979603
523 ms 202.248.5.5
16 2026-08-27 05:12 639234034999717463
515 ms 202.248.5.5
15 2026-08-27 04:55 639234024739225358
557 ms 202.248.5.5
14 2026-08-27 04:38 639234014311170162
513 ms 202.248.5.5
13 2026-08-27 04:20 639234003806017640
744 ms 202.248.5.5
12 2026-08-27 04:03 639233993356203030
520 ms 202.248.5.5
11 2026-08-27 03:10 639233961301716608
551 ms 202.248.5.5
10 2026-08-27 02:52 639233950834200647
524 ms 202.248.5.5
9 2026-08-27 02:35 639233940431849026
504 ms 202.248.5.5
8 2026-08-27 02:17 639233930110596398
508 ms 202.248.5.5
7 2026-08-27 02:00 639233919705434540
502 ms 202.248.5.5
6 2026-08-27 01:43 639233909452807845
524 ms 202.248.5.5
5 2026-08-27 01:26 639233899096420820
518 ms 202.248.5.5
4 2026-08-27 01:09 639233888707824939
517 ms 202.248.5.5
3 2026-08-27 00:51 639233878461203802
2265 ms 202.248.5.5
2 2026-08-27 00:34 639233868060868209
515 ms 202.248.5.5
1 2026-08-27 00:17 639233857450922991
511 ms 202.248.5.5