
PagerDuty
10.1K posts

PagerDuty
@pagerduty
We help developers, ITOps, DevOps and teams across the business provide an optimal digital experience to their customers.








🎫PagerDuty on Tour Tokyo 2026 4/16(木)13:00-20:30 🌟日本を代表する豪華スピーカー陣が集結! JAL・NTT・JTB・ベネッセ・楽天・GMO・JR東日本 ほか 特別講演 🎤さかなクン 氏(東京海洋大学 名誉博士/客員教授) 🎤原 晋 氏(青山学院大学 陸上競技部監督) 昨年は2000名超え・満席! お申込みはお早めに👇 bit.ly/4rFPsXE #PagerDuty #PagerDutyJapan #インシデント管理














It took @ResolvLabs 3h to pause their protocol. Roughly one hour of that delay came from the gap between submitting the multisig transaction and collecting the 4 required signatures to execute it. We should learn from this. Emergency pausing should only require a SINGLE signature, with that authority distributed across as many of your team members as possible. Including trusted external operators (like us) also makes sense. You'll get more eyes on any abnormalities onchain, a higher likelihood of a quick pause, and a better coverage of timezones. Teams should also have reliable communication channels to be coordinate instantly during incidents like this. Pagers, phones, whatever works. Tools like @HypernativeLabs, @hexagate_ and others offer proactive monitoring that can pause the protocol for you, and could one day save you.












