DNS response history for ns2.ijdmtoy.net

ns2.ijdmtoy.net 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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 213 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.ijdmtoy.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

213 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.111.69.225

Most recently resolved hosting IP on selected date

Successful Responses

27

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.ijdmtoy.net

Showing DNS history for 2026-08-26 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
27 2026-08-26 08:56 639233308387917838
218 ms 23.111.69.225
26 2026-08-26 08:39 639233297961740122
21 ms 23.111.69.225
25 2026-08-26 08:22 639233287487159094
116 ms 23.111.69.225
24 2026-08-26 08:04 639233276995531707
2009 ms 23.111.69.225
23 2026-08-26 07:46 639233266521568229
213 ms 23.111.69.225
22 2026-08-26 07:29 639233256081047431
233 ms 23.111.69.225
21 2026-08-26 06:35 639233223620132921
107 ms 23.111.69.225
20 2026-08-26 06:18 639233213287814244
115 ms 23.111.69.225
19 2026-08-26 06:00 639233202925983161
106 ms 23.111.69.225
18 2026-08-26 05:43 639233192644780696
157 ms 23.111.69.225
17 2026-08-26 05:26 639233182401183833
13 ms 23.111.69.225
16 2026-08-26 05:09 639233172074181051
3 ms 23.111.69.225
15 2026-08-26 04:52 639233161808421455
108 ms 23.111.69.225
14 2026-08-26 04:35 639233151357344052
113 ms 23.111.69.225
13 2026-08-26 04:17 639233141034116946
115 ms 23.111.69.225
12 2026-08-26 04:00 639233130828334142
114 ms 23.111.69.225
11 2026-08-26 03:43 639233120373450007
213 ms 23.111.69.225
10 2026-08-26 03:26 639233110066216193
216 ms 23.111.69.225
9 2026-08-26 02:32 639233078065410564
116 ms 23.111.69.225
8 2026-08-26 02:15 639233067787457832
209 ms 23.111.69.225
7 2026-08-26 01:58 639233057501801162
109 ms 23.111.69.225
6 2026-08-26 01:41 639233047089431703
216 ms 23.111.69.225
5 2026-08-26 01:24 639233036754790688
3 ms 23.111.69.225
4 2026-08-26 01:06 639233026412602472
212 ms 23.111.69.225
3 2026-08-26 00:49 639233016064066127
245 ms 23.111.69.225
2 2026-08-26 00:32 639233005922655772
216 ms 23.111.69.225
1 2026-08-26 00:15 639232995672256907
224 ms 23.111.69.225