DNS response history for ns.jbslr.com

ns.jbslr.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 549 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 ns.jbslr.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

549 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

119.67.6.147

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 ns.jbslr.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:57 639233414056832719
598 ms 119.67.6.147
35 2026-08-26 11:40 639233403515141099
589 ms 119.67.6.147
34 2026-08-26 10:45 639233370841350248
566 ms 119.67.6.147
33 2026-08-26 10:28 639233360361507238
599 ms 119.67.6.147
32 2026-08-26 10:11 639233350067824371
601 ms 119.67.6.147
31 2026-08-26 09:53 639233339545274518
593 ms 119.67.6.147
30 2026-08-26 09:36 639233329214918079
586 ms 119.67.6.147
29 2026-08-26 09:19 639233318749762337
592 ms 119.67.6.147
28 2026-08-26 09:01 639233308387917838
1189 ms 119.67.6.147
27 2026-08-26 08:44 639233297961740122
567 ms 119.67.6.147
26 2026-08-26 08:26 639233287487159094
585 ms 119.67.6.147
25 2026-08-26 08:09 639233276995531707
594 ms 119.67.6.147
24 2026-08-26 07:51 639233266521568229
588 ms 119.67.6.147
23 2026-08-26 07:34 639233256081047431
565 ms 119.67.6.147
22 2026-08-26 06:40 639233223620132921
9 ms 119.67.6.147
21 2026-08-26 06:23 639233213287814244
598 ms 119.67.6.147
20 2026-08-26 06:05 639233202925983161
4 ms 119.67.6.147
19 2026-08-26 05:48 639233192644780696
575 ms 119.67.6.147
18 2026-08-26 05:31 639233182401183833
3 ms 119.67.6.147
17 2026-08-26 05:14 639233172074181051
597 ms 119.67.6.147
16 2026-08-26 04:57 639233161808421455
584 ms 119.67.6.147
15 2026-08-26 04:40 639233151357344052
4 ms 119.67.6.147
14 2026-08-26 04:22 639233141034116946
606 ms 119.67.6.147
13 2026-08-26 04:05 639233130828334142
606 ms 119.67.6.147
12 2026-08-26 03:48 639233120373450007
615 ms 119.67.6.147
11 2026-08-26 03:31 639233110066216193
604 ms 119.67.6.147
10 2026-08-26 02:37 639233078065410564
607 ms 119.67.6.147
9 2026-08-26 02:20 639233067787457832
596 ms 119.67.6.147
8 2026-08-26 02:03 639233057501801162
577 ms 119.67.6.147
7 2026-08-26 01:46 639233047089431703
566 ms 119.67.6.147
6 2026-08-26 01:28 639233036754790688
3 ms 119.67.6.147
5 2026-08-26 01:11 639233026412602472
1381 ms 119.67.6.147
4 2026-08-26 00:54 639233016064066127
597 ms 119.67.6.147
3 2026-08-26 00:37 639233005922655772
621 ms 119.67.6.147
2 2026-08-26 00:20 639232995672256907
613 ms 119.67.6.147
1 2026-08-26 00:03 639232985300872416
590 ms 119.67.6.147