DNS response history for ns2.pyropixel.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

310 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 09:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.62.223.155

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

Showing DNS history for 2026-08-29 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-29 09:36 639235924465736791
29 ms 50.62.223.155
27 2026-08-29 09:19 639235914430611197
11 ms 50.62.223.155
26 2026-08-29 09:02 639235904343784853
26 ms 50.62.223.155
25 2026-08-29 08:46 639235894201078068
4 ms 50.62.223.155
24 2026-08-29 08:29 639235884233447452
31 ms 50.62.223.155
23 2026-08-29 08:12 639235874142207309
7 ms 50.62.223.155
22 2026-08-29 07:55 639235863974652466
4 ms 50.62.223.155
21 2026-08-29 07:38 639235853716243436
3 ms 50.62.223.155
20 2026-08-29 07:21 639235843614494759
23 ms 50.62.223.155
19 2026-08-29 07:04 639235833401459551
19 ms 50.62.223.155
18 2026-08-29 06:47 639235823220464528
46 ms 50.62.223.155
17 2026-08-29 06:30 639235812997510905
20 ms 50.62.223.155
16 2026-08-29 05:37 639235781101962521
23 ms 50.62.223.155
15 2026-08-29 05:20 639235771207673260
45 ms 50.62.223.155
14 2026-08-29 05:04 639235761047429642
2032 ms 50.62.223.155
13 2026-08-29 04:47 639235750964347246
15 ms 50.62.223.155
12 2026-08-29 04:30 639235740923490874
17 ms 50.62.223.155
11 2026-08-29 04:13 639235730842894399
18 ms 50.62.223.155
10 2026-08-29 03:56 639235720760084717
2014 ms 50.62.223.155
9 2026-08-29 03:40 639235710843666743
25 ms 50.62.223.155
8 2026-08-29 03:23 639235700733510561
8 ms 50.62.223.155
7 2026-08-29 03:06 639235690509906192
2012 ms 50.62.223.155
6 2026-08-29 02:49 639235680156673501
19 ms 50.62.223.155
5 2026-08-29 02:31 639235669720606443
4 ms 50.62.223.155
4 2026-08-29 01:38 639235637451417084
129 ms 50.62.223.155
3 2026-08-29 01:21 639235627307383453
37 ms 50.62.223.155
2 2026-08-29 01:04 639235616906386856
33 ms 50.62.223.155
1 2026-08-29 00:46 639235606582912691
2013 ms 50.62.223.155