DNS response history for cyber2.tpmex.com

cyber2.tpmex.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 33 DNS check records, 33 successful responses, 0 failed responses, and 336 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 cyber2.tpmex.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

336 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.244.86.197

Most recently resolved hosting IP on selected date

Successful Responses

33

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 cyber2.tpmex.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
33 2026-08-26 10:27 639233360361507238
156 ms 148.244.86.197
32 2026-08-26 10:10 639233350067824371
160 ms 148.244.86.197
31 2026-08-26 09:53 639233339545274518
159 ms 148.244.86.197
30 2026-08-26 09:35 639233329214918079
159 ms 148.244.86.197
29 2026-08-26 09:18 639233318749762337
159 ms 148.244.86.197
28 2026-08-26 09:00 639233308387917838
161 ms 148.244.86.197
27 2026-08-26 08:43 639233297961740122
158 ms 148.244.86.197
26 2026-08-26 08:26 639233287487159094
193 ms 148.244.86.197
25 2026-08-26 08:08 639233276995531707
158 ms 148.244.86.197
24 2026-08-26 07:51 639233266521568229
851 ms 148.244.86.197
23 2026-08-26 07:33 639233256081047431
158 ms 148.244.86.197
22 2026-08-26 06:39 639233223620132921
171 ms 148.244.86.197
21 2026-08-26 06:22 639233213287814244
10 ms 148.244.86.197
20 2026-08-26 06:05 639233202925983161
158 ms 148.244.86.197
19 2026-08-26 05:47 639233192644780696
159 ms 148.244.86.197
18 2026-08-26 05:30 639233182401183833
311 ms 148.244.86.197
17 2026-08-26 05:13 639233172074181051
312 ms 148.244.86.197
16 2026-08-26 04:56 639233161808421455
2210 ms 148.244.86.197
15 2026-08-26 04:39 639233151357344052
323 ms 148.244.86.197
14 2026-08-26 04:21 639233141034116946
157 ms 148.244.86.197
13 2026-08-26 04:04 639233130828334142
163 ms 148.244.86.197
12 2026-08-26 03:47 639233120373450007
311 ms 148.244.86.197
11 2026-08-26 03:30 639233110066216193
320 ms 148.244.86.197
10 2026-08-26 02:36 639233078065410564
157 ms 148.244.86.197
9 2026-08-26 02:19 639233067787457832
2167 ms 148.244.86.197
8 2026-08-26 02:02 639233057501801162
158 ms 148.244.86.197
7 2026-08-26 01:45 639233047089431703
176 ms 148.244.86.197
6 2026-08-26 01:28 639233036754790688
204 ms 148.244.86.197
5 2026-08-26 01:10 639233026412602472
164 ms 148.244.86.197
4 2026-08-26 00:53 639233016064066127
159 ms 148.244.86.197
3 2026-08-26 00:36 639233005922655772
314 ms 148.244.86.197
2 2026-08-26 00:19 639232995672256907
344 ms 148.244.86.197
1 2026-08-26 00:02 639232985300872416
158 ms 148.244.86.197