DNS response history for ns2.teleinfoo.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

595 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.61.61.1

Most recently resolved hosting IP on selected date

Successful Responses

35

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.teleinfoo.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
35 2026-08-26 11:40 639233403515141099
503 ms 103.61.61.1
34 2026-08-26 10:45 639233370841350248
536 ms 103.61.61.1
33 2026-08-26 10:28 639233360361507238
569 ms 103.61.61.1
32 2026-08-26 10:11 639233350067824371
486 ms 103.61.61.1
31 2026-08-26 09:53 639233339545274518
494 ms 103.61.61.1
30 2026-08-26 09:36 639233329214918079
552 ms 103.61.61.1
29 2026-08-26 09:19 639233318749762337
534 ms 103.61.61.1
28 2026-08-26 09:01 639233308387917838
867 ms 103.61.61.1
27 2026-08-26 08:44 639233297961740122
527 ms 103.61.61.1
26 2026-08-26 08:26 639233287487159094
519 ms 103.61.61.1
25 2026-08-26 08:09 639233276995531707
494 ms 103.61.61.1
24 2026-08-26 07:51 639233266521568229
305 ms 103.61.61.1
23 2026-08-26 07:34 639233256081047431
527 ms 103.61.61.1
22 2026-08-26 06:40 639233223620132921
464 ms 103.61.61.1
21 2026-08-26 06:23 639233213287814244
620 ms 103.61.61.1
20 2026-08-26 06:05 639233202925983161
517 ms 103.61.61.1
19 2026-08-26 05:48 639233192644780696
589 ms 103.61.61.1
18 2026-08-26 05:31 639233182401183833
2250 ms 103.61.61.1
17 2026-08-26 05:14 639233172074181051
629 ms 103.61.61.1
16 2026-08-26 04:57 639233161808421455
616 ms 103.61.61.1
15 2026-08-26 04:40 639233151357344052
499 ms 103.61.61.1
14 2026-08-26 04:22 639233141034116946
607 ms 103.61.61.1
13 2026-08-26 04:05 639233130828334142
601 ms 103.61.61.1
12 2026-08-26 03:48 639233120373450007
532 ms 103.61.61.1
11 2026-08-26 03:30 639233110066216193
564 ms 103.61.61.1
10 2026-08-26 02:37 639233078065410564
319 ms 103.61.61.1
9 2026-08-26 02:20 639233067787457832
616 ms 103.61.61.1
8 2026-08-26 02:03 639233057501801162
532 ms 103.61.61.1
7 2026-08-26 01:46 639233047089431703
523 ms 103.61.61.1
6 2026-08-26 01:28 639233036754790688
556 ms 103.61.61.1
5 2026-08-26 01:11 639233026412602472
884 ms 103.61.61.1
4 2026-08-26 00:54 639233016064066127
526 ms 103.61.61.1
3 2026-08-26 00:37 639233005922655772
519 ms 103.61.61.1
2 2026-08-26 00:20 639232995672256907
487 ms 103.61.61.1
1 2026-08-26 00:03 639232985300872416
468 ms 103.61.61.1