DNS response history for ns2.rtoros.com

ns2.rtoros.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 455 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.rtoros.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

455 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

132.148.77.193

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.rtoros.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:42 639233370841350248
336 ms 132.148.77.193
33 2026-08-26 10:25 639233360361507238
350 ms 132.148.77.193
32 2026-08-26 10:08 639233350067824371
332 ms 132.148.77.193
31 2026-08-26 09:51 639233339545274518
368 ms 132.148.77.193
30 2026-08-26 09:33 639233329214918079
332 ms 132.148.77.193
29 2026-08-26 09:16 639233318749762337
336 ms 132.148.77.193
28 2026-08-26 08:58 639233308387917838
7 ms 132.148.77.193
27 2026-08-26 08:41 639233297961740122
349 ms 132.148.77.193
26 2026-08-26 08:24 639233287487159094
346 ms 132.148.77.193
25 2026-08-26 08:06 639233276995531707
2161 ms 132.148.77.193
24 2026-08-26 07:49 639233266521568229
338 ms 132.148.77.193
23 2026-08-26 07:31 639233256081047431
334 ms 132.148.77.193
22 2026-08-26 06:37 639233223620132921
360 ms 132.148.77.193
21 2026-08-26 06:20 639233213287814244
350 ms 132.148.77.193
20 2026-08-26 06:03 639233202925983161
356 ms 132.148.77.193
19 2026-08-26 05:45 639233192644780696
2032 ms 132.148.77.193
18 2026-08-26 05:28 639233182401183833
348 ms 132.148.77.193
17 2026-08-26 05:11 639233172074181051
335 ms 132.148.77.193
16 2026-08-26 04:54 639233161808421455
347 ms 132.148.77.193
15 2026-08-26 04:37 639233151357344052
32 ms 132.148.77.193
14 2026-08-26 04:19 639233141034116946
341 ms 132.148.77.193
13 2026-08-26 04:02 639233130828334142
2007 ms 132.148.77.193
12 2026-08-26 03:45 639233120373450007
290 ms 132.148.77.193
11 2026-08-26 03:28 639233110066216193
355 ms 132.148.77.193
10 2026-08-26 02:34 639233078065410564
335 ms 132.148.77.193
9 2026-08-26 02:17 639233067787457832
335 ms 132.148.77.193
8 2026-08-26 02:00 639233057501801162
9 ms 132.148.77.193
7 2026-08-26 01:43 639233047089431703
157 ms 132.148.77.193
6 2026-08-26 01:26 639233036754790688
351 ms 132.148.77.193
5 2026-08-26 01:09 639233026412602472
348 ms 132.148.77.193
4 2026-08-26 00:51 639233016064066127
171 ms 132.148.77.193
3 2026-08-26 00:34 639233005922655772
333 ms 132.148.77.193
2 2026-08-26 00:17 639232995672256907
335 ms 132.148.77.193
1 2026-08-26 00:00 639232985300872416
341 ms 132.148.77.193