DNS response history for ns2.rupantar.com

ns2.rupantar.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 295 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.rupantar.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

295 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.14.121.176

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.rupantar.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:43 639233370841350248
152 ms 103.14.121.176
33 2026-08-26 10:26 639233360361507238
148 ms 103.14.121.176
32 2026-08-26 10:08 639233350067824371
147 ms 103.14.121.176
31 2026-08-26 09:51 639233339545274518
146 ms 103.14.121.176
30 2026-08-26 09:34 639233329214918079
287 ms 103.14.121.176
29 2026-08-26 09:16 639233318749762337
292 ms 103.14.121.176
28 2026-08-26 08:59 639233308387917838
303 ms 103.14.121.176
27 2026-08-26 08:42 639233297961740122
143 ms 103.14.121.176
26 2026-08-26 08:24 639233287487159094
150 ms 103.14.121.176
25 2026-08-26 08:07 639233276995531707
288 ms 103.14.121.176
24 2026-08-26 07:49 639233266521568229
287 ms 103.14.121.176
23 2026-08-26 07:32 639233256081047431
297 ms 103.14.121.176
22 2026-08-26 06:38 639233223620132921
294 ms 103.14.121.176
21 2026-08-26 06:21 639233213287814244
2352 ms 103.14.121.176
20 2026-08-26 06:03 639233202925983161
301 ms 103.14.121.176
19 2026-08-26 05:46 639233192644780696
154 ms 103.14.121.176
18 2026-08-26 05:29 639233182401183833
145 ms 103.14.121.176
17 2026-08-26 05:12 639233172074181051
288 ms 103.14.121.176
16 2026-08-26 04:55 639233161808421455
292 ms 103.14.121.176
15 2026-08-26 04:38 639233151357344052
292 ms 103.14.121.176
14 2026-08-26 04:20 639233141034116946
147 ms 103.14.121.176
13 2026-08-26 04:03 639233130828334142
307 ms 103.14.121.176
12 2026-08-26 03:46 639233120373450007
147 ms 103.14.121.176
11 2026-08-26 03:28 639233110066216193
147 ms 103.14.121.176
10 2026-08-26 02:35 639233078065410564
142 ms 103.14.121.176
9 2026-08-26 02:18 639233067787457832
369 ms 103.14.121.176
8 2026-08-26 02:01 639233057501801162
287 ms 103.14.121.176
7 2026-08-26 01:44 639233047089431703
287 ms 103.14.121.176
6 2026-08-26 01:26 639233036754790688
147 ms 103.14.121.176
5 2026-08-26 01:09 639233026412602472
292 ms 103.14.121.176
4 2026-08-26 00:52 639233016064066127
144 ms 103.14.121.176
3 2026-08-26 00:35 639233005922655772
290 ms 103.14.121.176
2 2026-08-26 00:18 639232995672256907
292 ms 103.14.121.176
1 2026-08-26 00:01 639232985300872416
289 ms 103.14.121.176