DNS response history for dns2.yeetec.com

dns2.yeetec.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 31 DNS check records, 31 successful responses, 0 failed responses, and 588 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 dns2.yeetec.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

588 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.201.58.121

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 dns2.yeetec.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
31 2026-08-26 09:54 639233339545274518
577 ms 121.201.58.121
30 2026-08-26 09:36 639233329214918079
587 ms 121.201.58.121
29 2026-08-26 09:19 639233318749762337
208 ms 121.201.58.121
28 2026-08-26 09:01 639233308387917838
581 ms 121.201.58.121
27 2026-08-26 08:44 639233297961740122
616 ms 121.201.58.121
26 2026-08-26 08:27 639233287487159094
503 ms 121.201.58.121
25 2026-08-26 08:09 639233276995531707
574 ms 121.201.58.121
24 2026-08-26 07:52 639233266521568229
502 ms 121.201.58.121
23 2026-08-26 07:34 639233256081047431
585 ms 121.201.58.121
22 2026-08-26 06:40 639233223620132921
522 ms 121.201.58.121
21 2026-08-26 06:23 639233213287814244
592 ms 121.201.58.121
20 2026-08-26 06:06 639233202925983161
519 ms 121.201.58.121
19 2026-08-26 05:48 639233192644780696
568 ms 121.201.58.121
18 2026-08-26 05:31 639233182401183833
573 ms 121.201.58.121
17 2026-08-26 05:14 639233172074181051
555 ms 121.201.58.121
16 2026-08-26 04:57 639233161808421455
526 ms 121.201.58.121
15 2026-08-26 04:40 639233151357344052
608 ms 121.201.58.121
14 2026-08-26 04:22 639233141034116946
602 ms 121.201.58.121
13 2026-08-26 04:05 639233130828334142
617 ms 121.201.58.121
12 2026-08-26 03:48 639233120373450007
471 ms 121.201.58.121
11 2026-08-26 03:31 639233110066216193
547 ms 121.201.58.121
10 2026-08-26 02:37 639233078065410564
513 ms 121.201.58.121
9 2026-08-26 02:20 639233067787457832
612 ms 121.201.58.121
8 2026-08-26 02:03 639233057501801162
613 ms 121.201.58.121
7 2026-08-26 01:46 639233047089431703
547 ms 121.201.58.121
6 2026-08-26 01:29 639233036754790688
563 ms 121.201.58.121
5 2026-08-26 01:11 639233026412602472
474 ms 121.201.58.121
4 2026-08-26 00:54 639233016064066127
512 ms 121.201.58.121
3 2026-08-26 00:37 639233005922655772
488 ms 121.201.58.121
2 2026-08-26 00:20 639232995672256907
2239 ms 121.201.58.121
1 2026-08-26 00:03 639232985300872416
224 ms 121.201.58.121