DNS response history for pink2.disbit.com

pink2.disbit.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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 307 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 pink2.disbit.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

307 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.146.98.122

Most recently resolved hosting IP on selected date

Successful Responses

32

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 pink2.disbit.com

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:25 639232535349285207
47 ms 91.146.98.122
31 2026-08-25 11:08 639232524938080723
10 ms 91.146.98.122
30 2026-08-25 10:14 639232492740373468
70 ms 91.146.98.122
29 2026-08-25 09:57 639232482235303141
46 ms 91.146.98.122
28 2026-08-25 09:39 639232471861770303
2081 ms 91.146.98.122
27 2026-08-25 09:22 639232461630217327
60 ms 91.146.98.122
26 2026-08-25 09:05 639232451282965990
64 ms 91.146.98.122
25 2026-08-25 08:48 639232440814614938
14 ms 91.146.98.122
24 2026-08-25 08:30 639232430410720425
104 ms 91.146.98.122
23 2026-08-25 08:13 639232420003096185
96 ms 91.146.98.122
22 2026-08-25 07:56 639232409467287444
97 ms 91.146.98.122
21 2026-08-25 07:38 639232399077195997
2065 ms 91.146.98.122
20 2026-08-25 07:21 639232388731528337
45 ms 91.146.98.122
19 2026-08-25 07:03 639232378288598612
34 ms 91.146.98.122
18 2026-08-25 06:10 639232346196373643
43 ms 91.146.98.122
17 2026-08-25 05:53 639232336112370741
8 ms 91.146.98.122
16 2026-08-25 05:37 639232326146508970
86 ms 91.146.98.122
15 2026-08-25 05:20 639232316189381720
103 ms 91.146.98.122
14 2026-08-25 05:03 639232306217998913
2098 ms 91.146.98.122
13 2026-08-25 04:47 639232296255744174
2 ms 91.146.98.122
12 2026-08-25 04:30 639232286095760789
86 ms 91.146.98.122
11 2026-08-25 04:13 639232276086186273
46 ms 91.146.98.122
10 2026-08-25 03:56 639232265900986425
43 ms 91.146.98.122
9 2026-08-25 03:39 639232255723518075
37 ms 91.146.98.122
8 2026-08-25 03:22 639232245484452890
2057 ms 91.146.98.122
7 2026-08-25 03:05 639232235157175331
86 ms 91.146.98.122
6 2026-08-25 02:12 639232203197189095
49 ms 91.146.98.122
5 2026-08-25 01:54 639232192844564298
26 ms 91.146.98.122
4 2026-08-25 01:37 639232182496008942
10 ms 91.146.98.122
3 2026-08-25 01:20 639232172197053132
48 ms 91.146.98.122
2 2026-08-25 00:27 639232140250307418
68 ms 91.146.98.122
1 2026-08-25 00:10 639232129927860324
87 ms 91.146.98.122