DNS response history for ns2.neopharm.bg

ns2.neopharm.bg 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, 35 successful responses, 0 failed responses, and 225 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.neopharm.bg.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

225 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

79.124.31.51

Most recently resolved hosting IP on selected date

Successful Responses

35

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.neopharm.bg

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:10 639234253963286387
48 ms 79.124.31.51
34 2026-08-27 10:53 639234243654907465
35 ms 79.124.31.51
33 2026-08-27 10:35 639234233269654413
34 ms 79.124.31.51
32 2026-08-27 10:18 639234222943951923
64 ms 79.124.31.51
31 2026-08-27 10:01 639234212558002823
2086 ms 79.124.31.51
30 2026-08-27 09:44 639234202117531850
33 ms 79.124.31.51
29 2026-08-27 09:26 639234191649612722
68 ms 79.124.31.51
28 2026-08-27 09:09 639234181105879568
41 ms 79.124.31.51
27 2026-08-27 08:51 639234170713214496
64 ms 79.124.31.51
26 2026-08-27 08:34 639234160341037652
74 ms 79.124.31.51
25 2026-08-27 08:16 639234149799404224
62 ms 79.124.31.51
24 2026-08-27 07:59 639234139553286469
68 ms 79.124.31.51
23 2026-08-27 07:05 639234107183588293
66 ms 79.124.31.51
22 2026-08-27 06:48 639234096905435724
66 ms 79.124.31.51
21 2026-08-27 06:31 639234086579410775
12 ms 79.124.31.51
20 2026-08-27 06:14 639234076291157956
30 ms 79.124.31.51
19 2026-08-27 05:57 639234065981939454
40 ms 79.124.31.51
18 2026-08-27 05:40 639234055548642997
2061 ms 79.124.31.51
17 2026-08-27 05:22 639234045267979603
39 ms 79.124.31.51
16 2026-08-27 05:05 639234034999717463
77 ms 79.124.31.51
15 2026-08-27 04:48 639234024739225358
14 ms 79.124.31.51
14 2026-08-27 04:31 639234014311170162
31 ms 79.124.31.51
13 2026-08-27 04:13 639234003806017640
62 ms 79.124.31.51
12 2026-08-27 03:56 639233993356203030
2078 ms 79.124.31.51
11 2026-08-27 03:02 639233961301716608
65 ms 79.124.31.51
10 2026-08-27 02:45 639233950834200647
76 ms 79.124.31.51
9 2026-08-27 02:28 639233940431849026
72 ms 79.124.31.51
8 2026-08-27 02:10 639233930110596398
33 ms 79.124.31.51
7 2026-08-27 01:53 639233919705434540
40 ms 79.124.31.51
6 2026-08-27 01:36 639233909452807845
67 ms 79.124.31.51
5 2026-08-27 01:19 639233899096420820
67 ms 79.124.31.51
4 2026-08-27 01:01 639233888707824939
39 ms 79.124.31.51
3 2026-08-27 00:44 639233878461203802
64 ms 79.124.31.51
2 2026-08-27 00:27 639233868060868209
47 ms 79.124.31.51
1 2026-08-27 00:09 639233857450922991
39 ms 79.124.31.51