DNS response history for ns2.teprotech.com

ns2.teprotech.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 477 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.teprotech.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

477 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

122.209.123.169

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.teprotech.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:45 639233370841350248
515 ms 122.209.123.169
33 2026-08-26 10:28 639233360361507238
483 ms 122.209.123.169
32 2026-08-26 10:10 639233350067824371
558 ms 122.209.123.169
31 2026-08-26 09:53 639233339545274518
524 ms 122.209.123.169
30 2026-08-26 09:36 639233329214918079
520 ms 122.209.123.169
29 2026-08-26 09:19 639233318749762337
544 ms 122.209.123.169
28 2026-08-26 09:01 639233308387917838
328 ms 122.209.123.169
27 2026-08-26 08:44 639233297961740122
479 ms 122.209.123.169
26 2026-08-26 08:26 639233287487159094
464 ms 122.209.123.169
25 2026-08-26 08:09 639233276995531707
519 ms 122.209.123.169
24 2026-08-26 07:51 639233266521568229
435 ms 122.209.123.169
23 2026-08-26 07:34 639233256081047431
530 ms 122.209.123.169
22 2026-08-26 06:40 639233223620132921
504 ms 122.209.123.169
21 2026-08-26 06:23 639233213287814244
486 ms 122.209.123.169
20 2026-08-26 06:05 639233202925983161
572 ms 122.209.123.169
19 2026-08-26 05:48 639233192644780696
481 ms 122.209.123.169
18 2026-08-26 05:31 639233182401183833
474 ms 122.209.123.169
17 2026-08-26 05:14 639233172074181051
523 ms 122.209.123.169
16 2026-08-26 04:57 639233161808421455
523 ms 122.209.123.169
15 2026-08-26 04:40 639233151357344052
519 ms 122.209.123.169
14 2026-08-26 04:22 639233141034116946
497 ms 122.209.123.169
13 2026-08-26 04:05 639233130828334142
523 ms 122.209.123.169
12 2026-08-26 03:48 639233120373450007
512 ms 122.209.123.169
11 2026-08-26 03:30 639233110066216193
548 ms 122.209.123.169
10 2026-08-26 02:37 639233078065410564
3 ms 122.209.123.169
9 2026-08-26 02:20 639233067787457832
3 ms 122.209.123.169
8 2026-08-26 02:03 639233057501801162
498 ms 122.209.123.169
7 2026-08-26 01:46 639233047089431703
620 ms 122.209.123.169
6 2026-08-26 01:28 639233036754790688
512 ms 122.209.123.169
5 2026-08-26 01:11 639233026412602472
532 ms 122.209.123.169
4 2026-08-26 00:54 639233016064066127
554 ms 122.209.123.169
3 2026-08-26 00:37 639233005922655772
493 ms 122.209.123.169
2 2026-08-26 00:20 639232995672256907
475 ms 122.209.123.169
1 2026-08-26 00:03 639232985300872416
454 ms 122.209.123.169