Did our app get banned because of too many connections?

Questions / Help
1

We recently have been trying to access our app payments.paypack.rw but it seems like we’ve been banned. on the frontend we are receiving a 502 Bad Gateway error and here is a Curl output:

* Rebuilt URL to: https://payments.paypack.rw/
*   Trying 213.188.209.3...
* TCP_NODELAY set
* Connected to payments.paypack.rw (213.188.209.3) port 443 (#0)
* schannel: SSL/TLS connection with payments.paypack.rw port 443 (step 1/3)
* schannel: checking server certificate revocation
* schannel: sending initial handshake data: sending 184 bytes...
* schannel: sent initial handshake data: sent 184 bytes
* schannel: SSL/TLS connection with payments.paypack.rw port 443 (step 2/3)
* schannel: failed to receive handshake, need more data
* schannel: SSL/TLS connection with payments.paypack.rw port 443 (step 2/3)
* schannel: encrypted data got 4038
* schannel: encrypted data buffer: offset 4038 length 4096
* schannel: sending next handshake data: sending 93 bytes...
* schannel: SSL/TLS connection with payments.paypack.rw port 443 (step 2/3)
* schannel: encrypted data got 51
* schannel: encrypted data buffer: offset 51 length 4096
* schannel: SSL/TLS handshake complete
* schannel: SSL/TLS connection with payments.paypack.rw port 443 (step 3/3)
* schannel: stored credential handle in session cache
> GET / HTTP/1.1
> Host: payments.paypack.rw
> User-Agent: curl/7.55.1
> Accept: */*
>
* schannel: client wants to read 102400 bytes
* schannel: encdata_buffer resized 103424
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: encrypted data got 208
* schannel: encrypted data buffer: offset 208 length 103424
* schannel: decrypted data length: 179
* schannel: decrypted data added: 179
* schannel: decrypted data cached: offset 179 length 102400
* schannel: encrypted data buffer: offset 0 length 103424
* schannel: decrypted data buffer: offset 179 length 102400
* schannel: schannel_recv cleanup
* schannel: decrypted data returned 179
* schannel: decrypted data buffer: offset 0 length 102400
< HTTP/1.1 502 Bad Gateway
< server: Fly/9044e14 (2021-08-04)
< date: Sat, 07 Aug 2021 07:53:40 GMT
< via: 1.1 fly.io
< fly-request-id: 01FCFSMJQSRRXMXQF3JJ954NRF
< content-length: 0
<
* Connection #0 to host payments.paypack.rw left intact
2

@shema can you run this command: flyctl ips private --app payments and show me the output?

3 
ID       REGION IP
4406adcd lhr    fdaa:0:1af2:a7b:a98:4406:adcd:2
4

It was some stale DNS entries. It has been solved.