Same here in Ohio. I get a white page and the favicon.ico Tracing route to twitter.com [199.59.148.10] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 10.10.10.1 2 3 ms 1 ms 1 ms rrcs-74-218-88-133.central.biz.rr.com[74.218.88.133] 3 4 ms 2 ms 2 ms rrcs-74-218-88-129.central.biz.rr.com[74.218.88.129] 4 4 ms 3 ms 2 ms vln864.dytnoh1-swt101.woh.rr.com[74.218.88.73] 5 4 ms 3 ms 4 ms gig2-1-801.dytnoh1-rtr102.woh.rr.com[70.60.47.5] 6 5 ms 3 ms 4 ms gig5-0.dytnoh1-rtr1.woh.rr.com[24.29.160.21] 7 143 ms 8 ms 8 ms tge8-1-0.tr00.clmkohpe.mwrtn.rr.com[65.25.137.217] 8 21 ms 19 ms 19 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16] 9 21 ms 19 ms 19 ms 107.14.17.147 10 95 ms 120 ms 19 ms xe-10-3-0.edge2.Chicago2.Level3.net[4.59.28.113] 11 20 ms 19 ms 19 ms vlan52.ebr2.Chicago2.Level3.net[4.69.138.190] 12 78 ms 26 ms 138 ms ae-6-6.ebr2.Washington12.Level3.net[4.69.148.145] 13 26 ms 26 ms 26 ms ae-5-5.ebr2.Washington1.Level3.net[4.69.143.221] 14 29 ms 109 ms 25 ms ae-72-72.csw2.Washington1.Level3.net[4.69.134.150] 15 100 ms 101 ms 100 ms ae-2-70.edge2.Washington4.Level3.net[4.69.149.80] 16 101 ms 26 ms 27 ms TWITTER-INC.edge2.Washington4.Level3.net[4.53.114.102] 17 175 ms 101 ms 101 ms 199.16.159.46 18 129 ms 101 ms 100 ms 199.16.159.49 19 128 ms 101 ms 101 ms r-199-59-148-10.twttr.com [199.59.148.10] Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Sat, Oct 15, 2011 at 3:36 PM, andrew.wallace < andrew.wallace@rocketmail.com> wrote:
Reaching Twitter at the moment is problematic.
Andrew
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages