DNS response history for ns2.multired.com.py

ns2.multired.com.py 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 33 DNS check records, 33 successful responses, 0 failed responses, and 200 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.multired.com.py.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

200 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.154.98.130

Most recently resolved hosting IP on selected date

Successful Responses

33

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.multired.com.py

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
33 2026-08-26 10:37 639233370841350248
103 ms 217.154.98.130
32 2026-08-26 10:19 639233360361507238
31 ms 217.154.98.130
31 2026-08-26 10:02 639233350067824371
29 ms 217.154.98.130
30 2026-08-26 09:45 639233339545274518
86 ms 217.154.98.130
29 2026-08-26 09:27 639233329214918079
97 ms 217.154.98.130
28 2026-08-26 09:10 639233318749762337
179 ms 217.154.98.130
27 2026-08-26 08:53 639233308387917838
2011 ms 217.154.98.130
26 2026-08-26 08:35 639233297961740122
115 ms 217.154.98.130
25 2026-08-26 08:18 639233287487159094
67 ms 217.154.98.130
24 2026-08-26 08:00 639233276995531707
93 ms 217.154.98.130
23 2026-08-26 07:43 639233266521568229
95 ms 217.154.98.130
22 2026-08-26 07:26 639233256081047431
9 ms 217.154.98.130
21 2026-08-26 06:32 639233223620132921
92 ms 217.154.98.130
20 2026-08-26 06:14 639233213287814244
145 ms 217.154.98.130
19 2026-08-26 05:57 639233202925983161
2012 ms 217.154.98.130
18 2026-08-26 05:40 639233192644780696
251 ms 217.154.98.130
17 2026-08-26 05:23 639233182401183833
94 ms 217.154.98.130
16 2026-08-26 05:06 639233172074181051
7 ms 217.154.98.130
15 2026-08-26 04:49 639233161808421455
15 ms 217.154.98.130
14 2026-08-26 04:31 639233151357344052
104 ms 217.154.98.130
13 2026-08-26 04:14 639233141034116946
161 ms 217.154.98.130
12 2026-08-26 03:57 639233130828334142
91 ms 217.154.98.130
11 2026-08-26 03:40 639233120373450007
9 ms 217.154.98.130
10 2026-08-26 03:22 639233110066216193
99 ms 217.154.98.130
9 2026-08-26 02:29 639233078065410564
42 ms 217.154.98.130
8 2026-08-26 02:12 639233067787457832
9 ms 217.154.98.130
7 2026-08-26 01:55 639233057501801162
91 ms 217.154.98.130
6 2026-08-26 01:37 639233047089431703
92 ms 217.154.98.130
5 2026-08-26 01:20 639233036754790688
52 ms 217.154.98.130
4 2026-08-26 01:03 639233026412602472
96 ms 217.154.98.130
3 2026-08-26 00:46 639233016064066127
92 ms 217.154.98.130
2 2026-08-26 00:29 639233005922655772
51 ms 217.154.98.130
1 2026-08-26 00:12 639232995672256907
91 ms 217.154.98.130