Anyone else having severe speed issues this morning? Getting barely 1.5Mbps down out of my 100/20 fibre connection this morning. Upload speed is close to normal. Have power-cycled ONT / router and checked from several devices including wired ones.
|
|
|
Normal here, Spark 100/20, Aidanfield
No change in number of authenticated fibre users, no change in traffic patterns on links from the BNGs to the core or on the LFC handovers. So there's no widespread issue. You should log a job with the helpdesk if you're still experiencing issues.
(and both my fibre lines are normal - connected to ch-bng03)
Cheers -N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
Im interested in which area of ChCh you are situated?
A lot of water in some parts of the city....
Goosey:
Im interested in which area of ChCh you are situated?
A lot of water in some parts of the city....
I'm in a subdivision in Kaiapoi fed with Chorus fibre. Been on the phone to spark most of the morning. Tried swapping out modems, cable between ONT and modem, connected three devices wired direct to modem to rule out local cabling and not managing more than 1.6Mbps down, however getting about 13Mbps up. The Spark tech asked if he could remote into my machine, gave me a URL to download a remote access app and it was downloading at 4KB/s so gave up on that. In the end he logged a fault with Chorus. Little bit dubious about it being referred to Chorus... could the layer 2 really cause this kind of problem on a fibre connection?
steve98:
Goosey:
Im interested in which area of ChCh you are situated?
A lot of water in some parts of the city....
I'm in a subdivision in Kaiapoi fed with Chorus fibre. Been on the phone to spark most of the morning. Tried swapping out modems, cable between ONT and modem, connected three devices wired direct to modem to rule out local cabling and not managing more than 1.6Mbps down, however getting about 13Mbps up. The Spark tech asked if he could remote into my machine, gave me a URL to download a remote access app and it was downloading at 4KB/s so gave up on that. In the end he logged a fault with Chorus. Little bit dubious about it being referred to Chorus... could the layer 2 really cause this kind of problem on a fibre connection?
Yes. Pm me your username and phone number as well as your current IP address please. I can't change anything but there's a couple of things I can check looking for obvious issues.
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
Talkiet:
steve98:
Goosey:
Im interested in which area of ChCh you are situated?
A lot of water in some parts of the city....
I'm in a subdivision in Kaiapoi fed with Chorus fibre. Been on the phone to spark most of the morning. Tried swapping out modems, cable between ONT and modem, connected three devices wired direct to modem to rule out local cabling and not managing more than 1.6Mbps down, however getting about 13Mbps up. The Spark tech asked if he could remote into my machine, gave me a URL to download a remote access app and it was downloading at 4KB/s so gave up on that. In the end he logged a fault with Chorus. Little bit dubious about it being referred to Chorus... could the layer 2 really cause this kind of problem on a fibre connection?
Yes. Pm me your username and phone number as well as your current IP address please. I can't change anything but there's a couple of things I can check looking for obvious issues.
Cheers - N
Cheers - have flicked you a PM
Certainly looks like something has gone wrong at about 2am this morning. Since then you've been having a significant number of reauthentications. Because we can't see all the Chorus logs I can't be clear about what's causing it but I can see that your line has had a steady rise in re-auths since about April. However you have until today had a reliable one per day which is really strange. There's no-one else on the same DSLAM card having a similar number of reauths but there are a couple of other users in the same street with an elevated number of reauths.
This all points to something most likely at the LFC level and I can see there has been an escalation raised to Chorus. Sorry there's not much more I can do. Let the Chorus escalation play out - they'll see the same (and better) info I have when they look at it.
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
Talkiet:
Certainly looks like something has gone wrong at about 2am this morning. Since then you've been having a significant number of reauthentications. Because we can't see all the Chorus logs I can't be clear about what's causing it but I can see that your line has had a steady rise in re-auths since about April. However you have until today had a reliable one per day which is really strange. There's no-one else on the same DSLAM card having a similar number of reauths but there are a couple of other users in the same street with an elevated number of reauths.
This all points to something most likely at the LFC level and I can see there has been an escalation raised to Chorus. Sorry there's not much more I can do. Let the Chorus escalation play out - they'll see the same (and better) info I have when they look at it.
Cheers - N
OK great, thanks for having a look at this. Hopefully Chorus will find the fault and fix it.
FYI I have heard of another Fibre user in Kaiapoi experiencing very very similar symptoms to yourself... They are on 2D however. So yeah, pointing more towards the LFC. I'm sure they'll deal with it as soon as possible but consider the amount of cleanup they will have to do after the showers we've just had!
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
Heh, Its Kaiapoi
2Degrees same deal noted since 930. Most the grannies round here wont notice TCP timeouts and sub 1mbit connection. But Netflix sure does!

Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Also like how you can see an internal task raised, yet nada on the notification page(s) for a similar status, leading to more calls to a HD with likely less staff being a weekend. FAAAILLLL
Oblivian:
Heh, Its Kaiapoi
2Degrees same deal noted since 930. Most the grannies round here wont notice TCP timeouts and sub 1mbit connection. But Netflix sure does!
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Sovereign Palms?
Oblivian:
Also like how you can see an internal task raised, yet nada on the notification page(s) for a similar status, leading to more calls to a HD with likely less staff being a weekend. FAAAILLLL
happens all the time, even if a whole cabinet is out they most often wont put it on their site. pretty crap really.
steve98:
Oblivian:
Heh, Its Kaiapoi
2Degrees same deal noted since 930. Most the grannies round here wont notice TCP timeouts and sub 1mbit connection. But Netflix sure does!
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Reply from 8.8.8.8: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=37ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Reply from 8.8.8.8: bytes=32 time=36ms TTL=60
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=38ms TTL=60
Sovereign Palms?
Stalker
Jase2985:
Oblivian:
Also like how you can see an internal task raised, yet nada on the notification page(s) for a similar status, leading to more calls to a HD with likely less staff being a weekend. FAAAILLLL
happens all the time, even if a whole cabinet is out they most often wont put it on their site. pretty crap really.
I laughed when I saw their cell cabinet on the corner of new brighton and Locksley half submerged with no mention. Preeeettyyy sure it would stop working.
|
|
|