CloudFront
tcp/80
Open service 2600:9000:28eb:8000:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:43 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 849149785eb810a2bb27d4e2bd0d82b4.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: mit35tEYrONJKdkYlSGIEgj4TgI4EBCX2B5lwOlohiJtQz4Nzm7XCw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: mit35tEYrONJKdkYlSGIEgj4TgI4EBCX2B5lwOlohiJtQz4Nzm7XCw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:4e00:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:43 GMT
x-amz-apigw-id: V9IRMG0MIAMEHeg=
x-amzn-RequestId: bf7074c5-b809-4f96-9601-890bd0757916
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 d9ded362658a71bc4f5c03fb78a1085c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: KB9NWnZ6WlUKJFmqxtmY-_d5Pe5-HSvyBUIcA3IAdGhtZ32rlA7KSQ==
{"message":"Missing Authentication Token"}
Open service 3.174.46.62:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:43 GMT
x-amz-apigw-id: V9IRLGzIoAMEeig=
x-amzn-RequestId: 16913926-bf97-4a1b-be6a-2857a758183a
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 2d72fd84d4c7c03cc33e65c393b3d0de.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: FoQLOu3FubMuDTK2bV5NGsLkJ57TPROG2srN5yrIIQ3s5z3eUdoSyA==
{"message":"Missing Authentication Token"}
Open service 3.174.46.46:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:42 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 5510ba86e3df44d161d0304fbdee228c.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: x2BeEROc9HzpkxRqELFG4lTdugJZPBbUzzMkEzpQGBeis8sqcoWOfw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: x2BeEROc9HzpkxRqELFG4lTdugJZPBbUzzMkEzpQGBeis8sqcoWOfw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.174.46.34:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:43 GMT
x-amz-apigw-id: V9IRKEaSIAMEbIA=
x-amzn-RequestId: 1bf9ab7d-b20d-499a-9ab6-0f8d20f41656
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 3ae34da451a19efe92d6bea00849f488.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: YGxmYmL46rMXSNCMFz4yI9q0iqKwgJbLh1apNaZ39B78N3JISzwSQA==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:8000:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRIHmgoAMED6w=
x-amzn-RequestId: f7742c6a-d8fa-4c53-b596-3248c4d84e6e
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 6a979963b4bbad2eae71dd7856d44c8c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: tPXWpkRM8c_d2UIPubu2NSQtjahY3SSTT6SeCiQy2OdmUfCvWW9k3g==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:e200:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:43 GMT
x-amz-apigw-id: V9IRKFVXIAMEIQA=
x-amzn-RequestId: 10e1320b-16c6-4cd8-a0af-2677e7659f21
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 91f9ae5c4c6ce22b44c67a0ef057a69c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: wcK8ZmNnozHHkM0Hvju8xYEWboaEJ6XziFXFnnzDZ-4sSud1eVtlWA==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:da00:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRJHacoAMEW4A=
x-amzn-RequestId: 239fdf41-860c-4944-a6c2-b509eae7befe
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 a76fa9726ee874821e5dfb7bf947ffbc.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: M6F9ZUrkAwmW4rtecVCPf4f8KTgtDqSi5d9pIl1bQn8vyDhR8hfPgA==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:da00:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:42 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 5510ba86e3df44d161d0304fbdee228c.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: i2zAdaCnSmDJMcGoSynnkniKI8TVRoKNSS5RPdeDwcothdYktj5sYA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: i2zAdaCnSmDJMcGoSynnkniKI8TVRoKNSS5RPdeDwcothdYktj5sYA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:4e00:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:42 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 10a31a8919932a2483a8dee40abc5178.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: WlckD2AJqAtKUeag91zXrYUntadGhjPC7uv5M6n5l7Fl0qvdq8gOFg== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: WlckD2AJqAtKUeag91zXrYUntadGhjPC7uv5M6n5l7Fl0qvdq8gOFg== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:ea00:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRJGfeoAMEgKQ=
x-amzn-RequestId: 95d38205-e982-4d05-bcfa-38b56f38fdc3
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 5510ba86e3df44d161d0304fbdee228c.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: zRQYZP6HdB6UCBPGrDIU-gp7pj_O_LMQXyM8fOPn_V4ltFovO88lpw==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:b000:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:42 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 9b54c47ba82fa634dd5f3b43f670c934.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: MBTUBBt405hsm8MyL6elPK1DTX9eVEimM4wo2nuLnjgMBa6NZ-P2sw== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: MBTUBBt405hsm8MyL6elPK1DTX9eVEimM4wo2nuLnjgMBa6NZ-P2sw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:e200:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:42 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 8ca6d808eca447f641ca06cbc81bf1e2.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: pttQLNuMLrBYAxTDbVmZr2ai2iGJ58aZY7iMyI1sOSHfX-R17iuvlQ== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: pttQLNuMLrBYAxTDbVmZr2ai2iGJ58aZY7iMyI1sOSHfX-R17iuvlQ== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.174.46.44:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRHFd8oAMEcZw=
x-amzn-RequestId: e1fa28b4-2e02-4fb5-aed6-4f9b7f9036b2
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 a76fa9726ee874821e5dfb7bf947ffbc.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: bmKsMKjbMohvKsd7l1KsrZQu60_MEuNCKELKnJJRAnrnUPp0d_Sv0w==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:f800:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRJGmGoAMECLg=
x-amzn-RequestId: e3afb15d-2a86-4de7-8935-85ad6d48ec50
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 849149785eb810a2bb27d4e2bd0d82b4.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: B_vxUxOu-aL-0m1j0ygqluSUk0ZHgs_1igphmNgdJ-oHlolRQsR7rQ==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:f800:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 c69902ded6396eee37d12b61d86f4414.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: A6Kd6PC9ySiux77BkbP670-z3wJW8QhRVFgE2TnwuXBhz3hlAzEKGg== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: A6Kd6PC9ySiux77BkbP670-z3wJW8QhRVFgE2TnwuXBhz3hlAzEKGg== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.174.46.46:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IRFG3KoAMEZ1A=
x-amzn-RequestId: 4579cf94-cac7-47c2-8326-a09d22557c66
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 02efb09910c56fb99344d44bcbe8e60e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: ZF1f8TJHT6hfZWvvJ3SsKu00qvDLVqzYm7GPqF2wPyV3WPBuU9dTNw==
{"message":"Missing Authentication Token"}
Open service 2600:9000:28eb:ee00:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 c9300fee53e483fd91f18a10d4431680.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: Bf7-zC9ygh-kBlRO6MOUIc8tTO2sidrs0l3l9hb-XHDEbTx6dFO2jQ== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: Bf7-zC9ygh-kBlRO6MOUIc8tTO2sidrs0l3l9hb-XHDEbTx6dFO2jQ== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.174.46.34:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 a6665fb360a5f54fc8b94f7b2c566192.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: BuH0SF2ymMPWfjvbwJh2ZcjqvlQbwDUWYozvv3vMvkFzLBZYJw86mA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: BuH0SF2ymMPWfjvbwJh2ZcjqvlQbwDUWYozvv3vMvkFzLBZYJw86mA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:ea00:0:d65a:5980:93a1:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 8ca6d808eca447f641ca06cbc81bf1e2.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: T_rsH3dI9TFRYy9H0ZZRpYyIo89IgoUMzO7btTgxh3Qy1pStCTq6wA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: T_rsH3dI9TFRYy9H0ZZRpYyIo89IgoUMzO7btTgxh3Qy1pStCTq6wA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 2600:9000:28eb:ee00:0:d65a:5980:93a1:443 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden
Content-Type: application/json
Content-Length: 42
Connection: close
Date: Sun, 21 Dec 2025 20:09:42 GMT
x-amz-apigw-id: V9IREH0KoAMEcjA=
x-amzn-RequestId: 6ebe346c-7cad-40eb-88b4-4728d8133cae
x-amzn-ErrorType: MissingAuthenticationTokenException
X-Cache: Error from cloudfront
Via: 1.1 edeee55acaf119bab76272bf57b28cc4.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: FRA60-P12
Alt-Svc: h3=":443"; ma=86400
X-Amz-Cf-Id: W-28YL8KL-pJVmrh_2MEH2NvKAbqPfq3q0A7mObMBbQF0jq_KreSUw==
{"message":"Missing Authentication Token"}
Open service 3.174.46.62:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 edeee55acaf119bab76272bf57b28cc4.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: SbMbqgT026dly2_0eXsZdUXdLwRq9nX_F8VE4l010rRD00NNrkyDvg== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: SbMbqgT026dly2_0eXsZdUXdLwRq9nX_F8VE4l010rRD00NNrkyDvg== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
Open service 3.174.46.44:80 · surg.api.dev.newwavesoftware.com
2025-12-21 20:09
HTTP/1.1 403 Forbidden Server: CloudFront Date: Sun, 21 Dec 2025 20:09:41 GMT Content-Type: text/html Content-Length: 915 Connection: close X-Cache: Error from cloudfront Via: 1.1 60b4a5085a39ab80fa3602a95fb5aa9e.cloudfront.net (CloudFront) X-Amz-Cf-Pop: FRA60-P12 Alt-Svc: h3=":443"; ma=86400 X-Amz-Cf-Id: 1vt0rq5FAMPOj0v4FUVyJm-EjHlsu7xvkB0DfDiaI7Kf_Sfto30wEA== Page title: ERROR: The request could not be satisfied <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: 1vt0rq5FAMPOj0v4FUVyJm-EjHlsu7xvkB0DfDiaI7Kf_Sfto30wEA== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>
2600:9000:28eb:8000:0:d65a:5980:93a1 1 2600:9000:28eb:4e00:0:d65a:5980:93a1 1 3.174.46.62 1 3.174.46.46 1 3.174.46.34 1 2600:9000:28eb:e200:0:d65a:5980:93a1 1 2600:9000:28eb:da00:0:d65a:5980:93a1 1 2600:9000:28eb:ea00:0:d65a:5980:93a1 1 2600:9000:28eb:b000:0:d65a:5980:93a1 1 3.174.46.44 1 2600:9000:28eb:f800:0:d65a:5980:93a1 1 2600:9000:28eb:ee00:0:d65a:5980:93a1 1