this post was submitted on 13 Jun 2023
29 points (100.0% liked)

Technology

37551 readers
280 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
top 6 comments
sorted by: hot top controversial new old
[–] kichithewolf@beehaw.org 7 points 1 year ago

Nothing quite like seeing "we need to track the outage for the affected service, but the tool we're using to track things is also out" on Slack at work.

[–] StupidManager@lemmy.one 6 points 1 year ago (1 children)

awesome timing too. End of sprint, big release. thanks AWS…

[–] eleanorOpossum@beehaw.org 2 points 1 year ago

Last day a sprint for me too, lol. At least we weren't in the middle of any big releases. Hope everything went okay on your end.

Yeah - this was a tad annoying at work today. Thank god for terraform if outages had become more severe

[–] eleanorOpossum@beehaw.org 1 points 1 year ago (1 children)

What was extra annoying about was even though the applications I work on are already multi-region; we still had a couple of transitive dependencies on us-east-1 that held things up a bit. And of course, their status page never said anything about the outage.

[–] 3sframe@beehaw.org 2 points 1 year ago

Same here. We have one service that uses dynamo. And that service was absolutely chugging. But they never mentioned dynamo on the status page.

load more comments
view more: next ›