DNS response history for ns2.jankidhamdevelopers.com

ns2.jankidhamdevelopers.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 498 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.jankidhamdevelopers.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

498 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.235.106.104

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.jankidhamdevelopers.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:44 639233370841350248
145 ms 103.235.106.104
33 2026-08-26 10:27 639233360361507238
308 ms 103.235.106.104
32 2026-08-26 10:09 639233350067824371
285 ms 103.235.106.104
31 2026-08-26 09:52 639233339545274518
288 ms 103.235.106.104
30 2026-08-26 09:34 639233329214918079
152 ms 103.235.106.104
29 2026-08-26 09:17 639233318749762337
4356 ms 103.235.106.104
28 2026-08-26 09:00 639233308387917838
490 ms 103.235.106.104
27 2026-08-26 08:42 639233297961740122
304 ms 103.235.106.104
26 2026-08-26 08:25 639233287487159094
288 ms 103.235.106.104
25 2026-08-26 08:08 639233276995531707
290 ms 103.235.106.104
24 2026-08-26 07:50 639233266521568229
302 ms 103.235.106.104
23 2026-08-26 07:33 639233256081047431
290 ms 103.235.106.104
22 2026-08-26 06:39 639233223620132921
152 ms 103.235.106.104
21 2026-08-26 06:21 639233213287814244
288 ms 103.235.106.104
20 2026-08-26 06:04 639233202925983161
2363 ms 103.235.106.104
19 2026-08-26 05:47 639233192644780696
283 ms 103.235.106.104
18 2026-08-26 05:30 639233182401183833
152 ms 103.235.106.104
17 2026-08-26 05:13 639233172074181051
296 ms 103.235.106.104
16 2026-08-26 04:55 639233161808421455
284 ms 103.235.106.104
15 2026-08-26 04:38 639233151357344052
2198 ms 103.235.106.104
14 2026-08-26 04:21 639233141034116946
295 ms 103.235.106.104
13 2026-08-26 04:04 639233130828334142
290 ms 103.235.106.104
12 2026-08-26 03:47 639233120373450007
307 ms 103.235.106.104
11 2026-08-26 03:29 639233110066216193
302 ms 103.235.106.104
10 2026-08-26 02:36 639233078065410564
291 ms 103.235.106.104
9 2026-08-26 02:19 639233067787457832
3 ms 103.235.106.104
8 2026-08-26 02:02 639233057501801162
299 ms 103.235.106.104
7 2026-08-26 01:44 639233047089431703
282 ms 103.235.106.104
6 2026-08-26 01:27 639233036754790688
290 ms 103.235.106.104
5 2026-08-26 01:10 639233026412602472
144 ms 103.235.106.104
4 2026-08-26 00:53 639233016064066127
139 ms 103.235.106.104
3 2026-08-26 00:35 639233005922655772
157 ms 103.235.106.104
2 2026-08-26 00:18 639232995672256907
297 ms 103.235.106.104
1 2026-08-26 00:01 639232985300872416
313 ms 103.235.106.104