[160903] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

regarding 188.24.168.0/21

daemon@ATHENA.MIT.EDU (Mihai Necsa)
Tue Feb 19 17:43:00 2013

Date: Tue, 19 Feb 2013 14:29:49 +0200
From: Mihai Necsa <mihai@ploiesti.rdsnet.ro>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Hi list

Any help will be appreciated, it seems that apple is filtering prefixes 
for untraceable reasons

I wrote emails to Apple-NOC@apple.com droot@apple.com but no answer.


	Staring about 2 weeks ago we encountered several complaints from our 
customers which are using 188.24.168.0/21. The prefix is  allocated to 
our residential customers, dynamically via pppoe.

	Actually they are not able to connect AppStore and associated resources 
like developer.apple.com from their IOS terminal  phones or tablets, nor 
using iTunes or browser from their respective operating systems.

	Using tcpdump we saw that 17.154.66.17 is not responding to client request.
  IP 188.27.253.245.63289 > 17.154.66.17.443: tcp 0

	Furthermore we did manage to ping hosts from 188.24.168.0/21 using a 
looking glass server (4.69.185.226) from LEVEL3 San Jose which seems to 
be last hop provider to apple network.

Ping results from San Jose, CA
to 188.27.248.26(188-27-248-26.rdsnet.ro)

icmp_seq=0 time=188 ms

----  statistics ----
1 packets transmitted, 1 packets received, 0% packet loss
rtt min/avg/median/max/mdev/stddev = 188/188/188/188/0/0 ms

Regards,

-- 
Mihai NECSA
network engineer @AS8708


home help back first fref pref prev next nref lref last post