DNS response history for ns2.eforhosting.com

ns2.eforhosting.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-16. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 88 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.eforhosting.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

88 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-16 23:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.141.149.250

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

Showing DNS history for 2026-08-16 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-16 23:45 639225198045815385
97 ms 45.141.149.250
31 2026-08-16 22:53 639225166825544741
96 ms 45.141.149.250
30 2026-08-16 22:37 639225157549461269
96 ms 45.141.149.250
29 2026-08-16 22:22 639225147914556308
2 ms 45.141.149.250
28 2026-08-16 22:06 639225138472322960
4 ms 45.141.149.250
27 2026-08-16 21:14 639225107211236826
101 ms 45.141.149.250
26 2026-08-16 20:58 639225097684457510
97 ms 45.141.149.250
25 2026-08-16 20:42 639225087942913396
99 ms 45.141.149.250
24 2026-08-16 20:26 639225078238684183
99 ms 45.141.149.250
23 2026-08-16 19:33 639225046944151094
98 ms 45.141.149.250
22 2026-08-16 19:17 639225037234857231
100 ms 45.141.149.250
21 2026-08-16 19:01 639225027423459920
97 ms 45.141.149.250
20 2026-08-16 18:45 639225017891613027
3 ms 45.141.149.250
19 2026-08-16 17:52 639224986298183527
95 ms 45.141.149.250
18 2026-08-16 17:37 639224976567107023
98 ms 45.141.149.250
17 2026-08-16 17:20 639224966709723386
101 ms 45.141.149.250
16 2026-08-16 17:04 639224957175756942
99 ms 45.141.149.250
15 2026-08-16 16:12 639224925782379869
98 ms 45.141.149.250
14 2026-08-16 15:56 639224916429532459
99 ms 45.141.149.250
13 2026-08-16 15:40 639224906878325623
100 ms 45.141.149.250
12 2026-08-16 15:24 639224897258974385
98 ms 45.141.149.250
11 2026-08-16 14:32 639224866169532828
49 ms 45.141.149.250
10 2026-08-16 14:16 639224856561831915
98 ms 45.141.149.250
9 2026-08-16 14:00 639224846830897794
99 ms 45.141.149.250
8 2026-08-16 13:44 639224836975863283
101 ms 45.141.149.250
7 2026-08-16 12:50 639224804985340946
100 ms 45.141.149.250
6 2026-08-16 11:10 639224744252113993
101 ms 45.141.149.250
5 2026-08-16 09:24 639224681063874153
98 ms 45.141.149.250
4 2026-08-16 07:40 639224618882283050
102 ms 45.141.149.250
3 2026-08-16 06:00 639224558901831832
96 ms 45.141.149.250
2 2026-08-16 04:21 639224499638024410
100 ms 45.141.149.250
1 2026-08-16 02:42 639224440124457324
98 ms 45.141.149.250