DNS response history for ns2.petbichano.com

ns2.petbichano.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 34 DNS check records, 34 successful responses, 0 failed responses, and 465 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.petbichano.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

186.202.126.135

Most recently resolved hosting IP on selected date

Successful Responses

34

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.petbichano.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
34 2026-08-25 12:06 639232556111768563
356 ms 186.202.126.135
33 2026-08-25 11:48 639232545839529039
407 ms 186.202.126.135
32 2026-08-25 11:31 639232535349285207
369 ms 186.202.126.135
31 2026-08-25 11:14 639232524938080723
392 ms 186.202.126.135
30 2026-08-25 10:20 639232492740373468
7 ms 186.202.126.135
29 2026-08-25 10:03 639232482235303141
369 ms 186.202.126.135
28 2026-08-25 09:45 639232471861770303
374 ms 186.202.126.135
27 2026-08-25 09:28 639232461630217327
8 ms 186.202.126.135
26 2026-08-25 09:11 639232451282965990
2032 ms 186.202.126.135
25 2026-08-25 08:54 639232440814614938
297 ms 186.202.126.135
24 2026-08-25 08:36 639232430410720425
382 ms 186.202.126.135
23 2026-08-25 08:19 639232420003096185
356 ms 186.202.126.135
22 2026-08-25 08:02 639232409467287444
740 ms 186.202.126.135
21 2026-08-25 07:44 639232399077195997
377 ms 186.202.126.135
20 2026-08-25 07:27 639232388731528337
2425 ms 186.202.126.135
19 2026-08-25 07:09 639232378288598612
406 ms 186.202.126.135
18 2026-08-25 06:16 639232346196373643
3 ms 186.202.126.135
17 2026-08-25 05:59 639232336112370741
393 ms 186.202.126.135
16 2026-08-25 05:42 639232326146508970
795 ms 186.202.126.135
15 2026-08-25 05:26 639232316189381720
3 ms 186.202.126.135
14 2026-08-25 05:09 639232306217998913
365 ms 186.202.126.135
13 2026-08-25 04:52 639232296255744174
381 ms 186.202.126.135
12 2026-08-25 04:36 639232286095760789
374 ms 186.202.126.135
11 2026-08-25 04:19 639232276086186273
664 ms 186.202.126.135
10 2026-08-25 04:02 639232265900986425
1010 ms 186.202.126.135
9 2026-08-25 03:45 639232255723518075
370 ms 186.202.126.135
8 2026-08-25 03:28 639232245484452890
376 ms 186.202.126.135
7 2026-08-25 03:11 639232235157175331
374 ms 186.202.126.135
6 2026-08-25 02:17 639232203197189095
5 ms 186.202.126.135
5 2026-08-25 02:00 639232192844564298
403 ms 186.202.126.135
4 2026-08-25 01:43 639232182496008942
3 ms 186.202.126.135
3 2026-08-25 01:26 639232172197053132
376 ms 186.202.126.135
2 2026-08-25 00:32 639232140250307418
388 ms 186.202.126.135
1 2026-08-25 00:15 639232129927860324
215 ms 186.202.126.135