DNS response history for ns2.travelbookinggroup.com

ns2.travelbookinggroup.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 373 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.travelbookinggroup.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

373 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.109.190.251

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 ns2.travelbookinggroup.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:19 639232492740373468
348 ms 208.109.190.251
29 2026-08-25 10:02 639232482235303141
345 ms 208.109.190.251
28 2026-08-25 09:44 639232471861770303
338 ms 208.109.190.251
27 2026-08-25 09:27 639232461630217327
348 ms 208.109.190.251
26 2026-08-25 09:10 639232451282965990
347 ms 208.109.190.251
25 2026-08-25 08:53 639232440814614938
348 ms 208.109.190.251
24 2026-08-25 08:35 639232430410720425
336 ms 208.109.190.251
23 2026-08-25 08:18 639232420003096185
352 ms 208.109.190.251
22 2026-08-25 08:01 639232409467287444
358 ms 208.109.190.251
21 2026-08-25 07:43 639232399077195997
342 ms 208.109.190.251
20 2026-08-25 07:26 639232388731528337
339 ms 208.109.190.251
19 2026-08-25 07:08 639232378288598612
2015 ms 208.109.190.251
18 2026-08-25 06:15 639232346196373643
197 ms 208.109.190.251
17 2026-08-25 05:58 639232336112370741
352 ms 208.109.190.251
16 2026-08-25 05:41 639232326146508970
4 ms 208.109.190.251
15 2026-08-25 05:25 639232316189381720
8 ms 208.109.190.251
14 2026-08-25 05:08 639232306217998913
359 ms 208.109.190.251
13 2026-08-25 04:52 639232296255744174
356 ms 208.109.190.251
12 2026-08-25 04:35 639232286095760789
342 ms 208.109.190.251
11 2026-08-25 04:18 639232276086186273
365 ms 208.109.190.251
10 2026-08-25 04:01 639232265900986425
340 ms 208.109.190.251
9 2026-08-25 03:44 639232255723518075
346 ms 208.109.190.251
8 2026-08-25 03:27 639232245484452890
337 ms 208.109.190.251
7 2026-08-25 03:10 639232235157175331
359 ms 208.109.190.251
6 2026-08-25 02:17 639232203197189095
331 ms 208.109.190.251
5 2026-08-25 01:59 639232192844564298
338 ms 208.109.190.251
4 2026-08-25 01:42 639232182496008942
332 ms 208.109.190.251
3 2026-08-25 01:25 639232172197053132
350 ms 208.109.190.251
2 2026-08-25 00:32 639232140250307418
331 ms 208.109.190.251
1 2026-08-25 00:15 639232129927860324
328 ms 208.109.190.251