IPv6 working for me too, didn't need to do anything. :)

Hi,
I recently noticed that I've lost IPv6 on my connection too. It was working until the 21st of March when I received notification that some SROS upgrades to resolve an incident have been completed. Could that be related?  I haven't changed anything on my end yet. I also use a Mikrotik Router - Model RB760iGS  and the current firmware is 6.49.18

It seems I'm still having this (similar?) issue with bng1-akl1. I am getting a prefix and clients get addresses but have no connectivity, address assigned from the /64 pool is getting duplicate address error.

I can't even ping bng1-akl1.

And you are not the only one as I've checked a few smokeping hosts in various homed connections.

I will ask around.

edit: I have asked, it is known. 

@quic tagging the account so someone can update when possible.

Indeed also having the issue, making internet very laggy as a result, as gateway and devices are getting IPv6 addresses, but its not routing...

Hey folks!

We’ve identified an issue which would explain these IPv6 routing irregularities, with one of our BNGs in Auckland. 

A temporary fix has been implemented which should keep the gremlins at bay while we liaise with our vendor to determine the root cause. 

Apologies for the trouble. 

Seeing ipv6 working again thanks 

Yes ipv6 is working now, but separate side issue now is Overwatch is getting 300~ms :(

Is there an option in Overwatch to turn IPv6 off? There is in Warcraft and it's from the same dev, so have a look.

It is high latency on ipv4, I think it’s 24.105.59.158

Edit: as of writing this it dropped to 200~ms, can’t tell which IP is the actual game connection.

SpartanVXL:

 

Yes ipv6 is working now, but separate side issue now is Overwatch is getting 300~ms :(

 

24.105.59.158 is going via Sydney, to Singapore and does not respond once it makes it back in USA. This could or could not be the end point and it's a bit hard to troubleshoot if it isn't.

It is supposedly geo'd to California or Illinois.

Not the most amazing of routes but that latency makes sense given the path it has to take.

SpartanVXL:

 

It is high latency on ipv4, I think it’s 24.105.59.158

 

Edit: as of writing this it dropped to 200~ms, can’t tell which IP is the actual game connection.

 

Thanks for the route! Looks like we are taking a bit of an average path which does have the shortest AS-path, but isn't the best actual path.

Have added it into our traffic engineering list for next week, as it does look like there's a better path available for us to perform some engineering to steer it towards.

Sorry jumped the gun, seems likes it dropped again after re-connecting to practice range a few times. It is now back to 44ms~

Some of the names/addresses I saw that the process was sending 5KB/s~ to are as follows:

ec01-eqla1.as57976.net [3.33.139.32]
ec04-eqsy4.as57976.net [137.221.85.103]
ec02-eqch2.as57976.net [3.33.139.32]

Latest is now ec04-eqsy4.as57976.net [3.33.139.32] which is working, is this an AWS accelerator? Might have been something else outside of network.

Seems something has happened again.

No change to any devices and now devices not getting IPv6 Addresses anymore...

This thread started in the middle of Jan & we are now at the beginning of May. 3 months of intermittent IPv6 issues is too much for me. It's off until I see less complaints.