DNS response history for ns.ebizerp.com

ns.ebizerp.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 30 DNS check records, 30 successful responses, 0 failed responses, and 1102 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.ebizerp.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

1102 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

115.68.17.253

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns.ebizerp.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
30 2026-08-27 09:35 639234191649612722
1664 ms 115.68.17.253
29 2026-08-27 09:17 639234181105879568
1728 ms 115.68.17.253
28 2026-08-27 08:59 639234170713214496
524 ms 115.68.17.253
27 2026-08-27 08:42 639234160341037652
1071 ms 115.68.17.253
26 2026-08-27 08:25 639234149799404224
1732 ms 115.68.17.253
25 2026-08-27 08:07 639234139553286469
1060 ms 115.68.17.253
24 2026-08-27 07:14 639234107183588293
1094 ms 115.68.17.253
23 2026-08-27 06:56 639234096905435724
1093 ms 115.68.17.253
22 2026-08-27 06:39 639234086579410775
517 ms 115.68.17.253
21 2026-08-27 06:22 639234076291157956
1648 ms 115.68.17.253
20 2026-08-27 06:05 639234065981939454
1084 ms 115.68.17.253
19 2026-08-27 05:48 639234055548642997
520 ms 115.68.17.253
18 2026-08-27 05:30 639234045267979603
1662 ms 115.68.17.253
17 2026-08-27 05:13 639234034999717463
1058 ms 115.68.17.253
16 2026-08-27 04:56 639234024739225358
1662 ms 115.68.17.253
15 2026-08-27 04:39 639234014311170162
1090 ms 115.68.17.253
14 2026-08-27 04:21 639234003806017640
1062 ms 115.68.17.253
13 2026-08-27 04:04 639233993356203030
1069 ms 115.68.17.253
12 2026-08-27 03:11 639233961301716608
843 ms 115.68.17.253
11 2026-08-27 02:53 639233950834200647
1672 ms 115.68.17.253
10 2026-08-27 02:36 639233940431849026
1664 ms 115.68.17.253
9 2026-08-27 02:18 639233930110596398
1081 ms 115.68.17.253
8 2026-08-27 02:01 639233919705434540
502 ms 115.68.17.253
7 2026-08-27 01:44 639233909452807845
1667 ms 115.68.17.253
6 2026-08-27 01:27 639233899096420820
2 ms 115.68.17.253
5 2026-08-27 01:10 639233888707824939
1698 ms 115.68.17.253
4 2026-08-27 00:52 639233878461203802
492 ms 115.68.17.253
3 2026-08-27 00:35 639233868060868209
504 ms 115.68.17.253
2 2026-08-27 00:18 639233857450922991
1105 ms 115.68.17.253
1 2026-08-27 00:00 639233846871926285
492 ms 115.68.17.253