Are you having issues? Provide feedback to Turbosquid by selecting the option you are having issues with.
by chris 6 months ago
HTTP Status 400 – Bad Request
HTTP/2 200 content-type: text/html;charset=UTF-8 content-length: 246711 date: Wed, 12 Apr 2023 17:41:10 GMT cache-control: public, max-age=3600 strict-transport-security: max-age=15724800; includeSubDomains x-cache: Hit from cloudfront via: 1.1 41f52bee72ba8c3a61ac3641274810c4.cloudfront.net (CloudFront) x-amz-cf-pop: ATL59-P1 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: VHfbu8kIZ4F4ypSYBaiFxuwi3NNuaBF0BxL2FvfZras9kv7H01UAjw== age: 2488
The DNS is up. We have tried pinging Turbosquid.com. There are no DNS Issues detected!
Type | Name | Value | Class | TTL |
A | turbosquid.com | 13.248.178.125 | IN | 60 |
A | turbosquid.com | 76.223.35.209 | IN | 60 |
NS | turbosquid.com | IN | 86400 | |
NS | turbosquid.com | IN | 86400 | |
NS | turbosquid.com | IN | 86400 | |
NS | turbosquid.com | IN | 86400 |
We have tried pinging Turbosquid.com using our servers and the Turbosquid.com server responded on time, indicating that there are no current Turbosquid.com problems today.
If Turbosquid.com is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.
If Turbosquid.com is UP for us but you cannot access it, try these solutions:
en_US