DNS response history for ns2.runstone.com

ns2.runstone.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 572 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.runstone.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

572 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

123.124.198.61

Most recently resolved hosting IP on selected date

Successful Responses

34

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

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
34 2026-08-26 10:44 639233370841350248
488 ms 123.124.198.61
33 2026-08-26 10:27 639233360361507238
475 ms 123.124.198.61
32 2026-08-26 10:10 639233350067824371
479 ms 123.124.198.61
31 2026-08-26 09:53 639233339545274518
557 ms 123.124.198.61
30 2026-08-26 09:35 639233329214918079
478 ms 123.124.198.61
29 2026-08-26 09:18 639233318749762337
553 ms 123.124.198.61
28 2026-08-26 09:00 639233308387917838
494 ms 123.124.198.61
27 2026-08-26 08:43 639233297961740122
539 ms 123.124.198.61
26 2026-08-26 08:26 639233287487159094
530 ms 123.124.198.61
25 2026-08-26 08:08 639233276995531707
526 ms 123.124.198.61
24 2026-08-26 07:51 639233266521568229
619 ms 123.124.198.61
23 2026-08-26 07:33 639233256081047431
2008 ms 123.124.198.61
22 2026-08-26 06:39 639233223620132921
648 ms 123.124.198.61
21 2026-08-26 06:22 639233213287814244
487 ms 123.124.198.61
20 2026-08-26 06:05 639233202925983161
587 ms 123.124.198.61
19 2026-08-26 05:47 639233192644780696
536 ms 123.124.198.61
18 2026-08-26 05:30 639233182401183833
524 ms 123.124.198.61
17 2026-08-26 05:13 639233172074181051
567 ms 123.124.198.61
16 2026-08-26 04:56 639233161808421455
489 ms 123.124.198.61
15 2026-08-26 04:39 639233151357344052
544 ms 123.124.198.61
14 2026-08-26 04:21 639233141034116946
534 ms 123.124.198.61
13 2026-08-26 04:04 639233130828334142
515 ms 123.124.198.61
12 2026-08-26 03:47 639233120373450007
592 ms 123.124.198.61
11 2026-08-26 03:30 639233110066216193
481 ms 123.124.198.61
10 2026-08-26 02:36 639233078065410564
543 ms 123.124.198.61
9 2026-08-26 02:19 639233067787457832
518 ms 123.124.198.61
8 2026-08-26 02:02 639233057501801162
522 ms 123.124.198.61
7 2026-08-26 01:45 639233047089431703
548 ms 123.124.198.61
6 2026-08-26 01:28 639233036754790688
460 ms 123.124.198.61
5 2026-08-26 01:11 639233026412602472
489 ms 123.124.198.61
4 2026-08-26 00:53 639233016064066127
602 ms 123.124.198.61
3 2026-08-26 00:36 639233005922655772
538 ms 123.124.198.61
2 2026-08-26 00:19 639232995672256907
506 ms 123.124.198.61
1 2026-08-26 00:02 639232985300872416
478 ms 123.124.198.61