Re: [AusNOG] what is acceptable jitter for VOIP & videoconferencing?

If it's not already obvious, I would like to mention that jitter/buffering on video is just about a non-issue (otherwise Microsoft Teams wouldn't exist) - but for audio it is everything. Users will notice 20ms of audio delay as a lip sync issue on a streaming movie, but for videoconferencing the

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

It's going to AKL IX on Vocus from Sydney (and other east-coast locations) as well. traceroute to 9.9.9.9 (9.9.9.9) from 114.31.192.89, 30 hops max, 52 byte packets 1 be102-290.bdr01.syd11.nsw.vocus.network (114.31.192.88) 1.169 ms 1.026 ms 0.854 ms 2 be107.cor01.syd11.nsw.vocus.network

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

"Looks like it might be another outage with Quad9's Sydney PoP. Traffic via GSL out to 9.9.9.9 is routing to Singapore via Guam." Yeah its either an outage or someone has messed up a configuration somewhere as traffic for that DNS service is going to NZ for me via Aukland IX via Swoop.

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Yeah my best route on our network is via PCH on WA-IX as well. Nathan Brookfield | VK2NAB General Manager p: 1300 592 330 | m: 0412 266 008 e: nathan.brookfi...@iperium.com.au | w: iperium.com.au Suite 4.02, 189 Kent Street Sydney NSW 2000

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Seeing the same through Telstra Internet Direct. AussieBB is getting to 9.9.9.9 via WA IX. On Wed, 20 Sept 2023 at 11:51, DaZZa wrote: > My default outbound is via Optus, and it's heading the same way > > traceroute 9.9.9.9 > traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets > 1

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

For want its worth, traffic in New Zealand is fine. [root@titan ~]# traceroute 9.9.9.9 traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets 1 103-208-140-185.feenix.co.nz (103.208.140.185) 0.733 ms 0.574 ms 0.550 ms 2 * * * 3 * * * 4 as42.akl.ix.nz (43.243.21.78) 1.099 ms

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Looks like it might be another outage with Quad9's Sydney PoP. Traffic via GSL out to 9.9.9.9 is routing to Singapore via Guam. [cid:8890c8ed-a51e-464f-9f3c-36acf6ff31f4] Regards, Christopher H. From: AusNOG on behalf of Luke Iggleden Sent: Wednesday,

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Hi Christopher, Last week quad9 had a significant outage, at least verified on all the Peering fabrics in Sydney. Perhaps TPG/AAPT routed around that? Have you tried their i...@tpg.com.au address? Cheers, Luke Iggleden On 20/9/2023 11:40 am, Christopher Hawker wrote: Hello all,

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Yes, we have raised a ticket upstream. Simply trying to ascertain if it's just us that are affected or if there is potentially a wider issue. Regards, Christopher H. From: Mark Smith Sent: Wednesday, September 20, 2023 11:48 AM To: Christopher Hawker Cc:

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

My default outbound is via Optus, and it's heading the same way traceroute 9.9.9.9 traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets 1 10.100.1.253 (10.100.1.253) 1.510 ms 10.100.1.252 (10.100.1.252) 0.958 ms 2 10.100.100.249 (10.100.1.249) 0.595 ms 0.576 ms 0.536 ms 3

Re: [AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Have you lodged a fault with APP/TPG? If there is a fault, only they can fix it, so it's best to talk to them first. On Wed, 20 Sept 2023, 11:41 Christopher Hawker, wrote: > Hello all, > > We are seeing some unusual behaviour with a TPG/AAPT service, where > traffic destined for Quad9 DNS is

[AusNOG] Quad9 DNS traffic to Singapore from AAPT/TPG

Hello all, We are seeing some unusual behaviour with a TPG/AAPT service, where traffic destined for Quad9 DNS is being routed to their PoP in Singapore via Level 3. According to Quad9's status page, there are no faults with the Sydney PoP. Is anyone else seeing similar behaviour? Regards,

[AusNOG] what is acceptable jitter for VOIP & videoconferencing?

Occasionally I question my baseline numbers, and struggle to find cites to support my increasingly ancient viewpoint, which goes back to CISCO LLQ, if not earlier. Recently this question came up that I lack an answer to, and was wondering what operators thought was the right number, and wondering