Packet loss getting to

Discussion in 'QRZ XML Logbook Data' started by KA1JY, Feb 13, 2019.


Are you seeing significant packet loss getting your xml lookups?

Poll closed Mar 5, 2019.
  1. Yes, my packet loss is high

  2. No, I don't see a lot of packet loss

  3. Maybe, I see some loss but under 20%

    0 vote(s)
ad: L-HROutlet
ad: l-rl
ad: Left-2
ad: MessiPaoloni-1
ad: L-MFJ
ad: Subscribe
ad: Left-3
  1. KA1JY

    KA1JY XML Subscriber QRZ Page

    Anyone else seeing large packet losses getting to I noticed this the other day during the RTTY contest. HRD's digithing does an xml look up to fill in contact info. I was getting this long delay which sort of hangs digital master 780. Because of this I did a little sniffing the path to I am seeing 8ms latency up to IP address (Nashville switch) from that address I see 20.7 average latency. Not bad. Off network I frequently see 50ms so this is good. Next hop is WOW! That hop is un-measurable because of the packet losses over 50%. Just terrible. I"m not sure why the path looks like it does. How is it the Nashville network jumps off directly to I can't really tell if this is an issue with the QRZ isp or something with the Nashville switch jump off to the site directly. Anyone else seeing these problems? PingPlotter (free or pro) is a nice tool for measuring latency or loss. I have the free version. Check it out from your location and let me know if your results are better than mine.
  2. VK3HJ

    VK3HJ Premium Subscriber QRZ Page

    Just using the system command "ping", with a couple of websites I checked, I get ping return times of approximately 600 - 700 ms, which is normal for my satellite Internet link.

    Pinging results in 100 % timeout and packet loss.

    I can use website ok, but XML does not work.
  3. KA1JY

    KA1JY XML Subscriber QRZ Page

    XML works for me but just BARELY. It is so slow to respond that I am considering finding some alternative to callsign look ups. At this point QRZ seems almost unusable. I have good internet conductivity with a 300M fiber connection which seems to do reasonably well to every place BUT qrz xml lookups. FYI - file uploads to the log book work fine. No problem moving a file with 50 contacts up to qrz logbook but looking stuff up is painfully slow.
  4. VK3HJ

    VK3HJ Premium Subscriber QRZ Page

    I now have HRD looking up callsign information at, where I found I had already set up a free account.

    Lookups are still very slow, maybe 20 seconds or so, but I still have no returns from

    I pinged and get a "normal" return.

    I have a support ticket with in progress. Latest is that there appears to be a DNS problem at my ISP.
  5. KA1JY

    KA1JY XML Subscriber QRZ Page

    Well I don't have any dns problem. Frankly if the problem is with DNS if you are using windows just put an entry in your "hosts" file and be done with it. Either that or use the IP address for the application you are using for the look up. HRD's logbook has not such flexibility and has a "fixed" hard coded callsign look up set up. (ugly) Still you can fix the dns in windoze if that is truly the issue. It is NOT the issue for me. Fixing and using the hosts file in windows is a bit tricky but you should be able to figure it out. Copy the file to a place you have edit rights, modify it and then copy it back to the original location \windows\system32\drivers\etc\hosts. Anyway that will solve the dns but it won't improve the qrz responsible time.
  6. AD1L

    AD1L Premium Subscriber QRZ Page

    Yesterday XML lookup via ACLog 6.4 was totally unusable crawling along and resulting in connection timeouts.

    What method do I use to log a formal trouble ticket for This paid service?
  7. KA1JY

    KA1JY XML Subscriber QRZ Page

    GOOD QUESTION! I get it that some modes (FT8) have resurrected interest and activity on the bands, logging programs, and look-ups but the performance for xml is almost unusable at times. Ya have to wonder if it is database performance or an ISP issue. I am seriously considering picking up a callsign database on dvd and parking it on a local SS SATA drive. Clearly the thing should be refreshed monthly to be helpful but at this point it is either run my own or investigate the other online lookup alternatives. Maybe this isn't news to serious award chasers but it is a new issue for me.
  8. VK3HJ

    VK3HJ Premium Subscriber QRZ Page

    I tried
    as advised by the QRZ Support Team, but both return "This site cannot be reached". I get the same result on two PCs and a phone, all connected to the Internet via home wifi and satellite link.
    I checked the "hosts" file, and there was nothing in there except a couple of examples.
    The latest from the Support Team (a week ago) is "Ticket Elevated to QRZ Headquarters for support."
    My callsign information lookup in HRD Logbook all stopped working for me on the 7th Feb. The website works normally.
  9. WB5WPA

    WB5WPA Ham Member QRZ Page

    Just a guess, but, aws hosted websites can't be "ping"ed; I get 100% loss trying too.

    I tried several off-site ping services and had the same result.
  10. KA9JLM

    KA9JLM Ham Member QRZ Page

    Have you tried;

    • In the open prompt, type “ipconfig /flushdns” (without the quotes). ?

Share This Page