DNS response history for ns2.nevimobilya.com

ns2.nevimobilya.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-30. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 124 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.nevimobilya.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

124 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

193.33.29.105

Most recently resolved hosting IP on selected date

Successful Responses

37

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.nevimobilya.com

Showing DNS history for 2026-08-30 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-30 12:02 639236878057367680
43 ms 193.33.29.105
36 2026-08-30 11:46 639236867916029489
100 ms 193.33.29.105
35 2026-08-30 11:29 639236858088772005
97 ms 193.33.29.105
34 2026-08-30 11:12 639236848158742395
61 ms 193.33.29.105
33 2026-08-30 10:56 639236838137395574
64 ms 193.33.29.105
32 2026-08-30 10:39 639236827967386881
87 ms 193.33.29.105
31 2026-08-30 10:22 639236817708615077
78 ms 193.33.29.105
30 2026-08-30 09:29 639236785770651804
37 ms 193.33.29.105
29 2026-08-30 09:12 639236775820686373
39 ms 193.33.29.105
28 2026-08-30 08:55 639236765768339082
12 ms 193.33.29.105
27 2026-08-30 08:38 639236755602384085
9 ms 193.33.29.105
26 2026-08-30 08:21 639236745600094925
2019 ms 193.33.29.105
25 2026-08-30 08:05 639236735311262753
85 ms 193.33.29.105
24 2026-08-30 07:47 639236724996745235
94 ms 193.33.29.105
23 2026-08-30 07:30 639236714839899761
3 ms 193.33.29.105
22 2026-08-30 07:13 639236704748431488
53 ms 193.33.29.105
21 2026-08-30 06:56 639236694430128550
78 ms 193.33.29.105
20 2026-08-30 06:39 639236684143292417
87 ms 193.33.29.105
19 2026-08-30 06:22 639236673972499943
84 ms 193.33.29.105
18 2026-08-30 05:29 639236642126522802
87 ms 193.33.29.105
17 2026-08-30 05:13 639236632183518198
78 ms 193.33.29.105
16 2026-08-30 04:56 639236622289312589
75 ms 193.33.29.105
15 2026-08-30 04:39 639236612490676525
85 ms 193.33.29.105
14 2026-08-30 04:23 639236602582494852
76 ms 193.33.29.105
13 2026-08-30 04:06 639236592511706469
87 ms 193.33.29.105
12 2026-08-30 03:50 639236582441006869
79 ms 193.33.29.105
11 2026-08-30 03:33 639236572478785089
102 ms 193.33.29.105
10 2026-08-30 03:17 639236562556749999
81 ms 193.33.29.105
9 2026-08-30 03:00 639236552353482281
80 ms 193.33.29.105
8 2026-08-30 02:43 639236542188881607
89 ms 193.33.29.105
7 2026-08-30 02:26 639236531885440105
9 ms 193.33.29.105
6 2026-08-30 01:32 639236499922985383
88 ms 193.33.29.105
5 2026-08-30 01:15 639236489713594431
92 ms 193.33.29.105
4 2026-08-30 00:59 639236479750443901
16 ms 193.33.29.105
3 2026-08-30 00:42 639236469719936375
88 ms 193.33.29.105
2 2026-08-30 00:25 639236459579244885
162 ms 193.33.29.105
1 2026-08-30 00:08 639236449582837549
98 ms 193.33.29.105