Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Stéphane Bortzmeyer
@bortzmeyer@mastodon.gougere.fr  ·  activity timestamp 2 days ago

"disabling a problematic route that we found to be related to this"

It was not #DNS, it was #OSPF! (Or IS-IS?)

https://azure.status.microsoft/en-us/status

Azure status

Check the current Azure health status and view past incidents.
  • Copy link
  • Flag this post
  • Block
Stéphane Bortzmeyer
@bortzmeyer@mastodon.gougere.fr replied  ·  activity timestamp 2 days ago

And just after, routing is removed as a possible cause (like DNS was before) and "We suspect that an inadvertent configuration change as the trigger event for this issue.'"

PEBKAC as usual?

https://azure.status.microsoft/en-us/status

Azure status

Check the current Azure health status and view past incidents.
  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login