Menu
Reply
  • 12
  • 0
  • 8
vori
Tuning in
394 Views
Message 11 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Looks like there's a lot of people in North London experiencing this issue, then.

Any info @ModTeam?

Highlighted
  • 1.08K
  • 29
  • 328
Moderator
Moderator
380 Views
Message 12 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Hello

Thanks for flagging this to us. We're aware of this issue in North London.

The team are looking in to this and will have this resolved as soon as possible. 

Community Moderators

 

  • 12
  • 0
  • 8
vori
Tuning in
377 Views
Message 13 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

@ModTeam wrote:

We're aware of this issue in North London


Thanks for the info - is there somewhere I can track the progress / get more info about the issue?

https://my.virginmedia.com/faults/service-status

Is reporting no known issues in my area

0 Kudos
Reply
  • 12
  • 0
  • 8
vori
Tuning in
334 Views
Message 14 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Updating with some current info:

Just played again this afternoon, same story, lag rubber banding and this time i'm getting booted from the server:

IMG_20190906_162410.jpgCapture.PNGCapture1.PNGCapture3.PNG

Network Log

TimePriorityDescription
03/09/2019 19:19:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:24criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:25Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:26criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:26Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:31Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:40Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:48criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:53Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/09/2019 19:19:58Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2019 01:09:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2019 16:21:23criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2019 16:21:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2019 16:21:24criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2019 16:21:28Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
  • 11
  • 0
  • 9
ffm_strife
Tuning in
295 Views
Message 15 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Same here, area 15, rubbish network, not playing apex legends at present, but Wow classic is borderline unplayable.

  • 11
  • 0
  • 9
ffm_strife
Tuning in
244 Views
Message 16 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Just as an update, just got off the phone from Virgin Media, seems the issue has been raised on their end yesterday at 6pm (why it took that long, no clue). 

They couldn't help with any estimated time for repair. It's quite embarassing to be paying 50£ monthly for this service, specially when there's zero information available, even if you login it shows as no fault. Could we get any update, @ModTeam ?

 

  • 1.17K
  • 67
  • 103
Forum Team
Forum Team
230 Views
Message 17 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Hi ffm_strife,

 

Thank you for reaching out to us in our community, AI am sorry to hear you haven't been able to get an update on the fix date, I would like to invite you into a private chat so I can look into this for you.

 

I will send you an invite shortly, please click on the purple envelope to accept.

 

Kind reggards

 

Paul.

  • 12
  • 0
  • 8
vori
Tuning in
222 Views
Message 18 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Hi Paul,

Can I get an update too? (This is my thread lol)

  • 11
  • 0
  • 9
ffm_strife
Tuning in
219 Views
Message 19 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Happy to post any infomation I get, although I don't understand the reasoning to not just put all information on this thread, it's more than one person affected, just put the information here so everyone can read it.

  • 12
  • 0
  • 8
vori
Tuning in
214 Views
Message 20 of 38
Flag for a moderator

Re: Apex Legends packet loss, rubber banding Area 15

Thanks - Paul has messaged me too now and I'll be updating the thread for sure.