cancel
Showing results for 
Search instead for 
Did you mean: 

--->> Still horrible ping.

gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

--->> Still horrible ping.

I've posted before, there was interleaving taken offmy line but im still experiencing nasty ping in games.
My speed test results are fine, 4mb down <400kb up. Im really thinking of switching ISP  as i have taken all steps to reduce my ping and increase speed.
I understand that you have something you call "peak time" but its not what im paying for. Every user should get stable latency worth the 20 pounds a month.

13 REPLIES 13
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: Still horrible ping.

When you are getting the slow pings, have you made sure that all other applications that could be downloading or uploading at the same time are closed. This is particularly important with P2P applications which, even if you are not downloading, could be uploading to other users which will then dramatically affect your pings.
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)
gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: Still horrible ping.

yes. Nothing is running.
i always close all programs from tray. It is an ongoing plus net problem.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Still horrible ping.

Without looking for your previous thread, have you tried another modem/router to be sure yours isn't play up? And are the ping times via a wireless link or ethernet?
_CN_
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 385
Registered: ‎11-06-2007

Re: Still horrible ping.

Quote from: gogeta126
I've posted before, there was interleaving taken offmy line but im still experiencing nasty ping in games.

Which games?
Quote from: gogeta126
My speed test results are fine, 4mb down <400kb up. Im really thinking of switching ISP  as i have taken all steps to reduce my ping and increase speed.

To increase speed you'll need to switch to a provider using fiber or using ADSL2+ something that is not available in all exchanges and ADSL2+ is not a guarantee to increasing speeds
gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: Still horrible ping.

all games. The one that i need the most(wont let me connect-time out because of latency) is Soldier front (sfront.ijji.com)  normal ping for me in this game is 158-180  and now im getting (more than 500. 500 is max that shows in the game)
even the adventure game "Shaiya" times out as it cant download key data in time.
_CN_
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 385
Registered: ‎11-06-2007

Re: Still horrible ping.

Can you open SF and play live, when your in then alt+tab until u get the popup box "blah blah you alt tabbed" when this is still open click start, run, cmd then type in netstat and it will show all the SF connections, post them here, thanks
VileReynard
Hero
Posts: 12,616
Thanks: 582
Fixes: 20
Registered: ‎01-09-2007

Re: Still horrible ping.

I have ADSL2+(21CN)  - which operates slightly slower than ADSL MAX (baffled) Smiley
But I get excellent pings.
Even though I never play games.
With Interleaving ON:-
Quote
PING pingtest.co.uk (85.113.82.116) 56(84) bytes of data.
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=1 ttl=57 time=18.1 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=2 ttl=57 time=18.8 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=3 ttl=57 time=17.6 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=4 ttl=57 time=18.0 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=5 ttl=57 time=20.0 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=6 ttl=57 time=17.2 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=7 ttl=57 time=17.9 ms
64 bytes from ws6.webmaint.net (85.113.82.116): icmp_seq=8 ttl=57 time=17.6 ms
^C
--- pingtest.co.uk ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7039ms
rtt min/avg/max/mdev = 17.203/18.185/20.002/0.824 ms

"In The Beginning Was The Word, And The Word Was Aardvark."

gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: Still horrible ping.

Quote from: _CN_
Can you open SF and play live, when your in then alt+tab until u get the popup box "blah blah you alt tabbed" when this is still open click start, run, cmd then type in netstat and it will show all the SF connections, post them here, thanks

i will post the netstat when i actually dont time out and still have 501 ping.
ps i somehow cant actually copy from the cmd box  Huh
gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: Still horrible ping.

just before timeout:
C:\Users\Filip>netstat
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:1110        Filip-PC:61766        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61787        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61793        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61805        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61862        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61867        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61879        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61901        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61942        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61952        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61953        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61963        TIME_WAIT
  TCP    127.0.0.1:60930        Filip-PC:60931        ESTABLISHED
  TCP    127.0.0.1:60931        Filip-PC:60930        ESTABLISHED
  TCP    127.0.0.1:60932        Filip-PC:60933        ESTABLISHED
  TCP    127.0.0.1:60933        Filip-PC:60932        ESTABLISHED
  TCP    127.0.0.1:61769        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61772        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61775        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61784        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61789        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61793        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61802        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61805        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61808        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61810        Filip-PC:61812        ESTABLISHED
  TCP    127.0.0.1:61812        Filip-PC:61810        ESTABLISHED
  TCP    127.0.0.1:61813        Filip-PC:61814        ESTABLISHED
  TCP    127.0.0.1:61814        Filip-PC:61813        ESTABLISHED
  TCP    127.0.0.1:61817        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61828        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61829        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61834        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61837        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61840        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61843        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61846        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61849        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61858        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61861        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61879        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61889        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61890        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61895        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61898        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61904        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61907        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61910        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61919        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61922        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61925        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61928        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61942        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61974        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61975        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61980        Filip-PC:nfsd-status  TIME_WAIT
  TCP    192.168.2.2:49381      cs:25999              ESTABLISHED
  TCP    192.168.2.2:61780      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61801      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61807      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61815      206.82.213.151:10105  TIME_WAIT
  TCP    192.168.2.2:61815      206.82.213.155:10105  TIME_WAIT
  TCP    192.168.2.2:61816      206.82.213.158:10205  ESTABLISHED
  TCP    192.168.2.2:61820      121.156.73.149:11101  TIME_WAIT
  TCP    192.168.2.2:61823      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61854      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61857      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61872      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61875      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61881      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61884      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61888      u-sf-ss01:27230        TIME_WAIT
  TCP    192.168.2.2:61897      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61915      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61918      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61933      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61936      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61939      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61944      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61945      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61948      206.82.212.77:http    TIME_WAIT
  TCP    192.168.2.2:61965      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61967      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61968      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61972      206.82.212.84:http    TIME_WAIT
  TCP    192.168.2.2:61973      u-sf-ss01:27230        ESTABLISHED
after timeout, when the soldierfront.exe and the timeout error are still open:
C:\Users\Filip>netstat
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:1110        Filip-PC:61766        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61787        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61793        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61805        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61862        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61867        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61879        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61901        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61942        FIN_WAIT_2
  TCP    127.0.0.1:1110        Filip-PC:61952        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61953        TIME_WAIT
  TCP    127.0.0.1:1110        Filip-PC:61963        TIME_WAIT
  TCP    127.0.0.1:60930        Filip-PC:60931        ESTABLISHED
  TCP    127.0.0.1:60931        Filip-PC:60930        ESTABLISHED
  TCP    127.0.0.1:60932        Filip-PC:60933        ESTABLISHED
  TCP    127.0.0.1:60933        Filip-PC:60932        ESTABLISHED
  TCP    127.0.0.1:61769        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61772        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61775        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61784        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61789        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61793        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61802        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61805        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61808        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61810        Filip-PC:61812        ESTABLISHED
  TCP    127.0.0.1:61812        Filip-PC:61810        ESTABLISHED
  TCP    127.0.0.1:61813        Filip-PC:61814        ESTABLISHED
  TCP    127.0.0.1:61814        Filip-PC:61813        ESTABLISHED
  TCP    127.0.0.1:61817        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61828        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61829        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61834        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61837        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61840        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61843        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61846        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61849        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61858        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61861        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61879        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61889        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61890        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61895        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61898        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61904        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61907        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61910        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61919        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61922        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61925        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61928        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61942        Filip-PC:nfsd-status  CLOSE_WAIT
  TCP    127.0.0.1:61974        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61975        Filip-PC:nfsd-status  TIME_WAIT
  TCP    127.0.0.1:61980        Filip-PC:nfsd-status  TIME_WAIT
  TCP    192.168.2.2:49381      cs:25999              ESTABLISHED
  TCP    192.168.2.2:61780      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61801      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61807      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61815      206.82.213.151:10105  TIME_WAIT
  TCP    192.168.2.2:61815      206.82.213.155:10105  TIME_WAIT
  TCP    192.168.2.2:61816      206.82.213.158:10205  ESTABLISHED
  TCP    192.168.2.2:61820      121.156.73.149:11101  TIME_WAIT
  TCP    192.168.2.2:61823      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61854      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61857      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61872      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61875      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61881      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61884      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61888      u-sf-ss01:27230        TIME_WAIT
  TCP    192.168.2.2:61897      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61915      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61918      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61933      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61936      cdn:http              TIME_WAIT
  TCP    192.168.2.2:61939      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61944      wbers:http            TIME_WAIT
  TCP    192.168.2.2:61945      cdn:http              CLOSE_WAIT
  TCP    192.168.2.2:61948      206.82.212.77:http    TIME_WAIT
  TCP    192.168.2.2:61965      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61967      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61968      imagesijji:http        TIME_WAIT
  TCP    192.168.2.2:61972      206.82.212.84:http    TIME_WAIT
  TCP    192.168.2.2:61973      u-sf-ss01:27230        ESTABLISHED
gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: --->> Still horrible ping.

this is  sick. i miraculously managed to connect but im lagging SO HARD that everyone has 10 ping, there are shots and grenades all around but everyone is not moving from base. ITS REALLY [Censored] ME OFF



Moderators note by chemical brother: Attempts to bypass swear filter removed. Please read the Forum Rules
@ moderators note
i only put a bunch of stars **************
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: --->> Still horrible ping.

Have you ping able to compare your pings with another player in the UK?
How do you connect to your router, wired or wireless?
My connection goes via the BT RIN network, not Plusnet's and this is the trace I get to sfront.ijji.com:
C:\Documents and Settings\John>tracert sfront.ijji.com
Tracing route to sfront.ijji.com [206.82.212.77]
over a maximum of 30 hops:
  1     3 ms    <1 ms    <1 ms  dg834 [192.168.0.1]
  2    12 ms    10 ms    10 ms  217.47.89.122
  3    11 ms    10 ms    10 ms  217.47.88.161
  4    10 ms    10 ms    10 ms  217.47.66.170
  5    10 ms    10 ms    10 ms  217.41.217.1
  6    11 ms    11 ms    10 ms  217.41.171.146
  7    11 ms    11 ms    11 ms  217.41.171.50
  8    11 ms    10 ms    10 ms  217.47.88.241
  9    10 ms    10 ms    10 ms  core1-pos5-2.kingston.ukcore.bt.net [62.6.40.66]
10    11 ms    11 ms    11 ms  core1-pos0-15-0-8.ealing.ukcore.bt.net [62.6.201.73]
11    11 ms    10 ms    11 ms  transit1-gig8-0-0.ealing.ukcore.bt.net [62.6.200.110]
12    11 ms    10 ms    11 ms  t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.168.17]
13    12 ms    11 ms    11 ms  t2c2-p3-2.uk-lon1.eu.bt.net [166.49.164.138]
14    12 ms    11 ms    11 ms  t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
15    12 ms    11 ms    12 ms  195.66.224.130
16    12 ms    12 ms    12 ms  p5-0-0d0.rar1.london-en.uk.xo.net [71.5.174.133]
17    80 ms    79 ms    79 ms  p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
18   113 ms   113 ms   112 ms  p6-0-0.RAR2.Chicago-IL.us.xo.net [65.106.0.29]
19   136 ms   136 ms   153 ms  p1-0-0.rar1.dallas-tx.us.xo.net [65.106.0.34]
20   169 ms   169 ms   168 ms  p6-0-0.rar2.la-ca.us.xo.net [65.106.0.14]
21   168 ms   168 ms   168 ms  te-11-2-0.rar3.la-ca.us.xo.net [207.88.14.45]
22   167 ms   167 ms   167 ms  207.88.14.46.ptr.us.xo.net [207.88.14.46]
23   162 ms   230 ms   162 ms  ip65-47-228-18.z228-47-65.customer.algx.net [65.47.228.18]
24   169 ms   160 ms   160 ms  p2c3.irv.intelenet.net [206.82.223.69]
25   160 ms   160 ms   160 ms  p6a5.irv.intelenet.net [206.82.223.86]
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)
gogeta126
Grafter
Posts: 33
Registered: ‎04-02-2009

Re: --->> Still horrible ping.

well never mind anymore. Raised a ticket to close my contract. Moving to 20mb cable broadband.
jelv
Seasoned Hero
Posts: 26,785
Thanks: 971
Fixes: 10
Registered: ‎10-04-2007

Re: --->> Still horrible ping.

If your problem is that (a) you are expecting low pings on a stateside server and (b) you are connecting wirelessly you will see very little improvement moving to cable.
jelv (a.k.a Spoon Whittler)
   Why I have left Plusnet (warning: long post!)   
Broadband: Andrews & Arnold Home::1 (FTTC 80/20)
Line rental: Pulse 8 Home Line Rental (£14.40/month)
Mobile: iD mobile (£4/month)