@Pinboard confirmed from my side
Network-savvy people, can you take a look at traceroute to 71.19.151.26 and 71.19.151.30 and confirm that the issue is http://core1.sjc1.he.net ?
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard both from Paris/FR and Amsterdam/NL that's the one giving problemsThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard I'm seeing a back and forth with two locations… http://goo.gl/gqF9TThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard Yup. That's the last hop that works for me here in .au. It loops infinitely on it. -
@pipequanta mildly surprised you can even get online from .au! Whole country seems to run on one DSL line - Show replies
New conversation -
-
-
@Pinboard Self-referential DNS entry?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard Traceroute from Comcast in SF ends up in a loop between 69.46.67.202 and 69.46.67.201. Last valid hop was to …http://as18779.xe-4-0-4.ar2.sjc1.us.nlayer.netThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard 69.46.67.201 (69.46.67.201) 213.727 ms * 220.066 msThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard …http://connex-internet-services-inc.gigabitethernet4-4.core1.sjc1.he.net (64.71.184.42) 210.304 ms 209.355 ms 209.359 msThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@Pinboard tracert seems to just bounce back and forth between 69.46.67.202 and 69.46.67.201 endlessly -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.