It's the Sprites plugin causing this, as it has the URL hard-coded: https://github.com/vanilla/addons/blob/7665df562e5d3c26fde36098852cc886a3090c0f/plugins/Sprites/design/sprites.css line 123. Replace

ae-123-3509.edge5.London1.Level3.net (4.69.166.33) 0.445 ms ae-236-3612.edge5.London1.Level3.net (4.69.166.61) 0.496 ms

64 bytes from 216.189.149.3: icmp_seq=5 ttl=51 time=207.123 ms

(Quote)

Pingdom Alert: Incident #123 for xxx (www.xxx), has been assigned to you.

I/O (1st run) : 123 MB/s

Total time: : 5.123 sec.

12 EASY-ONLINE.car1.Detroit1.Level3.net (4.31.123.98) 226.921 ms 227.094 ms

total: matches=0 hash_hits=123 false_alarms=0 data=123456

Dear LET-ers,

Current Promo's (Applied to first invoice only)

Test network: http://209.126.123.254/1000.MB

Last time I dropped nyr a pm about openvpn's connection log and he noticed and said(kidechire's was 123.123.123.123 in the example and the 192.168.0.1 is our router on wifi):

The pi's ifconfig shows it being on 169.254.123.0/24 private subnet on eth0, wlan0 remains unchanged.

(62.157.249.233) [AS 3320] 14.457 ms 14.123 ms 80.157.130.77 (80.157.130.77) [AS 3320] 0.739 ms 3 87.190.233.114 (87.190.233.114) [AS 3320] 0.789 ms 14.606 ms 14.271 ms 4 fra4.xe-0-1-0.acc

Current Promo's (Applied to first invoice only)

* Test IPv4: 123.103.253.1

I remember reading one of your complaint threads about 123 ip hoarding ltd or ip systems hoarding ips ltd, I don't remember exactly. I was suspicious why would a vps be so cheap.

(Quote)

They've probably just blocked port 123