DNS response history for ns5.jiopartner.com

ns5.jiopartner.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 597 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 ns5.jiopartner.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

597 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.45.43.42

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns5.jiopartner.com

Showing DNS history for 2026-08-25 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-25 10:18 639232492740373468
260 ms 49.45.43.42
29 2026-08-25 10:01 639232482235303141
264 ms 49.45.43.42
28 2026-08-25 09:43 639232471861770303
2134 ms 49.45.43.42
27 2026-08-25 09:26 639232461630217327
131 ms 49.45.43.42
26 2026-08-25 09:09 639232451282965990
237 ms 49.45.43.42
25 2026-08-25 08:52 639232440814614938
247 ms 49.45.43.42
24 2026-08-25 08:34 639232430410720425
126 ms 49.45.43.42
23 2026-08-25 08:17 639232420003096185
242 ms 49.45.43.42
22 2026-08-25 08:00 639232409467287444
314 ms 49.45.43.42
21 2026-08-25 07:42 639232399077195997
2341 ms 49.45.43.42
20 2026-08-25 07:25 639232388731528337
120 ms 49.45.43.42
19 2026-08-25 07:07 639232378288598612
245 ms 49.45.43.42
18 2026-08-25 06:14 639232346196373643
2160 ms 49.45.43.42
17 2026-08-25 05:57 639232336112370741
2303 ms 49.45.43.42
16 2026-08-25 05:40 639232326146508970
247 ms 49.45.43.42
15 2026-08-25 05:24 639232316189381720
125 ms 49.45.43.42
14 2026-08-25 05:07 639232306217998913
157 ms 49.45.43.42
13 2026-08-25 04:51 639232296255744174
171 ms 49.45.43.42
12 2026-08-25 04:34 639232286095760789
244 ms 49.45.43.42
11 2026-08-25 04:17 639232276086186273
130 ms 49.45.43.42
10 2026-08-25 04:00 639232265900986425
2032 ms 49.45.43.42
9 2026-08-25 03:43 639232255723518075
245 ms 49.45.43.42
8 2026-08-25 03:26 639232245484452890
251 ms 49.45.43.42
7 2026-08-25 03:09 639232235157175331
243 ms 49.45.43.42
6 2026-08-25 02:16 639232203197189095
2161 ms 49.45.43.42
5 2026-08-25 01:58 639232192844564298
21 ms 49.45.43.42
4 2026-08-25 01:41 639232182496008942
250 ms 49.45.43.42
3 2026-08-25 01:24 639232172197053132
255 ms 49.45.43.42
2 2026-08-25 00:30 639232140250307418
233 ms 49.45.43.42
1 2026-08-25 00:14 639232129927860324
33 ms 49.45.43.42