Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kitz]

@ Darren
I think its pretty obvious from your tracerts youve provided that yours is a routing problem between hop 3 and hop 4 which are both on the BT 21CN network which is causing the increased latency. 

When it happened to me I had similar tracerts which mapped out the old and the new higher latency showing the increase time in the BTw core network.   

My old (BTw based) ISP at the time did actually take it up to BTw on my behalf.   iirc mine increased from 16ms to 28ms and despite a well known (now ex) CS rep taking it further up the heirarchy in BTw... he didnt get any joy as they seem to consider anything less than 30ms acceptible.

The suggestion to leave the router off really was just a vain hope..  because mine stuck for a few weeks several times and me trying a d/c didnt work.   It would always occur after some planned works... and it would go back again after yet another PEW.    Because its on the backhaul then its probably going to need a d/c from between the exchange MSAN and the RAS before it picks up any new routing.

I know once it went 'back to normal' after a planned lift and shift for some other unrelated issue.  Off the top of my head I probably saw about 5 or 6 of these incidents during a 3 year period.  I would get stuck with the longer routing anything from about a week to about 8 weeks.

Sorry I cant recall exact details because its quite a while ago and Im now LLU.   But I can fully sympathise with you because Ive "been there" several times and its so annoying that you know full well its routing between the exchange and the RAS...  you have the proof.. yet BTw still consider it acceptible.

I hate to say this, but I think you may just have to sit tight for a few weeks and hope that a PEW comes up soon.
(Sorry for the bad pun). 

[.Griff.]

Still no joy..

C:\Users\Griff>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.2
  2     6 ms     6 ms     6 ms  213.120.155.227
  3     8 ms     6 ms     7 ms  213.120.155.158
  4    14 ms    13 ms    13 ms  213.120.161.110
  5    13 ms    13 ms    13 ms  217.32.26.82
  6    14 ms    13 ms    15 ms  217.32.26.178
  7    14 ms    13 ms    13 ms  acc1-10GigE-0-0-0-4.bm.21cn-ipp.bt.net [109.159.
248.66]
  8    32 ms    24 ms    23 ms  core1-te0-4-0-4.ealing.ukcore.bt.net [109.159.24
8.4]
  9    20 ms    20 ms    20 ms  peer2-xe0-0-0.telehouse.ukcore.bt.net [109.159.2
54.102]
 10    23 ms    23 ms    22 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12    23 ms    22 ms    21 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 13    21 ms    21 ms    21 ms  132.185.255.134
 14    23 ms    22 ms    22 ms  212.58.241.131

Trace complete.

[Darren]

Griff, I know what you mean, I'm very suspicious of that person.

kitz, That's very helpfull thank you, fingers crossed for some PEW. I sent a ticket to the mods yesterday but have not heard anything back yet, will be interesting to see what they say. I can live with a waiting game now I know what's going on, still a bit annoying though as you say.

The wolverhampton exchange joined the fttc rollout plans in the last batch so maybe that has something to do with it aswell. I'm on the tetenhall exchange which is just on the outskirts of wolverhampton.

Funny how the 80/20 trial ends and the routing goes tits up for a lot of people. There are more and more tracerts being posted showing the same pattern.  Hopefully it will iron out sooner rather than later.

I seem to be haveing a dense moment because i didn't notice a pun, sorry. 

[.Griff.]

He's certainly an oddball and in my experience at least the mods on there are equally unhelpful.

I recently had an issue where a lot of the information concerning my account was missing from the "My BT" section of the website. The mods insisted I hand over my username and password so they could "investigate". Naturally I refused to divulge my account password and the issue was resolved without it yet to this day I still get updates from the mods telling me the problem is still being investigated?!?

Back on subject; I notice you don't live a million miles from me in Walsall so I wonder if the issue we're both experiencing has some geographical aspect to it?

[Darren]

Walsall ay, small world

Check yours now Griff.. it's gone back to normal here over night.

Code: [Select]

C:\Documents and Settings\Administrator>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     6 ms     6 ms     6 ms  213.120.155.227
  3     6 ms     6 ms     6 ms  213.120.155.142
  4     7 ms     6 ms     6 ms  213.120.161.106
  5     7 ms     6 ms     6 ms  217.32.26.74
  6     6 ms     6 ms     6 ms  217.32.26.182
  7     6 ms     6 ms     6 ms  acc2-10GigE-0-0-0-4.bm.21cn-ipp.bt.net [109.159.248.194]
  8    13 ms    11 ms    11 ms  core2-te0-2-5-0.ealing.ukcore.bt.net [109.159.248.130]
  9    11 ms    11 ms    11 ms  peer2-xe10-1-0.telehouse.ukcore.bt.net [109.159.254.116]
 10    11 ms    11 ms    11 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12    11 ms    12 ms    11 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 13    11 ms    11 ms    11 ms  132.185.255.134
 14    12 ms    12 ms    12 ms  212.58.241.131

Trace complete.

[.Griff.]

Looks like the routing changed at 6am -

Code: [Select]

C:\Users\Griff>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.2
  2     6 ms     5 ms     5 ms  213.120.155.227
  3     7 ms     6 ms     6 ms  213.120.155.158
  4     7 ms     6 ms     6 ms  213.120.161.106
  5     7 ms     6 ms     7 ms  217.32.26.74
  6     7 ms     7 ms     6 ms  217.32.26.182
  7     7 ms     7 ms     7 ms  acc2-10GigE-0-3-0-1.bm.21cn-ipp.bt.net [109.159
248.240]
  8    14 ms    11 ms    11 ms  core2-te0-3-0-3.ealing.ukcore.bt.net [109.159.2
8.150]
  9    11 ms    11 ms    11 ms  peer2-xe11-1-0.telehouse.ukcore.bt.net [109.159
254.118]
 10    10 ms    11 ms    11 ms  194.74.65.42
 11     *        *        *     Request timed out.
 12    11 ms    12 ms    11 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 13    12 ms    12 ms    11 ms  132.185.255.134
 14    12 ms    12 ms    11 ms  212.58.241.131

Trace complete.
All back to normal.

[Darren]

 

it stays that way.

[.Griff.]

Same issue has returned this afternoon.

Darren are you experiencing it again by any chance?