DNS response history for ns2.jbssk.com

ns2.jbssk.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 36 DNS check records, 36 successful responses, 0 failed responses, and 338 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.jbssk.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

338 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.181.179

Most recently resolved hosting IP on selected date

Successful Responses

36

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.jbssk.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
36 2026-08-26 11:54 639233414056832719
275 ms 103.171.181.179
35 2026-08-26 11:37 639233403515141099
2131 ms 103.171.181.179
34 2026-08-26 10:42 639233370841350248
284 ms 103.171.181.179
33 2026-08-26 10:25 639233360361507238
280 ms 103.171.181.179
32 2026-08-26 10:07 639233350067824371
272 ms 103.171.181.179
31 2026-08-26 09:50 639233339545274518
6 ms 103.171.181.179
30 2026-08-26 09:33 639233329214918079
2133 ms 103.171.181.179
29 2026-08-26 09:15 639233318749762337
4 ms 103.171.181.179
28 2026-08-26 08:58 639233308387917838
276 ms 103.171.181.179
27 2026-08-26 08:41 639233297961740122
297 ms 103.171.181.179
26 2026-08-26 08:23 639233287487159094
280 ms 103.171.181.179
25 2026-08-26 08:06 639233276995531707
267 ms 103.171.181.179
24 2026-08-26 07:48 639233266521568229
283 ms 103.171.181.179
23 2026-08-26 07:31 639233256081047431
292 ms 103.171.181.179
22 2026-08-26 06:37 639233223620132921
282 ms 103.171.181.179
21 2026-08-26 06:20 639233213287814244
140 ms 103.171.181.179
20 2026-08-26 06:02 639233202925983161
281 ms 103.171.181.179
19 2026-08-26 05:45 639233192644780696
274 ms 103.171.181.179
18 2026-08-26 05:28 639233182401183833
286 ms 103.171.181.179
17 2026-08-26 05:11 639233172074181051
258 ms 103.171.181.179
16 2026-08-26 04:54 639233161808421455
283 ms 103.171.181.179
15 2026-08-26 04:37 639233151357344052
16 ms 103.171.181.179
14 2026-08-26 04:19 639233141034116946
135 ms 103.171.181.179
13 2026-08-26 04:02 639233130828334142
263 ms 103.171.181.179
12 2026-08-26 03:45 639233120373450007
277 ms 103.171.181.179
11 2026-08-26 03:27 639233110066216193
269 ms 103.171.181.179
10 2026-08-26 02:34 639233078065410564
270 ms 103.171.181.179
9 2026-08-26 02:17 639233067787457832
279 ms 103.171.181.179
8 2026-08-26 02:00 639233057501801162
283 ms 103.171.181.179
7 2026-08-26 01:43 639233047089431703
269 ms 103.171.181.179
6 2026-08-26 01:25 639233036754790688
9 ms 103.171.181.179
5 2026-08-26 01:08 639233026412602472
267 ms 103.171.181.179
4 2026-08-26 00:51 639233016064066127
135 ms 103.171.181.179
3 2026-08-26 00:34 639233005922655772
263 ms 103.171.181.179
2 2026-08-26 00:17 639232995672256907
288 ms 103.171.181.179
1 2026-08-26 00:00 639232985300872416
265 ms 103.171.181.179