Stomme Salon Blogs nog altijd plat.
C:\>ping blogs.salon.com
Pinging blogs.salon.com [64.75.32.139] with 32 bytes of data:
Reply from 64.75.32.139: bytes=32 time=183ms TTL=118
Reply from 64.75.32.139: bytes=32 time=190ms TTL=118
Reply from 64.75.32.139: bytes=32 time=337ms TTL=118
Reply from 64.75.32.139: bytes=32 time=463ms TTL=118Ping statistics for 64.75.32.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 463ms, Average = 293msC:\>
Da’s al de hele bloederige werkdag. En ze pingen gewoon, en traceroute werkt ook proper, dus ’t is gewoon een geval van één idioot die ergens een server in gang moet duwen. Aaargh.
C:\>tracert blogs.salon.com
Tracing route to blogs.salon.com [64.75.32.139]
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms lan [x.x.x.x]
2 4 ms 2 ms 3 ms router [y.y.y.y]
3 310 ms 298 ms 300 ms flupke-from-x-u.be.colt.net [z.z.z.z]
4 509 ms 469 ms 512 ms quick-from-flupke.router.be.colt.net [212.35.96.1]
5 339 ms 341 ms 316 ms blake-from-quick.router.be.colt.net [212.35.96.17]
6 414 ms 331 ms 355 ms stimpy-from-blake-2.router.be.colt.net [212.35.111.41]
7 400 ms 390 ms 417 ms pos1-3-kenny.NYC.router.COLT.NET [212.74.74.161]
8 422 ms 411 ms 403 ms gige5-1-310.ipcolo2.NewYork1.Level3.net [63.214.53.253]
9 416 ms 438 ms 432 ms gigabitethernet2-0.core2.NewYork1.Level3.net [64.159.17.6]
10 377 ms 421 ms 402 ms acr2.NewYork.cw.net [209.244.160.190]
11 403 ms 410 ms 422 ms agr3-loopback.NewYork.cw.net [206.24.194.103]
12 374 ms 391 ms 418 ms dcr1-so-6-2-0.NewYork.cw.net [206.24.207.57]
13 494 ms 482 ms 481 ms dcr1-loopback.SantaClara.cw.net [208.172.146.99]
14 748 ms 866 ms 910 ms bhr1-pos-0-0.SantaClarasc5.cw.net [208.172.156.74]
15 497 ms 477 ms 474 ms 216.34.3.82
16 491 ms 497 ms 493 ms 64.75.32.139Trace complete.
C:\>