Same for me, still down. North West Germany. Error code [NE-21194400]. Really annoying.
Anybody have an idea what the infrastructure behind GTS looks like? I don't have much insight, but Sony's own stuff seems to be up. Could update PS4 to 5.03, the store and PSPlus front loads etc. But the GTS bits are most certainly not running as intended.
From DNS logs, only thing I can find adhoc is two servers that look GTS related:
* gt7sp.ps4.online.gran-turismo.com
* gtsport.api.wwsga.me
First one currently resolves to gt7sp-ps4-online-1462309357.us-east-1.elb.amazonaws.com.
Second one to gtsport.api.wwsga.me. Neither are pingable. Traceroutes stop along the way.
tracert -d gt7sp.ps4.online.gran-turismo.com
Tracing route to gt7sp-ps4-online-1462309357.us-east-1.elb.amazonaws.com [34.200.100.187] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.1
2 16 ms 16 ms 16 ms 87.186.224.140
3 16 ms 16 ms 16 ms 87.186.235.114
4 16 ms 16 ms 16 ms 217.239.53.46
5 17 ms 16 ms 16 ms 80.157.204.58
6 109 ms 125 ms 109 ms 89.149.142.238
7 108 ms 107 ms 107 ms 173.205.42.6
8 * * * Request timed out.
9 * * * Request timed out.
10 135 ms 117 ms 123 ms 52.93.27.9
11 111 ms 111 ms 113 ms 54.239.108.195
12 110 ms 109 ms 109 ms 205.251.245.191
13 * * * Request timed out.
tracert -d gtsport.api.wwsga.me
Tracing route to awseb-e-f-awsebloa-15sn9xus6gotr-1498485990.us-east-1.elb.amazonaws.com [52.201.110.237] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.1
2 16 ms 16 ms 16 ms 87.186.224.140
3 17 ms 16 ms 16 ms 87.186.235.118
4 16 ms 16 ms 16 ms 217.239.53.1
5 16 ms 16 ms 16 ms 80.157.204.58
6 108 ms 109 ms 108 ms 89.149.142.238
7 107 ms 107 ms 107 ms 173.205.42.6
8 * * * Request timed out.
9 * * * Request timed out.
10 119 ms 121 ms 114 ms 54.239.110.181
11 107 ms 107 ms 107 ms 52.93.25.124
12 142 ms 146 ms 140 ms 52.93.27.215
13 110 ms 110 ms 110 ms 52.93.24.39
14 * * * Request timed out.
Does not look good but might also not mean much. Unfortunately some IT sec 'pros' think ICMP is dangerous... But nevertheless, Sony's PS4 stuff looks operational and there's no outage warnings for AWS. So most likely something is broken application side on Polyphony's end (or whoever is in charge for their backend ops).
Grml...