Hello Robert,
I just want to make sure I understand your explanation before resolving this case, as this is all giving me a fascinating look into your organization, and I'd like to make sure all the facts are straight before writing my report.
1) You stated that this was a "temporary glitch", but you do not know what the glitch was and cannot recreate it despite the screenshot I provided (NOTE: I can still reproduce with a cleared cache). How were you able to determine that the glitch was temporary? Was that just a guess, or an intentional fabrication for PR purposes? Having done this kind of support for over a decade, I feel I can recognize a 'broad answer' when I see one.
2) You said you cannot reproduce, but am I to understand that you cannot check your web server's logs to find out what happened? I suppose it is theoretically possible that the request died before it reached your server, however you should be able to trace back to my IP (which should be in your logs from when I created this account, unless you're the one tech company on Earth who does not record this) to see if there is any loss. Additionally, you should be able to check your name servers to see if there have been lookup problems, or perhaps a noticeable decrease in requests (which would typically indicate a DNS resolution issue).
I'm tempted to forward this thread and screenshots of my private messages with your support staff to a popular tech blog in order to illustrate the difficulty I've had getting a few straight answers, and the lack of clarity you seem to have about your own system. I'm sure they would be interested to know that Intel's response to a simple networking question essentially amounts to 'I dunno, and never will, but I hope it won't happen again'. A bit embarrassing, to say the least. Let me see if I can help a little - you may want to escalate this to an engineer with access to address these questions, instead of guessing at the answers.