<html><head>
<style id="css_styles">
blockquote.cite { margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc }
blockquote.cite2 {margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #cccccc; margin-top: 3px; padding-top: 0px; }
a img { border: 0px; }
li[style='text-align: center;'], li[style='text-align: center; '], li[style='text-align: right;'], li[style='text-align: right; '] { list-style-position: inside;}
body { font-family: Segoe UI; font-size: 12pt; }
.quote { margin-left: 1em; margin-right: 1em; border-left: 5px #ebebeb solid; padding-left: 0.3em; }
</style>
</head>
<body>G'day list<div><br /></div><div> Is there a good communication channel for 'singtel' as a whole, i.e. some kind of NOC who has investigative authority into both 7473 and 7474?<br /><br /> I'm having a weird BGP issue where I 'believe' 7473 is holding a route that 7474 have withdrawn, and is screwing up BGP failover. 7474 route-views server shows correct route but all LG's out in the world show a path via 7473 to 7474 still active (and loops around).<br /> Given they are 1 'conglomerate', I was hoping there's a way I could get it investigated without being pushed between 2 NOCs with blame shifting.</div><div><br /></div><div>Thanks,</div><div>Joe</div></body></html>