DNS response history for ns4.nexibloom.com

ns4.nexibloom.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 30 DNS check records, 30 successful responses, 0 failed responses, and 362 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 ns4.nexibloom.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

362 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.153.165.116

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns4.nexibloom.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
30 2026-08-25 10:10 639232492740373468
8 ms 131.153.165.116
29 2026-08-25 09:53 639232482235303141
54 ms 131.153.165.116
28 2026-08-25 09:35 639232471861770303
81 ms 131.153.165.116
27 2026-08-25 09:18 639232461630217327
17 ms 131.153.165.116
26 2026-08-25 09:01 639232451282965990
6 ms 131.153.165.116
25 2026-08-25 08:44 639232440814614938
4040 ms 131.153.165.116
24 2026-08-25 08:26 639232430410720425
9 ms 131.153.165.116
23 2026-08-25 08:09 639232420003096185
50 ms 131.153.165.116
22 2026-08-25 07:51 639232409467287444
57 ms 131.153.165.116
21 2026-08-25 07:34 639232399077195997
7 ms 131.153.165.116
20 2026-08-25 07:17 639232388731528337
43 ms 131.153.165.116
19 2026-08-25 06:59 639232378288598612
23 ms 131.153.165.116
18 2026-08-25 06:06 639232346196373643
11 ms 131.153.165.116
17 2026-08-25 05:49 639232336112370741
19 ms 131.153.165.116
16 2026-08-25 05:32 639232326146508970
5 ms 131.153.165.116
15 2026-08-25 05:16 639232316189381720
62 ms 131.153.165.116
14 2026-08-25 04:59 639232306217998913
2041 ms 131.153.165.116
13 2026-08-25 04:43 639232296255744174
36 ms 131.153.165.116
12 2026-08-25 04:26 639232286095760789
11 ms 131.153.165.116
11 2026-08-25 04:09 639232276086186273
8 ms 131.153.165.116
10 2026-08-25 03:52 639232265900986425
4038 ms 131.153.165.116
9 2026-08-25 03:35 639232255723518075
40 ms 131.153.165.116
8 2026-08-25 03:18 639232245484452890
6 ms 131.153.165.116
7 2026-08-25 03:01 639232235157175331
13 ms 131.153.165.116
6 2026-08-25 02:07 639232203197189095
34 ms 131.153.165.116
5 2026-08-25 01:50 639232192844564298
72 ms 131.153.165.116
4 2026-08-25 01:33 639232182496008942
19 ms 131.153.165.116
3 2026-08-25 01:16 639232172197053132
10 ms 131.153.165.116
2 2026-08-25 00:22 639232140250307418
9 ms 131.153.165.116
1 2026-08-25 00:05 639232129927860324
36 ms 131.153.165.116