DNS response history for ns2.enterpyme.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

493 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.24.154.79

Most recently resolved hosting IP on selected date

Successful Responses

28

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

Showing DNS history for 2026-08-28 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
28 2026-08-28 11:33 639235132147470568
91 ms 31.24.154.79
27 2026-08-28 11:16 639235121907744088
2170 ms 31.24.154.79
26 2026-08-28 10:59 639235111428014262
46 ms 31.24.154.79
25 2026-08-28 10:41 639235100921813626
164 ms 31.24.154.79
24 2026-08-28 09:47 639235068670703481
47 ms 31.24.154.79
23 2026-08-28 09:30 639235058337459445
48 ms 31.24.154.79
22 2026-08-28 09:13 639235047825109146
2066 ms 31.24.154.79
21 2026-08-28 08:55 639235037383229033
2056 ms 31.24.154.79
20 2026-08-28 08:02 639235005619242711
54 ms 31.24.154.79
19 2026-08-28 07:45 639234995310346584
62 ms 31.24.154.79
18 2026-08-28 07:28 639234984946548933
56 ms 31.24.154.79
17 2026-08-28 07:11 639234974608077290
49 ms 31.24.154.79
16 2026-08-28 06:17 639234942529845595
2053 ms 31.24.154.79
15 2026-08-28 06:00 639234932259126627
2049 ms 31.24.154.79
14 2026-08-28 05:43 639234921916735988
99 ms 31.24.154.79
13 2026-08-28 05:26 639234911470038027
45 ms 31.24.154.79
12 2026-08-28 04:32 639234879588411654
55 ms 31.24.154.79
11 2026-08-28 04:15 639234869341589104
43 ms 31.24.154.79
10 2026-08-28 03:58 639234859012216675
51 ms 31.24.154.79
9 2026-08-28 03:41 639234848695364934
99 ms 31.24.154.79
8 2026-08-28 02:48 639234816952458162
2017 ms 31.24.154.79
7 2026-08-28 02:31 639234806773081598
45 ms 31.24.154.79
6 2026-08-28 02:14 639234796382955255
60 ms 31.24.154.79
5 2026-08-28 01:56 639234786015782563
85 ms 31.24.154.79
4 2026-08-28 01:03 639234753811917646
42 ms 31.24.154.79
3 2026-08-28 00:46 639234743739767811
25 ms 31.24.154.79
2 2026-08-28 00:29 639234733372362811
35 ms 31.24.154.79
1 2026-08-28 00:11 639234723048550337
104 ms 31.24.154.79