0 Members and 3 Guests are viewing this topic.
Quote from: gnif on December 06, 2022, 02:48:58 pmQuote from: PA0PBZ on December 06, 2022, 02:40:23 pmQuote from: gnif on December 06, 2022, 02:33:25 pmSorry mate, not a server issue our side, must be a connectivity issue on your end.Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.Ping times are not a good indicator for packet loss, or fragmentation. If you want something somewhat more reliable, use `mtr`I've tried mtr on linux, and seem to be getting HUGE packet losses. The output, is as follows: My traceroute [v0.94]mx (192.168.0.29) -> www.eevblog.com 2022-12-06T15:14:24+0000Keys: Help Display mode Restart statistics Order of fields quit Packets PingsHost Loss% Snt Last Avg Best Wrst StDev1. _gateway 0.0% 85 3.8 4.0 3.7 6.5 0.52. host-62-24-254-204.as13285.net 0.0% 85 32.5 32.0 31.3 33.7 0.53. ae53-ner002.bre.as13285.net 0.0% 85 32.4 32.4 31.5 39.5 1.14. ae53-scr101.loh.as13285.net 0.0% 85 32.7 34.8 32.0 69.3 6.25. ae61-scr101.thw.as13285.net 0.0% 84 32.8 34.5 32.5 49.3 3.16. e0-30.core3.lon1.he.net 0.0% 84 33.6 33.9 33.0 35.6 0.57. 100ge0-75.core3.lon2.he.net 88.0% 84 72.4 59.7 33.7 146.6 37.48. port-channel2.core2.nyc5.he.net 75.0% 84 102.1 101.1 100.0 104.5 1.19. e0-79.core3.nyc4.he.net 89.2% 84 102.9 101.2 100.2 102.9 1.110. port-channel6.core2.mci3.he.net 85.7% 84 132.6 130.8 126.6 154.1 7.811. port-channel2.core3.mci3.he.net 76.2% 84 128.1 128.4 126.6 142.5 3.812. port-channel8.core2.den1.he.net 88.0% 84 137.0 136.9 136.2 137.8 0.513. port-channel10.core2.slc1.he.net 50.6% 84 147.4 148.5 147.4 153.6 1.214. webnx-inc.100gigabitethernet0-25.switch2.slc1.he.net 52.4% 84 185.4 186.4 185.2 188.9 0.815. 104-250-156-167.static.gorillaservers.com 42.2% 84 185.9 186.3 185.2 190.4 0.816. 192-154-109-3.static.gorillaservers.com 38.1% 84 185.5 185.6 184.5 187.1 0.6
Quote from: PA0PBZ on December 06, 2022, 02:40:23 pmQuote from: gnif on December 06, 2022, 02:33:25 pmSorry mate, not a server issue our side, must be a connectivity issue on your end.Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.Ping times are not a good indicator for packet loss, or fragmentation. If you want something somewhat more reliable, use `mtr`
Quote from: gnif on December 06, 2022, 02:33:25 pmSorry mate, not a server issue our side, must be a connectivity issue on your end.Ping times to the server are a stable 130ms from several EU countries (FR, NL, UK) and 160ms from Sidney. It doesn't look like a connectivity issue. However, if you don't seen anything strange on the server there's not much we (you) can do.
Sorry mate, not a server issue our side, must be a connectivity issue on your end.
Same here. 2022-12-22 19:44-19:45 UTC
This was due to some server maintenance that was planned and Dave announced on Twitter. Work has been completed now and services should return to normal.
404 Not Foundnginx
Quote from: xrunner on February 02, 2023, 02:37:19 am404 Not FoundnginxI have seen the same error when the forward slash / is omitted from the URL.The link below takes you to the first page of this thread:https://www.eevblog.com/forum/chat/website-error-reports/The link below will give a '404 not found' error:https://www.eevblog.com/forum/chat/website-error-reports