Packet Loss, web pages not loading

Started by h22a, Apr 02, 2012, 23:09:25

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

h22a

Hi
Been having a lot of problems this evening, pages not loading etc.
Have sent an email to Support, but thought I would post some results on here to get an idea where the Community thinks my problems may be...

Long and short, normally have a very stable broadband connection, very rarely have any issues at all, no hardware or software changes.
Router is a Netgear DG834GT. Router has been powered down etc, BT Speedtester reporting profile of around 4Mb which is about right.
ADSL filter changed, no difference.

Have run quite a few pings on major websites and getting about a 1 in 5 drop rate.

Have now downloaded WinMTR, here's the results. Looks like an IDNET problem to me with the first IDNET router that I hit, what do you guys think?
ping.thinkbroadband.com
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  123 |  123 |    0 |    0 |    0 |    0 |
|             telehouse-gw2-lo1.idnet.net -    9 |   91 |   83 |   34 |   37 |   73 |   34 |
|          telehouse-gw5-e4-400.idnet.net -   13 |   82 |   72 |   34 |   37 |   46 |   38 |
|                 lonap-gw1.thdo.ncuk.net -   13 |   79 |   69 |   34 |   40 |  163 |   38 |
gi0-24-10-star1.core-rs2.thdo.ncuk.net -   16 |   75 |   63 |   35 |   39 |   83 |   39 |
|                  www.thinkbroadband.com -   15 |   76 |   65 |   34 |   37 |   47 |   36 |
|________________________________________________|______|______|______|______|______|______|


www.google.co.uk
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |   89 |   89 |    0 |    0 |    0 |    0 |
|             telehouse-gw2-lo1.idnet.net -   10 |   60 |   54 |   34 |   79 |  736 |   44 |
|          telehouse-gw5-e4-400.idnet.net -   15 |   55 |   47 |   34 |   41 |   55 |   35 |
|           redbus-gw2-g0-1-331.idnet.net -   16 |   52 |   44 |   34 |   41 |   58 |   40 |
|                       google1.lonap.net -   15 |   57 |   49 |   35 |   45 |  100 |   42 |
|                           209.85.255.76 -   21 |   49 |   39 |    0 |   44 |  120 |   38 |
|                           209.85.253.92 -   15 |   57 |   49 |   36 |   43 |   56 |   45 |
|                           72.14.232.134 -   17 |   53 |   44 |   41 |   48 |   73 |   42 |
|                          209.85.250.165 -   33 |   37 |   25 |   40 |   53 |  117 |   41 |
|                   No response from host -  100 |   17 |    0 |    0 |    0 |    0 |    0 |
|                     wi-in-f94.1e100.net -   12 |   61 |   54 |   40 |   47 |   79 |   43 |
|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Also have tried pingtest.net multiple times, here's the results of ones of the tests

Packet Loss: 13%
Ping: 165ms
Jitter: 176ms
Grade: F

Any ideas?
If it is an IDNET issue, then wierd it just seems to be me...

Lance

Can't offer any suggestions I'm afraid, but don't be too worried about getting s high ping from any Idnet server - they all give pings a low priority.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: h22a on Apr 02, 2012, 23:09:25
Any ideas?
If it is an IDNET issue, then wierd it just seems to be me...

It's possibly exchange congestion. Does it vary at different times of day?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech


Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

If problems have been ongoing with the Faraday node for some weeks I'm wondering if its been the cause of my issues too.


Ray

Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

h22a

Rik - never had the problem before, so don't think it is exchange congestion - however I did check around 7.30 am this morning and the problem was still the same.

Thanks for the link to the BT work that was being carried out yesterday evening - I'll power the router down for a while and feedback.

Thanks also for the karmas!  :)

pctech

I'm assuming here fromn notes previously posted that as IDNet's POP is in London the traffic is still backhauled via the Stepney Green and Faraday nodes or was this changed after the two hostlink outages (I've no idea where these two nodes are in relation to Telehouse)

Rik

I think most people go through one or the other, Mitch.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

h22a

This may shed some light on it...

http://usertools.plus.net/exchanges/mso.php?ac=3Lktq%2F6v6Nwa%2Fu8HmiN4TSGts7o37pRAaErBHkyLWmNSZPZwx5nHWJqaHm260U2p

and

http://btbusiness.custhelp.com/app/service_status_consumer/ss_cat/2468,2470

Whilst my telephone line is connected to the Chartham exchange, there are problems reported at the Boughton MUX which is about 5 miles from me.
I assume that maybe traffic is routed from Chartham via Boughton, hence the problems. Does that sound feasible? (sorry I know v little about telephone line infrastructure!) ???

h22a

Problem resolved   :)

Looks like problems were caused by the degradation issues reported at the Boughton exchange.

Thanks for the replies  :)

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.