|
|
Hi All,
Thinking of going with this package, can anyone recommend this ISP?
Looking for a 12month Contract, No In-Contract Price Rises. Also looking at GigaNet and IDNet but again don't know which is the better ISP reference service.
Pure Fibre 1000
FTTP Technology
Average Speed 900Mbps (Down)
Average Speed 100Mbps (Up) ✔Unlimited Monthly Usage
✔12 Month Contract
✔Static IPv4 Address
✔Static IPv6 Addresses (/56)
✔Standard Care
✔No Telephone Line Rental
✔No In-Contract Price Rises
✔No Annual CPI Increases
✔Rated 5* on Trustpilot
✔Rated 5* on Google Reviews
Exclusive Online Offer Price
£27.50a month, for 6 months
£55.00a month, thereafter
£0.00 activation / install
Prices shown are inclusive of VAT
Offer equivalent to £41.25 per month
Edited by Scoot (Tue 02-Jan-24 18:55:29)
|
|
|
That has to be the largest 'in contract price rise' of any 'no in contract price rise' providers.
Things were better under Labour.
|
|
|
That has to be the largest 'in contract price rise' of any 'no in contract price rise' providers.
And yet they're still cheaper than BT -- currently advertising £57.99 plus CPI+3.9% price increases for 900Mb. Of course, I suspect BT will run a "January sale" at some point soon...
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
Have you considered a suitable router that you may have or need for Aquiss Pure Fibre 1000 FTTP?
|
|
|
That has to be the largest 'in contract price rise' of any 'no in contract price rise' providers. The contract is £55 per month for 1Gbps. There is a half price offer period for the first 6 months. That isn't a price rise that is an introductory offer - but I suspect you know that.
I'm on the 500Mbps package with them and the headline price is the same now as it was over 10 months ago when I joined them, they haven't put the price up and I was able to enjoy half price for the first 6 months. Gave me an average of £37.50 per month for a 500Mbps service with static IPv4 and static IPv6. Not bad pricing at all for the first 12 months.
There was a couple of days where there were issues with the service and high latency that appear to have been caused by one of their upstream providers and did get resolved. Other than that the service has been good.
|
|
|
|
I'm 4 months into using the Aquiss 300/50 service and I'm mostly happy.
A couple of times, IPv6 connectivity has stopped working. Once I got it back immediately by bouncing the PPPoE session; the second time I left it alone to allow Aquiss to investigate, but it cleared after a couple of days.
Aquiss have been excellent in responding promptly to tickets, but in this case the only course of action they had was to escalate to Cityfibre (who apparently run their BRASes) and they weren't able to locate the problem.
|
|
|
|
I'm also a couple of months into a 1GB Aquiss package and overall I'm very pleased, especially with comms which has included them ringing me at one point which I wasn't expecting. Did have a bit of a delay during the Openreach installation but that wasn't Aquiss' fault (scaffolding on building didn't come down in time).
Throughput is very good and consistent and ping times low on IPv4 & 6. Good info on the Aquiss portal as well.
Funnily enough like @candlerb I've seen some IPv6 issues on an RT-AX86U Pro running Merlin where it randomly loses the default route next hop router and requires a reboot or 2 for it to come back. I'm still looking at this and suspect RA issues but I don't know yet whether this is my configuration, the router s/w or Aquiss. IPv4 is rock solid.
|
|
|
I have been with Aquiss for 3 years and never had any issues. It works quite well, the support is responsive and never had any prices increased.
I am on 900/100 and speeds are quite consistent, but at the end of the day it's a BT Wholesale quality.
Aquiss doesn't provide any hardware btw.
Edited by ramzez (Wed 03-Jan-24 16:20:19)
|
|
|
|
I was with Aquiss a year and I would've stayed with them but my new work contract insisted on me using their chosen broadband provider.
When I was with them, they were solid on FTTP 330/50, I used my own router and I think I phoned them once and they phoned me once, I even managed to reach the CEO on two occasions (not through escalation, he also mans the phones) and he's a lovely guy and has a good sense of humour.
The price is pretty reasonable and the service is way beyond anything you'll get with the usual suspects, I also believe the static IP is included as part of your package if that's what you need.
I would recommend them.
|
|
|
Funnily enough like @candlerb I've seen some IPv6 issues on an RT-AX86U Pro running Merlin where it randomly loses the default route next hop router and requires a reboot or 2 for it to come back. I'm still looking at this and suspect RA issues but I don't know yet whether this is my configuration, the router s/w or Aquiss. IPv4 is rock solid.
Interesting: Aquiss said other people had reported the problem at the same time as me, but that all were using Mikrotik routers.
I was able to capture the PPPoE traffic (first by using "/tool sniffer quick", and later by putting a small switch between the router and ONT). I was able to show that:
* incoming packets were arriving successfully (e.g. inbound pings from TBB BQM, or pings from a cloud server that I logged into via IPv4)
* The server on my side was responding and the response packets being sent to Aquiss - but they were not reaching their final destination
* traceroute to an IPv6 address went outside one hop (the Aquiss BRAS) and then no further
* I could ping the Aquiss BRAS's IPv6 address, but not general destinations on the Internet
All these suggest routing on my side was working, and that the Aquiss BRAS had lost its IPv6 default gateway, at least in the context of my PPPoE session.
I have set up some monitoring now. The first time it happened I didn't notice straight away - "Happy Eyeballs" masks this sort of problem when you're just browsing.
In any case, v4 has been solid.
|
|
|
All these suggest routing on my side was working, and that the Aquiss BRAS had lost its IPv6 default gateway, at least in the context of my PPPoE session.
I have set up some monitoring now. The first time it happened I didn't notice straight away - "Happy Eyeballs" masks this sort of problem when you're just browsing.
Interesting indeed (& apols to the OP for the thread hijack).
I hadn't thought to check whether v6 traffic was still being received - next time it happens I'll run tcpdump on the Asus and see if I can see v6 Internet traffic arriving. If so I'll see if I can change the default route to the new LL address and get routing back.
|
|
|
|
I just gave up on ipv6 with my pfsense, every time I enable it something else fails to work. usual suspects things like Disney plus or amazon prime video taking ages to load. Yahoo seems to have issues with ipv6, just like random things. Dont' really see any point for home user tbh.
|
|
|
|
Come March this year, I will have been with Aquiss for 4 years. I'm on the Pure Fibre 80 plan (more than enough for our current needs), and would thoroughly recommend them.
A smooth and impressively rapid pick-up from the previous supplier, and faultless service ever since! Need I say more?
|
|
|
I hadn't thought to check whether v6 traffic was still being received - next time it happens I'll run tcpdump on the Asus and see if I can see v6 Internet traffic arriving. If so I'll see if I can change the default route to the new LL address and get routing back.
Which LL (link-local?) address are you referring to? An interface identifier on the PPPoE WAN interface? IPv6CP does allow negotiation of this.
Checking on my RB4011:
| Text | 1
23
45
| /ipv6 address print where interface=pppoe-out2
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local # ADDRESS FROM-POOL INTERFACE ADVERTISE
0 G 2001:4d48:XXXX:XX00::1/128 pppoe-out2 no 1 DL fe80::d/64 |
I statically assigned the global IP to the interface, so the (D)ynamic address fe80:: d is probably assigned by the BRAS.
But I don't use any link-local address for routing, I just point default route at the pppoe interface by name (actually just IPv6 unicast space):
| Text | 1
2 | /ipv6 route
add distance=1 dst-address=2000::/3 gateway=pppoe-out2 |
Hmm, I just noticed something very weird:
| Text | 1
23
| /ipv6 neighbor print where interface=pppoe-out2
Flags: R - router 0 address=2a02:68:1::164 interface=pppoe-out2 status="noarp" |
That IPv6 address is ipv6.pingbox1.thinkbroadband.com (i.e. the TBB BQM). I have no idea why it should appear as a direct interface neighbor, but it does hint at a Mikrotik IPv6 bug.
If IPv6 breaks again, I'll check whether any of this has changed.
FWIW, I'm running RouterOS 6.49.11. Mikrotik aren't really supporting v6 any more (I reported a memory leak problem a while ago and they told me to upgrade to 7.10.1 to see if the problem still exists), so I guess I'll be forced to go to 7.x sooner rather than later.
|
|
|
|
I was with zen fttp 900mb service, when the contract was up I moved to Aquiss with out any issues my speed is always full and don't have any issues, when. service is this good you don't need to look anywhere else
|
|
|
Which LL (link-local?) address are you referring to? An interface identifier on the PPPoE WAN interface? IPv6CP does allow negotiation of this.
Apols for the delay in replying - I've been away. The LL address is the IPv6 neighbour allocated by Aquiss via dhcpv6. I've been monitoring the RA traffic and these are also coming through fine and inside the route expiry figures.
I'm pretty sure the issue I'm seeing is the router s/w as when I don't get IPv6 routing I can see that the router is allocating a route to my delegated IPv6 range to the ppp interface as well as to the correct bridge interface:-
| Text | 1
23
45
67
89
1011
1213
1415
16 | Lexy:/tmp/home/root# ip -6 r
2001:xxxx:xxxx:xxxx::/56 dev br0 proto kernel metric 256 pref medium2001:xxx:xxxx:xxxx::/56 dev ppp0 proto kernel metric 256 expires 2591961sec pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref mediumfe80::/64 dev spu_us_dummy proto kernel metric 256 pref medium
fe80::/64 dev spu_ds_dummy proto kernel metric 256 pref mediumfe80::/64 dev eth6 proto kernel metric 256 pref medium
fe80::/64 dev eth7 proto kernel metric 256 pref mediumfe80::/64 dev br0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 linkdown pref mediumfe80::/64 dev eth2 proto kernel metric 256 linkdown pref medium
fe80::/64 dev eth3 proto kernel metric 256 linkdown pref mediumfe80::/64 dev eth4 proto kernel metric 256 linkdown pref medium
fe80::/10 dev ppp0 metric 1 pref mediumfe80::/10 dev ppp0 proto kernel metric 256 pref medium
default via fe80::f60f:1bff:fe17:b100 dev ppp0 proto ra metric 1024 expires 1761sec hoplimit 64 pref medium |
If I delete the errant ppp0 route then IPv6 works correctly for all clients. Unfortunately something then occasionally re-creates the route. Repeated reboots tend to "fix" the problem with the wrong routing table entry not being created. There's no global IPv6 address allocated to the ppp0 interface and I wouldn't expect one:
| Text | 1
23
45
67
89
10 | Lexy:/tmp/home/root# ip -6 a show dev br0
27: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 inet6 2001:xxxx:xxxx:xxxx::1/56 scope global
valid_lft forever preferred_lft forever inet6 fe80::ca7f:54ff:fed3:3010/64 scope link
valid_lft forever preferred_lft foreverLexy:/tmp/home/root# ip -6 a show dev ppp0
31: ppp0: <POINTOPOINT,MULTICAST,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN group default qlen 3 inet6 fe80::3133:a3d1:e2a:789/10 scope link
valid_lft forever preferred_lft forever |
I may post to the SNBForum site where the Merlin support people tend to hang out. It certainly doesn't look like an Aquiss problem.
|
|
|
|
I disabled ipv6 on pfsense, as it's also gives random working result. too lazy to figure it out as don't really think ipv6 support worth it for home.
|
|
|
If you're doing IPoE and DHCPv6 that's a whole different ballgame to my PPPoE setup.
But I'm a bit confused about what you're saying, because I didn't think DHCPv6 can allocate link-local addresses. From RFC8415 section 5:
"The client uses a link-local address or
addresses determined through other mechanisms for transmitting and
receiving DHCP messages."
And you show a ppp0 interface. Perhaps you're using DHCPv6 for prefix delegation only?
Also, what seems problematic to me is this:
| Text | 1
2 | 2001:xxxx:xxxx:xxxx::/56 dev br0 proto kernel metric 256 pref medium
2001:xxx:xxxx:xxxx::/56 dev ppp0 proto kernel metric 256 expires 2591961sec pref medium |
You shouldn't have a route to your own /56 via the ppp interface; and if there are two identical routes like that, both with preference medium, it's arbitrary which one will be used.
|
|
|
Thanks for the replies all, still not sorted my move to another ISP yet.
Can anyone answer is Aquiss on CityFibre or Openreach, seeing mixed posts suggesting they might be on Openreach and if thats so I wont need a new ONT from CityFiber installed and that might make me choose them over anyone else.
Have you considered a suitable router that you may have or need for Aquiss Pure Fibre 1000 FTTP?
Yes thanks, I have my own router which is more than capable to handle a 1Gig line including my NIC on PC.
I'm also a couple of months into a 1GB Aquiss package and overall I'm very pleased.
Thanks for the reply.
|
|
|
|
Mine is OpenReach as Cityfibre have no presence here. I have no idea if they have the ability to use wholesale services from both, if they do then I would guess they would use whichever was cheapest in an area.
|
|
|
Have you considered a suitable router that you may have or need for Aquiss Pure Fibre 1000 FTTP?
Yes thanks, I have my own router which is more than capable to handle a 1Gig line including my NIC on PC.
Router setup is very straight forward for an Aquiss Openreach FTTP connection. You just need to use PPPoE, a username and password.
I use an old Billion router for Aquiss Openreach FTTP and I've had no breaks in the internet connection for months!
|
|
|
https://cityfibre.com/homes/broadband-providers
No mention of Aquiss.net on their ‘partner’ list.
|
|
|
|
I use an Amazon Eero 6 router and that works just fine as well. Just entered the details and it connected.
|
|
|
|
different technology stack, they don't do city fibre only openreach.
|
|
|
I use an Amazon Eero 6 router and that works just fine as well. Just entered the details and it connected.
I'll probably have to replace the Billion router when dear old PSTN is ceased though... 
|
|
|
Can anyone answer is Aquiss on CityFibre or Openreach
We actually list this directly on our sales pages:
https://www.aquiss.net/unlimited-fttp-fibre-broadband/
Are Aquiss FTTP packages based on the Openreach network?
Yes. We deploy our FTTP (Fibre to the Premises) packages across the Openreach network.
Martin Pitt
Managing Director
Aquiss Limited
https://www.aquiss.net
SoGEA, FTTP, FTTH, Leased Lines, Telecoms and Hosting Edited by aquiss (Mon 22-Jan-24 16:48:03)
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
Its a shame you couldn't offering SoGfast for someone who can't get FTTP but do have G.fast!
|
|
|
|
Thank you, I have just signed up. Hoping for a seamless and stable service like I have on BT.
Signing up on a weekend, I am guessing I will see no movement or progression of my order until Monday? do I need to inform BT of anything or will as part of the migration terminate that service?
|
|
|
|
You've made a good choice, if you have any questions just give them a call or raise a support ticket, they are very quick with replies and you can see they even watch this forum.
Tell us how you get on!
|
|
|
do I need to inform BT of anything or will as part of the migration terminate that service?
At this stage don't inform BT of anything. One course of action, that is often recommended, is to keep an active existing xDSL connection (copper line) together with a new fibre installation (FTTP). This will rule out any potential loss of an internet connection if there should be any unforeseen issues with FTTP. Once you are happy with the new FTTP service then you can cease the BT service - there shouldn't be any more than approx month of overlap.
If you do decide to do it this way ensure that the fibre installer is aware that you want to keep the copper line active, i.e. not disconnect the active copper line to the NTE5 master socket. She/he will fit an ONT for the fibre optic cable separately in a location that will be suitable within the property.
|
|
|
Hello,
I do appreciate you taking the time to respond, however I am already on FTTP with BT. So was just wondering if the migration would also inform BT to stop charging me and end my service. I assume it will but can never be sure they old ISP will stop taking direct debits 
|
|
|
Your profile mentions BT Infinity 80Mbps so I wrongly assumed you were on a FTTC connection...
Yes a FTTP migration shouldn't be a problem - Aquiss will handle that but as you fear there could be an issue with BT's billing which, hopefully in such a possible event, you wont have to chase up after the migration is completed.
Good luck.
Edited by 4M2 (Sat 10-Feb-24 18:44:46)
|
|
|
So was just wondering if the migration would also inform BT to stop charging me and end my service.
It will - you should *not* give notice to BT of your intention to move.
Of course, they will charge you a penalty if you are still within your contract period when the service is migrated away.
|
Pages in this thread: 
Print Thread
Scoot
aquiss