Grabit not updating groups
However many people forget that there can be many hops across the internet between your ISP and the servers, and issues at any of these intermediate nodes can also be a cause of performance problems.If intermediate nodes are getting overloaded then you can wide swings in your speed according to the level of congestion at these intermediate nodes.
Two obvious places to check are whether your ISP is having issues, or whether the servers you are trying to connect to are having issues.
To run this command you need to go into a DOS Command Window and then type a command of the form: Tracing route to news.[220.127.116.11] over a maximum of 30 hops: 1 4 ms 5 ms 5 ms air.setup [192.168.1.1] 2 13 ms 19 ms 17 ms .1 3 14 ms 21 ms 15 ms wtfd-t2cam1-a-ge911.network.[18.104.22.168] 4 87 ms 197 ms 198 ms wtfd-t2core-a-ge-wan61.network.[22.214.171.124] 5 29 ms 20 ms 27 ms wtfd-t2core-b-pc1.network.[126.96.36.199] 6 31 ms 13 ms 18 ms pop-bb-b-so-710-0.network.[188.8.131.52] 7 16 ms 18 ms 20 ms pop-bb-a-ae0-0.network.[184.108.40.206] 8 21 ms 23 ms 26 ms amst-ic-1-as0-0.network.[220.127.116.11] 9 28 ms 33 ms 31 ms nikhef.[1.189] 10 26 ms 21 ms 22 ms openpeering-10g.[18.104.22.168] 11 57 ms 56 ms 58 ms [22.214.171.124] Trace complete.
although it will differ (especially for the first steps) depending on who you use as an ISP.
If they do this will tend to be easier to use, but it may not give identical results as there is no guarantee that the message you send and the replies from them are routed exactly the same.
Once a problem node has been identified you should then be able get your ISP or news server support to contact the owners of the problem nodes to get them to fix the issue.