| 9:57 pm on Jan 7, 2014 (gmt 0)|
keyplr - it's cloud. The range could easily be some technical service or proxy service. If it's genuine mobile access then someone is being a bit naive.
And which thetrasher's link confirms. Nokia are obviously trying to do things on the cheap. If they provide a proper IP range they will get through.
It all comes down to trust. It's amazon: I don't.
| 2:32 am on Jan 8, 2014 (gmt 0)|
The mobile hits I see do contain "proxy" in the UA string.
| 12:57 am on Jan 9, 2014 (gmt 0)|
Sample using a new Nokia, and you'll breathe-easy discovering why any "human" using one will soon deposit the Nokia in the dustbin.
As intuitive and effortlessly interactive as bats in the pantry.
| 10:01 am on Jan 9, 2014 (gmt 0)|
Well I poked a hole & let a few through. Look human to me, no issues yet. Keeping a close watch.
| 3:46 pm on Jan 30, 2014 (gmt 0)|
Three hits today from a major new amazon range, registered in November.
126.96.36.199 - 188.8.131.52
| 4:59 pm on Jan 30, 2014 (gmt 0)|
Thanks dstiles, new for me.
| 8:06 pm on Jan 30, 2014 (gmt 0)|
I had to look that up because it seemed so odd. Looks like the bottom half of 72-79 is still Merck-- at least this week-- but honestly, would anything bad happen if you just lock out the whole 184.108.40.206/8 and be done with it? I've never personally met anyone from <192.
:: idly wondering how Merck stock is doing these days ::
| 8:12 pm on Jan 30, 2014 (gmt 0)|
The ranges either side of the amazon one are merck but I've left them alone, since they leave me alone. I have only two merck ranges listed and both are enabled.
| 2:56 pm on Feb 21, 2014 (gmt 0)|
Another large amazon range...
NetRange: 220.127.116.11 - 18.104.22.168
That runs straight into one I logged Dec 2012...
22.214.171.124 - 126.96.36.199
| 6:38 pm on Feb 21, 2014 (gmt 0)|
Cool, that covers a lot
| This 40 message thread spans 2 pages: < < 40 ( 1  ) |