5 ms·

Is there talk of an ETA for any fix yet?

• fuckyah 6y ago
  Never
• deleted 6y ago
  [deleted]
  • rabee3 6y ago
    Thank you
  • toast0 6y ago
    I managed to capture a traceroute on the lg.softlayer.com from seattle to my home near seattle, that went via London (networklayer to london, then telia back to seattle). lol Looks like things are getting better now though; looking glass says seattle and dallas can get to me without going to crazy destinations. wdc is still icky.
  • bigiain 6y ago
    Does it smell of fuckup, or of intentional BGP hijack?
    • nixgeek 6y ago
      If it was a BGP peer who normally sends you 3 prefixes with under a /20 in aggregate and they suddenly started sending you a whole table, or if you allowed a peer to send you a default route, then both of those are highly avoidable through session configuration and filtering. If the route which caused the madness came in via a large settlement-free peer (like a big eyeball/access network) or a transit (which is probably giving you the whole table) that's entirely another story.
      • deleted 6y ago
        [deleted]
        • nixgeek 6y ago
          That wasn't my point though. If you normally take 3 prefixes and suddenly you are receiving 800k+ prefixes then that likely classifies as "unexpected" (and avoidable since you can define max prefixes accepted per session). I wasn't suggesting you could, I was questioning whether you should. :-)
    • deleted 6y ago
      [deleted]
  • rubatuga 6y ago
    I thought BGP shouldn't take longer than half an hour to propagate?
    • Narkov 6y ago
      That's true however an external party might still be sending the bad advertisements that cause the issue. IBM can't really fix that.
      • rubatuga 6y ago
        Well IBM could start announcing all their routes as /24.
• aiisjustanif 6y ago
  cloud.ibm.com/status?selected=status is back up. Multiple cloud services are being reported as down still at 7:25PM CT.