Just migrated from Nildram

VaderDSL

VaderDSL

VaderDSL

Soldato
Joined
18 Oct 2002
Posts
16,531
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 :)
 
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
 
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
 
HighlandeR said:
lol yeah dunno why theres talk of this IDnet on here.... 30gig cap makes life very difficult for some ;)
Click to expand...

:) I've never downloaded much really ... 30Gb will suit me fine, only ever download patches ... open source stuff, maybe stuff over Worldwind etc. :)
 
Just switchd to IDNet ... only problem was the extraordinary long downtime ... Internet was down for 1 minute :( because I typed the login name wrong :) very impressed, all went swimmingly
 
You must log in or register to reply here.
Back
Top Bottom