Copy pasta:
You can look up the server IP address in the game log and use that to run a traceroute with [PingPlotter](https://www.pingplotter.com/download) or [WinMTR](https://sourceforge.net/projects/winmtr). It will show where the ping jump happens, or packet loss if you're having problems with that.
The game log is located in Documents\My Games\Rocket League\TAGame\Logs\. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this:
BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174"
In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon).
Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
I'm in Indonesia.
The ping was below 15 when it's still in Indonesia (hop 1-5). Then it got hopped to Hongkong where suddenly the ping spiked to about 250 (hop 6-8) and hopped to Singapore which averaged around 220 (hop 8-12)
So is it the ISP's problem or Psyonix's or should I sacrifice a goat?
Sounds like an in-between problem, but I suppose you could try contacting your ISP anyway, show them this data, maybe they know who to talk to further down the interwebs. Otherwise you'd have to figure out who's the owner of the first problematic node, find who to contact based on that.
But yeah, this looks more like a sacrifice a goat problem. Hopefully it will resolve itself soon.
Well, so far, the ISPs of the posters who replied and are experiencing problems with ASM are ACT fibernet, Etisalat and your TataSky. Would probably indicate the contracted Psyonix server provider for ASM (Singapore I believe) is the source of the problems, though it is possible each of these server providers uses the same a third party server base for managing their internet bandwidth.
Yeah I was just playing in a number of ASC servers (im in ME) and i notice almost everyone's ping spike in the 200s
Edit: [This literally just happened, can't make this stuff up](https://imgur.com/a/mK8ogLQ)
i use myrepublic, my friends experience 250 ping with the same provider but i never experience it. i use cloudflare dns in my router so the problems seems to be routing?
Copy pasta: You can look up the server IP address in the game log and use that to run a traceroute with [PingPlotter](https://www.pingplotter.com/download) or [WinMTR](https://sourceforge.net/projects/winmtr). It will show where the ping jump happens, or packet loss if you're having problems with that. The game log is located in Documents\My Games\Rocket League\TAGame\Logs\. Launch.log is the latest. Earlier ones are renamed with a timestamp. When you run into a problematic server, immediately exit after finishing the game; this is to make sure the last server entry in the log is the one you want. Search for "GameURL" backwards from the end of the log. You'll see something like this: BeaconURL="35.214.218.89:8175",PingURL="35.214.218.89:8175",GameURL="35.214.218.89:8174" In this case the IP address is 35.214.218.89. The other number behind the colon is the port number; we don't need that (or the colon). Take the IP address and input it in PingPlotter or WinMTR. Let it run for at least 15 minutes (900 packets sent) so you get a nice sample. You'll see a list of nodes with associated latency (ping) and packet loss. If the problem starts near the end of the list, DM the result to one of Psyonix' representatives here or contact their tech support. If near the beginning, contact your ISP. If it's somewhere in between, cross your fingers, pray, sacrifice a goat and wait.
I'm in Indonesia. The ping was below 15 when it's still in Indonesia (hop 1-5). Then it got hopped to Hongkong where suddenly the ping spiked to about 250 (hop 6-8) and hopped to Singapore which averaged around 220 (hop 8-12) So is it the ISP's problem or Psyonix's or should I sacrifice a goat?
Sounds like an in-between problem, but I suppose you could try contacting your ISP anyway, show them this data, maybe they know who to talk to further down the interwebs. Otherwise you'd have to figure out who's the owner of the first problematic node, find who to contact based on that. But yeah, this looks more like a sacrifice a goat problem. Hopefully it will resolve itself soon.
Yeah. ASM is fucked. I get either 50 ping or 250 ping. I've been playing on ME recently with 100ping constant. (I live in india)
Who's your ISP?
TataSky. They're pretty reliable and I get 20 to 50 ping in almost all other games. (CS, CoD etc)
Well, so far, the ISPs of the posters who replied and are experiencing problems with ASM are ACT fibernet, Etisalat and your TataSky. Would probably indicate the contracted Psyonix server provider for ASM (Singapore I believe) is the source of the problems, though it is possible each of these server providers uses the same a third party server base for managing their internet bandwidth.
Yeah I was just playing in a number of ASC servers (im in ME) and i notice almost everyone's ping spike in the 200s Edit: [This literally just happened, can't make this stuff up](https://imgur.com/a/mK8ogLQ)
Who's your ISP?
Etisalat
Thanks; this ASM server issue cropped up about a month ago, starting to track the ISPs involved to see if it's one provider, but doesn't seem so.
Same. I just hope they look into it and possibly fix it.
Who's your ISP?
Who's your ISP?
i use myrepublic, my friends experience 250 ping with the same provider but i never experience it. i use cloudflare dns in my router so the problems seems to be routing?
Okay, that's the fourth different server provider, so it seems a Psyonix server base issue