Just migrated from Nildram

VaderDSL

VaderDSL

VaderDSL

Soldato
Joined
18 Oct 2002
Posts
16,451
Location
Manchester
Well :) it was my mistake ... I had used Nildram for a long time before Pipex bought them out with no problems, both over 512kb and the 2mb offerings.

Now the other month I made the decision of going with Nildram, and paid for it ... as a long time user of Nildram before the Pipex buyout the service was phenomenal. However since re-ordering with them, they seem to have degraded somewhat :(

But, alls looking well, got our MAC today, ordered with IDNet and hopefully should be back up and running by 3rd August :)

I really like Nildram, their support is very good, however the constant problem with pings is a huge problem for my housemate ... plus this problem has, by all accounts, been happening for a long time now.

Anyway, apologies for such a useless post :)
 
VaderDSL said:
Well, it was my mistake ... I had used Nildram for a long time before Pipex bought them out with no problems, both over 512kb and the 2mb offerings.

Now the other month I made the decision of going with Nildram, and paid for it ... as a long time user of Nildram before the Pipex buyout the service was phenomenal. However since re-ordering with them, they seem to have degraded somewhat :(

But, alls looking well, got our MAC today, ordered with IDNet and hopefully should be back up and running by 3rd August :)

I really like Nildram, their support is very good, however the constant problem with pings is a huge problem for my housemate ... plus this problem has, by all accounts, been happening for a long time now.

Anyway, apologies for such a useless post :)
Click to expand...

Getting rubbish pings here now aswell, might be a move to IDNet also I feel :o

BeatMaster :D
 
Hey guys,

Been with Nilly for just over a month now, things started okay; activation, training period, set sync of 2.4 MB (Until then only had 1 MB :) ) and I was happy...

Then I started to notice erratic ping changes in my games? I sometimes go from being in the low 20's to 200+ for no obvious reason :eek:

My torrents suddenly got considerably slower - I wasn't hammering them; I was keeping everything to well within my limits?

And now, I seem to re-sync about ten times a day, just like in the training period, with my connection speed ranging from 0.8 MB to 1.2 MB. Atm it seems stuck on 0.9 MB :(

I've had a couple of emails back from them, they took over a week, but that's faster that phoning them ;)

They just told me to use master socket, change filters and even consider changing router (Netgear DG834G); I've done all they suggested bar changing the router, which I'm almost certain is fine.

Failing this they've told me to give them a call and they'll investigate it further.

I just thought I’d put my five eggs in!

SW.
 
Haven't had any problems with pings on Nildram for quite a while now, not since a few years ago when their central pipe was running at capacity. Currently getting 11-13ms to www.bbc.co.uk, and I believe some londoners get even lower than that.

I do however know that quite a lot of WoW players have ping issues due to Telia routing which Nildram uses.

FWIW I think that now so many people (not just Nildram customers) have faster (>512kbit) ADSL connections, exchange congestion is playing a much bigger part than it used to.
 
HangTime, would you be able to do a huge favour???

If possuible, could you ping or tracert to :

212.187.209.103

please? :)
 
Dave2150 said:
Im on Nildram, 172ms average to that IP Address :eek:
Click to expand...

Aye, been like that for a while now. It's a house mates CS:S server ... anything routed over Telia is suffering from extremely high latencies atm
 
VaderDSL said:
HangTime, would you be able to do a huge favour???

If possuible, could you ping or tracert to :

212.187.209.103

please? :)
Click to expand...

I was getting ready to explain how it wasn't Nildram/PIPEX problem and that the latency was with your first-hop but that actually is a routing problem with Nildram/PIPEX. Have you logged a support ticket about it? I'm sure they are already aware but the more people that moan about it the more likely it is to get resolved.
 
Doesn't look like a Nildram problem to me...

Hop #5 is the problem.

Code: 
Tracing route to 212.187.209.103 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  WAN [10.0.0.2]
  2    15 ms    14 ms    19 ms  lo1-lon3-adsl20.nildram.net [195.112.5.29]
  3    13 ms    13 ms    13 ms  ge-1-0-1.cr2.gs1.bb.pipex.net [84.12.224.29]
  4    23 ms    16 ms    17 ms  ldn-b3-geth5-1.telia.net [213.248.100.29]
[u]  5   152 ms   151 ms   159 ms  ldn-bb1-pos6-1-0.telia.net [213.248.65.237][/u]
  6   154 ms   157 ms   154 ms  ldn-b1-pos13-0.telia.net [213.248.64.98]
  7   164 ms   176 ms   169 ms  ge-6-22.car2.London1.Level3.net [4.68.111.181]
  8   171 ms   170 ms   168 ms  ge-10-2.ipcolo2.London1.Level3.net [4.68.116.138]
  9   166 ms   171 ms   168 ms  212.187.209.103

Trace complete.
 
VaderDSL said:
HangTime, would you be able to do a huge favour???

If possuible, could you ping or tracert to :

212.187.209.103

please? :)
Click to expand...

Code: 
G:\>tracert 212.187.209.103

Tracing route to 212.187.209.103 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  
  2    13 ms    12 ms    13 ms  lo1-lon3-adsl21.nildram.net [195.112.5.30]
  3    13 ms    13 ms    12 ms  ge-0-1-1.cr2.gs1.bb.pipex.net [84.12.224.25]
  4    12 ms    13 ms    13 ms  ldn-b3-geth5-1.telia.net [213.248.100.29]
  5   152 ms   152 ms   148 ms  ldn-bb2-pos6-1-0.telia.net [213.248.64.49]
  6   152 ms   151 ms   152 ms  ldn-b1-link.telia.net [80.91.250.14]
  7   148 ms   150 ms   151 ms  ge-6-22.car2.London1.Level3.net [4.68.111.181]
  8   131 ms   135 ms   140 ms  ge-10-1.ipcolo2.London1.Level3.net [4.68.116.74]

  9   153 ms   148 ms   148 ms  212.187.209.103

As mentioned it's a Telia problem, unfortunately this makes it harder for Nildram to resolve. Of course some people will get fed up waiting and migrate to an isp which uses different peering, even though it isn't the ISPs fault per se, as at the end of the day, you have to look after number 1, whatever the reason for the fault may be.
 
NathanE said:
Doesn't look like a Nildram problem to me...

Hop #5 is the problem.

Code: 
Tracing route to 212.187.209.103 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  WAN [10.0.0.2]
  2    15 ms    14 ms    19 ms  lo1-lon3-adsl20.nildram.net [195.112.5.29]
  3    13 ms    13 ms    13 ms  ge-1-0-1.cr2.gs1.bb.pipex.net [84.12.224.29]
  4    23 ms    16 ms    17 ms  ldn-b3-geth5-1.telia.net [213.248.100.29]
[u]  5   152 ms   151 ms   159 ms  ldn-bb1-pos6-1-0.telia.net [213.248.65.237][/u]
  6   154 ms   157 ms   154 ms  ldn-b1-pos13-0.telia.net [213.248.64.98]
  7   164 ms   176 ms   169 ms  ge-6-22.car2.London1.Level3.net [4.68.111.181]
  8   171 ms   170 ms   168 ms  ge-10-2.ipcolo2.London1.Level3.net [4.68.116.138]
  9   166 ms   171 ms   168 ms  212.187.209.103

Trace complete.
Click to expand...

This is most definitely a problem Nildram/Pipex need to sort. Telia are a transit provider for them so it's up to them to put pressure to resolve. That kind of latency for a tier1 in London is shocking.
 
Seems to be fixed now :)

Tracing route to jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

1 31 ms 32 ms 32 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
2 32 ms 30 ms 31 ms ge-1-1-1.cr2.gs1.bb.pipex.net [84.12.224.33]
3 31 ms 31 ms 30 ms lon1-9.nildram.net [84.12.224.14]
4 31 ms 30 ms 30 ms jolt-gw.nildram.net [195.149.20.214]
5 31 ms 33 ms 31 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.

BeatMaster :D
 
just for your info through Multiplay DSL i get:

Code: 
Tracing route to 212.187.209.103 over a maximum of 30 hops

1     1 ms    <1 ms    <1 ms  ***.**.**.**
2    26 ms    26 ms    30 ms  gi0-2-0-ar0.sovlon.as35028.net [85.236.110.1]
3    30 ms    29 ms    26 ms  po0-1-651-cr0.sovlon.as35028.net [85.236.110.9]
4    25 ms    26 ms    25 ms  po0-1-650-cr1.sovlon.as35028.net [85.236.110.6]
5    26 ms    27 ms    25 ms  ge-1-7-810.r01.londen03.uk.bb.gin.ntt.net [83.231.146.173]
6    26 ms    27 ms    30 ms  xe-0.level3.londen03.uk.bb.gin.ntt.net [129.250.8.138]
7    26 ms    26 ms    26 ms  ge-10-2.ipcolo2.London1.Level3.net [4.68.116.138]
8    29 ms    25 ms    26 ms  212.187.209.103

Trace complete.

I live in Aberdeen which does seem to add a few ms when gaming etc..
 
Pinging 212.187.209.103 with 32 bytes of data:

Reply from 212.187.209.103: bytes=32 time=29ms TTL=54
Reply from 212.187.209.103: bytes=32 time=28ms TTL=54
Reply from 212.187.209.103: bytes=32 time=29ms TTL=54
Reply from 212.187.209.103: bytes=32 time=29ms TTL=54

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


C:\Documents and Settings\andy>tracert 212.187.209.103

Tracing route to 212.187.209.103 over a maximum of 30 hops

1 29 ms 29 ms 47 ms lo1-lon3-adsl21.nildram.net [195.112.5.30]
2 28 ms 29 ms 29 ms ge-1-1-1.cr2.gs1.bb.pipex.net [84.12.224.33]
3 29 ms 30 ms 29 ms ldn-b3-geth5-1.telia.net [213.248.100.29]
4 29 ms 30 ms 31 ms ldn-bb2-pos6-1-0.telia.net [213.248.64.49]
5 29 ms 29 ms 29 ms ldn-b1-pos9-2.telia.net [213.248.64.94]
6 29 ms 29 ms 30 ms ge-6-22.car2.London1.Level3.net [4.68.111.181]
7 28 ms 29 ms 29 ms ge-10-1.ipcolo2.London1.Level3.net [4.68.116.74]

8 29 ms 30 ms 30 ms 212.187.209.103

Trace complete.

Can't say i really have any problems with NIldram, i get 3 meg day and night and pings i never have any probs with.
 
Last edited:
Problems once more ....

Tracing route to 212.187.209.13 [212.187.209.13] with 32 bytes:


1 0ms 192.168.1.1 *
2 14ms 195.112.5.30 lo1-lon3-adsl21.nildram.net
3 15ms 84.12.224.33 ge-1-1-1.cr2.gs1.bb.pipex.net
4 14ms 213.248.100.29 ldn-b3-geth5-1.telia.net
5 14ms 213.248.65.237 ldn-bb1-pos6-1-0.telia.net
6 15ms 213.248.74.6 ldn-b1-pos3-0.telia.net
7 15ms 4.68.111.181 ge-1-1-1.cr2.gs1.bb.pipex.net
8 83ms 4.68.116.138 ge-1-1-1.cr2.gs1.bb.pipex.net
9 15ms 212.187.209.13 212.187.209.13

Trace complete
Tracing route to 212.187.209.13 [212.187.209.13] with 32 bytes:


1 0ms 192.168.1.1 *
2 17ms 195.112.5.30 lo1-lon3-adsl21.nildram.net
3 14ms 84.12.224.33 ge-1-1-1.cr2.gs1.bb.pipex.net
4 15ms 213.248.100.29 ldn-b3-geth5-1.telia.net
5 14ms 213.248.65.237 ldn-bb1-pos6-1-0.telia.net
6 15ms 213.248.74.6 ldn-b1-pos3-0.telia.net
7 115ms 4.68.111.181 ge-1-1-1.cr2.gs1.bb.pipex.net
8 83ms 4.68.116.138 ge-1-1-1.cr2.gs1.bb.pipex.net
9 14ms 212.187.209.13 212.187.209.13

Trace complete
Tracing route to 212.187.209.13 [212.187.209.13] with 32 bytes:


1 0ms 192.168.1.1 *
2 16ms 195.112.5.30 lo1-lon3-adsl21.nildram.net
3 14ms 84.12.224.33 ge-1-1-1.cr2.gs1.bb.pipex.net
4 14ms 213.248.100.29 ldn-b3-geth5-1.telia.net
5 14ms 213.248.65.237 ldn-bb1-pos6-1-0.telia.net
6 14ms 213.248.74.6 ldn-b1-pos3-0.telia.net
7 214ms 4.68.111.181 ge-1-1-1.cr2.gs1.bb.pipex.net
8 83ms 4.68.116.138 ge-1-1-1.cr2.gs1.bb.pipex.net
9 15ms 212.187.209.13 212.187.209.13

Trace complete

Winder when/if they'll fix it ... like I've said .. been going on for to long now
 
You must log in or register to reply here.
Back
Top Bottom