[s3bubble]

Sam:

Hi Michael,

I have ran that, it took a while but responded with.

telnet: connect to address 216.70.112.79: Connection timed out Trying 216.70.112.79…

[s3bubble]

Hi Samuel,
This has been escalated to me, I’m a network and devops engineer here. I watched your videos and can feel your frustration. I verified in our routers that there is nothing blocking your IPs there. I verified on our DDoS mitigation system that we aren’t mitigating your DV ip or any of the ip’s listed.

Additionally I did some tests from your DV to the affected IPs that you listed. I can make connections from your DV to all of those IPs and I can even pull data from those IPs from your DV. It is interesting that these users are experiencing the issue you describe and show in your videos.

Here is an example from your DV to that last IP that you provided
CT-108060-bash-4.1# hostname
s3bubble.com
CT-108060-bash-4.1# telnet 198.23.86.85 80
Trying 198.23.86.85…
Connected to 198.23.86.85.
Escape character is ‘^]’.
HEAD / 1.1/

HTTP/1.1 200 OK
Date: Thu, 16 Jul 2015 17:55:11 GMT
Server: Apache
Vary: Accept-Encoding,Cookie
Cache-Control: max-age=3, must-revalidate
WP-Super-Cache: Served supercache file from PHP
Connection: close
Content-Type: text/html; charset=UTF-8

Connection closed by foreign host.

#####

As you can see I’m able to pull HTTP headers from the webserver on the IP your provided FROM your DV.

I think there must be something else blocking things and I’d like to help debug. I’d be nice to do some interactive tests to see if things are being blocked inside your server itself. Is there anyway I would be able to initiate the requests myself from these blocked hosts?

Also, are you able to do telnet tests from these IPs to your DV? If so, try telneting from these IPs to port 443 on your host:

telnet api.s3bubble.com 443

^^^ Using that command.

Best Regards,

Michael H.
Customer Support
(mt) Media Temple
877-578-4000
310-564-2007

[s3bubble]

What is going on! i am pretty much watching my business go under day by day new issues today.

http://cpioutreach.com/portfolio/only-a-shadow

http://ten12designs.com/media-streaming-devices/

http://sparketh.com/rtmp-issue-3/

What number can i contact you on from the UK this needs to get fixed?

[s3bubble]

Softlayer is a hosting company which mindfulnessexercises.com looks to be hosted at. I have emailed their support email address asking about any routing or peering problems they might be having. I have also forwarded your traceroute videos to our provider’s network engineer. While we are investigating, could you try using a different set of DNS servers for your test from mindfulnessexercises.com? Maybe try Google’s DNS servers?

Best regards,

Kenneth P.
Systems Engineer
(mt) Media Temple
877-578-4000
310-564-2007

[s3bubble]

Sam:

Please also watch this video.

https://s3.amazonaws.com/wp.video/mediatempleissue.mp4

[s3bubble]

Hi Kenneth,

I am not sure what softlayer is?

http://www.softlayer.com

My users that are having issues are hosting with site5 godaddy TsoHost and its not just that one ip i am now having the same issue with at least 4 different users.

They have contacted their providers and this is their response below.

Hi Christopher,

It’s almost certainly that the IP you’re connecting to or their upstream provider are blocking 91.208.99.2. If I were a betting man I’d put money on it 🙂

Kind Regards,

Adam Smith TsoHost.

Why would certain hosts or users be unable to get to api.s3bubble.com with the following traceroute.

1 50.23.120.193-static.reverse.softlayer.com (50.23.120.193) 0.513 ms 0.491 ms 0.481 ms
2 ae0.dar02.sr01.sjc01.networklayer.com (50.23.118.132) 0.366 ms ae0.dar01.sr01.sjc01.networklayer.com (50.23.118.130) 0.406 ms ae0.dar02.sr01.sjc01.networklayer.com (50.23.118.132) 0.302 ms
3 50.97.19.164-static.reverse.softlayer.com (50.97.19.164) 0.775 ms 0.701 ms ae8.bbr01.eq01.sjc02.networklayer.com (173.192.18.248) 0.803 ms
4 equinix-ix.sjc1.us.voxel.net (206.223.116.4) 0.741 ms 0.794 ms 0.868 ms
5 173.231.161.193 (173.231.161.193) 48.109 ms 44.392 ms 44.397 ms
6 0.te1-2.tsr1.dal2.us.voxel.net (107.6.99.249) 79.040 ms 79.065 ms 80.685 ms
7 0.te2-2.tsr3.iad1.us.voxel.net (173.231.161.189) 78.472 ms 78.438 ms 78.414 ms
8 173.231.160.90 (173.231.160.90) 81.183 ms 81.158 ms 173.231.160.82 (173.231.160.82) 78.348 ms
9 internap.iad1.us.voxel.net (173.231.161.74) 78.815 ms 78.794 ms 78.751 ms
10 border2.te4-1-bbnet1.wdc012.pnap.net (216.52.127.39) 78.455 ms border2.pc2-bbnet2.wdc012.pnap.net (216.52.127.76) 78.282 ms 78.261 ms
11 net2ez-3.border2.wdc012.pnap.net (64.94.31.142) 79.218 ms 79.159 ms 79.094 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *

How can i resolve this?

• This reply was modified 9 years, 9 months ago by s3bubble.

[s3bubble]

We have received feedback from our provider’s network engineer and he asked if your clients or the customers of softlayer open a ticket with softlayer. From what testing they have done it appears that there are some routing peering issues between various ISPs and softlayer.

You can test traceroutes between providers and the IP 50.23.120.193 using the looking glass URLs below:

http://www.us.ntt.net/support/looking-glass/
http://lg.zayo.com/lg.cgi
http://www.cogentco.com/en/network/looking-glass

If you have any further questions regarding your (mt) Media Temple services, please feel free to contact us at any time.

Best regards,

Kenneth P.
Systems Engineer
(mt) Media Temple
877-578-4000
310-564-2007

[s3bubble]

Hi All,

Here is another issue why is this happen what is going on! what can i do to resolve this can someone please let me know why this is happening.

This is what i am getting from my users more everyday this is ruining my service.
https://s3bubble.com/forums/topic/rtmp-videos-not-streaming/#post-24931

Here is what is happening to his video.
http://sparketh.com/rtmp-issue-3/

This looks like the same issue.
https://www.joomlacontenteditor.net/support/forum/curl-error-connection-timed-out-after-10001-milli seconds

What can i do to resolve this do i need to change hosting upgrade anything????

Please help me this is basically making my service look unreliable and i cant do anything my end to fix.
2015.07.15 10:02 AM

[s3bubble]

Hi Kenneth,

Thanks for looking into this but i am still experiencing issues maybe a video will help.

https://s3.amazonaws.com/wp.video/mediatemple.mp4

[s3bubble]

Access from the IP address 198.23.86.85 should be okay. Please let us know if you are still experiencing problems from this source.

Best regards,

Kenneth P.
Systems Engineer
(mt) Media Temple
877-578-4000
310-564-2007

[s3bubble]

Sorry for the inconvenience, we are currently having our provider’s network engineer’s look into this issue. We will report back to as soon as we obtain an update. Thank you for your patience.

Best regards,

Kenneth P.
Systems Engineer
(mt) Media Temple
877-578-4000
310-564-2007

[s3bubble]

Sam :

Hi,

Still awaiting a response on this can some please tell me why this is happening?

What do i tell my user he keeps asking me and i have said i am waiting from a response from media temple?

Thanks

[s3bubble]

Sam

Any updates on this my users would like to know why this is happening??

• This reply was modified 9 years, 9 months ago by s3bubble.

[s3bubble]

Hi Kenneth,

Yes i still need help with this issue as its not resolved that is just one site that is working.

Here is a traceroute ran from http://mindfulnessexercises.com.

traceroute to api.s3bubble.com (216.70.112.79), 30 hops max, 40 byte packets
1 * * *
2 ae0.dar02.sr01.sjc01.networklayer.com (50.23.118.132) 0.424 ms ae0.dar01.sr01.sjc01.networklayer.com (50.23.118.130) 23.967 ms 23.974 ms
3 ae8.bbr01.eq01.sjc02.networklayer.com (173.192.18.248) 7.570 ms 0.809 ms 50.97.19.164-static.reverse.softlayer.com (50.97.19.164) 0.780 ms
4 equinix-ix.sjc1.us.voxel.net (206.223.116.4) 0.932 ms 0.893 ms 0.855 ms
5 173.231.161.193 (173.231.161.193) 44.622 ms 44.619 ms 44.589 ms
6 0.te1-2.tsr1.dal2.us.voxel.net (107.6.99.249) 79.289 ms 79.355 ms 79.060 ms
7 0.te2-2.tsr3.iad1.us.voxel.net (173.231.161.189) 79.180 ms 78.987 ms 78.952 ms
8 173.231.160.82 (173.231.160.82) 78.627 ms 82.617 ms 78.688 ms
9 internap.iad1.us.voxel.net (173.231.161.74) 79.082 ms 80.838 ms 80.706 ms
10 border2.te4-1-bbnet1.wdc012.pnap.net (216.52.127.39) 79.344 ms border2.pc2-bbnet2.wdc012.pnap.net (216.52.127.76) 79.681 ms border2.te4-1-bbnet1.wdc012.pnap.net (216.52.127.39) 80.733 ms
11 net2ez-3.border2.wdc012.pnap.net (64.94.31.142) 80.994 ms 80.980 ms 80.956 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Thanks

Sam

[s3bubble]

Thank You for the update. The “3” you mentioned previously may have been DNS lookup timeout. You can perform a trace route without name resolution for faster results.

Please let us know if there is anything else we can do for you.

Best regards,

Kenneth P.
Systems Engineer
(mt) Media Temple
877-578-4000
310-564-2007

[Author]

Posts