DNS response history for ns.evorm.com

ns.evorm.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-27. For this date, NameServerHistory found 35 DNS check records, 34 successful responses, 1 failed responses, and 2263 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 ns.evorm.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

2263 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.122.26.139

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns.evorm.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:02 639234243654907465
2041 ms 195.122.26.139
34 2026-08-27 10:45 639234233269654413
2044 ms 195.122.26.139
33 2026-08-27 10:27 639234222943951923
3 ms 195.122.26.139
32 2026-08-27 10:10 639234212558002823
3 ms 195.122.26.139
31 2026-08-27 09:53 639234202117531850
2055 ms 195.122.26.139
30 2026-08-27 09:35 639234191649612722
2044 ms 195.122.26.139
29 2026-08-27 09:18 639234181105879568
2309 ms 195.122.26.139
28 2026-08-27 09:00 639234170713214496
2041 ms 195.122.26.139
27 2026-08-27 08:43 639234160341037652
2055 ms 195.122.26.139
26 2026-08-27 08:26 639234149799404224
3545 ms 195.122.26.139
25 2026-08-27 08:08 639234139553286469
2139 ms 195.122.26.139
24 2026-08-27 07:15 639234107183588293
8 ms 195.122.26.139
23 2026-08-27 06:57 639234096905435724
3508 ms 195.122.26.139
22 2026-08-27 06:40 639234086579410775
3579 ms 195.122.26.139
21 2026-08-27 06:23 639234076291157956
3723 ms 195.122.26.139
20 2026-08-27 06:06 639234065981939454
3540 ms 195.122.26.139
19 2026-08-27 05:49 639234055548642997
2044 ms 195.122.26.139
18 2026-08-27 05:31 639234045267979603
2008 ms 195.122.26.139
17 2026-08-27 05:14 639234034999717463
2031 ms 195.122.26.139
16 2026-08-27 04:57 639234024739225358
2069 ms 195.122.26.139
15 2026-08-27 04:40 639234014311170162
2032 ms 195.122.26.139
14 2026-08-27 04:22 639234003806017640
2141 ms 195.122.26.139
13 2026-08-27 04:05 639233993356203030
3573 ms 195.122.26.139
12 2026-08-27 03:11 639233961301716608
2043 ms 195.122.26.139
11 2026-08-27 02:54 639233950834200647
3571 ms 195.122.26.139
10 2026-08-27 02:37 639233940431849026
2070 ms 195.122.26.139
9 2026-08-27 02:19 639233930110596398
3532 ms 195.122.26.139
8 2026-08-27 02:02 639233919705434540
2 ms 195.122.26.139
7 2026-08-27 01:45 639233909452807845
2042 ms 195.122.26.139
6 2026-08-27 01:28 639233899096420820
2044 ms 195.122.26.139
5 2026-08-27 01:11 639233888707824939
2047 ms 195.122.26.139
4 2026-08-27 00:53 639233878461203802
3510 ms 195.122.26.139
3 2026-08-27 00:36 639233868060868209
-
2 2026-08-27 00:19 639233857450922991
2044 ms 195.122.26.139
1 2026-08-27 00:01 639233846871926285
3509 ms 195.122.26.139