DNS response history for ns2.teleeye.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

1588 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.199.148.72

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 ns2.teleeye.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
34 2026-08-26 10:47 639233370841350248
1924 ms 104.199.148.72
33 2026-08-26 10:30 639233360361507238
1917 ms 104.199.148.72
32 2026-08-26 10:12 639233350067824371
1933 ms 104.199.148.72
31 2026-08-26 09:55 639233339545274518
442 ms 104.199.148.72
30 2026-08-26 09:37 639233329214918079
1926 ms 104.199.148.72
29 2026-08-26 09:20 639233318749762337
1932 ms 104.199.148.72
28 2026-08-26 09:03 639233308387917838
1926 ms 104.199.148.72
27 2026-08-26 08:45 639233297961740122
1943 ms 104.199.148.72
26 2026-08-26 08:28 639233287487159094
443 ms 104.199.148.72
25 2026-08-26 08:11 639233276995531707
1912 ms 104.199.148.72
24 2026-08-26 07:53 639233266521568229
438 ms 104.199.148.72
23 2026-08-26 07:36 639233256081047431
886 ms 104.199.148.72
22 2026-08-26 06:41 639233223620132921
900 ms 104.199.148.72
21 2026-08-26 06:24 639233213287814244
1936 ms 104.199.148.72
20 2026-08-26 06:07 639233202925983161
1923 ms 104.199.148.72
19 2026-08-26 05:50 639233192644780696
1939 ms 104.199.148.72
18 2026-08-26 05:32 639233182401183833
1930 ms 104.199.148.72
17 2026-08-26 05:16 639233172074181051
1917 ms 104.199.148.72
16 2026-08-26 04:58 639233161808421455
1932 ms 104.199.148.72
15 2026-08-26 04:41 639233151357344052
1934 ms 104.199.148.72
14 2026-08-26 04:24 639233141034116946
446 ms 104.199.148.72
13 2026-08-26 04:07 639233130828334142
1932 ms 104.199.148.72
12 2026-08-26 03:49 639233120373450007
1921 ms 104.199.148.72
11 2026-08-26 03:32 639233110066216193
893 ms 104.199.148.72
10 2026-08-26 02:39 639233078065410564
890 ms 104.199.148.72
9 2026-08-26 02:22 639233067787457832
1922 ms 104.199.148.72
8 2026-08-26 02:04 639233057501801162
1926 ms 104.199.148.72
7 2026-08-26 01:47 639233047089431703
1928 ms 104.199.148.72
6 2026-08-26 01:30 639233036754790688
1924 ms 104.199.148.72
5 2026-08-26 01:13 639233026412602472
1928 ms 104.199.148.72
4 2026-08-26 00:55 639233016064066127
1930 ms 104.199.148.72
3 2026-08-26 00:38 639233005922655772
1925 ms 104.199.148.72
2 2026-08-26 00:21 639232995672256907
447 ms 104.199.148.72
1 2026-08-26 00:04 639232985300872416
1943 ms 104.199.148.72