03/09 Maintenance Announcement

[Ritual 629]

Hello, everyone!

 

The standard weekly maintenance will occur this Wednesday (03/09), 9 AM UTC. It is expected to last up to 4 hours. As always, this maintenance also includes the regular console maintenance.

 

Thank you for your patience during this period!

 

Regards,

Ritual

 

P.S: The information has been cross-posted from Game Updates.

[BlatMan 711]

Why is NA East no longer hosted on the east coast of the USA? Is Path still performing maintenance?

 

Server time is set to UK timezone (UTC 0).

Server IP is 205.220.229.82

Latency to the server from the east coast is about 80ms.

[Sadira 292]

32 minutes ago, BlatMan said:

Why is NA East no longer hosted on the east coast of the USA? Is Path still performing maintenance?

 

Server time is set to UK timezone (UTC 0).

Server IP is 205.220.229.82

Latency to the server from the east coast is about 80ms.

All servers are set to UTC time, which is industry standard.

 

That IP is the general server, not the district.

The districts server IP's (that you're directly connected to) are in their respective locations as they should be. NA-East instances point to NYC locations.

 

If you're getting more latency than expected, you should contact your ISP to fix the routing to the district instance IP.

[BlatMan 711]

3 minutes ago, Sadira said:

All servers are set to UTC time, which is industry standard.

 

That IP is the general server, not the district.

The districts server IP's (that you're directly connected to) are in their respective locations as they should be. NA-East instances point to NYC locations.

 

If you're getting more latency than expected, you should contact your ISP to fix the routing to the district instance IP.

The in game /latencytest shows stable ping on each hop until it reaches the district. If it had anything to do with my ISP, I would see latency variations on the hops before Path's IP addresses, not after. I would see packet loss in other games, not just APB. It's something screwed up on Path's side or Little Orbit's side.

 

It started happening after this post:

 

[Rivona 59]

When new clothes???? its verry limited chose for girls! and i don't think need engine update just to make new clothes! I am here 1 year now and not seen anything new in this game =(

[Hexerin 1140]

Change consumables to mods with a cooldown, like they should've been in the first place.

[MonkaS 215]

14 hours ago, BlatMan said:

The in game /latencytest shows stable ping on each hop until it reaches the district. If it had anything to do with my ISP, I would see latency variations on the hops before Path's IP addresses, not after. I would see packet loss in other games, not just APB. It's something screwed up on Path's side or Little Orbit's side.

 

It started happening after this post:

 

this. my guess is misconfigured ddos protection or just trash servers who knows

[BlatMan 711]

I'm leaning on servers. Here's charts from the /latencytest on Waterfront West, 10 minute time frame. 20/20 player pop.

 

205.220.229.82 is the last hop in the traceroute, District Server is the district. The last hop is stable, about 77ms average. The district however looks weird. Most pings are 99ms or 132ms. Not much in between. There's two routes and one takes longer, or I'm seeing the server tickrate due to the packet being received between ticks. 132ms - 99ms = 33ms (same as tickrate). If the latter, then the network might be fine.

 

https://i.imgur.com/RTtiqLS.png

 

Lets check out the server's frametime/tickrate. The average is 33ms, but it's constantly spiking over 35ms, often over 40ms. I don't know if those 200ms spikes are the server or the client performing garbage collection. This was only 20/20 player pop. If we're seeing spikes at half capacity, expect it to be way worse with more players.
 

https://i.imgur.com/vXPpvQV.png

[CookiePuss 5378]

Wherever the server is I hope it stays there. I get 22ms from Chicago.

[BlatMan 711]

2 hours ago, CookiePuss said:

Wherever the server is I hope it stays there. I get 22ms from Chicago.

It looks like east was fixed with maintenance. Probably just needed a restart to correct the routing internally. I was getting like 80-90ms, Friend in Montana was getting 150ms or so. Now it's 20ms for me, 50-60ms for them. If it's over 30/30 population tonight I'll run some more tests. West is always bad, so nothing new there, but still it could be better. There shouldn't be constant 40+ ms server tick spkes, especially with a half populated district. Full I can understand.

 

It's kinda neat that APB has a proper network diagnostics tool built in.

Edited March 11, 2022 by BlatMan

[CookiePuss 5378]

1 hour ago, BlatMan said:

It looks like east was fixed with maintenance. Probably just needed a restart to correct the routing internally. I was getting like 80-90ms, Friend in Montana was getting 150ms or so. Now it's 20ms for me, 50-60ms for them. If it's over 30/30 population tonight I'll run some more tests. West is always bad, so nothing new there, but still it could be better. There shouldn't be constant 40+ ms server tick spkes, especially with a half populated district. Full I can understand.

 

It's kinda neat that APB has a proper network diagnostics tool built in.

I was only joking, Ive always gotten 22ms to East.

[BlatMan 711]

East servers are still screwed up. Here's waterfront 1 US East. 80-90 ms to the last hop, 60-70 ms to the district server. The last hop, 205.220.229.82, geolocation is in California.

 

13/03/2022 03:19:03,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,35,40
13/03/2022 03:19:04,PACKET_RECEIVED,0,192.168.11.1,0,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,2,67.59.227.69,6,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,3,67.83.246.22,7,11013,
13/03/2022 03:19:04,CLIENT_FRAMETIME,,,0,,Outlier Stats:,13,1
13/03/2022 03:19:04,SERVER_FRAMETIME,,,33,,Outlier Stats:,56,0
13/03/2022 03:19:04,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,34,40
13/03/2022 03:19:04,PACKET_RECEIVED,4,64.15.7.186,11,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,5,65.19.120.210,13,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,6,62.115.153.104,13,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,7,62.115.167.205,13,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,8,89.149.187.102,84,11013,
13/03/2022 03:19:04,PACKET_RECEIVED,10,205.220.229.82,85,0,
13/03/2022 03:19:05,CLIENT_FRAMETIME,,,0,,Outlier Stats:,13,1
13/03/2022 03:19:05,SERVER_FRAMETIME,,,33,,Outlier Stats:,56,0
13/03/2022 03:19:05,DISTRICT_SERVER,,,69,,Packet loss:,0,CCU:,34,40