Resolved after 1 day 2 hours, on September 10, 2026.
We have no longer seen any concerning signals in over 24 hours. This incident has been resolved # Aftermath On September 10, 2026, we experienced an unplanned outage from 16:50 to 18:00 UTC — a total of 1 hour and 10 minutes during which Occasion was unavailable. At 16:50 UTC, we received a sudden and unusually large increase in traffic. Under normal circumstances, increases in traffic of this nature have little noticeable impact on performance and trigger alerts that allow us to take action. In this case, however, the increase was both exceptionally abrupt and significantly larger than usual, leaving our infrastructure insufficient time to respond. The traffic spike lasted several minutes before subsiding, but the resulting pressure on our infrastructure left the system in a degraded state and unable to serve requests reliably. We have identified and addressed the underlying cause of this incident and have taken steps to prevent this particular failure mode from recurring. We are also actively working to improve Occasion's ability to scale rapidly, reducing the impact that sudden traffic spikes can have on reliability in the future.
Update timeline
- investigating Sep 10, 2026, 06:22 PM UTC
The platform should have returned to normal operation. We’re continuing to monitor performance closely and are implementing a change that should help prevent this issue from happening again in the future.
- resolved Sep 11, 2026, 08:01 PM UTC
We have no longer seen any concerning signals in over 24 hours. This incident has been resolved # Aftermath On September 10, 2026, we experienced an unplanned outage from 16:50 to 18:00 UTC — a total of 1 hour and 10 minutes during which Occasion was unavailable. At 16:50 UTC, we received a sudden and unusually large increase in traffic. Under normal circumstances, increases in traffic of this nature have little noticeable impact on performance and trigger alerts that allow us to take action. In this case, however, the increase was both exceptionally abrupt and significantly larger than usual, leaving our infrastructure insufficient time to respond. The traffic spike lasted several minutes before subsiding, but the resulting pressure on our infrastructure left the system in a degraded state and unable to serve requests reliably. We have identified and addressed the underlying cause of this incident and have taken steps to prevent this particular failure mode from recurring. We are also actively working to improve Occasion's ability to scale rapidly, reducing the impact that sudden traffic spikes can have on reliability in the future.
Your product runs on more than Occasion
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services