DNS response history for ns2.svrtr.org

ns2.svrtr.org 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 37 DNS check records, 33 successful responses, 4 failed responses, and 258 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.svrtr.org.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

258 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.107.122.128

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

4

Checks with no response or no returned latency

Failure Rate

11%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.svrtr.org

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
37 2026-08-26 12:27 639233434974187439
620 ms 91.107.122.128
36 2026-08-26 12:09 639233424567558554
382 ms 91.107.122.128
35 2026-08-26 11:52 639233414056832719
77 ms 91.107.122.128
34 2026-08-26 11:34 639233403515141099
279 ms 91.107.122.128
33 2026-08-26 10:40 639233370841350248
518 ms 91.107.122.128
32 2026-08-26 10:22 639233360361507238
146 ms 91.107.122.128
31 2026-08-26 10:05 639233350067824371
-
30 2026-08-26 09:48 639233339545274518
-
29 2026-08-26 09:30 639233329214918079
137 ms 91.107.122.128
28 2026-08-26 09:13 639233318749762337
387 ms 91.107.122.128
27 2026-08-26 08:56 639233308387917838
583 ms 91.107.122.128
26 2026-08-26 08:38 639233297961740122
145 ms 91.107.122.128
25 2026-08-26 08:21 639233287487159094
-
24 2026-08-26 08:03 639233276995531707
65 ms 91.107.122.128
23 2026-08-26 07:46 639233266521568229
67 ms 91.107.122.128
22 2026-08-26 07:28 639233256081047431
199 ms 91.107.122.128
21 2026-08-26 06:35 639233223620132921
395 ms 91.107.122.128
20 2026-08-26 06:17 639233213287814244
62 ms 91.107.122.128
19 2026-08-26 06:00 639233202925983161
66 ms 91.107.122.128
18 2026-08-26 05:43 639233192644780696
55 ms 91.107.122.128
17 2026-08-26 05:26 639233182401183833
356 ms 91.107.122.128
16 2026-08-26 05:09 639233172074181051
436 ms 91.107.122.128
15 2026-08-26 04:51 639233161808421455
121 ms 91.107.122.128
14 2026-08-26 04:34 639233151357344052
66 ms 91.107.122.128
13 2026-08-26 04:17 639233141034116946
434 ms 91.107.122.128
12 2026-08-26 04:00 639233130828334142
152 ms 91.107.122.128
11 2026-08-26 03:42 639233120373450007
69 ms 91.107.122.128
10 2026-08-26 03:25 639233110066216193
131 ms 91.107.122.128
9 2026-08-26 02:32 639233078065410564
577 ms 91.107.122.128
8 2026-08-26 02:15 639233067787457832
-
7 2026-08-26 01:57 639233057501801162
107 ms 91.107.122.128
6 2026-08-26 01:40 639233047089431703
214 ms 91.107.122.128
5 2026-08-26 01:23 639233036754790688
379 ms 91.107.122.128
4 2026-08-26 01:06 639233026412602472
308 ms 91.107.122.128
3 2026-08-26 00:48 639233016064066127
71 ms 91.107.122.128
2 2026-08-26 00:31 639233005922655772
351 ms 91.107.122.128
1 2026-08-26 00:14 639232995672256907
553 ms 91.107.122.128