DNS response history for b.ns.orbivox.com

b.ns.orbivox.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 315 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 b.ns.orbivox.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

315 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

75.152.104.105

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 b.ns.orbivox.com

Showing DNS history for 2026-08-26 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-26 11:38 639233403515141099
469 ms 75.152.104.105
34 2026-08-26 10:44 639233370841350248
156 ms 75.152.104.105
33 2026-08-26 10:27 639233360361507238
313 ms 75.152.104.105
32 2026-08-26 10:09 639233350067824371
295 ms 75.152.104.105
31 2026-08-26 09:52 639233339545274518
318 ms 75.152.104.105
30 2026-08-26 09:34 639233329214918079
3 ms 75.152.104.105
29 2026-08-26 09:17 639233318749762337
736 ms 75.152.104.105
28 2026-08-26 09:00 639233308387917838
326 ms 75.152.104.105
27 2026-08-26 08:42 639233297961740122
342 ms 75.152.104.105
26 2026-08-26 08:25 639233287487159094
475 ms 75.152.104.105
25 2026-08-26 08:08 639233276995531707
155 ms 75.152.104.105
24 2026-08-26 07:50 639233266521568229
471 ms 75.152.104.105
23 2026-08-26 07:33 639233256081047431
468 ms 75.152.104.105
22 2026-08-26 06:39 639233223620132921
328 ms 75.152.104.105
21 2026-08-26 06:21 639233213287814244
469 ms 75.152.104.105
20 2026-08-26 06:04 639233202925983161
319 ms 75.152.104.105
19 2026-08-26 05:47 639233192644780696
486 ms 75.152.104.105
18 2026-08-26 05:30 639233182401183833
4 ms 75.152.104.105
17 2026-08-26 05:13 639233172074181051
161 ms 75.152.104.105
16 2026-08-26 04:55 639233161808421455
157 ms 75.152.104.105
15 2026-08-26 04:38 639233151357344052
3 ms 75.152.104.105
14 2026-08-26 04:21 639233141034116946
157 ms 75.152.104.105
13 2026-08-26 04:04 639233130828334142
471 ms 75.152.104.105
12 2026-08-26 03:47 639233120373450007
324 ms 75.152.104.105
11 2026-08-26 03:29 639233110066216193
478 ms 75.152.104.105
10 2026-08-26 02:36 639233078065410564
158 ms 75.152.104.105
9 2026-08-26 02:19 639233067787457832
319 ms 75.152.104.105
8 2026-08-26 02:02 639233057501801162
315 ms 75.152.104.105
7 2026-08-26 01:44 639233047089431703
473 ms 75.152.104.105
6 2026-08-26 01:27 639233036754790688
466 ms 75.152.104.105
5 2026-08-26 01:10 639233026412602472
157 ms 75.152.104.105
4 2026-08-26 00:53 639233016064066127
316 ms 75.152.104.105
3 2026-08-26 00:35 639233005922655772
317 ms 75.152.104.105
2 2026-08-26 00:18 639232995672256907
316 ms 75.152.104.105
1 2026-08-26 00:01 639232985300872416
313 ms 75.152.104.105