DNS response history for ns.classlobebyworldtealabo.com

ns.classlobebyworldtealabo.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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 312 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.classlobebyworldtealabo.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

312 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.9.155

Most recently resolved hosting IP on selected date

Successful Responses

31

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.classlobebyworldtealabo.com

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:19 639231735407682062
3 ms 153.123.9.155
30 2026-08-24 12:26 639231703815441688
19 ms 153.123.9.155
29 2026-08-24 12:09 639231693747052549
541 ms 153.123.9.155
28 2026-08-24 11:53 639231683712487276
554 ms 153.123.9.155
27 2026-08-24 11:36 639231673513573868
543 ms 153.123.9.155
26 2026-08-24 10:42 639231641791249939
516 ms 153.123.9.155
25 2026-08-24 10:26 639231631866211033
559 ms 153.123.9.155
24 2026-08-24 10:09 639231621644955316
4 ms 153.123.9.155
23 2026-08-24 09:52 639231611478799259
18 ms 153.123.9.155
22 2026-08-24 09:00 639231579923718211
549 ms 153.123.9.155
21 2026-08-24 08:43 639231569810702936
615 ms 153.123.9.155
20 2026-08-24 08:26 639231559762411619
258 ms 153.123.9.155
19 2026-08-24 08:09 639231549663595407
547 ms 153.123.9.155
18 2026-08-24 07:16 639231518076817246
565 ms 153.123.9.155
17 2026-08-24 07:00 639231508078650885
550 ms 153.123.9.155
16 2026-08-24 06:43 639231498210697093
30 ms 153.123.9.155
15 2026-08-24 06:27 639231488109699360
2 ms 153.123.9.155
14 2026-08-24 05:34 639231456772510692
271 ms 153.123.9.155
13 2026-08-24 05:18 639231447084631185
546 ms 153.123.9.155
12 2026-08-24 05:01 639231437208519473
546 ms 153.123.9.155
11 2026-08-24 04:45 639231427209627490
2 ms 153.123.9.155
10 2026-08-24 03:52 639231395791246644
7 ms 153.123.9.155
9 2026-08-24 03:36 639231386075551458
3 ms 153.123.9.155
8 2026-08-24 03:20 639231376208713791
535 ms 153.123.9.155
7 2026-08-24 03:03 639231366170589276
3 ms 153.123.9.155
6 2026-08-24 02:11 639231334732159368
526 ms 153.123.9.155
5 2026-08-24 01:55 639231325035670078
5 ms 153.123.9.155
4 2026-08-24 01:38 639231315132253837
552 ms 153.123.9.155
3 2026-08-24 01:22 639231305014280808
4 ms 153.123.9.155
2 2026-08-24 00:29 639231273779380675
268 ms 153.123.9.155
1 2026-08-24 00:13 639231264180839154
535 ms 153.123.9.155