Whoa, I'd say the last thing we want is traffic shaping in any way shape or form.

I've no idea what's causing your problems but I'm on a "red" exchange and these are my pings to the beeb. My latest speedtest is 4.8.


Ping statistics for 212.58.224.131:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 30ms, Average = 24ms

In reply to:

---

besides that, Zen seems to have a network configuration problem, my router is hit every ~1h on the WAN port from IP 172.16.1.2, this is a private IP (similar to 192.168.x.x, most likely used by CISCO routers)

---

Probably more likely someone is sending out ICMP traffic with forged source IPs.

I was also thinking about spoofed IP, but shouldn't Zen's network discard unroutable private IP's ?

Unroutable yes, but think about it - the destination IP - the one that Zen's network needs to do something with in sending the traffic to you - is valid. Only the source IP - the one your equipment is supposed to respond to - is invalid. That said, it should be possible to setup something that stopped any traffic coming in with an RFC1918 IP as the source (the Zen network should by default prevent anything routing out).

I'm a bit puzzled by the log entries you're seeing, it's the sort of thing someone would do in a DoS attack, but the fact that you're only seeing one every hour or so hardly suggests it is a DoS attack. I suspect it's actually another Zen customer who hasn't setup their router properly, whose "correct" IP is close to your own. Or, it may be that your own router is seeing traffic from within your network. It wouldn't be the first time that someone had posted logs only to find that the traffic was originating from within.