i got on another nearby WiFi network which didn’t block those domains, and it worked again. once i switched back, those failing requests killed the editor again.
I’t be awesome if we could opt out of tracking, or just prevent these errors from killing the host application.
Thanks for filing this - in general we don’t block editor access if calls to Segment fail. However yesterday we pushed out a modification to how we were tracking, and that caused issues for many signed in users. We just rolled out a fix though, so this shouldn’t happen again. Let me know if it’s working for you again, and apologies for the inconvenience!