DNS response history for ns4.12530.com

ns4.12530.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 414 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 ns4.12530.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

218.200.160.91

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns4.12530.com

Showing DNS history for 2026-08-25 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
36 2026-08-25 12:41 639232576780683689
223 ms 218.200.160.91
35 2026-08-25 12:24 639232566381512620
258 ms 218.200.160.91
34 2026-08-25 12:07 639232556111768563
244 ms 218.200.160.91
33 2026-08-25 11:49 639232545839529039
447 ms 218.200.160.91
32 2026-08-25 11:32 639232535349285207
243 ms 218.200.160.91
31 2026-08-25 11:15 639232524938080723
2275 ms 218.200.160.91
30 2026-08-25 10:21 639232492740373468
463 ms 218.200.160.91
29 2026-08-25 10:04 639232482235303141
194 ms 218.200.160.91
28 2026-08-25 09:46 639232471861770303
242 ms 218.200.160.91
27 2026-08-25 09:29 639232461630217327
244 ms 218.200.160.91
26 2026-08-25 09:12 639232451282965990
470 ms 218.200.160.91
25 2026-08-25 08:55 639232440814614938
251 ms 218.200.160.91
24 2026-08-25 08:37 639232430410720425
265 ms 218.200.160.91
23 2026-08-25 08:20 639232420003096185
227 ms 218.200.160.91
22 2026-08-25 08:02 639232409467287444
197 ms 218.200.160.91
21 2026-08-25 07:45 639232399077195997
281 ms 218.200.160.91
20 2026-08-25 07:28 639232388731528337
248 ms 218.200.160.91
19 2026-08-25 07:10 639232378288598612
219 ms 218.200.160.91
18 2026-08-25 06:17 639232346196373643
259 ms 218.200.160.91
17 2026-08-25 06:00 639232336112370741
2264 ms 218.200.160.91
16 2026-08-25 05:43 639232326146508970
284 ms 218.200.160.91
15 2026-08-25 05:26 639232316189381720
219 ms 218.200.160.91
14 2026-08-25 05:10 639232306217998913
319 ms 218.200.160.91
13 2026-08-25 04:53 639232296255744174
251 ms 218.200.160.91
12 2026-08-25 04:36 639232286095760789
453 ms 218.200.160.91
11 2026-08-25 04:19 639232276086186273
465 ms 218.200.160.91
10 2026-08-25 04:03 639232265900986425
307 ms 218.200.160.91
9 2026-08-25 03:46 639232255723518075
472 ms 218.200.160.91
8 2026-08-25 03:29 639232245484452890
442 ms 218.200.160.91
7 2026-08-25 03:12 639232235157175331
486 ms 218.200.160.91
6 2026-08-25 02:18 639232203197189095
306 ms 218.200.160.91
5 2026-08-25 02:01 639232192844564298
353 ms 218.200.160.91
4 2026-08-25 01:44 639232182496008942
240 ms 218.200.160.91
3 2026-08-25 01:27 639232172197053132
263 ms 218.200.160.91
2 2026-08-25 00:33 639232140250307418
252 ms 218.200.160.91
1 2026-08-25 00:16 639232129927860324
295 ms 218.200.160.91