Quote:
Originally Posted by chambohambo
Please explain what info you need.
|
The beginning part of the traceroute. Y'know the bit that says what address you're actually trying to trace to. Which I see you've now edited into your post retrospectively.
---------- Post added at 17:22 ---------- Previous post was at 17:18 ----------
Quote:
Originally Posted by Kymmy
Sounds then possibly like a local routing issue
Try http://www.4proxy.de as a proxy (it's slow as hell and might take a good 30 seconds for it to come in but it will tell you if it's a local routing issue, btw..local could mean anywhere from your router to the UBR) |
It's between the UBR and core according to his tracert. There's a core node somewhere around Preston and it's forever acting funny... Though a problem of this scale I'd have expected would be spotted sooner.
Have you tried accessing mozilla.org through any other devices on your network (e.g. a mobile phone, tablet, etc.) or a VPN? Unlikely to matter but worth knowing.