DNS response history for dns2.jabikha.net

dns2.jabikha.net 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 439 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 dns2.jabikha.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

439 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.7.87.78

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 dns2.jabikha.net

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
2204 ms 103.7.87.78
33 2026-08-26 10:26 639233360361507238
350 ms 103.7.87.78
32 2026-08-26 10:08 639233350067824371
359 ms 103.7.87.78
31 2026-08-26 09:51 639233339545274518
344 ms 103.7.87.78
30 2026-08-26 09:34 639233329214918079
349 ms 103.7.87.78
29 2026-08-26 09:16 639233318749762337
338 ms 103.7.87.78
28 2026-08-26 08:59 639233308387917838
175 ms 103.7.87.78
27 2026-08-26 08:42 639233297961740122
355 ms 103.7.87.78
26 2026-08-26 08:24 639233287487159094
167 ms 103.7.87.78
25 2026-08-26 08:07 639233276995531707
350 ms 103.7.87.78
24 2026-08-26 07:49 639233266521568229
354 ms 103.7.87.78
23 2026-08-26 07:32 639233256081047431
182 ms 103.7.87.78
22 2026-08-26 06:38 639233223620132921
180 ms 103.7.87.78
21 2026-08-26 06:21 639233213287814244
175 ms 103.7.87.78
20 2026-08-26 06:03 639233202925983161
346 ms 103.7.87.78
19 2026-08-26 05:46 639233192644780696
187 ms 103.7.87.78
18 2026-08-26 05:29 639233182401183833
353 ms 103.7.87.78
17 2026-08-26 05:12 639233172074181051
190 ms 103.7.87.78
16 2026-08-26 04:55 639233161808421455
444 ms 103.7.87.78
15 2026-08-26 04:38 639233151357344052
2195 ms 103.7.87.78
14 2026-08-26 04:20 639233141034116946
166 ms 103.7.87.78
13 2026-08-26 04:03 639233130828334142
180 ms 103.7.87.78
12 2026-08-26 03:46 639233120373450007
178 ms 103.7.87.78
11 2026-08-26 03:28 639233110066216193
334 ms 103.7.87.78
10 2026-08-26 02:35 639233078065410564
166 ms 103.7.87.78
9 2026-08-26 02:18 639233067787457832
337 ms 103.7.87.78
8 2026-08-26 02:01 639233057501801162
346 ms 103.7.87.78
7 2026-08-26 01:44 639233047089431703
172 ms 103.7.87.78
6 2026-08-26 01:26 639233036754790688
170 ms 103.7.87.78
5 2026-08-26 01:09 639233026412602472
347 ms 103.7.87.78
4 2026-08-26 00:52 639233016064066127
169 ms 103.7.87.78
3 2026-08-26 00:35 639233005922655772
167 ms 103.7.87.78
2 2026-08-26 00:18 639232995672256907
2264 ms 103.7.87.78
1 2026-08-26 00:01 639232985300872416
349 ms 103.7.87.78