DNS response history for ns2.seiyoginza.com

ns2.seiyoginza.com 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 38 DNS check records, 38 successful responses, 0 failed responses, and 506 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.seiyoginza.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

506 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.140.42.201

Most recently resolved hosting IP on selected date

Successful Responses

38

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.seiyoginza.com

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
38 2026-08-27 12:46 639234307007468133
520 ms 210.140.42.201
37 2026-08-27 12:28 639234296664302575
516 ms 210.140.42.201
36 2026-08-27 12:11 639234286253196126
498 ms 210.140.42.201
35 2026-08-27 11:17 639234253963286387
510 ms 210.140.42.201
34 2026-08-27 11:00 639234243654907465
508 ms 210.140.42.201
33 2026-08-27 10:43 639234233269654413
508 ms 210.140.42.201
32 2026-08-27 10:25 639234222943951923
505 ms 210.140.42.201
31 2026-08-27 10:08 639234212558002823
538 ms 210.140.42.201
30 2026-08-27 09:51 639234202117531850
506 ms 210.140.42.201
29 2026-08-27 09:33 639234191649612722
500 ms 210.140.42.201
28 2026-08-27 09:16 639234181105879568
507 ms 210.140.42.201
27 2026-08-27 08:58 639234170713214496
499 ms 210.140.42.201
26 2026-08-27 08:41 639234160341037652
511 ms 210.140.42.201
25 2026-08-27 08:24 639234149799404224
520 ms 210.140.42.201
24 2026-08-27 08:06 639234139553286469
511 ms 210.140.42.201
23 2026-08-27 07:12 639234107183588293
505 ms 210.140.42.201
22 2026-08-27 06:55 639234096905435724
512 ms 210.140.42.201
21 2026-08-27 06:38 639234086579410775
505 ms 210.140.42.201
20 2026-08-27 06:21 639234076291157956
504 ms 210.140.42.201
19 2026-08-27 06:04 639234065981939454
511 ms 210.140.42.201
18 2026-08-27 05:46 639234055548642997
492 ms 210.140.42.201
17 2026-08-27 05:29 639234045267979603
493 ms 210.140.42.201
16 2026-08-27 05:12 639234034999717463
513 ms 210.140.42.201
15 2026-08-27 04:55 639234024739225358
488 ms 210.140.42.201
14 2026-08-27 04:38 639234014311170162
513 ms 210.140.42.201
13 2026-08-27 04:20 639234003806017640
493 ms 210.140.42.201
12 2026-08-27 04:03 639233993356203030
489 ms 210.140.42.201
11 2026-08-27 03:09 639233961301716608
488 ms 210.140.42.201
10 2026-08-27 02:52 639233950834200647
508 ms 210.140.42.201
9 2026-08-27 02:35 639233940431849026
500 ms 210.140.42.201
8 2026-08-27 02:17 639233930110596398
499 ms 210.140.42.201
7 2026-08-27 02:00 639233919705434540
517 ms 210.140.42.201
6 2026-08-27 01:43 639233909452807845
508 ms 210.140.42.201
5 2026-08-27 01:26 639233899096420820
508 ms 210.140.42.201
4 2026-08-27 01:08 639233888707824939
521 ms 210.140.42.201
3 2026-08-27 00:51 639233878461203802
499 ms 210.140.42.201
2 2026-08-27 00:34 639233868060868209
511 ms 210.140.42.201
1 2026-08-27 00:17 639233857450922991
494 ms 210.140.42.201