DNS response history for no2.pythonho.st

no2.pythonho.st 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 103 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 no2.pythonho.st.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

103 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.159.49.195

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 no2.pythonho.st

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:08 639234253963286387
189 ms 5.159.49.195
34 2026-08-27 10:50 639234243654907465
205 ms 5.159.49.195
33 2026-08-27 10:33 639234233269654413
5 ms 5.159.49.195
32 2026-08-27 10:16 639234222943951923
25 ms 5.159.49.195
31 2026-08-27 09:59 639234212558002823
15 ms 5.159.49.195
30 2026-08-27 09:41 639234202117531850
12 ms 5.159.49.195
29 2026-08-27 09:24 639234191649612722
26 ms 5.159.49.195
28 2026-08-27 09:06 639234181105879568
15 ms 5.159.49.195
27 2026-08-27 08:49 639234170713214496
4 ms 5.159.49.195
26 2026-08-27 08:31 639234160341037652
39 ms 5.159.49.195
25 2026-08-27 08:14 639234149799404224
43 ms 5.159.49.195
24 2026-08-27 07:57 639234139553286469
9 ms 5.159.49.195
23 2026-08-27 07:03 639234107183588293
30 ms 5.159.49.195
22 2026-08-27 06:46 639234096905435724
103 ms 5.159.49.195
21 2026-08-27 06:29 639234086579410775
7 ms 5.159.49.195
20 2026-08-27 06:12 639234076291157956
30 ms 5.159.49.195
19 2026-08-27 05:54 639234065981939454
30 ms 5.159.49.195
18 2026-08-27 05:37 639234055548642997
37 ms 5.159.49.195
17 2026-08-27 05:20 639234045267979603
52 ms 5.159.49.195
16 2026-08-27 05:03 639234034999717463
2039 ms 5.159.49.195
15 2026-08-27 04:46 639234024739225358
45 ms 5.159.49.195
14 2026-08-27 04:28 639234014311170162
55 ms 5.159.49.195
13 2026-08-27 04:11 639234003806017640
9 ms 5.159.49.195
12 2026-08-27 03:53 639233993356203030
5 ms 5.159.49.195
11 2026-08-27 03:00 639233961301716608
5 ms 5.159.49.195
10 2026-08-27 02:43 639233950834200647
30 ms 5.159.49.195
9 2026-08-27 02:25 639233940431849026
78 ms 5.159.49.195
8 2026-08-27 02:08 639233930110596398
272 ms 5.159.49.195
7 2026-08-27 01:51 639233919705434540
22 ms 5.159.49.195
6 2026-08-27 01:33 639233909452807845
37 ms 5.159.49.195
5 2026-08-27 01:16 639233899096420820
40 ms 5.159.49.195
4 2026-08-27 00:59 639233888707824939
46 ms 5.159.49.195
3 2026-08-27 00:42 639233878461203802
4 ms 5.159.49.195
2 2026-08-27 00:24 639233868060868209
6 ms 5.159.49.195
1 2026-08-27 00:07 639233857450922991
28 ms 5.159.49.195