CHYP.ai · ORBIT // Cloudy_Day Security Suite

🌩️ STORM REPLAY · 5-minute replay · ~5 min · 60 XP

Storm Replay: The carrier that stopped printing labels

Scope a vendor incident to the component it names, keep region claims honest, and write a cited alert.

REAL PUBLIC OUTAGE · FROZEN SNAPSHOT EasyPost's own status page, quoted word for word. Frozen 2026-11-20, reviewed 2026-11-20 · revision e4af410681f0b92c · original incident ↗ · ORBIT ledger easypost:b8yp8vjylfz4. Independent, not affiliated with EasyPost.

Phase 1 · 2026-11-18 22:21 UTC

EasyPost status page · 2026-11-18 22:21 UTC · investigating

We are currently experiencing issues with our Amazon Shipping integration, affecting label purchases across multiple customers. Our team is actively investigating this as an urgent issue.

Components: Carriers - Amazon Shipping: major outage

From the first update, what is affected?
Which region does the evidence say is affected?

Phase 2 · 2026-11-18 22:39 UTC

EasyPost status page · 2026-11-18 22:39 UTC · investigating

We are in contact and actively working with the carrier to resolve the situation as quickly as possible.

Components: Carriers - Amazon Shipping: major outage

What does the 22:39 UTC update add?

Phase 3 · 2026-11-18 23:16 UTC

EasyPost status page · 2026-11-18 23:16 UTC · resolved

This incident has been resolved.

Components: Carriers - Amazon Shipping: operational

How long from the vendor's first post to "resolved"?
What does the public record still leave unknown?
ORBIT's ledger first recorded this incident on Nov 20, about two days after it resolved. What does that mean?

Playing as a guest: you'll see your score and the reasoning, but nothing is saved. Join (one click, no email) to earn XP.

Simulated targets only. For education on simulated targets only; never test systems you don't own or have written permission to test. The Arena is an independent researcher project, not affiliated with or endorsed by any company or agency named. Every company, host and log here is fictional unless a page says it's ORBIT's own public outage data.

Where to next