www.sendspace.com not loading

Reported on the O2 forum, www.sendspace.com is not loading for me, and others. Judging by the traceroute, it's going through the IWF filter which is probably the cause of the block.

94.194.xx.xx IP address here. Anyone else seeing this?

Oliver.

Not coming up here either, also on an 94.194.xx.xx range.

MKD

__________
20m+ v.happy o2 Broadband LLU Standard ADSL2+ 29/10/07+ using o2 box @4.3/0.9Mbps down/up on 60dB Attn; 35% above ADSLmax! (Consistent c84% throughput, with 3 outages (5.5hrs) & 5 'go-slow' evenings since). Don't forget sign-up cashback (eg £50 quidco.com @01/07/09).
Happy VoIP calls too via Betamax InternetCalls on the o2 box ST780WL SIP
__________
See my features/comparison doc giving the lowdown on the 17x o2/Be Broadband ADSL offerings at http://tinyurl.com/5mzmrs (275KB PDF) updated 02/07/09 or later

Not working for me and I'm 94.195.xxx.xx

I'm also unable to access www.purenetworks.com but I can't access that from my mobile either so it may be a different problem.

Not working here.

94.193.xx.xxx

O2 Standard 8 Meg

Working here so must be an o2 problem !!!

o2 Access -> IDNet Max

In reply to a post by spokes:

I'm also unable to access www.purenetworks.com but I can't access that from my mobile either so it may be a different problem.

Yeah different problem. The nameservers for purenetworks.com are currently dead.

Oliver.

Looks like they are blocking that 94.x.x.x range for some reason

This is one of the ranges that the was problematic for Dutch and Swedish based websites a few weeks back

Best get on to O2 Support

Be* Unlimited

There's a whole stack of 10.1.xx.xx IP addresses in the traceroute, which indicates an IWF filter issue. Traceroute completes which indicates sendspace are not blocking 94.xx.xx.xx packets.

What's your IP range? Does it load?

Oliver.

Edited by Oliver341 (Fri 03-Jul-09 16:20:05)

In reply to a post by nredwood:

Looks like they are blocking that 94.x.x.x range for some reason

Not working here 93.96.xxx.xxx

Nigel

I thought you said in the original post that you didn't think it was an IWF filter issue

Blocked here also on a 87.x.x.x address

Tracing route to www.sendspace.com [216.151.186.5]
over a maximum of 30 hops:

1 2 ms 99 ms 99 ms BeBox [192.168.1.254]
2 * * * Request timed out.
3 15 ms 15 ms 16 ms 10.1.0.1
4 16 ms 24 ms 15 ms 10.1.1.94
5 16 ms 15 ms 15 ms 10.1.1.73
6 15 ms 15 ms 14 ms 10.1.1.141
7 15 ms 15 ms 15 ms 10.1.2.114
8 15 ms 21 ms 15 ms 259.ge-1-2-2.mpr1.lhr3.uk.above.net [213.152.232.65]
9 38 ms 23 ms 20 ms above-gblx.lhr3.uk.above.net [64.125.12.154]
10 97 ms 96 ms 97 ms bandwidth-consulting.tengigabitethernet8-3.ar4.nyc1.gblx.net [64.210.29.14]
11 * * * Request timed out.
12 121 ms 121 ms 122 ms 216.151.186.130
13 120 ms 120 ms 120 ms 216.151.186.5

Trace complete.
The above traceroute and the excessive number of 10.1.x.x does suggest an IWF issue again

Be* Unlimited