DNS response history for ns03.twinring.jp

ns03.twinring.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 35 DNS check records, 35 successful responses, 0 failed responses, and 465 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.twinring.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

125.101.157.226

Most recently resolved hosting IP on selected date

Successful Responses

35

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.twinring.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
35 2026-08-27 11:17 639234253963286387
501 ms 125.101.157.226
34 2026-08-27 10:59 639234243654907465
538 ms 125.101.157.226
33 2026-08-27 10:42 639234233269654413
514 ms 125.101.157.226
32 2026-08-27 10:25 639234222943951923
246 ms 125.101.157.226
31 2026-08-27 10:07 639234212558002823
519 ms 125.101.157.226
30 2026-08-27 09:50 639234202117531850
970 ms 125.101.157.226
29 2026-08-27 09:33 639234191649612722
500 ms 125.101.157.226
28 2026-08-27 09:15 639234181105879568
526 ms 125.101.157.226
27 2026-08-27 08:58 639234170713214496
500 ms 125.101.157.226
26 2026-08-27 08:40 639234160341037652
241 ms 125.101.157.226
25 2026-08-27 08:23 639234149799404224
935 ms 125.101.157.226
24 2026-08-27 08:05 639234139553286469
503 ms 125.101.157.226
23 2026-08-27 07:12 639234107183588293
529 ms 125.101.157.226
22 2026-08-27 06:55 639234096905435724
500 ms 125.101.157.226
21 2026-08-27 06:37 639234086579410775
505 ms 125.101.157.226
20 2026-08-27 06:20 639234076291157956
248 ms 125.101.157.226
19 2026-08-27 06:03 639234065981939454
2 ms 125.101.157.226
18 2026-08-27 05:46 639234055548642997
517 ms 125.101.157.226
17 2026-08-27 05:29 639234045267979603
492 ms 125.101.157.226
16 2026-08-27 05:11 639234034999717463
309 ms 125.101.157.226
15 2026-08-27 04:54 639234024739225358
541 ms 125.101.157.226
14 2026-08-27 04:37 639234014311170162
240 ms 125.101.157.226
13 2026-08-27 04:20 639234003806017640
240 ms 125.101.157.226
12 2026-08-27 04:02 639233993356203030
241 ms 125.101.157.226
11 2026-08-27 03:09 639233961301716608
523 ms 125.101.157.226
10 2026-08-27 02:52 639233950834200647
243 ms 125.101.157.226
9 2026-08-27 02:34 639233940431849026
494 ms 125.101.157.226
8 2026-08-27 02:17 639233930110596398
508 ms 125.101.157.226
7 2026-08-27 02:00 639233919705434540
539 ms 125.101.157.226
6 2026-08-27 01:42 639233909452807845
524 ms 125.101.157.226
5 2026-08-27 01:25 639233899096420820
530 ms 125.101.157.226
4 2026-08-27 01:08 639233888707824939
500 ms 125.101.157.226
3 2026-08-27 00:51 639233878461203802
510 ms 125.101.157.226
2 2026-08-27 00:33 639233868060868209
802 ms 125.101.157.226
1 2026-08-27 00:16 639233857450922991
247 ms 125.101.157.226