DNS response history for ns2.jiosign.com

ns2.jiosign.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-24. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 413 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.jiosign.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

413 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.45.43.43

Most recently resolved hosting IP on selected date

Successful Responses

39

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

Showing DNS history for 2026-08-24 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
39 2026-08-24 16:44 639231860258429562
260 ms 49.45.43.43
38 2026-08-24 15:50 639231828211839931
253 ms 49.45.43.43
37 2026-08-24 15:34 639231818080917481
355 ms 49.45.43.43
36 2026-08-24 15:16 639231807961539652
2357 ms 49.45.43.43
35 2026-08-24 15:00 639231797631669865
234 ms 49.45.43.43
34 2026-08-24 14:07 639231765923559455
156 ms 49.45.43.43
33 2026-08-24 13:50 639231755868832964
170 ms 49.45.43.43
32 2026-08-24 13:33 639231745628278877
260 ms 49.45.43.43
31 2026-08-24 13:16 639231735407682062
2015 ms 49.45.43.43
30 2026-08-24 12:23 639231703815441688
110 ms 49.45.43.43
29 2026-08-24 12:06 639231693747052549
278 ms 49.45.43.43
28 2026-08-24 11:49 639231683712487276
272 ms 49.45.43.43
27 2026-08-24 11:32 639231673513573868
146 ms 49.45.43.43
26 2026-08-24 10:39 639231641791249939
138 ms 49.45.43.43
25 2026-08-24 10:23 639231631866211033
150 ms 49.45.43.43
24 2026-08-24 10:06 639231621644955316
431 ms 49.45.43.43
23 2026-08-24 09:49 639231611478799259
124 ms 49.45.43.43
22 2026-08-24 08:57 639231579923718211
263 ms 49.45.43.43
21 2026-08-24 08:40 639231569810702936
265 ms 49.45.43.43
20 2026-08-24 08:23 639231559762411619
135 ms 49.45.43.43
19 2026-08-24 08:06 639231549663595407
249 ms 49.45.43.43
18 2026-08-24 07:13 639231518076817246
350 ms 49.45.43.43
17 2026-08-24 06:57 639231508078650885
124 ms 49.45.43.43
16 2026-08-24 06:40 639231498210697093
248 ms 49.45.43.43
15 2026-08-24 06:24 639231488109699360
124 ms 49.45.43.43
14 2026-08-24 05:31 639231456772510692
3 ms 49.45.43.43
13 2026-08-24 05:15 639231447084631185
123 ms 49.45.43.43
12 2026-08-24 04:59 639231437208519473
251 ms 49.45.43.43
11 2026-08-24 04:42 639231427209627490
126 ms 49.45.43.43
10 2026-08-24 03:49 639231395791246644
280 ms 49.45.43.43
9 2026-08-24 03:33 639231386075551458
33 ms 49.45.43.43
8 2026-08-24 03:17 639231376208713791
2376 ms 49.45.43.43
7 2026-08-24 03:00 639231366170589276
133 ms 49.45.43.43
6 2026-08-24 02:08 639231334732159368
325 ms 49.45.43.43
5 2026-08-24 01:52 639231325035670078
3 ms 49.45.43.43
4 2026-08-24 01:35 639231315132253837
233 ms 49.45.43.43
3 2026-08-24 01:18 639231305014280808
116 ms 49.45.43.43
2 2026-08-24 00:26 639231273779380675
267 ms 49.45.43.43
1 2026-08-24 00:10 639231264180839154
2363 ms 49.45.43.43