This is clearly your or your ISP problem. Working in IT Security myself I assume a DDOS against you or your provider. I'm in the Netherlands and neither Wifi nor Mobile works, your ping responses are terrible. All other games - Simpsons, Star Wars, Pocket City - and Services - Twitter, Accuweather - work. So do your job and not blame on the costumers.
My wifi uses the home connection and that does use IpV6 and that doesn't work.
Cell data IPv6 is not configured, game works
VPN doesn't support IpV6, game works.
I would test this my self but my child is glued to Netflix, anyone here having this problem and can make changes to their router DISABLE IpV6 and try wifi again then report in. I'm 90% sure that something at the Db server end had been misconfigured and isn't allowing IpV6 connections.
Unfortunately, I'm sure I'm not connecting over IPv6. I've run TCPdump on the router. Could it be MTU discovery? All packets are set to "don't fragment" and some are 1500 bytes ... BTW the server is somewhere in amazon AWS, hard to believe amazon have incorrect routes.
I'm in Bristol UK and not been able to to get on the game for 6 hours, is anyone working on this problem as it seems it's not just the UK that is effected, what about the event 6 hours no game play is a long time.
I'm in Bristol UK and not been able to to get on the game for 6 hours, is anyone working on this problem as it seems it's not just the UK that is effected, what about the event 6 hours no game play is a long time.
It'll take some hefty compo to stop the peasants revolting
stt.disruptorbeam.com is an alias for stt-production-708320633.us-west-2.elb.amazonaws.com.
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.89.24.117
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.42.217.135
thorium.disruptorbeam.com is an alias for production-platform-alb-1622574438.us-west-2.elb.amazonaws.com.
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.69.201.79
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.68.191.243
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.186.212.60
... what I'm doing on us-west?
Traceroute:
traceroute to thorium.disruptorbeam.com (54.68.191.243), 30 hops max, 40 byte packets
2 * * *
3 ip-86-49-52-33.net.upcbroadband.cz (86.49.52.33) 6.774 ms 6.811 ms 6.847 ms
4 cz-prg02a-ra2-vla2006.net.upc.cz (84.116.222.185) 7.655 ms 8.575 ms 8.575 ms
5 cz-prg02b-ri1-ae18-0.aorta.net (84.116.138.145) 7.870 ms 8.097 ms 7.975 ms
6 ae1.cr1-prg1.ip4.gtt.net (77.67.90.25) 8.130 ms 7.948 ms 7.857 ms
7 et-0-0-53.cr4-lax2.ip4.gtt.net (213.254.230.250) 170.774 ms 169.975 ms 169.967 ms
8 a100-gw.ip4.gtt.net (173.205.58.58) 170.684 ms 169.950 ms 170.897 ms
9 54.239.103.42 (54.239.103.42) 185.710 ms 54.239.103.30 (54.239.103.30) 191.952 ms 54.239.103.78 (54.239.103.78) 184.646 ms
10 54.239.103.109 (54.239.103.109) 165.329 ms 54.239.102.229 (54.239.102.229) 170.001 ms 54.239.103.61 (54.239.103.61) 170.904 ms
11 * * *
12 * * 54.239.44.22 (54.239.44.22) 182.429 ms
13 * 52.93.14.251 (52.93.14.251) 187.373 ms *
14 52.93.14.90 (52.93.14.90) 212.217 ms 203.552 ms *
15 52.93.14.129 (52.93.14.129) 185.983 ms 52.93.14.237 (52.93.14.237) 186.418 ms 52.93.14.177 (52.93.14.177) 185.888 ms
16 52.93.240.41 (52.93.240.41) 186.511 ms 52.93.15.233 (52.93.15.233) 186.658 ms 205.251.232.221 (205.251.232.221) 198.752 ms
17 52.93.14.165 (52.93.14.165) 185.970 ms 52.93.14.129 (52.93.14.129) 186.312 ms 52.93.14.93 (52.93.14.93) 182.015 ms
18 * 52.93.15.239 (52.93.15.239) 181.037 ms *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
This is clearly your or your ISP problem. Working in IT Security myself I assume a DDOS against you or your provider. I'm in the Netherlands and neither Wifi nor Mobile works, your ping responses are terrible. All other games - Simpsons, Star Wars, Pocket City - and Services - Twitter, Accuweather - work. So do your job and not blame on the costumers.
Unfortunately, I'm sure I'm not connecting over IPv6. I've run TCPdump on the router. Could it be MTU discovery? All packets are set to "don't fragment" and some are 1500 bytes ... BTW the server is somewhere in amazon AWS, hard to believe amazon have incorrect routes.
Unless you recently changed your MTU settings then it's absolutely not an MTU issue because I doubt this many of us adjusted their MTU settings. Usually I think MTU is set at 1476 if I remember correctly but 1500 still shouldn't cause this.
To check if your rubbing on IpV6 you have to specifically look for it with a special online scanner. (Easier then figuring out the check settings for every os everyone here may use)
Same problems with the game since 8 hours ago from Argentina, already lost 2k places in the event roster... Lovely
Update, even trying to get in DB pages and forum was really hard, DNS issues o DDoS are my guesses
Complain to your ISP that supplies your broadband.
Well, if I can get into any other game or to every other website in the world, I don't think my ISP is to blame. I don't think anyone at the ISP has thought: "Let's block DB STT and nothing else".....
All other games and websites are controlled by different records in a database. One glitched record = one affected server.
In the uk, where an isp has been mentioned only virginmedia has been mentioned.
Complain to your ISP that supplies your broadband.
Well, if I can get into any other game or to every other website in the world, I don't think my ISP is to blame. I don't think anyone at the ISP has thought: "Let's block DB STT and nothing else".....
All other games and websites are controlled by different records in a database. One glitched record = one affected server.
In the uk, where an isp has been mentioned only virginmedia has been mentioned.
I work in IT. If you tell me what is the correct record I can put it in my DNS server. Would be harder with routing record, but somehow I don't believe routing to amazon AWS is damaged.
Some ISP providers over the world, either in South and North America, and Europe seem to be having problem or a connection might have been lost for DB...
Same problems with the game since 8 hours ago from Argentina, already lost 2k places in the event roster... Lovely
Update, even trying to get in DB pages and forum was really hard, DNS issues o DDoS are my guesses
I would add a link down on DB's side...
Fibertel from Argentina seems to be the problem, because Arnet and/or Speedy/Movistar work apparently fine.
The same thing seems to happen on the UK! One provider works and the other does not. I have been playing over the cell phone antenna but speed here are really bad...
Same problems with the game since 8 hours ago from Argentina, already lost 2k places in the event roster... Lovely
Update, even trying to get in DB pages and forum was really hard, DNS issues o DDoS are my guesses
I would add a link down on DB's side...
Fibertel from Argentina seems to be the problem, because Arnet and/or Speedy/Movistar work apparently fine.
Well, I'm on Fibertel and Personal, didn't check over LTE
Same problems with the game since 8 hours ago from Argentina, already lost 2k places in the event roster... Lovely
Update, even trying to get in DB pages and forum was really hard, DNS issues o DDoS are my guesses
I would add a link down on DB's side...
Fibertel from Argentina seems to be the problem, because Arnet and/or Speedy/Movistar work apparently fine.
Well, I'm on Fibertel and Personal, didn't check over LTE
stt.disruptorbeam.com is an alias for stt-production-708320633.us-west-2.elb.amazonaws.com.
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.89.24.117
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.42.217.135
thorium.disruptorbeam.com is an alias for production-platform-alb-1622574438.us-west-2.elb.amazonaws.com.
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.69.201.79
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.68.191.243
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.186.212.60
Pings to all these ip addresses time out on virginmedia.
Comments
My wifi uses the home connection and that does use IpV6 and that doesn't work.
Cell data IPv6 is not configured, game works
VPN doesn't support IpV6, game works.
I would test this my self but my child is glued to Netflix, anyone here having this problem and can make changes to their router DISABLE IpV6 and try wifi again then report in. I'm 90% sure that something at the Db server end had been misconfigured and isn't allowing IpV6 connections.
It'll take some hefty compo to stop the peasants revolting
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.89.24.117
stt-production-708320633.us-west-2.elb.amazonaws.com has address 52.42.217.135
thorium.disruptorbeam.com is an alias for production-platform-alb-1622574438.us-west-2.elb.amazonaws.com.
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.69.201.79
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.68.191.243
production-platform-alb-1622574438.us-west-2.elb.amazonaws.com has address 54.186.212.60
... what I'm doing on us-west?
Traceroute:
traceroute to thorium.disruptorbeam.com (54.68.191.243), 30 hops max, 40 byte packets
2 * * *
3 ip-86-49-52-33.net.upcbroadband.cz (86.49.52.33) 6.774 ms 6.811 ms 6.847 ms
4 cz-prg02a-ra2-vla2006.net.upc.cz (84.116.222.185) 7.655 ms 8.575 ms 8.575 ms
5 cz-prg02b-ri1-ae18-0.aorta.net (84.116.138.145) 7.870 ms 8.097 ms 7.975 ms
6 ae1.cr1-prg1.ip4.gtt.net (77.67.90.25) 8.130 ms 7.948 ms 7.857 ms
7 et-0-0-53.cr4-lax2.ip4.gtt.net (213.254.230.250) 170.774 ms 169.975 ms 169.967 ms
8 a100-gw.ip4.gtt.net (173.205.58.58) 170.684 ms 169.950 ms 170.897 ms
9 54.239.103.42 (54.239.103.42) 185.710 ms 54.239.103.30 (54.239.103.30) 191.952 ms 54.239.103.78 (54.239.103.78) 184.646 ms
10 54.239.103.109 (54.239.103.109) 165.329 ms 54.239.102.229 (54.239.102.229) 170.001 ms 54.239.103.61 (54.239.103.61) 170.904 ms
11 * * *
12 * * 54.239.44.22 (54.239.44.22) 182.429 ms
13 * 52.93.14.251 (52.93.14.251) 187.373 ms *
14 52.93.14.90 (52.93.14.90) 212.217 ms 203.552 ms *
15 52.93.14.129 (52.93.14.129) 185.983 ms 52.93.14.237 (52.93.14.237) 186.418 ms 52.93.14.177 (52.93.14.177) 185.888 ms
16 52.93.240.41 (52.93.240.41) 186.511 ms 52.93.15.233 (52.93.15.233) 186.658 ms 205.251.232.221 (205.251.232.221) 198.752 ms
17 52.93.14.165 (52.93.14.165) 185.970 ms 52.93.14.129 (52.93.14.129) 186.312 ms 52.93.14.93 (52.93.14.93) 182.015 ms
18 * 52.93.15.239 (52.93.15.239) 181.037 ms *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Unless you recently changed your MTU settings then it's absolutely not an MTU issue because I doubt this many of us adjusted their MTU settings. Usually I think MTU is set at 1476 if I remember correctly but 1500 still shouldn't cause this.
We have a captain in the Netherlands with the same issue, and some UK captains (but not all). Not working on all platforms.
I guess there goes my top 1k finish... 😂
Ipleak.net should tell you..
Update, even trying to get in DB pages and forum was really hard, DNS issues o DDoS are my guesses
All other games and websites are controlled by different records in a database. One glitched record = one affected server.
In the uk, where an isp has been mentioned only virginmedia has been mentioned.
Just tell us your trying, or you can't figure it out but that your actually paying attention ?
I work in IT. If you tell me what is the correct record I can put it in my DNS server. Would be harder with routing record, but somehow I don't believe routing to amazon AWS is damaged.
I would add a link down on DB's side...
Fibertel from Argentina seems to be the problem, because Arnet and/or Speedy/Movistar work apparently fine.
Really? I feel like an actual acknowledgment of the problem by DB would leave me way more stunned.
Well, I'm on Fibertel and Personal, didn't check over LTE
Heh. Touché sir
Seems to work fine over Personal's LTE network
Pings to all these ip addresses time out on virginmedia.