DNS response history for ironman.mcs.co.id

ironman.mcs.co.id 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 30 DNS check records, 29 successful responses, 1 failed responses, and 55 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 ironman.mcs.co.id.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

55 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.53.192.98

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ironman.mcs.co.id

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
30 2026-08-26 09:40 639233339545274518
13 ms 103.53.192.98
29 2026-08-26 09:22 639233329214918079
167 ms 103.53.192.98
28 2026-08-26 09:05 639233318749762337
59 ms 103.53.192.98
27 2026-08-26 08:48 639233308387917838
37 ms 103.53.192.98
26 2026-08-26 08:30 639233297961740122
133 ms 103.53.192.98
25 2026-08-26 08:13 639233287487159094
26 ms 103.53.192.98
24 2026-08-26 07:55 639233276995531707
46 ms 103.53.192.98
23 2026-08-26 07:38 639233266521568229
137 ms 103.53.192.98
22 2026-08-26 07:20 639233256081047431
46 ms 103.53.192.98
21 2026-08-26 06:26 639233223620132921
28 ms 103.53.192.98
20 2026-08-26 06:09 639233213287814244
42 ms 103.53.192.98
19 2026-08-26 05:52 639233202925983161
51 ms 103.53.192.98
18 2026-08-26 05:35 639233192644780696
24 ms 103.53.192.98
17 2026-08-26 05:18 639233182401183833
14 ms 103.53.192.98
16 2026-08-26 05:00 639233172074181051
55 ms 103.53.192.98
15 2026-08-26 04:43 639233161808421455
123 ms 103.53.192.98
14 2026-08-26 04:26 639233151357344052
42 ms 103.53.192.98
13 2026-08-26 04:09 639233141034116946
29 ms 103.53.192.98
12 2026-08-26 03:52 639233130828334142
128 ms 103.53.192.98
11 2026-08-26 03:34 639233120373450007
24 ms 103.53.192.98
10 2026-08-26 03:17 639233110066216193
37 ms 103.53.192.98
9 2026-08-26 02:24 639233078065410564
93 ms 103.53.192.98
8 2026-08-26 02:07 639233067787457832
34 ms 103.53.192.98
7 2026-08-26 01:49 639233057501801162
31 ms 103.53.192.98
6 2026-08-26 01:32 639233047089431703
35 ms 103.53.192.98
5 2026-08-26 01:15 639233036754790688
33 ms 103.53.192.98
4 2026-08-26 00:58 639233026412602472
26 ms 103.53.192.98
3 2026-08-26 00:40 639233016064066127
71 ms 103.53.192.98
2 2026-08-26 00:24 639233005922655772
-
1 2026-08-26 00:06 639232995672256907
15 ms 103.53.192.98