FTTB Sydney NSW Packetloss

[tlai]

Hello,

Today I am expericing packlet and ping spikes within games. I have reset my modem, and it didn't do anything.

Here are my stats:

Ping statistics for 203.26.27.38:
Packets: Sent = 1000, Received = 994, Lost = 6 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 22ms, Average = 6ms

Ping statistics for 192.168.0.1:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 0ms

[BasilDV]

Hi @tlai

Are you still experiencing issues with your service?

If yes, is it time specific or random?

BasilDV

[tlai]

Hi @BasilDV,

I am not sure it is related with the rain that is happening, but it does seem to be periodic.

Yesterday after a few hours it seemed to be okay.

Right now i've run the same tests just to the modem/router and to tpg and there still seems to be some packetloss.

Ping statistics for 192.168.0.1:
Packets: Sent = 1000, Received = 1000, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms

Ping statistics for 203.26.27.38:
Packets: Sent = 2833, Received = 2825, Lost = 8 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 46ms, Average = 6ms

The weather is forcasted to rain all week... so let's see how it goes.

[tlai]

1pm 14/7/20 it's definately still happening, I was in a game when I was running this and every ping spike on a local server, equals to a timeout on the ping.

Ping statistics for 203.26.27.38:
Packets: Sent = 974, Received = 968, Lost = 6 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 14ms, Average = 6ms

[Riezl]

Hi @tlai, we'd like to arrange one of our senior technical specialists to contact you for assistance. Please send us a private message with your best contact number and most convenient time to receive a call tomorrow. 

To send a PM, please refer to this link: How do I private message (PM) in the community

[Shane]

Hi @tlai,

We arranged one of our Technicians to contact you tomorrow between 10-12NN AEST. Make sure to keep your mobile phone available for the call and let us know how it will go.

Cheers! 

[tlai]

@Shane 

Thanks, I have received the call just now. As the issue seems to periodic, normallly lasting a few hours, they told me to monitor the situation for now and to let them know if there's further issues, where they can more testing on their side.

Thanks

[tlai]

This this is happening again 16/7 8:30-9pm.

Ping statistics for 203.26.27.38:
Packets: Sent = 957, Received = 950, Lost = 7 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 14ms, Average = 6ms

10:47 PM

Ping statistics for 203.26.27.38:
Packets: Sent = 1000, Received = 991, Lost = 9 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 46ms, Average = 6ms

I don't think I can do anything else on my end.

[Shane]

Hi @tlai,

I re-open the previous escalated fault from our Technical Team and arranged them to contact you tomorrow between 8-9PM AEST to make a real-time test in the event the issue will occur again.

Regards, 

This this is happening again 16/7 8:30-9pm.

Ping statistics for 203.26.27.38:
Packets: Sent = 957, Received = 950, Lost = 7 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 14ms, Average = 6ms

10:47 PM

Ping statistics for 203.26.27.38:
Packets: Sent = 1000, Received = 991, Lost = 9 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 46ms, Average = 6ms

I don't think I can do anything else on my end.

[tlai]

@Shane 

Thanks. As the issue seems to be perioidc hopefully they can find something from the testing.

During these times, the speed itself isn't affected.

Thanks