Any Problems Today?

psp83 · Sep 28, 2009, 11:05:27

Is there any reported problems today?

I've just been disconnected (reconnected at same sync) and now got very high pings and slow speed.

Rik · Sep 28, 2009, 11:06:29

Nothing I've heard of, Paul, but if you had a resync it would suggest a burst of noise or BT work.

psp83 · Sep 28, 2009, 11:35:13

Connection fully down now

support say nothing wrong with the line / connection.

Rik · Sep 28, 2009, 11:36:05

Have you checked at the test socket, Paul?

psp83 · Sep 28, 2009, 11:59:24

Not yet. Can't get to it at the mo. To much junk infront of it at mo.

I've done a router reset and it still it won't connect. Won't even connect to bt_test@startup_domain like support told me to try.

Rik · Sep 28, 2009, 12:18:19

It's possibly a dead router, of course. Do you have one you could swap?

psp83 · Sep 28, 2009, 12:24:00

Picking a spare one up on my way back.

I've left the router of for now and hope that fixes any problems when I get back.

Rik · Sep 28, 2009, 12:27:05

Let us know how it goes, will you?

psp83 · Sep 28, 2009, 13:28:24

Just got back in, turned the router on and it connected.

psp83 · Sep 28, 2009, 13:35:53

still getting very low speeds and high ping though

Sebby · Sep 28, 2009, 13:42:28

What do the stats look like? Also, please run a BT speed test as the profile may have taken a hit.

psp83 · Sep 28, 2009, 13:47:48

Speed has gone up abit now. Still not right though.

Download speedachieved during the test was - 2842 Kbps
For your connection, the acceptable range of speeds is 600-7150 Kbps.
Additional Information:
Your DSL Connection Rate :5504 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
IP Profile for your line is - 4000 Kbps

I was getting around 3900 Kbps before my troubles.

ADSL Link    Downstream    Upstream
Connection Speed    5504 kbps    448 kbps
Line Attenuation    39 db    12.5 db
Noise Margin    11 db    26 db

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 123 ms 113 ms 131 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 166 ms 162 ms 145 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 133 ms 134 ms 147 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 145 ms 139 ms 152 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 131 ms 135 ms 144 ms www.idnet.net [212.69.36.10]

Trace complete.

Tracing route to psp83.co.uk [77.92.89.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 129 ms 117 ms 120 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 156 ms 152 ms 470 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 141 ms 149 ms 155 ms lonap1.enta.net [193.203.5.134]
5 149 ms 133 ms 129 ms te5-2.gs1.core.enta.net [87.127.236.42]
6 168 ms 155 ms 138 ms te1-1.interxion.core.enta.net [87.127.236.86]
7 164 ms 159 ms 147 ms 78-33-30-154.static.enta.net [78.33.30.154]
8 149 ms 135 ms 140 ms atlas.safeukdns.net [77.92.89.1]

Trace complete.

psp83 · Sep 28, 2009, 14:02:16

Everything seems to be back to normal now.

Speed is backup to around 3900 Kbps and pings back low.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 14 ms 14 ms 15 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 445 ms 109 ms 162 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 14 ms 14 ms 15 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 15 ms 14 ms 16 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 14 ms 15 ms www.idnet.net [212.69.36.10]

Trace complete.

Dunno what the hell caused it though.

Ardua · Sep 28, 2009, 14:42:05

My speed issues continue as well. Speed variations have increased markedly over the past month or so. My BT Speedtest donstream is down to 1597 Kbps compared with 6300 Kpbs when I checked on Friday afternoon. My pings are as follows:

G idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=114.505 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=143.631 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=160.147 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=131.963 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=127.536 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=139.244 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=149.138 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=183.294 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=131.235 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=105.848 ms

--- idnet.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 105.848/138.654/183.294/21.148 ms

I am reluctant to keep on re-booting my router. I sense that IdNet is having some capacity issues. Am I right?

Regards

psp83 · Sep 28, 2009, 14:52:33

Spoke to soon, High pings again.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 152 ms 152 ms 143 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 162 ms 165 ms 154 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 158 ms 147 ms 130 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 148 ms 141 ms 141 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 162 ms 168 ms 164 ms www.idnet.net [212.69.36.10]

Trace complete.

psp83 · Sep 28, 2009, 14:57:02

Speed has dropped again aswell

Ardua · Sep 28, 2009, 15:01:15

I have just spoken to Simon at IdNet and he has admitted that they have had problems and they are trying to rebalance the load. At his suggestion (again), I have re-booted my router. This has resulted in a further drop in my downstream speed to 1107 Kbps.

Ping has started...

PING idnet.com (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=163.423 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=181.034 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=159.294 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=151.614 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=172.027 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=118.353 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=144.371 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=163.431 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=183.523 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=153.754 ms

--- idnet.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 118.353/159.082/183.523/18.011 ms

I confess that I am unsure what I should do next.

psp83 · Sep 28, 2009, 15:03:35

I rebooted my router, speed regained, pings low, 2 mins later. Pings are now getting higher and speeds getting slower

psp83 · Sep 28, 2009, 15:06:36

All over the place today, was gunna make a skype call but think i will use the phone insted!

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 58 ms 56 ms 70 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 24 ms 28 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 69 ms 87 ms 302 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 68 ms 58 ms 68 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 111 ms 115 ms 103 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 69 ms 73 ms 80 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 90 ms 95 ms 84 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 205 ms 135 ms 147 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 114 ms 102 ms 100 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 105 ms 100 ms 100 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 19 ms 14 ms 19 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 28 ms 29 ms 30 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 36 ms 36 ms 40 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 57 ms 67 ms 53 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 41 ms 43 ms 40 ms www.idnet.net [212.69.36.10]

Trace complete.

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 16 ms 16 ms 16 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 22 ms 20 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

4 45 ms 28 ms 26 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 22 ms 19 ms 20 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 43 ms 38 ms 28 ms www.idnet.net [212.69.36.10]

Trace complete.

Looks like no arse kicking on xbox tonight aswell

Wags · Sep 28, 2009, 15:25:28

I had a power cut at home this morning

. Router has synced at around usual speed of 6274, but pings have shot up to 150ms. They have been behaving themeselves at 14-15ms for the past few days (after weeks of volatility). Looks like the power-cut imposed reboot has connected me to one of the congested centrals again

I will have a look again this evening, but it seems likely I will have to go through the rebooting saga again until I find that uncongested central

psp83 · Sep 28, 2009, 15:46:38

I'm just about to give up on pings,

Mines going from 14ms to over 2000 ms.

Rik · Sep 28, 2009, 15:52:18

I understand there was a capacity issue this morning, but that it's now clear. If people are still having speed or ping issues, and a re-boot doesn't cure it, please contact support so that they can look into it for you.

Ardua · Sep 28, 2009, 16:13:09

Back up to 4000 Kbps now without any further re-boot. I just wish that IdNet would put out a proper SB on the main website when have problems. It would save them a lot of hassle.

Dopamine · Sep 28, 2009, 16:38:00

High pings here:

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=102ms TTL=59
Reply from 212.69.36.10: bytes=32 time=133ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 102ms, Maximum = 144ms, Average = 122ms

Dopamine · Sep 28, 2009, 16:43:33

Just rebooted router, which has made pings slightly worse:

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=151ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 151ms, Average = 144ms