Quote from: giqcass on February 04, 2014, 10:48:40 AM
I think Obitalk is hosted on a shared server. Amazon AWS so I'm not sure if the IP addresses are dedicated. It's common practice to use multiple shared IP addresses with cloud computing. This increases the ability to scale services. All that said they appeared to be using this address. I can't say if it's current.
54.241.160.4
A VPN is the only way to ensure access in your situation.
It'll be a little more complex than that. They do appear hosted on Amazon AWS. The route used is running through AWS network spanning 205.251.192.0 - 205.251.255.255 which I assume is routing internal for Amazon (I'm hitting 3 nodes in that network from my current location). Their WhoIs info indicates something related to roles. It then terminates at 54.251.157.146 which is part of their network spanning 54.251.0.0 - 54.251.255.255 which is their Elastic Compute Cloud services according to their WhoIs.
I don't know if those ranges are fixed or if the are specific to specific availability zones or availability regions.
Tried a second time and went through Amazon network 72.21.192.0 - 72.21.223.255 in addition to 205.251.192.0 - 205.251.255.255. Perhaps some sort of load balancer?
TraceRT is interesting to look at.
us.above.net has some jacked up routes for
Obitalk.com. Takes 8 hops inside their network to get to Amazon's net, WTF?