DNS response history for ns2.rtpcerutu4d.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

196 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.177.123.115

Most recently resolved hosting IP on selected date

Successful Responses

32

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.rtpcerutu4d.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
32 2026-08-26 10:11 639233350067824371
285 ms 198.177.123.115
31 2026-08-26 09:54 639233339545274518
3 ms 198.177.123.115
30 2026-08-26 09:36 639233329214918079
303 ms 198.177.123.115
29 2026-08-26 09:19 639233318749762337
149 ms 198.177.123.115
28 2026-08-26 09:02 639233308387917838
341 ms 198.177.123.115
27 2026-08-26 08:45 639233297961740122
311 ms 198.177.123.115
26 2026-08-26 08:27 639233287487159094
287 ms 198.177.123.115
25 2026-08-26 08:10 639233276995531707
183 ms 198.177.123.115
24 2026-08-26 07:52 639233266521568229
3 ms 198.177.123.115
23 2026-08-26 07:35 639233256081047431
332 ms 198.177.123.115
22 2026-08-26 06:41 639233223620132921
2 ms 198.177.123.115
21 2026-08-26 06:23 639233213287814244
294 ms 198.177.123.115
20 2026-08-26 06:06 639233202925983161
3 ms 198.177.123.115
19 2026-08-26 05:49 639233192644780696
3 ms 198.177.123.115
18 2026-08-26 05:32 639233182401183833
296 ms 198.177.123.115
17 2026-08-26 05:15 639233172074181051
313 ms 198.177.123.115
16 2026-08-26 04:57 639233161808421455
3 ms 198.177.123.115
15 2026-08-26 04:40 639233151357344052
163 ms 198.177.123.115
14 2026-08-26 04:23 639233141034116946
3 ms 198.177.123.115
13 2026-08-26 04:06 639233130828334142
298 ms 198.177.123.115
12 2026-08-26 03:49 639233120373450007
3 ms 198.177.123.115
11 2026-08-26 03:31 639233110066216193
2 ms 198.177.123.115
10 2026-08-26 02:38 639233078065410564
321 ms 198.177.123.115
9 2026-08-26 02:21 639233067787457832
161 ms 198.177.123.115
8 2026-08-26 02:04 639233057501801162
143 ms 198.177.123.115
7 2026-08-26 01:47 639233047089431703
292 ms 198.177.123.115
6 2026-08-26 01:29 639233036754790688
260 ms 198.177.123.115
5 2026-08-26 01:12 639233026412602472
298 ms 198.177.123.115
4 2026-08-26 00:55 639233016064066127
315 ms 198.177.123.115
3 2026-08-26 00:37 639233005922655772
294 ms 198.177.123.115
2 2026-08-26 00:20 639232995672256907
308 ms 198.177.123.115
1 2026-08-26 00:03 639232985300872416
288 ms 198.177.123.115